Why Does Lossless Surround Audio Trigger Conversion on Some Clients?
Lossless surround audio triggers conversion when any device or software layer in the playback chain cannot accept that codec and channel layout unchanged.
A movie can direct play its video while the media server converts Dolby TrueHD, DTS-HD Master Audio, multichannel FLAC, or another lossless track into AC-3, E-AC-3, AAC, or stereo PCM. The decision depends on the client app, television, streaming box, HDMI connection, ARC or eARC path, receiver, selected player, and reported capabilities. Diagnose the exact audio path rather than assuming the television’s product page proves end-to-end passthrough.
Confirm That Only the Audio Stream Is Being Converted
Start the same title on the affected client with video quality set to original and subtitles disabled. Record the server dashboard’s video mode, audio mode, selected track, output codec, channel count, and transcode reason.
Audio conversion does not always require video encoding. A Jellyfin issue shows H.264 video being copied while the unsupported audio stream was converted to AAC through HLS, proving that audio-only transcoding is a separate path.
If the dashboard also reports video conversion, remove the subtitle, bitrate, HDR, and container variables before diagnosing the surround track. The goal is one controlled session where only the audio selection changes.
Identify the Exact Codec, Profile, and Channel Layout
Inspect the selected stream with the media server or a media probe. Record whether it is TrueHD, TrueHD with Atmos, DTS-HD MA, DTS:X, multichannel FLAC, PCM, E-AC-3, or AC-3, plus its channel layout and sample rate.
A client that supports ordinary DTS or Dolby Digital does not automatically support the lossless extension. A current Android TV regression report describes DTS-HD MA passthrough failing even though the same device and another player could pass the track correctly.
Compare the lossless track with an embedded AC-3, E-AC-3, AAC, or stereo fallback from the same file. If the fallback direct plays while the lossless track converts, the video, storage, and network are not the primary cause.
Trace the Complete Client-to-Receiver Audio Path
Write the actual route: media app to streaming box or TV, then HDMI to television or receiver, followed by ARC or eARC if audio returns from the display. Every hop must carry the selected codec unchanged.
Some devices can decode a format locally but cannot bitstream it through the selected output path. Jellyfin’s client interface warns that TrueHD should be enabled only when the device or connected receiver supports it, because an incorrect capability choice can cause playback failure rather than passthrough.
Test the player connected directly to the receiver, then through the television. If direct receiver connection works but the TV-return path converts or fails, inspect eARC mode, digital-audio output, passthrough settings, HDMI input capability, and cable negotiation instead of changing the media server.
Compare Client Passthrough Settings and Player Versions
Check whether the app uses automatic, direct, or disabled audio passthrough and whether it selects a native player, ExoPlayer, web player, or external player. Record the client version before changing settings.
Client software can under-report hardware that actually supports a lossless codec. One Android TV issue shows TrueHD and DTS audio being converted even though the receiver and client were reported to support them, indicating a capability-reporting mismatch.
Test another app on the same device and receiver without changing the file. If one player passes the track and another converts it, preserve the server configuration and focus on the failing client profile, app version, and selected playback engine.
Check Channel Limits and Downmix Behavior
A client may accept AAC or PCM but only in stereo, or it may advertise six channels while the app requests two. Compare the server’s output channel count with the receiver’s front-panel format and speaker activity.
Jellyfin WebOS users have reported DTS-HD MA and multichannel FLAC being converted and then reduced to stereo, showing that codec conversion and channel reduction can occur in the same session.
If the receiver shows stereo after conversion, inspect the client’s maximum audio channels and the server’s transcode profile. Do not increase channels blindly when the delivery container or television cannot carry multichannel PCM or AAC through that path.
Choose a Compatible Fallback Without Re-Encoding the Video
Prefer an existing AC-3 or E-AC-3 compatibility track when the affected clients cannot pass lossless audio. Keep the original TrueHD or DTS-HD stream for capable theater clients.
When the library lacks a fallback, create a secondary audio track or an alternate media version rather than replacing the lossless source. An audio-only conversion is much lighter than video transcoding and preserves the original picture.
The ZimaSpace explanation of the audio transcoding pipeline provides the adjacent mechanism for understanding why a compatible fallback can preserve direct-play video.
Verify Passthrough, Synchronization, and Resume Behavior
Retest the lossless and fallback tracks from the start, after seeking, and after resume. Confirm server mode, receiver format, channel output, lip synchronization, and whether playback survives an app restart.
Audio-only conversion can expose client-specific seek problems. A Jellyfin television issue reports playback hanging after seeking when only the audio required transcoding.
The diagnosis is complete when capable clients pass the lossless track unchanged, limited clients select a stable compatible track, video remains direct play where possible, and the receiver displays the expected codec and channel layout throughout normal playback.
Recommended products
Support & Tips
More to Read
Why Does a Docker Volume Restore Recreate File Contents but Drop Extended Attributes?
A volume-restore diagnosis covering xattr inventory, tar and Rsync options, namespaces, destination support, privileges, labels, app metadata, and tests.
Why Does a Running Container Keep Its Old Memory Limit After the Compose File Changes?
A memory-limit diagnosis covering live cgroups, restart versus recreation, Compose fields, hard and soft limits, parent scopes, swap, and runtime heaps.
Why Does Restarting a Reverse Proxy Invalidate Every Session for One Self-Hosted App?
A session-loss diagnosis covering restart scope, cookie ownership, secret rotation, cache-backed sessions, sticky routing, auth gateways, and recovery.
