Configure per-title encoding in Bitmovin with a complex encoding and auto representations
domain: bitmovin · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create an Encoding resource via POST /encoding/encodings and set a name and cloud region
Add a VideoStream with codec configuration referencing an H.264 or H.265 config, then attach PerTitleFixedResolutionAndBitrateConfiguration or auto representation settings to let Bitmovin derive the ladder
Create a ProgressiveMp4 or Fmp4 muxing per representation and link it to the stream; set output path to your S3 or GCS output resource
Start the encoding via POST /encoding/encodings/{encoding_id}/start; set the startEncodingRequest body to enable perTitle and optionally set autoRepresentations
Poll GET /encoding/encodings/{encoding_id} for status FINISHED, then retrieve the manifests via the manifest creation API to produce HLS and DASH outputs
Known gotchas
Per-title requires a two-pass analysis; encoding minutes are consumed for both passes — budget accordingly, as the bill is roughly double that of a single-pass job
AutoRepresentations cannot be combined with manually defined fixed representations in the same encoding; the API returns a validation error — choose one approach per job
Output paths must be unique per encoding job; reusing the same S3 prefix without versioning causes the new job to overwrite segments from a previous job, breaking existing manifests
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?