Media profiles define reusable encoding settings that can be applied across one or more outputs. Instead of entering codec, bitrate, container, and related parameters every time an output is created, profiles are created once and reused wherever needed. This improves consistency, speeds up setup, and reduces the chance of configuration errors.
In practice, outputs are often built by combining multiple profiles. A single output might use one video encoding profile, one audio encoding profile, and one muxing profile to produce a finished stream.
Video walkthrough
This walkthrough tours the Media profiles tab and the creation of video, audio, and muxing profiles.
Video link: https://vimeo.com/1223030031
Why reusable profiles matter
Consistency — the same settings can be applied across many jobs or channels.
Efficiency — teams build outputs faster by selecting existing profiles instead of re-entering technical settings.
Quality control — approved settings can be standardised for specific use cases such as web delivery, mobile playback, archive, or broadcast workflows.
Simpler maintenance — when standards change, profiles are updated centrally rather than redefining every output from scratch.
Scalability — reusable profiles make it easier to support multiple renditions, adaptive bitrate ladders, and repeatable workflows.
Video encoding profiles
A video encoding profile stores the settings used to compress the video stream. These settings determine output quality, compression efficiency, compatibility, and bandwidth requirements. Typical parameters include codec, bitrate, resolution, frame rate, rate control settings, GoP structure, profile and level, and other codec-specific options.
Advanced settings
Video encoding profiles also include ADVANCED SETTINGS for fine-tuning encoding behaviour beyond the basic codec, resolution, FPS, and bitrate fields. These should normally be adjusted only when the output requires specific compatibility, quality, or delivery behaviour.
Setting | What it controls |
Scan type | Whether the output is progressive or interlaced, such as Progressive or Interlaced TFF. |
Rate control mode | How bitrate is managed, for example constant bit rate. |
Max bit rate | An upper bitrate limit where applicable, using the selected bitrate unit such as Mbps. |
Profile and level | Codec compatibility and capability limits, including automatic level calculation where supported. |
GoP size | The keyframe interval, using frames or seconds depending on the selected option. |
B frames and reference frames | Compression efficiency and playback compatibility. |
VBV buffer | Buffering behaviour for rate control and delivery stability. |
Video bitrate formats
Bitrate in video profiles may be entered in different units depending on system configuration or user preference.
Bps = bits per second — 5000000 Bps is typically interpreted as 5,000,000 bits per second.
Kbps = kilobits per second — 5000 Kbps = 5 Mbps.
Mbps = megabits per second — 5 Mbps = 5000 Kbps = 5,000,000 bps.
📕 Note: Supported bitrate range: video bitrate in a media profile can be set from 0.4 Mbps to 20 Mbps. Values outside this range are not accepted.
Audio encoding profiles
An audio encoding profile stores the settings used to compress the audio stream. These settings influence clarity, bandwidth use, device compatibility, and how audio is delivered alongside video. The supported audio codec is AAC.
When creating a new audio encoding profile, provide a required NAME, then configure the required audio fields: CODEC, CHANNEL LAYOUT, BIT RATE, and SAMPLE RATE. An optional description clarifies where the profile should be used.
Field | What it controls | Example values |
Name | The profile name used when selecting it for outputs. | Required free-text field. |
Codec | The audio codec used to compress the audio stream. | AAC |
Channel layout | The number and arrangement of audio channels. | Mono, Stereo, Surround 5.1 |
Bit rate | The target audio bitrate for the encoded stream. | 64,000; 128,000; 192,000; 256,000; 320,000 |
Sample rate | The number of audio samples captured per second. | 48,000 |
Description | Optional notes explaining the profile purpose or recommended usage. | “AAC stereo for web outputs” |
Audio bitrate formats
Bps = bits per second — 128000 bps = 128 Kbps.
Kbps = kilobits per second — 192000 bps = 192 Kbps.
Mbps = megabits per second, less common for audio because audio bitrates are usually much lower — 320 Kbps = 0.32 Mbps.
Muxing profiles
A muxing profile defines how encoded elementary streams, such as separate video and audio tracks, are packaged into a final deliverable format. Muxing does not usually change the encoded quality of the streams; it controls the container and packaging behaviour of the final output.
📕 Note: Muxing is the process of combining one or more encoded streams into a container. For muxing profiles, the only available container is MPEG TS.
Define the container format — MPEG TS.
Set the rate control mode, such as Constant bit rate (calculated), Constant bit rate (fixed), or Variable bit rate.
Set a muxing bit rate when required by the selected rate control mode.
Configure stream identifiers such as VIDEO START PID, AUDIO START PID, SCTE 35 START PID, and SMPTE 2038 START PID.
Determine how video, audio, signalling, and ancillary data are packaged together in the MPEG TS output.
📕 Note: Supported PID range: start PID values must fall between 16 and 8,190. This applies to Video start PID, Audio start PID, SCTE 35 start PID, and SMPTE 2038 start PID. Assign distinct values so streams do not collide within the transport stream.
Typical muxing use cases:
Packaging encoded video and AAC audio into an MPEG TS transport stream.
Creating transport stream outputs for broadcast-style delivery.
Including signalling or ancillary data by configuring SCTE-35 and SMPTE 2038 start PID values where required.
How profiles support outputs
Outputs are the final media deliverables generated by the system. A single output typically references one or more profiles, depending on what the output needs to contain. This model makes outputs modular: instead of treating every output as a one-off configuration, the system assembles outputs from reusable building blocks.
Video profile | Audio profile | Muxing profile |
Defines how the video stream is encoded. | Defines how the audio stream is encoded. | Defines how streams are packaged into the final output. |
Reusable profiles support standardisation and modular design. The same audio or video profile can be attached to many outputs, while different muxing profiles can package those encoded streams for different destinations.
Example output combinations
Use case | Video profile | Audio profile | Muxing profile | Result |
Broadcast-style delivery | H.264 1080p at 5 Mbps | AAC stereo at 128 Kbps | MPEG TS, constant bit rate | Standard high-quality transport stream |
Bandwidth-constrained delivery | H.264 720p at 2.5 Mbps | AAC stereo at 96 Kbps | MPEG TS | Smaller stream optimised for limited bandwidth |
Multi-rendition workflow | Multiple video profiles at different resolutions and bitrates | Shared AAC stereo profile | MPEG TS per rendition | Multi-bitrate set of outputs from reusable parts |
Best practices
Create profiles by purpose — organise them around delivery goals such as web, mobile, archive, or streaming.
Use clear naming — include codec, resolution, and bitrate in profile names where helpful.
Standardise bitrate units — choose bps, Kbps, or Mbps consistently across the environment.
Reuse approved profiles — limit ad hoc configuration where consistency matters.
Match muxing to destination — select packaging settings and PID values that fit the downstream workflow.
Review profile compatibility — ensure selected audio, video, and muxing settings work together for the target output.