fix: remove eac3 from web direct play profile#839
Merged
PartyDonut merged 1 commit intoDonutWare:developfrom Mar 14, 2026
Merged
fix: remove eac3 from web direct play profile#839PartyDonut merged 1 commit intoDonutWare:developfrom
PartyDonut merged 1 commit intoDonutWare:developfrom
Conversation
EAC3 (Dolby Digital Plus / Atmos) is not supported by most browsers (only Safari and Edge via platform media frameworks). Listing it in the web DirectPlayProfile causes Jellyfin to attempt direct play, resulting in silent audio playback in Chrome and Firefox. Removing eac3 from the web profile causes Jellyfin to fall through to the TranscodingProfile, which transcodes audio to AAC — supported by all browsers.
PartyDonut
approved these changes
Mar 14, 2026
Collaborator
PartyDonut
left a comment
PartyDonut
left a comment
There was a problem hiding this comment.
Thanks for having a look at this.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request Description
The web profile lists
eac3as a supported direct-play audio codec for mkv/webm containers. Most browsers (Chrome, Firefox) cannot decode EAC3 (Dolby Digital Plus / Atmos) — only Safari and Edge support it via platform media frameworks.This causes silent audio when playing MKV files with EAC3/DDP Atmos audio tracks in the web build. Jellyfin sees
eac3in the device profile, attempts direct play, and the browser silently fails to decode the audio stream.Removing
eac3from the webDirectPlayProfilecauses Jellyfin to fall through to theTranscodingProfile, which transcodes audio to AAC — universally supported. Video with AAC/Opus/Vorbis audio is unaffected and continues to direct play.