capabilities.work

Dolby OptiView Attach Ingest and Engine then Go Live

A 4-step recipe with Dolby.io. We can help you get access.

Recipe · 4 steps

Dolby OptiView Attach Ingest and Engine then Go Live

with Dolby.io · OTT & Streaming Delivery

Create an ingest and engine on a channel, start it, and wait for playing.

  1. Create the ingest (source feed) on the channel. Returns the ingest id and stream key under data.
  2. Provision a transcoding engine bound to the new ingest, deployed in the requested region with the chosen ABR ladder.
  3. Start the channel, which boots the newly attached engine.
  4. Poll the channel until its status reaches playing (live) or error. Status transitions through deploying, starting, waiting and ingesting while the engine spins up.
What you'll need to have ready
  • authorization: HTTP Basic Authorization header value.
  • channelId: The id of the channel to attach the ingest and engine to.
  • ingestName: Name of the ingest to create.
  • ingestType: Ingest type (rtmp-push, rtmp-pull, srt-pull, srt-push, or sdi-pull).
  • ingestUrl: Source URL (required for pull ingest types).
  • region: Region id to deploy the engine in (and required for rtmp-push ingests).
  • engineName: Name of the transcoding engine to create.
  • abrLadderId: ABR ladder id used for the engine quality configuration.
For your developer

Arazzo workflow dolby-io:attach-ingest-engine-and-go-live, 4 operations: create-channel-ingest → create-channel-engine → start-channel → get-channel. Specs on APIs.io.

More recipes with Dolby.io

Dolby OptiView Audit Channel Run HistoryDolby OptiView Enable Recording Webhook and TokenDolby OptiView Inspect an Engine's Last RunDolby OptiView Provision and Start a ChannelDolby OptiView Provision a Broadcast Token with ClusterDolby OptiView Provision a Viewer TokenDolby OptiView Publish a Secured DistributionDolby OptiView Start a Single Engine and ConfirmDolby OptiView Stop a Channel and Confirm IdleDolby OptiView Tear Down a Channel