TurboPlayer Service

Dependencies:

TurboPlayer Service 6.8.417.0

1. API

1.1 New Features

• New Synchronous request SetTurboPlayerModeSync

1.2 Fixes

• NodeMove requests now use a proper default timeout.

• UpdateTreePartially no longer sends stale notifications after a prelistened element is deleted.

• Field names in DataModelMarkupLanguage.json were updated so the documentation matches the data model.

1.3 Known Issues

• Metadata “Node" returns invalid time values. As a workaround, read time fields directly by name from the DataModel, e.g. use Time_Start instead of Node\element\Time_Start.

1.4 Future changes

• Breaking change for the next release (Release 2026.4): Synchronous requests will no longer return the default fields in the response body. Instead, you can specify exactly which fields to return. If you don't specify any, the response body will contain no fields.

2. Service

2.1 New Features

• Migrated to .NET 10.

• The start-up log now records the full service configuration (parameters, log level) and any configuration errors.

• Removed handling for list types not supported by TurboPlayer.

2.2 Fixes

• Critical: The service now reconnects properly to TurboPlayer Engine after the engine is closed and restarted.

• Remote TurboPlayer configuration parameters are now read correctly.

• Improved internal metadata cache handling:

  • Elements are removed from the cache only when they are unloaded in the TurboPlayer Engine or removed from the TreeManager.

  • Prelisten elements are no longer kept in the cache until the service terminates.

  • The cache no longer becomes inconsistent after handling UpdateTreePartially notifications.

2.3 Known Issues

• When the TurboPlayer IP address is changed in DigasAdmin and Reload Settings is triggered, the service does not connect to the new address. A service restart is required.

• Out-of-memory error with large shows under frequent changes

  When a large show with many elements is changed intensively and frequently. After several hours, the service throws an out-of-memory exception and must be restarted.

  This issue affects all previous releases, but it was identified during this release cycle.

3. Setup

3.1 Fixes

• Setup now installs the .NET 10 runtime required by the services.