TurboPlayer

Dependencies

• DigaSQL.dll 3.23.3528.0 (recommended)

• MultiRec_4.ocx 4.10.364.0 or newer (recommended)

• OnAIR TrackMixer 2.10.840.0 or newer (recommended)

• DigaStory.ocx 1.5.87.0 (recommended)

• DigaRTF 1.6.96.0 (recommended)

Known issues

• Drag & Drop from Content Manager to TurboPlayer of group / story / endpoint stories is not supported, yet.

Changes

• A feature for a very special video workflow has been implemented: if the global flag BroadcastSystem\PlayVideoInsteadOfMediaFile is set to TRUE and if an element with media type Audio references an additional video file in the medium list together with type “VIDEO” and one of the flags “.HIRES.” (or “.LOWRES.” for a preview) then TurboPlayer will (1) use this video file instead of the audio file for playout and (2) play this video file instead of the audio file when the user starts prelistening (e.g. with a middle mouse click). (The used preview module can be configured as usual in the global settings, tab “Video preview” or the corresponding settings for each rundown list and MiniDBM.)

• It is no longer possible to load shows from different programs/services in free-showlist mode. So far this was possible (e.g. with TP_LoadNode) but caused problems afterwards.

• Changed the used boost library to version 1.84 and OpenSSL to version 3.5. (OIA-9820)

• 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.

  • Hint1: this only works if the link-in value is positive, not for negative link-ins.

  • Hint2: in case a stinger should act on remote TurboPlayers, too, the definition of stingers must be identical for all TP computers. (CCD-45878/OIA-9250)

• A new macro parameter called ‘Select’ extends the capabilities of the TP_MiniDBM command and allows the user to perform a search in the MiniDBM window using an SQL clause. (OIA-6394)

• With the macro function DataOfGUI ( ) it is possibe now to query 4 additional values: HostName, ComputerName, StationName, StudioName. Hint: this is only possible for a desktop GUI of this version or higher, but not for a GUI connected via TPService. (CCD-45792/OIA-8772)

• So far, the name of an instance in an IO module was given by the registry key name below “TurboPlayer\IO”. Now the name of the instance can differ from the key name by using the new/optional parameter: “TurboPlayer\IO\…\InstanceName”. This can be configured in the IO module tab of the general settings dialog, too. The instance name is used within macro commands, messages or log output. (CCD-45792/OIA-8772)

• 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)

Fixed Issues

• Fixed the issue where, when a Jingle with long title from the Jingle Group was played, its title overdrew the Jingle duration in the header. (OIA-10173)

• MiniDBM: Search via Definitions bar returned no results for entries with apostrophes (OIA-9083)

• Throw C# compatible exceptions for incompatible with nullability arguments to not crash host based on .NET 9.0 and high (TurboPlayerWrapper2)

• The bugfix about sending fade(-out) commands for regional elements to a remote TurboPlayer did not work in case of using the macro command TP_FadeOut in conjunction with the keyword “All” as second parameter. (OIA-9508)

• Sending a fade(-out) command for regional elements playing on a remote TurboPlayer did not always work. This happened if no pre-start operation was necessary for the master element (no line-open, no switching of sound processing, no internal start event, …)  (OIA-9508)

• More log output for missing waveform can be activated with the parameter: Logging/DebugLog=FileAccess

  • This logging creates might many log entries and must not activated during normal usage. (CCD-43635/OIA-8599)

• Displaying a waveform instead of a progress bar in the player window sometimes did not work. This could happen during initial loading of a show when the “preload succeeded” message for an element form MultiPlayer/kernel reached the GUI faster than the XML data for this element from BCS/TreeManager. (CCD-43635/OIA-8599)

• Multiple bugfixes and modifications around the handling of regional elements were implemented. All of the underlying problems have in common that one element is used in multiple regions (explicitly or implicitly, e.g. by filling in a neutral element): (CCD-45874/OIA-9023+9508)

  • The player windows in the GUI could freeze and go on displaying an already stopped element as still playing.

  • A stinger for the neutral element was inherited to the elements in other regions, causing an unwanted stop of other elements when the regional elements were started.

  • A fade-out triggered from the player window of the master GUI was not replicated to all regional elements (local ones or remote ones).

  • An original element in the schedule track was set multiple times to "Sending" and then to "Sent". Now this is only done once: for the first usage of an element in a region, but not for further regions. Nevertheless, for each usage of an element a new element is being created in the corresponding protocol track.

  • Setting playing elements in the schedule track to "Sending" could prevent the start of the same element in other regions, because TurboPlayer stops an ongoing start if he sees that an element is already running on a different TurboPlayer. This protection was removed for the case of elements used in multiple regions.

  • The message for synchronizing the fade-out of regional elements was not sent via BCS, only a direct connection to the other TurboPlayers worked.

• Evaluating the four new values of DataOfGUI ( ) from the last version does now work in case of an automatic reconnect of a standalone GUI to the TP engine. (CCD-45792/OIA-8772)

• 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)

• 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)

• 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)

• 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)