Chosen audio track suboptimal on Chrome #3293

Closed
opened 2026-02-06 23:05:20 +03:00 by OVERLORD · 5 comments
Owner

Originally created by @brianjmurrell on GitHub (Oct 3, 2021).

Describe the bug
When playing media on Chrome that has both an AAC media track as well as a surround sound track such as AC3, the AAC track is not chosen by default, incurring an unnecessary transcode at playback time.

Additionally, the audio track selector shows Default for all tracks.

System (please complete the following information):

  • OS: Linux
  • Virtualization: None
  • Clients: Browser
  • Browser: Chrome 93.0.4577.82 (Official Build) (64-bit)
  • Jellyfin Version: 10.7.7
  • FFmpeg Version: N/A
  • Playback: Direct, with suboptimal transcode of audio -- which this issue is about
  • Hardware Acceleration: none
  • Installed Plugins: N/A
  • Reverse Proxy: none
  • Base URL: none
  • Networking: native
  • Storage: local

To Reproduce

  1. Obtain or create media with both an AC3 track as well as AAC track
  2. Play media in Chrome from Jellyfin
  3. Observe in playback data that the original is AC3 and that the track playing is AAC. Also observe in the track list that the AC3 track is being played. Also observe on the Jellyfin server an unnecessary ffmpeg running to transcode the audio.
  4. Choose the AAC native track from the player
  5. Observe all of the nasty behaviour from #4 above is gone.

Expected behavior
Should automatically choose the AAC track
Also, should not show Default on every track in the track list

Server Logs
N/A

FFmpeg Logs
N/A

Browser Console Logs
N/A

Screenshots
Default playback without explicitly selecting an audio track:
image

Available tracks:
image
(Notice how both say Default, as an aside)

Playback data when AAC track is explicitly chosen:
image

Additional context
None

Originally created by @brianjmurrell on GitHub (Oct 3, 2021). **Describe the bug** When playing media on Chrome that has both an AAC media track as well as a surround sound track such as AC3, the AAC track is not chosen by default, incurring an unnecessary transcode at playback time. Additionally, the audio track selector shows _Default_ for all tracks. **System (please complete the following information):** - OS: Linux - Virtualization: None - Clients: Browser - Browser: Chrome 93.0.4577.82 (Official Build) (64-bit) - Jellyfin Version: 10.7.7 - FFmpeg Version: N/A - Playback: Direct, with suboptimal transcode of audio -- which this issue is about - Hardware Acceleration: none - Installed Plugins: N/A - Reverse Proxy: none - Base URL: none - Networking: native - Storage: local **To Reproduce** <!-- Steps to reproduce the behavior: --> 1. Obtain or create media with both an AC3 track as well as AAC track 2. Play media in Chrome from Jellyfin 4. Observe in playback data that the original is AC3 and that the track playing is AAC. Also observe in the track list that the AC3 track is being played. Also observe on the Jellyfin server an unnecessary ffmpeg running to transcode the audio. 5. Choose the AAC native track from the player 6. Observe all of the nasty behaviour from #4 above is gone. **Expected behavior** Should automatically choose the AAC track Also, should not show _Default_ on every track in the track list **Server Logs** N/A **FFmpeg Logs** N/A **Browser Console Logs** N/A **Screenshots** Default playback without explicitly selecting an audio track: ![image](https://user-images.githubusercontent.com/559317/135755160-f97b7e9c-4562-403a-bf5f-9966a9dab77b.png) Available tracks: ![image](https://user-images.githubusercontent.com/559317/135755185-5aab69c5-318c-4aad-adb2-cb6946a4b6e1.png) (Notice how both say _Default_, as an aside) Playback data when AAC track is explicitly chosen: ![image](https://user-images.githubusercontent.com/559317/135755237-f04feb55-6571-4d98-9c1f-0d19131f6126.png) **Additional context** None
OVERLORD added the bugstale labels 2026-02-06 23:05:20 +03:00
Author
Owner

@Shadowghost commented on GitHub (Oct 3, 2021):

Except the fact that the default track is the intended track to be played alongside the video we don't know what the other tracks are meant for.

Automagically choosing the track based on best compatibility and language could lead to e.g. using a commentary track. If the track languages aren't properly tagged this could also lead to choosing a track with a totally different language than the intended one on movies with more than one audio language.

