TurboPlayer

Dependencies

• DigaSQL.dll 3.20.3503.0 or newer (recommended)

• MultiRec4 4.8.340.0 or newer (recommended)

• OnAIR TrackMixer 2.9.803.0 or newer (recommended)

• DigaStory.ocx 1.5.87.0 (recommended)

Fixed Issues 

• The end level of a demute operation was not correct if a mute-start element had a fade at the end but none at the beginning. When previous elements stopped, the level for the mute-start element was moved to the value of Fade_AmplicifationIn – which is much too low, normally. (CCD-44315/OIA-5251)

• When the first element in the initially loaded rundown had start mode and/or start type “Unused”, the icons for these fields were displayed distorted and non-recognizable. This affected further lines in the rundown, too. (CCD-44256/OIA-4808)

• Import buttons of the GUI did not read their settings correctly and were then displayed grey/disabled. This was a bug since version 5.10.2388.0 and the feature of TurboPlayer reading the settings from global registry, too. (CCD-43903/OIA-5510)

• In server connection modes ”Standalone” and “Rehearsal” it could happen that the current show was unloaded within 1 minute after changing the mode. The same problem could happen when the connection to BCS was lost or disturbed while TurboPlayer just wanted to verify that all loaded shows were still existing on BCS. This was a new bug since version 6.1.2505.0 (OIA-5697)

• Microsoft has made a fundamental change in Windows 10 version 2004. As a result, the required precision of internally used timers can no longer be guaranteed to be 1 millisecond. This could possibly affect TurboPlayer - depending on other previously started DigaSystem programs. (Hint: MultiPlayer is nearly always affected, and a new MP version 5.9.0.12522 is available, too.) TP has now a workaround, which should prevent this problem. (CCD-44118/OIA-5296)
  

Fixed Issues

• An element in the rundown with flag “Time_Overlaid” being set but without the otherwise necessary start attributes, could make TurboPlayer be blocked in a loop, trying to correct this invalid situation. BCS notifications and internal states were no longer handled correctly. This affected the GUI, too. (CCD-43302)

• When an exception happened while handling a macro, the internal structures for macro handling were not cleaned up properly. This could lead to problems with further macro executions. Also no stack dump was written. (CCD-43288/OIA-2620)