How To

We usually use a standard USB serial interface and a miniature relay.

It depends a bit on the way your video mixer outputs the tally signals for the control. Usually it is an open-collector circuit. Some devices actually short-circuit two pins of the connection socket.

From a purely technical point of view, PLAYDECK outputs a data stream via TX when GPIO remote control is activated. When this runs back into the system via RX, PLAYDECK starts playback.

So you have to switch a bridge between TX and RX with your interface.

The Devices

The image shows a “USB TTL adapter” connected to a minituare relay connected to a COM port.

Setting in PLAYDECK

After inserting the USB TTL adapter into the PC, a new COM port will become available to activate in PLAYDECK.

PLAYDECK supports both Internal and External Keying, given that the Output card supports it too. You can also output the key or fill signal seperatly.

Internal Keying

In internal keying mode, PLAYDECK will superimpose the graphics over an incoming signal:

External Keying

In external keying mode, PLAYDECK generates both fill and key signals and the keying is made by an external keyer:

Supported Devices

Please check your device specifications to ensure whether it support keying.

The following information is for Blackmagic cards, which are the most commonly used with PLAYDECK:

External Keying with Decklink Duo 2

Here is an example for External Keying with the Decklink Duo 2.

First you would need to combine 2 SDI Outputs into one connector with the Blackmagic Desktop Video App likes this:

We basically support all cards of the following manufacturers, since we always include the latest drivers. But because of the vast amount of cards out there, we only tested the most common ones.

These are the devices that have been tested with PLAYDECK.

AJA

• Corvid 24 R1
• Corvid 44
• Corvid 88
• KONA LHi
• KONA IP

Blackmagic Design

• DeckLink 4K Extreme 12G
• DeckLink 8K Pro
• DeckLink Duo 2
• DeckLink Intensity Pro 4K
• DeckLink Mini Monitor / Mini Recorder
• DeckLink Quad 1 / 2 / HDMI Recorder
• DeckLink SDI 4K
• DeckLink Studio 2 / 4K
• Ultra Studio HD Mini / 4K Mini / 4K Extreme 3 / Monitor 3G

Bluefish444

• Epoch 4K Neutron
• Epoch 4K Supernova S+
• Epoch Neutron
• Epoch Supernova CG
• KRONOS K8

Deltacast

• DELTA-3G-e 22
• DELTA-3G-elp-d 8c
• DELTA-3G-elp-key 11

DekTec

• DTA-2144B

Magewell

• Pro Capture Quad HDMI
• Pro Capture Quad SDI

Osprey

• Osprey 915
• Osprey 925
• Osprey 927
• Osprey 935
• Osprey 945
• Osprey 914
• Osprey 924
• Osprey 944
• Osprey 1214
• Osprey 1215
• Osprey 1225
• Osprey 1227
• Osprey 1245
• Osprey 1285
• Osprey M15
• Osprey M14
• Osprey M24
• Osprey M25

Stream Labs

• Alpha HD
• MH4LM
• MS4
• MSP2

Yuan

• SC550N1

RustDesk is a free Remote Destop Software, which we use to login to remote systems.

1. To get started, download our customized RustDesk from our website:
https://get.remote-joy-event-media.de/

This version will use our private RustDesk server (and not the public server) to protect your data and improve the connection speed.

2. Now start RustDesk and send us your connection info, looking like this:

Multichannel Audio is supported in PLAYDECK for all Inputs/Outputs, that being: Device, NDI, Internal. To activate Multichannel Audio, you only have to increase the Audio Channels in Playlist Output:

After that you may select how many Audio Channel you want to display in the VU Meter by Right-clicking it. Now add any Multichannel Clip into the Playlist. We prepared a 7.1 Clip SAMPLE (right-click and “Save as..”) for you:

Audio Channel Routing

In PLAYDECK, all Audio Channels are enumerated from 1 upwards, within the current selected Audio Track. If you have multiple Audio Tracks, you first have to select the Track you want to output. Then you can mix the Audio channels in any way possible:

Now you can reference your Audio channels (source) and route them to the NEW channels seperated by comma (target). There are several examples listed with the Routing Popup:

Send to OBS via NDI

If you want to use 8 Channel in OBS, activate NDI in PLAYDECK Playlist Output, then insert PLAYDECK as NDI Source and you are ready to go:

For cases, where NDI tally flag trigger or ATEM/vMix remote connections cant be used, you can setup a custom trigger at any given point.

Send trigger via TCP command

If your receiving side is able to understand any custom TCP command, you would setup the remote connection like this:

