Open Bug 1906273 Opened 2 months ago Updated 9 days ago

Choosing an audio track with fewer channels than preferredAudioChannelCount results in no audio when using Shaka Player and Firefox

Categories

(Core :: Audio/Video: Playback, defect)

Firefox 127
defect

Tracking

()

UNCONFIRMED

People

(Reporter: oscar.nord, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36

Steps to reproduce:

Example with Shaka Player: https://www.oscarnord.com/shaka-test/
Stream that is used in above example: https://storage.googleapis.com/shaka-demo-assets/tos-surround/dash.mpd

If you start with 6 channels, then change 2, the browser does not play the sound, if you then change to 6, the 6 channel does play. If you start with 2 channels, all other channel transitions work fine.

This works as expected in Chrome, Edge and Safari.

Issue created in the Shaka Player repo: https://github.com/shaka-project/shaka-player/issues/6980

Actual results:

No audio is playing when switching track (audio segments are loaded correctly in the player).

Expected results:

Firefox should be able to switch between to a track with fewer audio channels even when starting on a track with 6 channels.

Summary: Choosing an audio track with fewer channels than preferredAudioChannelCount results in no audio when using Shaka Player → Choosing an audio track with fewer channels than preferredAudioChannelCount results in no audio when using Shaka Player and Firefox

The Bugbug bot thinks this bug should belong to the 'Core::Audio/Video: Playback' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Audio/Video: Playback
Product: Firefox → Core

The severity field is not set for this bug.
:jimm, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(jmathies)
Flags: needinfo?(jmathies)
You need to log in before you can comment on or make changes to this bug.