TurboPlayer

Component	Version
TurboPlayer	6.5.2909.0

Dependencies

New: A stinger can now be configured to be executed at the link-in point of the stinger element instead of the usual start/mark-in point. This can be configured with the new parameter TurboPlayer\Stinger\...\ReferencePoint=LinkIn. For the standard stinger the parameter
TurboPlayer\Stinger\DefaultReferencePoint can be used. (CCD-45878/ OIA-9250)
- Hint 1: This only works if the link-in value is positive, not for negative link-ins.
- Hint 2: In case also a stinger should act on remote TurboPlayers, the definition of stingers must be identical for all TurboPlayers computers.

Bugfix: The macro command TP_AutoSetMarkIn did not work correctly. When iterating above the loaded shows in order to find an element to be handled, the implementation could ignore whole shows. This happened depending on the loaded content. (CCD-45754/ OIA-8770)
Bugfix: Some versions ago a protection was implemented, which prevents loading or unloading of shows if the current time is near around the start time of any loaded show. It came out that this protection is not sufficient. Now, the code takes the stop time of loaded shows into account, too. (CCD-45690/OIA-8554)
Bugfix: It can happen that MultiPlayer preloads an element in the rundown earlier than an element above of it (load inversion). In automatic activation mode TurboPlayer then could set a relative start timer for the wrong element – leaving out the element just being preloaded. If the timing was very bad, it could even happen that this wrong start timer was executed, destroying the correct sequence of elements. (CCD-45690/ OIA-8554)

Bugfix: Loudness adjustment did not work when an element was already prepared to a channel and the user then started the element on a different channel. (CCD-45188)
New: It was not yet possible to define allowed computers, which could remotely trigger a standard stinger. This is now possible by using the parameter TurboPlayer\Stinger\TriggeredFrom.
(CCD-45839/ OIA-8883)