Transcode Profiles

A transcode profile is an encoding recipe with a name: codec, quality, size and filters decided once, then applied wherever you point it — a stream, a movie, a created channel, a watch folder. Change the profile and everything using it follows.

Open Transcode Profiles → Create Profile.

The knobs that matter

Codec and hardware. Encode on CPU or hand the job to a GPU — with the device selectable on multi-GPU machines, and a software-decoding switch for sources that hardware decoders dislike. Presets and profiles are exposed for both H.264 and HEVC.

Quality. Constant quality by CRF, or explicit bitrate with buffer size and min/max tolerance for delivery that must hold a predictable rate.

Picture. Resize and scaling mode, aspect ratio, frame rate, and yadif deinterlacing for interlaced sources.

Audio. Codec, bitrate, channels and sample rate.

Branding. A logo overlay — your watermark, positioned where you want it, burned into the output.

Throughput. Thread count per job, which pairs with the encoding queue’s concurrency limits to keep a busy server responsive.

Where profiles apply

• Live streams — transcode on ingest, or pass through untouched at zero CPU cost.
• Movies and episodes — encoded once at add time into a target container, not per viewer.
• Watch folders — auto-encode every arrival with the folder’s profile.
• Created channels — normalise a playlist of mixed files into one consistent output.

The panel ships FFmpeg 8.0 and 7.1 with CUDA and VAAPI acceleration; which build runs is a panel-wide setting. The practical rule stands regardless of hardware: transcode with intent. Every profile costs CPU or GPU per channel — content that is already delivery-ready earns more served as it is.

Profiles finish the content story. Back on the subscriber side, one device family remains — Enigma2 receivers.