1. Setup and activate the Connection in the settings via “Remote Control > Outgoing > TCP Custom”.
2. You would then create a new Overlay of type “Remote Control” and insert your custom TCP command there.
3. (Optional) You would then add the Overlay to any point in the Playlist, e.g. on Clip 1 of a new Block via “Right Click Clip > Overlays”.

As a result the TCP command will be send at the given time in the playlist or when you press the overlay button.

Send trigger via JavaScript

If your receiving side is a custom API or needs special formatting, you would need to setup your own script for this:

1. Create a new Overlay of type “Webpage / HTML File”.
2. Use JavaScript in your HTML File to embed any custom command. A good examle would be a NodeJS server sending customized TCP commands.

Send trigger via API (WebSockets)

If you want the current PLAYDECK status in your script, you can use our API:

1. Create a new Overlay of type “HTML Templates”.
2. For an Introduction on how to use the API, click on “Main Menu > Settings > Scripting > How to create Scripts”
3. Modify any Sample (duplicate it) or create your own Script

The best way to connect vMix with PLAYDECK (both ways) is NDI. Multichannel Audio is supported.

Send Video from vMix to PLAYDECK

You only need to activate NDI as External Output like this:

Send Video from PLAYDECK to vMix

Activate NDI Output in PLAYDECK and add the NDI as new Source in vMix like this:

The best way to connect OBS with PLAYDECK (both ways) is NDI. Multichannel Audio is supported.

OBS doesn’t deliver NDI out of the box. You need to install an additional PlugIn, which is a quick and easy process:

1. Download PlugIn HERE (Select “obs-ndi…..Windows-Installer.exe”)
2. Close OBS and install the PlugIn like any other Windows App

Send Video from OBS to PLAYDECK

The NDI PlugIn inserts a new Option into the Tools Menu. Pick NDI Output and activate it:

Send Video from PLAYDECK to OBS

Activate NDI Output in PLAYDECK. The OBS NDI PlugIn inserts a new NDI Source, which you can add to your OBS Scene like this:

Sometimes the SYNC feature isn’t enough to have simultaneous playback and the operator wants to setup more complex ways of automation between the playlists. This can be done by setting PLAYDECK to remote control itself.

Sending Commands to anywhere in PLAYDECK via Overlays

To send a Command, you want to create a new “Remote Control” Overlay. You can now add one of the Custom Commands, that will be recognized by PLAYDECK. Basically you can CUE and PLAY clips, start Actions, show Overlays, etc..

Example: <cueandplay|2|1|1>
This will instantly play Playlist 2, Block 1, Clip 1.

A complete list of all commands can be found within PLAYDECK via “Show Commands”
Your overlay will look something like this:

Setup PLAYDECK events for automation

You add events to the playlist by adding the overlay with the commands to the clip. For example, if you want to start Playlist 2 (first clip) as soon as Playlist 1 starts playing, you would add the above Overlay to Clip 1 like this:

PLAYDECK supports most Amazon EC2 server instances and the NVidia GPU Power they provide. This allows you to setup a cloud based infrastructure for NDI transport or other purposes.

Quick start instruction

1. There is a quick start guide by Amazon, where you can also select your instance:
   https://docs.nvidia.com/grid/qvws/latest/qvws-quick-start-guide-amazon-web-services-ec2/index.html
2. A typical instance would be “Windows 2019 / g4dn.xlarge” – It has a Tesla Virtual NVidia GPU and enough specs to run PLAYDECK: 16 vCPUs (Intel Xeon), 64GB RAM, 1 vGPU (NVidia T4) with 16GB GPU RAM.
3. Install the Instance, which will conclude in running it within Amazons EC2 instance manager.
4. To connect to the instance via RDP you first have to open Port 3389 in the Instance Security Settings.
5. Once connected, you find yourself unable to download anything via the Browser. Therefore enable Downloads like this: START Menu > Server Manager > Local Server > IE Enhanced Security Configuration > Off
6. Now download and install PLAYDECK as usual:
   https://playdeck.tv/download/
7. Since NVidia driver are pre-installed, the GPU support in PLAYDECK will be enabled by default

Additional information

PLAYDECK can be installed on any Windows EC2 instance. Allthough GPU support isnt a requirement with PLAYDECK, it still is recommended for best performance. A list of all EC2 instances:
https://aws.amazon.com/ec2/instance-types/

If you decide to go with a clean installation of an instance (without a preselected windows image), you need to install the NVidia driver manually like this:
https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/install-nvidia-driver.html

PLAYDECK also supports a multi-user environment and saves licensed for the whole server instance.