Optional transcoding without changing every stream
Keep working sources in Original / copy mode. Re-encode selected streams and VOD downloads only when codec, resolution or bitrate requirements justify it.
Start Free Trial Read setup guideSelect a source quality or actually encode it
Selecting an existing 720p source rendition is not transcoding. xOTT separates source track preferences from the Media processing selection. A saved Transcode profile controls the encoded output of the selected input; it does not silently change every channel after a global save.
The current output profile is one H.264 SDR rendition up to 1080p with no upscaling. It is not a 4K/HDR encoder or an automatically generated multi-resolution bitrate ladder. Compatible source multi-quality HLS/DASH is a separate capability.
Profiles and capacity stay explicit
Media Processing settings define enabled profiles, target/max bitrate, buffer and encoder effort alongside CPU jobs, threads, GPU admission and memory limits. Automatic device selection can prefer a suitable GPU with allowed CPU fallback; GPU-only requests require usable hardware.
A model name is not a readiness test. FFmpeg, drivers, device permissions, host resources and the actual source all matter. Synthetic encode/decode smoke checks are a useful baseline, not a guarantee of sustained throughput.
Use the processing host you actually intended
Live placement and VOD destinations select the relevant host. A worker needs its own usable encoding environment and capacity. Native worker VOD storage can move both processing and final storage; SFTP or cloud transfer may still require main-server staging.
Existing jobs retain their resolved profile revision. Editing a profile controls future work rather than rewriting an active stream or completed media file.
Measure one real channel before scaling
Test picture, audio tracks, output codec/resolution, sustained resource use and the intended receiving client. For headend loudness correction, inspect the separate UDP/audio processing scope and receiver behavior. A video bitrate profile is not a loudness target or a network-interface bandwidth shaper.
Follow the complete transcoder walkthrough, then expand cautiously using observed capacity.
Plan, configure and verify
CPU/GPU transcoding: configure and verify · Configuration map · Release history
Test your own sources and infrastructure
Use the full-feature trial with authorized accounts and representative clients. Verify the workflow before scaling.
Create account Plans and worker licensing