DigAIRange
Component | Version |
|---|---|
DigAIRange | 6.4.974.3 6.3.967.2 |
Dependencies
DigaSQL.dll 3.20.3503.0 or newer (recommended)
MultiRec4 4.8.343.0 or newer (recommended)
OnAIR TrackMixer 2.9.803.0 or newer (recommended)
Visual C++ redistributable for Visual Studio 2022 (Download “vcredist_x86.exe” at https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads )
New/Changes/Fixed Issues in version 6.4.974.1
Build: 974.3
OIA-8250: An intermediate bug of version 6.4.974.0 was fixed: the answer when triggering a ConsistencyCheck task of BUS was not recognized and the dialog box to trigger the task stayed open.
Build: 974.2
Keep the position of marked element when you activate via button to show comments per
element. (OIA-5373)
Build: 974.1
Bugfix: Fix for DA starts without user credentials and won’t work (OIA-8000)
Build: 974.0
Bugfix: In version 6.2.950.0 the merge step of an import was modified to ignore the times of elements or groups in many new cases. This was applied in too many cases and as a result options or merge modes, which require an evaluation of the time of elements or groups, did no longer work. E.g. in merge mode “Find matching blocks of the import and the plan from the start time” wrong destination blocks/groups could be picked and content was possibly inserted into the wrong place. (CCD-45183/ OIA-7705)
Bugfix: When for importing the option “Full block alignment for all imported classes” was set, the option “If destination is empty insert full list with structure” did not work and nonsense
content was inserted.
Build: 973.0
Change: Added setting under settings -> tree “Load current show on startup”. If enabled the current show will load on startup. (OIA-7722)
Build: 972.0
Change: Added setting in the View Tab for the scroll bar move to the top or stay at the same position if a new show is loaded. (OIA-3143)
Build: 971.0
Change: Images for events-out, mixer sources and custom fields in the rundown view were only made smaller, when necessary, but never bigger. Now they are made bigger when the size of the image is smaller than 90% of the available output space. (OIA-6841)
Change: Usability improvements in Settings dialog (OIA-7719)
Change: The “Open groups…” option can now also be configured for stories and endpoint stories. (OIA-7056, CCD-45165)
Build: 970.0
Change: Usage of UIScheme colors in two places: for highlighting the drop target in the tree view and for the text color in the table of the dialog for synchronizing the show structure.
Change: The parameter “CheckFlags” in key Digas\PlanServer\<BCS name>\<service name>\DigAIRange is no longer active when inserting content into the day pool. The
behaviour of DigAIRange when checking flags was unintentionally modified in version
6.3.965.0. Now, the old behaviour has been restored. (CCD-45267/OIA-7338)Change: The warning, which was displayed since version 6.3.965.0 when the user tried to load a group, story or endpoint-story into OTM was removed again. (OIA-6638)
Bugfix: When the manage dialog was opened for shows, it was no longer possible to edit the field “Name”, the field was disabled. This was a new bug since version 6.3.964.0. (CCD-45203/OIA-7050)
New: DigAIRange allows now to connect to a BCS, which is running as a buddy/backup server, if the current user is “ADMIN”. Therefore, the context menu for a server within the tree
view was extended. Hint: this is only intended for debugging - in order to monitor ongoing
changes on a backup BCS. Such a BCS will not allow any write operations.New: In the settings dialogs for the visible columns of a rundown view it is possible now tosort for the column names. A sort button or a click into the header toggles between up, down
and legacy sorting. DigAIRange remembers the chosen sorting for a user.New: DigAIRange supports now a direct start/stop of prelistening by a middle-mouse-click onto a result line of BCSSearch.ocx. Therefore, at least BCSSearch.ocx version 2.0.55.0 is
required. (OIA-6981)New: The context menu for an individual element in a rundown has a new command:
“Search for selected element in schedule”. This feature requires an installed BCSSearch.ocx
with version 2.0.55.0 or higher and a maintained full-text index stored in ElasticSearch. It is
possible to specify different search expressions for different types of elements.
For more information, please have a look into BCSTechManual chapter 9.2.3 (Fulltext-search within
BroadcastSystem/Installation/ BCSSSearch.ocx). (OIA-6974)
Hint: This feature is available via the new DDE command “Soundfile\SearchForElement”,
too. This is intended for a future usage by DBM.
New/Changes/Fixed Issues in version 6.4.967.2
Build: 967.2
Bugfix: In version 6.2.950.0 the merge step of an import was modified to ignore the times of elements or groups in many new cases. This was applied in too many cases and as a result options or merge modes, which require an evaluation of the time of elements or groups, did no longer work. E.g. in merge mode “Find matching blocks of the import and the plan from the start time” wrong destination blocks/groups could be picked and content was possibly inserted into the wrong place. (CCD-45183/ OIA-7705)
Bugfix: When for importing the option “Full block alignment for all imported classes” was set, the option “If destination is empty insert full list with structure” did not work and nonsense content was inserted.
Bugfix: Fix for DA starts without user credentials and won’t work (OIA-8000)
2) Build: 967.1
Change: The parameter “CheckFlags” in key Digas\PlanServer\<BCS name>\<service name>\DigAIRange is no longer active when inserting content into the day pool. The behaviour of DigAIRange when checking flags was unintentionally modified in version 6.3.965.0. Now, the old behaviour has been restored. (CCD-45267/OIA-7338)
Change: The warning, which was displayed since version 6.3.965.0 when the user tried to load a group, story or endpoint-story into OTM was removed again. (OIA-6638)
Bugfix: When the manage dialog was opened for shows, it was no longer possible to edit the field “Name”, the field was disabled. This was a new bug since version 6.3.964.0. (CCD-45203/OIA-7050)