Transcoding converts media from one encoded representation to another, usually by decoding it and then encoding new output. The conversion can change video codec, bitrate, frame dimensions, frame rate or audio format to meet a delivery or playback requirement. It can make an otherwise incompatible source usable, but it requires processing and can introduce delay or lose detail when lossy media is encoded again. Transcoding is different from remuxing, which changes packaging while retaining the compressed streams. The intended target device and output requirements should determine which operation is actually necessary.
Transcoding and Remuxing
Remuxing changes packaging without re-encoding the underlying media streams.
What the conversion changes
A transcoder reconstructs source samples, applies any requested processing and creates newly encoded samples. Different tracks can receive different treatment: video might be copied while only audio is converted. Resizing, burning subtitles into the picture or changing the video codec generally requires video processing and re-encoding. Merely changing the filename cannot accomplish those transformations or make a missing decoder appear.
Understanding quality and performance cost
A lossy source has already discarded information. Re-encoding can preserve much of its appearance at suitable settings, but it does not recover the missing original detail. Processing may also fail to keep pace with real-time playback if the encoder workload exceeds available resources. A live or on-demand transcoding system can therefore become the bottleneck even when the viewer's internet connection is fast.
Checking whether remuxing is enough
If the device supports the enclosed codecs but not the current container, a compatible remux may avoid unnecessary quality loss and processing. If an audio codec alone is unsupported, converting only that track can be sufficient. Inspect all required tracks, timing and subtitle behavior, preserve the original and validate the resulting file on the intended playback path rather than assuming successful export guarantees compatibility.
An illustrative example
A television supports a film's video codec but not its audio format. A conversion copies the video stream and transcodes only the audio into a documented supported format. The result addresses that specific mismatch while avoiding an unnecessary second video encode, although playback and synchronization still need checking on the target device.
Practical actions
- Inspect the target device requirements
- Convert only tracks that need conversion
- Preserve the original and validate playback synchronization