PLAYDECK supports most Amazon EC2 server instances and the NVidia GPU Power they provide. Modify any Sample (duplicate it) or create your own Script.
Create a new Overlay of type “Webpage / HTML File”.If your receiving side is a custom API or needs special formatting, you would need to setup your own script for this: on Clip 1 of a new Block via “Right Click Clip > Overlays”.Īs a result the TCP command will be send at the given time in the playlist or when you press the overlay button. (Optional) You would then add the Overlay to any point in the Playlist, e.g.You would then create a new Overlay of type “Remote Control” and insert your custom TCP command there.Setup and activate the Connection in the settings via “Remote Control > Outgoing > TCP Custom”.If your receiving side is able to understand any custom TCP command, you would setup the remote connection like this: 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:įor cases, where NDI tally flag trigger or ATEM/vMix remote connections cant be used, you can setup a custom trigger at any given point. There are several examples listed with the Routing Popup: Send to OBS via NDI Now you can reference your Audio channels (source) and route them to the NEW channels seperated by comma (target).
Then you can mix the Audio channels in any way possible:
If you have multiple Audio Tracks, you first have to select the Track you want to output. In PLAYDECK, all Audio Channels are enumerated from 1 upwards, within the current selected Audio Track. We prepared a 7.1 Clip SAMPLE (right-click and “Save as.”) for you: Audio Channel Routing Now add any Multichannel Clip into the Playlist. To activate Multichannel Audio, you only have to increase the Audio Channels in Playlist Output:Īfter that you may select how many Audio Channel you want to display in the VU Meter by Right-clicking it. Multichannel Audio is supported in PLAYDECK for all Inputs/Outputs, that being: Device, NDI, Internal.