Release Notes
Release Notes
Breadcrumbs

TurboPlayer Service

TurboPlayer Service and the TurboPlayer Service SDK are in preview status

We strongly recommend to first use this version in a test environment before going productive with it. A stress test in a productive-like situation is needed in order to ensure the stability of this version.

Talk to our support team to get this version.

TurboPlayer Service

Component

Version

TurboPlayer Service

6.3.226.0 (Test version)

Dependencies

  • NET 6 Core Runtime and .NET 6 Runtime, x64 & x86

  • Installed DigaSystem core

    • Some parameters should be configured in DigaSystem registry

      • Section “TurboPlayerService” with at least one valid configuration should be created

      • Full BCS configuration should be existing

  • DPE 2.7.x with OIDC authentication support and followed services

    • Rights service

    • Parameters service

    • Log Service (optional)

  • TurboPlayer 6.3.2705.x (new minimum required TurboPlayer version!)

  • TurboPlayerServiceLicence.dll 1.0.2.0 - required for full functional version

  • DigaSQL 3.14.3466.0 or higher


Non-backwards compatible changes:

  • New names for the rights objects to be compatible with global naming scheme. All rights object names have now the point separator between “TurboPlayerService” and the rest of the name

  • Right name TurboPlayerService.ExecuteKernelMacro is renamed TurboPlayerService.ExecuteCommand

  • If the TurboPlayer configuration name is specified, all parameters for the Manual TurboPlayer configuration are ignored

New features

Service

  • New API
    warning Warning! The New API is incompatible with the previous TurboPlayer Service API (TurboPlayer Service Version 1.x)

  • Improve memory usage

  • Extended logging TurboPlayer metadata used to generate notifications

  • Compatibility with slow TurboPlayer hosts

  • New locking mechanism

  • Support TurboPlayer configurations from remote hosts

  • Encrypt plain text credentials in configuration file at start

  • Extended lock logs

Setup

  • DPE Default credential dialog added

  • DPE credential page added

  • TurboPlayer Connection Configuration Dialog added

  • Writing TurboPlayer Service settings to DigaSystem Registry

  • Service user Logon dialog added; Service is installed

  • Importing TurboPlayerService configuration into DigaSystem Registry

  • Setup: Windows Service is installed and provides an option to start after installation

  • Check if the Domain in the Service Logon configuration can be contacted

  • Support for reading and writing pseudo-encrypted DPE Credentials

  • Cleanup Custom Actions

  • Support for Upgrade installation added

  • Support for 'Modify' maintenance installation added

  • Empty Check of Configuration Name on Service instance Dialog added

  • Maximum TurboPlayer GUI number implemented

  • Maximum TurboPlayer GUI number range implemented

Fixes

Service

  • Log service user & password are used for DPE logging instead of DPE ParameterService user & password

  • Performance issue by very large (more than 50.000 lines per each) TurboPlayer configurations

Setup

  • Return error message if SetRubndownListMode request is used with Prelisten rundown list type

  • Fixed DPE credential wrong URL; Support for skipping DPE credential test

  • Fixed appsettings.json is not deleted on uninstall

  • Service user does not require admin rights; fixed populating combo boxes on the TurboPlayer connection dialog

  • Fixing appsettings.json Host name by appending "DpeWebApplication/" if a folder is not specifed

  • Setup does not recognize Service user if domain is david-gmbh.de

  • Fixed listed TP configurations

  • Existing TurboPlayer Service Configuration settings are not overwritten

  • Unattended Setup fixed

  • Fixed Support for Upgrade installation added

  • Fixed Windows Registry Path to DigaSQL.dll points to non-existing path

  • Really fixed Windows Registry path to DigaSQL.dll points to non-existing path