Skip to main content
Skip table of contents

TIOGenericSerial.dll Sample configuration

The TIOGenericSerial.dll is an Input/Ouput DLL for Turboplayer. It can be used to control mixers or to send commands to audio switching devices. The attached .par file contains a sample configuration for both cases.

The DLL can be configured directly in the TurboPlayer GUI and will end up under the following key:
[Local Settings/TurboPlayer/IO/.../Settings/]

A) Mixer commands are solely handled within this key.

An example:
Somebody opens Fader 1 on the console. The console is configured to send out a unique serial string (in our case the hexadecimal value: 4D3130303130303035).
TurboPlayer listens on the serial port and compares the incoming serial commands with it's own configuraton. It will find the pattern under:

[Local Settings/TurboPlayer/IO/Serial/Settings/InputEvents/FaderMoved/Ch1On].
In this key you will also find an "AutomaticOutputFunction=Ch1On".
This triggers a couple of events. First of all the "next" item in the showlist will be played on Channel 1.
Second, the output function (that can be found under [Local Settings/TurboPlayer/IO/Serial/Settings/OutputFunctions/MoveFader/Ch1On]) will also fire a serial command to the mixer console to notify it that it received the message and started playing.

B) Generic Events are handled a little bit differntly. The "pattern" of the serial command is configured in [Local Settings/TurboPlayer/IO/Serial/Settings/OutputFunctions/Event].
These Functions can be "called" by an Event in the global or local [/.../TurboPlayer/EventsOut/.../] Section.

Look at [Local Settings/TurboPlayer/SerialEventOut1]. It fires the event "[Local Settings/TurboPlayer/IO/Serial/Settings/OutputFunctions/EventsOut/SwitcherCh1On]".
All you have to do is to enter the key (SwitcherCh1on) + "()" in the "Command" entry.

Managing different TurboPlayer configurations

With the release of TurboPlayer 3.1 a new feature is introduced: Handling of different configurations.

Up to now all settings of TurboPlayer were read from Global/Local Settings \ TurboPlayer

With this workflow it was difficult running a TurboPlayer for different scenarios or programs. Only DigaLocation could be used to choose different local parameter files before startup of TurboPlayer.

With TurboPlayer 3.1 several configurations can be stored inside the parameter files.

First of all the configurations must be defined. This is done inside the following subkey:

Local Settings \ TurboPlayer \ Configurations

Here each parameter will be named like the corresponding subkey for the configuration. The value will contain a screen friendly name which will be displayed in a selection window during startup of TurboPlayer.


TurboPlayer_Program1 = TurboPlayer for Program 1
TurboPlayer_Program2 = TurboPlayer for Program 2
TurboPlayer Training = TurboPlayer for Training
TurboPlayer_Default* = TurboPlayer (Default configuration)

The * at the end of a parameter will signal that this one will be preselected inside the selection window.

Now you would need to create several subkeys:

Local Settings \ TurboPlayer_Program1
Local Settings \ TurboPlayer_Program2
Local Settings \ TurboPlayer_Training
Local Settings \ TurboPlayer_Default

Now you can copy the default configuration from Local Settings \ TurboPlayer to each of these subkeys. You should not copy the subkey Configurations because it is not needed there.

If you now launch TurboPlayer you need to choose one of these configurations. If there is no user action the default profile is loaded after a while.

On the other hand it is possible creating shortcuts on the desktop to launch a configuration directly. This is done by the following command line:

C:\DigaSystem\TurboPlayer -c:TurboPlayer_Default

Please note: As it is possible storing parameters globally for all OnAir clients you need to pay attention that using configurations will no longer read the values from the default TurboPlayer subkey. Therefore you need to copy all parameters to the same subkeys as created inside the local parameter file

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.