SCTE-35 Insertion

zixi supports scte 35 insertion on inputs using the api (speak to your account rep for access to broadcaster api documentation) the scte 35 payload must be pre formed by the customer and encoded as base 64 or hex to be inserted scte 35 options can be enabled by using ?advanced=1 option when logging into broadcaster gui in version 17+ to insert scte 35 (pre version 19) setup on supported inputs, select support scte 35 injection support scte 35 injection enter a pid number for scte 35 injection (or leave as auto to match existing scte 35 pid) scte 35 pid select remove old scte 35 packets to clear out existing packets remove old scte 35 choose “keep stream cbr” to insert on null packets and maintain pcr accuracy in cbr streams keep stream cbr insertion use the api to insert desired scte 35 payload encoded as base64 or hex auth=basic auth using broadcaster login post to ?add stream scte json?stream=\<stream id>\&scte=\<base64 scte35 payload> to insert scte 35 (version 19+) setup on supported inputs, select support scte 35 injection support scte 35 injection enter a pid number for scte 35 injection (or leave as auto to match existing scte 35 pid) scte 35 pid select remove old scte 35 packets to clear out existing packets remove old scte 35 packets designate an appropriate timeout interval when searching for null packet to replace with the scte 35 packet to maintain pcr accuracy in cbr streams if no null packet is detected by the time the timeout is reached, the scte 35 will be inserted anyway breaking pcr accuracy momentarily (if stream is vbr, set this to 0) the value is in cycle ticks, so 90,000 = 1000 ms, 180,000 = 2000 ms, etc timeout interval for scte 35 injection insertion use the api to insert desired scte 35 payload encoded as base64 or hex auth=basic auth using broadcaster login post to ?add stream scte json?stream=\<stream id>\&scte=\<base64 scte35 payload>