Remote Control Playlist 2 via Playlist 1 events

Sometimes the SYNC feature isnt 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.

Configure PLAYDECK for Internal Remote Control

First, you want to setup PLAYDECK to receive and transmit TCP commands to itself like this:

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, 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:
Settings > Remote Connections > Incoming > TCP Commands > 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:

Install PLAYDECK on Amazon EC2

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. Select the following EC2 image with pre-installed NVidia driver:
    https://aws.amazon.com/marketplace/pp/prodview-ef3s5qtefim32
  2. As instance type select “g4dn.xlarge” – it is very capable performance-wise. It represents these server specification: 16 vCPUs (Intel Xeon), 64GB RAM, 1 vGPU (NVidia T4) with 16GB GPU RAM
  3. Start the EC2 instance and connect to it
  4. Allow browser downloads:
    START Menu > Server Manager > Local Server > IE Enhanced Security Configuration > Off
  5. Now download and install PLAYDECK as usual:
    https://playdeck.tv/download/
  6. 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.

Use Playlist 2 as alpha channel over Playlist 1

This can be achieved via any supported output card, which supports internal keying.
For this example we use the “Decklink Duo 2”. In PLAYDECK this sample will look like this:

Configure Decklink for Internal Keying

Open the Decklink setup utility “Desktop Video Setup” and set SDI 1+2 like this. This will be used for internal keying, where SDI 1 will receive the video signal from Playlist 1 and will key Playlist 2 over it and output the combined video via SDI 2.

Now you setup SDI 3 as standalone without keying. This will be used to send the video signal from Playlist 1 to Playlist 2 via SDI Loop.

Decklink SDI connections (Loop Cable and Output)

Use a short SDI cable and connect SDI 3 directly with SDI 1. We use this to feed the Playlist 1 signal via SDI 3 into the keying input SDI 1. Connect your final mixed output to SDI 2.

Setup PLAYDECK für Internal Keying

Channel 1 will send the video signal via SDI 3 to SDI 1 for mixing. Therefore you output Channel 1 like normal:

Channel 2 will receive the video layer on SDI 1. Now let PLAYDECK tell the Decklink to use Internal Keying to mix the Channel 2 signal over the one coming via SDI 1. Your final mixed output will be send to SDI 2.