TurboPlayer

Dependencies

• DigaSQL.dll 3.21.3518.0 or newer (recommended)

• MultiRec_4.ocx 4.8.347.0 or newer (recommended)

• OnAIR TrackMixer 2.10.822.0 2.9.803.0 or newer (recommended)

• DigaStory.ocx 1.5.87.0 (recommended)

• DigaRTF 1.6.96.0 (recommended)

New/Changes/Fixed Issues

for 6.4.

Build: 2812.0

Release build without any substantial changes.

Build: 2811.0

• Bugfix: After an explicit or implicit disconnect from BCS and a later reconnect, it could happen that the report from TurboPlayer to BCS about the current activation did no longer work. (This report is needed if only a single TurboPlayer of multiple ones should be active.) This was a new problem since version 6.0.2403.0. (CCD-45458/OIA-7960)

Build: 2810.0

• New: A new option has been added for clearing an undocked OTM/CFM. There is now a new option in OTM and CFM settings to dock in addition to the pre-existing hide and keep open settings: (OIA7723)

Build: 2809.0

• New: Multiple macro commands have been modified in regards to the handling of endpoint-stories. The goal was to handle an endpoint-story like a single element by default. For more information, please have a look into the description of the macro commands in TurboPlayerTechManual. The following commands have been modified: (CCD-45278/OIA-7741)

  • TP_Fade: If mode CopyEPSFades is active, the fade command is executed for regional elements of the same endpoint-story (playing on the same computer or on a remote computer).

  • TP_Fadeout: Like TP_Fade. - TP_Flip: Endpoint-stories are always treated as a unit.

  • TP_Recall: In addition to the children, the endpoint-story “header” is now reset, too.

  • TP_SetNext: By default, a whole endpoint-story is handled, new option “EndpointStoryIndividually”.

  • TP_Skip: Endpoint-stories are always treated as a unit.

  • TP_ToggleStartMode: Was not changed in TurboPlayer, but with BCS version 6.4.466.0 and StartAttributeInheritance=Regular BCS will copy the start mode from an element to its parents.

• Bugfix: Fixed multiple small issues around the possibility to combine the special distribution endpoint “TurboPlayer” together with other endpoints/regions for one element (which was implemented in build 2802). (CCD-45205/OIA-7412) The macro command TP_SetControlOfElement ignored the last optional parameter7 – the parameter for the control to be set.

Build: 2808.0

• New: There is a new general TP mode: “CopyEPSFades”. If this mode is activated, TurboPlayer tries to copy fade values (mark/link/fade/amplification values, fade curve) as best as possible from the neutral elements of an endpoint story to all siblings with a specific endpoint/region. This allows to make transitions only for the neutral elements and then they will automatically be applied to all regions. Pay attention that this works well if the number and duration of the elements for all sequences are (nearly) identical, but in case of very varying sequences TurboPlayer tries to find a solution but the result might not be what you expect. (CCD-45276/OIA-7455)

Build: 2807.0

• Bugfix: During first execution of TurboPlayer, the path to MultiPlayer.exe was by default stored so that MultiPlayer could not be executed; manual intervention was required. (OIA-7671)

Build: 2806.0

• Bugfix: Since build 2804, mini DBM didn’t display class icons, and in build 2805, the new “group” column failed to display the group icons

Build: 2805.0

• New: MiniDBM can now display the “group” column. (CCD-45369/OIA-7540)

Build: 2804.0

• Migrated TurboPlayerWrapper2 to .NET 8. (OIA-7419)

for 6.3.

Build: 2709.2

• Bugfix: After an explicit or implicit disconnect from BCS and a later reconnect, it could happen that the report from TurboPlayer to BCS about the current activation did no longer work. (This report is needed if only a single TurboPlayer of multiple ones should be active.) This was a new problem since version 6.0.2403.0. (CCD-45458)