Nimble Advertizer is a server-side ads insertion framework for Nimble Streamer. Its business logic may be defined by both a dynamic handler and a pre-defined config, you can find full tech specification here.
Ads insertion time points within a live stream can be set in 3 ways:
Before you start using SCTE-35, you need to add the following parameter into Nimble Streamer config file:
Here's a brief summary of how Nimble Streamer handles the markers for ads insertion:
You can find example of handler response with marker-based insertion as well as other samples in Advertizer github repo. You can read all information regarding Advertizer usage on its website.
You may also insert SCTE-35 markers any moment to trigger ads insertion or pass them though for further use.
If you find any issues with SCTE-35 ads insertion, please file us a support ticket so we could help you.
Nimble Advertizer, SCTE-35 markers forwarding and passthrough, Trigger SCTE-35 marker insertion by Nimble API
Ads insertion time points within a live stream can be set in 3 ways:
- Specify the exact moment of time in GMT.
- Time spots relative to the beginning of the viewing session.
- According to SCTE-35 markers from the original stream.
Before you start using SCTE-35, you need to add the following parameter into Nimble Streamer config file:
scte35_processing_enabled = trueYou can read this page to find out how exactly you can make changes to Nimble Streamer config.
Here's a brief summary of how Nimble Streamer handles the markers for ads insertion:
- You create a handler app which will tell Nimble how to operate ads. This may also be plain JSON file with static pre-defined setting. Advertizer spec described handler in more details.
- Nimble Streamer processes incoming MPEG-TS and HLS streams with SCTE-35 markers to get the original content.
- Nimble Advertizer calls your handler app or static config and gets response with ads scenarios.
- Advertizer gets files with ads content to process them via Nimble Streamer according to ads scenarios logic defined by handler response.
- If the handler response defines that current stream needs to insert ads according to SCTE-35 markers (by using "time-sync":"scte35" field), Nimble inserts the ads into original media right at the time points specified in SCTE-35 marker.
- You can use this file as example of handler response which defines the usage of markers.
- End user connects to Nimble and watches media stream containing original content mixed with advertisements.
You can find example of handler response with marker-based insertion as well as other samples in Advertizer github repo. You can read all information regarding Advertizer usage on its website.
You may also insert SCTE-35 markers any moment to trigger ads insertion or pass them though for further use.
If you find any issues with SCTE-35 ads insertion, please file us a support ticket so we could help you.
Related documentation
Nimble Advertizer, SCTE-35 markers forwarding and passthrough, Trigger SCTE-35 marker insertion by Nimble API
