Release Notes
2026.3.0 2026.2.0 2026.1.0 2025.3.0 2025.2.0 2025.1.0 2024.3.0 2024.2.0 2024.1.0 2023.3.0 2023.2.0 2023.1.0 2022.3.0 2022.2.0 2022.1.0
2026.3.0 2026.2.0 2026.1.0 2025.3.0 2025.2.0 2025.1.0 2024.3.0 2024.2.0 2024.1.0 2023.3.0 2023.2.0 2023.1.0 2022.3.0 2022.2.0 2022.1.0

TurboPlayer Service

Component

Version

TurboPlayer Service

6.8.401.0

TurboPlayer Service 6.8.401.0

1. API

1.1. New Features

  • Support ElementStartSync and ElementStartASync requests

  • Support ElementStopSync and ElementStopAsync requests

  • Support LoadShowSync and LoadShowASync requests

  • Support LoadFreeShowListSync requests

  • Support LoadJingleGroupSync request

  • Added timestamp on each message emitted from the service

  • GetShowList command now supports querying by Program ID

    • Added the 'ProgramNodeId" attribute to the command.

    • Marked the "Program" attribute as obsolete in the documentation and introduced "ProgramName" as its alias. Both attributes remain supported for compatibility.

1.2 Fixes

  • [CRITICAL] Fixed duplicated child elements in the service cache for containers

    • Effect: UpdateTreePartially event sent payloads containing duplicate notifications (both stale and current state), causing flickering and inconsistent UI state.

  • Properly handle elements skipped during playback

  • Properly handle deleted elements reported from TurboPlayer via UpdateTree notification

  • Don't send notifications with metadata changed before first DataModel activation

  • Synchronous requests don't block handling incoming following requests

  • Properly handle synchronous loading empty shows

  • Properly handle playtime information for prelisten elements

  • Properly handle playtime information on element recall or re-play before it is sent

  • Service send only single notifications by loading show into empty TurboPlayer

  • Always send changed BCS nodes with full nodeId

  • Service returns correct Time Information for items where hours is more than 24

  • Client receive information about running show from subscribed DataModels only after TurboPlayer transmit information about show to the service

  • Always send PlayState for started elements for the Data Model with condition "Changed"

  • Service returns correct Time Information with leading zeros for hours and minutes

  • Provide proper information changed by TurboPlayer in UpdateTreePartially notifications in metadata Node - UpdateData

  • Provide proper information changed by TurboPlayer in UpdateTreePartially notifications in metadata Node - Insert, UpdateTree, Delete

  • Properly handle playtime information for prelisten elements

  • NodeCopySync work properly by slow workstations

  • Properly parsing Integer and Float values while converting XML to Json

  • Provide proper time information changed by TurboPlayer in UpdateTreePartially notifications in metadata Node

  • Proper handle RTF files linked to elements to provide RTF in events

  • GetLoadedRundown request return actual broadcast list

  • Extra protection from invalid parameter values in multiple requests

  • Proper handle metadata changes for prelistened next played element

1.3 Known Issues

Using TurboPlayer macro TP_Recall can bring randomly to the wrong returned SendState metadata for the recalled element or played-after-recalled element

2. Service

2.1 New Features

  • Support for user rights management without using the "Request" folder

2.2. Fixes

  • none

3. Setup

3.1. Fixes

  • Setup fails when DigaSystem Registry GuiNumber is of type integer and not string

  • Service doesn't install TurboPlayerService.args.json and nuget.config

  • Service uses only .NET 8 in all packages. Setup script use properly files to install