Cinegy Air Control application allows to broadcast regional variations apart from the main programming channel, thus providing programming specific for a particular region. A common example of using regional variations is local news or advertisements.

Regional variations broadcast can be achieved using the automatic opt-out and multichannel variation.

Automatic Opt-Out

Configuration of this workflow should be done on both main and regional channels sides.

Main Channel Configuration

To configure the opt-out workflow on the main channel side, follow the steps:

  1. Create a playlist; add content to be broadcast as an RTP, UDP or SRT stream to the regional channel.

  2. Set the "Automatic opt-out" block type for that content and define its "Avail Id":

  3. The playlist containing opt-out blocks can be exported for further use in regional channels. To do this, use the "Export opt-out playlist…​" command from the "File" main menu.

    In the exported playlist, opt-out blocks are cleared and marked as empty; "Avail Id" is preserved. All items outside opt-out blocks are replaced with live items (one per block), preserving their duration.
  4. Configure the RTP/UDP/SRT output for Cinegy Playout instance to be used for playlist broadcasting from the main channel. In the "RTP/UDP/SRT output transport settings" dialog, make sure to select the "SCTE35 cueing messages stream PID" option and define the PID value to enable SCTE-35 messaging:

Refer to the SCTE-35 Messaging section below for more information on SCTE-35 implementation.

Automatic opt-out workflow can be also built using SDI signal. SCTE-104 messages are embedded in VANC at line 11 in the SDI output signal. The line number parameter is hidden in the configuration and can be changed directly in the instance configuration file. Insertion of SCTE-104 can be disabled by setting the line number parameter to 0.

Regional Channel Configuration

To configure the workflow on the regional channel side, follow the steps below:

  1. Create a playlist that will use content from the main channel, set the same "Avail Id" for automatic opt-out blocks.

    Alternatively, you can use the playlist template generated on the main channel as it described in point 3. Fill in the opt-out blocks with regional content.
  2. For the Cinegy Playout instance that will receive the IP stream from the main channel, define the settings of RTP/UDP/SRT input and listening for the SCTE-35/104 cueing stream:


    The default URL defined here will be used as default RTP/UDP/SRT input for Live items in the playlist if "RTP/UDP Live Source" is not configured in the Live item parameters in Cinegy Air.

    The "Listen for SCTE-35/104 cueing stream" option should be selected to enable listening for SCTE-35/104 packets; the RTP/UDP/SRT URL should be specified in the "URL" field or the board number should be defined in the "Device number" field if SDI input is used.

    Refer to the RTP Input article in the Cinegy Playout Manual for detailed information on RTP input setup.

SCTE-35 Messaging

The default SCTE-35 implementation within Cinegy Air is to automatically insert the required SCTE-35 splice insert messages at the start and end of any program blocks of "automatic opt-out" type.

If possible, these SCTE-35 messages are sent 4 seconds before the event and use the PTS clock to accurately mark the splice point. If the change in ‘out of network’ status is due to an operator ‘jumping’ in the playlist, the SCTE-35 message will be sent as an ‘immediate’ out-of-network message and be labelled as such.

An early return to network caused by a clocked item ‘jumping’ the play head back into a normal block will still use the default 4 second pre-send, as this is a scheduled event in the playlist and can be predicted.

If an "Avail ID" has been set for the block, a DTMF descriptor is attached to out-of-network events with that "Avail ID" set in the body of the descriptor, if no "Avail ID" is set for an automatic-opt-out block, the DTMF descriptor and value will be suppressed.

All SCTE-35 events are uniquely identified, using a starting value indicating an automation system and restricted to the range 0x40000000, 0x40000001 …​. 0x4fffffff. The relevant PTS value is attached to the messages contained within a splice time field to allow frame-accurate operations.

For more details about the event ID allocation, please see section 6.4 of the ANSI/SCTE 67 2017 specification.

Out-of-network events include an estimated duration, even when a return event is fired (this value is in PTS ‘ticks’ and there are 90,000 PTS ticks/second). Return messages will be sent when the "automatic opt-out" block is completed, either through the natural progression of the playlist or via operator intervention (jumping out). Regardless of the reason why the return message is sent, no updated duration is included in the return to network message.

To prevent alarming for ‘phantom PIDs’ and to help diagnose correct configuration in the absence of trigger events, ‘splice null’ messages are sent as heartbeats, with a default of one per second.

The SCTE-35 PID is marked within the PMT with a “Cue Identifier Descriptor” and a value of 0x00 indicating a cue stream type that shall contain only "splice_insert", "splice_null", "splice_schedule" events.

All events are compliant with the ANSI/SCTE 35 specification, with messages conforming to the described structure and use.