TurboPlayer
Component | Version |
|---|---|
TurboPlayer | 6.5.2908.0 6.4.2812.6 |
Dependencies
DigaSQL.dll 3.22.3522.0 or newer (recommended)
MultiRec_4.ocx 4.8.347.0 or newer (recommended)
OnAIR TrackMixer 2.9.803.15 or newer (recommended)
DigaStory.ocx 1.5.87.0 (recommended)
DigaRTF 1.6.96.0 (recommended)
New/Changes/Fixed Issues
for 6.5.
Build 6.5.2908.0
Requires DigaSQL 3.22.3522.0 or higher
Bugfix: Removed the Windows Version check in TP Engine so that it can run on Window Server versions (OIA-8692/CCD-45765)
Build 6.5.2907.0
Requires DigaSQL 3.22.3522.0 or higher!
New: Mini DBM no longer includes soft deleted members of groups, stories, or end point stories, when such items are dragged into other parts of Turbo Player. (OIA-8156, CCD-45523)
Build 6.5.2906.0
• Bugfix: The command line parameter -RKAIOM was not evaluated by the TurboPlayer GUI (only). (CCD45661)
• Bugfix: The new keyword “Timers” for parameter TurboPlayer\Logging\DebugLog from build 2900 was active by default. This should not have been the case. (CCD-43302/OIA-1739)
• New: Support for MultiPlayer V6 and Windows 11.
Some details:
MultiPlayer V5 is still supported. The name of the pipe for the communication changed slightly. This is automatically handled as long as you did only use a single instance of MultiPlayer in the past and if the parameter TurboPlayer\Communication\RundownKernel\MultiPlayerNumber=0 (which is the default). In the very unlikely case that you did run more than one MP instance and if you have configured a MultiPlayerNumber, you will have to adapt the number
probably by increasing the number by 1 (because formerly 1 was added to the configured number to get the MultiPlayer instance and now the configured number is directly used).
As MultiPlayer V6 can run as a Windows service, the possibility to run TurboPlayerEngine as Windows service makes sense now. If you want to use this combination you must first install the MultiPlayer service and then TurboPlayerEngine as service, because the engine will configure a dependency of the MP service. (Hint: this is not done if you use the /NoMP command line switch).
A special OS call is made to ensure that the needed precision of the multi-media timer is still 1 millisecond. - Added new preventions against starting TurboPlayer engine multiple times. This became necessary because now you can run TurboPlayer engine (and MultiPlayer) as Windows service, which makes it more likely to try starting multiple instances unintendently.
Added some additional log output when TurboPlayer tries to open the named pipe for the communication with MultiPlayer. This can help in case of problems – like e.g. multiple instances trying to get a connection
Build 6.5.2905.0
• Bugfix: With intensive use of MiniDBM, it may occasionally happen that complex search queries (multi-table searches, wildcards) cause the GUI to seemingly freeze (for a few seconds). This mainly refers to the display of the progress bar/envelope and the time display. (CCD-42823/OIA-1560)
Build 6.5.2904.0
• Change: Due to a hard limit in a used Windows function for the inter-module communication there is a limit of thread message boxes, which can be configured. For RundownKernel the limit was now set to: max 25 GUIs (unchanged), 25 IOManagers (increased), 16 remote TurboPlayers (unchanged) and the sum of all three must not exceed 59. (CCD-45661/OIA-8451)
• Bugfix: It was not possible to configure a GUI number greater than 9. (CCD-45661/OIA-8451)
• Bugfix: When a jingle was started with a mouse click, it was impossible to stop it until after a few seconds. (CCD-45538/OIA-8057)
Build 6.5.2903.0
• Bugfix: Displaying a waveform instead of a progress bar in the player window sometimes did not work. This could happen when a new main show was loaded with the macro command TP_LoadNode, because then the necessary internal reset of the GUI was executed too late, removing already loaded waveforms for the first already preloaded elements. (CCD-43635/OIA-5538)
• Bugfix: When a player window was configured to display more than one channel and to display a waveform instead of a progress bar, displaying the waveform did no longer work when a short playing element (like a jingle) temporarily replaced a longer playing element. (CCD-44427/OIA-5538)
Build 6.5.2901.0
Unusable build.
Build 6.5.2900.0
• Bugfix: The new keyword “Timers” for parameter TurboPlayer\Logging\DebugLog adds output to the BCSTechLogEx destination around setting or removing start- and stop timers for elements. (OIA-1739/CCD-43302)
for 6.4.
Build 6.4.2812.6
Requires DigaSQL 3.22.3522.0 or higher!
New: Mini DBM no longer includes soft deleted members of groups, stories, or end point stories, when such items are dragged into other parts of Turbo Player. (OIA-8156/CCD-45523)
Build 6.4.2812.5
Bugfix: The command line parameter -RKAIOM was not evaluated by the TurboPlayer GUI (only). (CCD-45661)
Build 6.4.2812.4
Bugfix: With intensive use of MiniDBM, it may occasionally happen that complex search queries (multi-table searches, wildcards) cause the GUI to seemingly freeze (for a few seconds). This mainly refers to the display of the progress bar/envelope and the time display. (CCD-42823/OIA-1560)
Bugfix: It was not possible to configure a GUI number greater than 9. (CCD-45661/OIA-8451)
Build 6.4.2812.3
New: Due to a hard limit in a used Windows function for the inter-module communication there is a limit of thread message boxes, which can be configured. For RundownKernel the limit was now set to: max 25 GUIs (unchanged), 25 IOManagers (increased), 16 remote TurboPlayers (unchanged) and the sum of all three must not exceed 59. (CCD-45661/OIA-8451)
Bugfix: When a jingle was started with a mouse click, it was impossible to stop it until after a few seconds. (CCD-45538/OIA-8057)
Build 6.4.2812.2
Bugfix: Displaying a waveform instead of a progress bar in the player window sometimes did not work. This could happen when a new main show was loaded with the macro command TP_LoadNode, because then the necessary internal reset of the GUI was executed too late, removing already loaded waveforms for the first already preloaded elements. (CCD-43635/OIA-5538)
Bugfix: When a player window was configured to display more than one channel and to display a waveform instead of a progress bar, displaying the waveform did no longer work when a short playing element (like a jingle) temporarily replaced a longer playing element. (CCD-44427/OIA-5538)