Send any Trigger to external Systems/APIs

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 Connections > Outgoing > TCP Custom”.
  2. You would then create a new Overlay of type “Remote Control” and insert your custom TCP command there.
  3. 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.

Send trigger via JavaScript / API

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 “WEB / HTML” and click on “Use Sample”.
  2. 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”.
  3. Modify the Sample (or duplicate it) to send a command via your prefered API.

You might also want to extend the “runtime” of the script to the whole playlist and react on the playback status within the script, instead of starting the script on seperate blocks/clips.

As a result, you can send any custom command to any client in the network.

Send trigger via COM / Closed Circuit (TTL) hardware

In this case, you would need to send a trigger directly via cable, instead of software/network. For this you could setup like this:

  1. Buy any commercial USB to TTL adapter to simulate a COM port
  2. Create a new Overlay of type “WEB / HTML” and click on “Use Sample”.
  3. 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”.
  4. Modify the Sample (or duplicate it) to send a “RX character” to the COM port. You might need to use a websocket for this.