capabilities.work

Dolby OptiView Start a Single Engine and Confirm

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

Recipe · 3 steps

Dolby OptiView Start a Single Engine and Confirm

with Dolby.io · OTT & Streaming Delivery

Start one engine on a channel and wait until it reaches the playing state.

  1. List the engines attached to the channel and capture the id of the first engine to act on.
  2. Start the selected engine. Returns 204 No Content on success.
  3. Read the engine and inspect its status. The documented status enum includes deploying, starting, waiting, ingesting and playing. Loop back until the engine is playing or has errored.
What you'll need to have ready
  • authorization: HTTP Basic Authorization header value.
  • channelId: The id of the channel whose engine should be started.
For your developer

Arazzo workflow dolby-io:start-single-engine-and-confirm, 3 operations: get-channel-engines → start-engine → get-engine. Specs on APIs.io.

More recipes with Dolby.io

Dolby OptiView Attach Ingest and Engine then Go LiveDolby 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 Stop a Channel and Confirm IdleDolby OptiView Tear Down a Channel