Articles in this section

See more

Using SCTE-35 marker insertion via REST API

  • Updated
Follow

Introduction

Videon devices support inserting SCTE-35 splice markers via REST API commands. Our general REST API documentation can be found here: Datasheets, REST API, and Setup Guides

Inserting SCTE-35 splice markers is most popularly used for denoting when ads are to be run in a stream in order to further monetize live video content.

SCTE-35 splice markers are currently supported for any MPEG2-TS output. These include Unicast, Multicast, RTSP, and SRT.

Steps to insert SCTE-35 splice markers

The process for inserting a SCTE-35 marker for downstream use is fairly simple. The perquisites are the following:

  • Know the IP of the target Videon device
  • Have a Unicast, Multicast, RTSP, or SRT stream successfully running to the desired destination
  • Have a method of sending a REST API command to the IP of the target Videon device (cURL, Postman, Advanced REST Client, etc.)

Once those prerequisites are met, perform the following steps:

  1. Power on and confirm the IP of the Videon device by entering it in a browser URL. This should load the Videon Web UI. You may close out of that webpage once the device is confirmed to be booted up.
  2. Configure the SCTE-35 settings by sending a command via your preferred REST command method. Below is an example. Refer to the REST API documentation for more details on command parameters
    • The only setting - duration - is how many milliseconds will be between the start and end of the splice marker section in the MPEG2-TS stream (in this instance, the splice marker section will be 30 seconds in duration) 
      #Check for SCTE-35 in available codecs
      GET http://[IP_ADDRESS]:2020/v2/encoders/data_encoders

      #If SCTE-35 is present already, note the data_encoder_id 
      #for codec: scte35.       Do not run the POST command below or 
      #you will receive a 500 error.

      #However, if NO data_encoder_id returned for codec: scte35, 
      #please run the following:

      POST http://[IP_ADDRESS]:2020/v2/encoders/data_encoders
      #Body 
      { 
       "codec": "scte35" 
      }

      #You should receive an id from the POST command

      #URI
      PUT http://[IP_ADDRESS]:2020/v2/encoders/data_encoders/[id]
      #Body    
      {      
       "codec": {
        "value": "scte35",        
        "scte35": {
      #Set the duration of the splice here (30 seconds)
         "splice_duration": 30000
        }      
       }    
      }

      #If you happen to receive any unexpected 500 errors 
      #from these requests, make sure to       remove any comments 
      #marked with '#'
  3. Insert a splice marker according the the configuration set above by simply making the following command: 
    • POST http://[IP_ADDRESS]:2020/v2/encoders/data_encoders/{id}/action/insert_splice
  4. The splice marker will now be inserted in the stream to be used downstream in your workflow, where you should be able to confirm based on how those tools operate.

Related articles