I understand why choosing the most compatible track may seem like a good idea but I think it'd lead to way more problems than it solves.

@Shadowghost commented on GitHub (Oct 3, 2021): Except the fact that the default track is the intended track to be played alongside the video we don't know what the other tracks are meant for. Automagically choosing the track based on best compatibility and language could lead to e.g. using a commentary track. If the track languages aren't properly tagged this could also lead to choosing a track with a totally different language than the intended one on movies with more than one audio language. I understand why choosing the most compatible track may seem like a good idea but I think it'd lead to way more problems than it solves.
Author
Owner

@Artiume commented on GitHub (Oct 3, 2021):

For 10.8 (or Jellyfin Media Player), we have an algorithm for selecting the best audio or subs. Try it to see if you think this bug is still an issue.

https://github.com/jellyfin/jellyfin-web/pull/2621

@Artiume commented on GitHub (Oct 3, 2021): For 10.8 (or Jellyfin Media Player), we have an algorithm for selecting the best audio or subs. Try it to see if you think this bug is still an issue. https://github.com/jellyfin/jellyfin-web/pull/2621
Author
Owner

@brianjmurrell commented on GitHub (Oct 5, 2021):

Except the fact that the default track is the intended track to be played alongside the video we don't know what the other tracks are meant for.

Ahhh. So are you saying that all tracks that are just different encodings (6ch, 2ch, etc.) of the actual sound track will all say Default and that it's not intended that Default to be applied to just one those different encodings of the same track?

Automagically choosing the track based on best compatibility and language could lead to e.g. using a commentary track.

Yes, if my understanding of what you are saying above is correct. So my desired behaviour then is to automatically choose, among the different tracks marked as Default, the one that is encoded to match the output hardware.

For 10.8 (or Jellyfin Media Player), we have an algorithm for selecting the best audio or subs. Try it to see if you think this bug is still an issue.

jellyfin/jellyfin-web#2621

Am I misunderstanding that this only affects multiple media items played one after another and has no benefit to the first/initial item played?

@brianjmurrell commented on GitHub (Oct 5, 2021): > Except the fact that the default track is the intended track to be played alongside the video we don't know what the other tracks are meant for. Ahhh. So are you saying that all tracks that are just different encodings (6ch, 2ch, etc.) of the actual sound track will all say _Default_ and that it's not intended that _Default_ to be applied to just one those different encodings of the same track? > Automagically choosing the track based on best compatibility and language could lead to e.g. using a commentary track. Yes, if my understanding of what you are saying above is correct. So my desired behaviour then is to automatically choose, among the different tracks marked as _Default_, the one that is encoded to match the output hardware. > For 10.8 (or Jellyfin Media Player), we have an algorithm for selecting the best audio or subs. Try it to see if you think this bug is still an issue. > > [jellyfin/jellyfin-web#2621](https://github.com/jellyfin/jellyfin-web/pull/2621) Am I misunderstanding that this only affects multiple media items played one after another and has no benefit to the first/initial item played?
Author
Owner

@Artiume commented on GitHub (Oct 5, 2021):

Correct, so it's for Shows and not movies. I personally encode the stereo track first and the 5.1 second so you have to manually select the 5.1 if you want surround sound. There really isn't a good way to 'assume' what is the best track to play. Based on experience, the stereo tracks that are listed last are typically the commentary tracks. I feel like if we tried to make Jellyfin smarter than it really is, it would cause people to complain about audio preference because of odd-case encoded media.

@Artiume commented on GitHub (Oct 5, 2021): Correct, so it's for Shows and not movies. I personally encode the stereo track first and the 5.1 second so you have to manually select the 5.1 if you want surround sound. There really isn't a good way to 'assume' what is the best track to play. Based on experience, the stereo tracks that are listed last are typically the commentary tracks. I feel like if we tried to make Jellyfin smarter than it really is, it would cause people to complain about audio preference because of odd-case encoded media.
Author
Owner

@jellyfin-bot commented on GitHub (Feb 3, 2022):

This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.

If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.

This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.

@jellyfin-bot commented on GitHub (Feb 3, 2022): This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments. If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label. This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on [Matrix or Social Media](https://docs.jellyfin.org/general/getting-help.html).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#3293