New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
preferredAudioChannelCount not filtering variants as expected #6491
Comments
This causes an issue when the player tries to switch to variant with a different audio codec. The player freezes and does not resume; cannot seek or pause/play out. No error is thrown. Last log emitted is |
preferredAudioChannelCount is not a variant filter, what it does is indicate to the ABR which channel we should start with. |
@avelad It looks like If this is working as intended, when a manifest has variants with 2 channels of audio and variants with 6 channels of audio, is there a way I can now configure Shaka to provide me with the variants that only have 2 channels of audio? |
@avelad Here is the change where We previously relied on that filtering to give us a variant track list with only stereo audio. Without it we can end up with a variant track list of differing audio codecs and channel counts like this. In this scenario, if I try switching to a variant with a different audio codec and channel count, playback either permanently freezes or the audio just completely drops after the switch. I have not seen this be an issue when auto abr switching is enabled, I'm assuming auto switching only considers variants of the same codec or channel count. But we have some use cases where we provide users the option to manually switch variants and that's when the issue occurs. I noticed the #5859 fix where this change was introduced, was ultimately not the necessary fix for it's parent issue: #5858. It looks like another fix was needed: #5869. I'm wondering if #5859 could be reverted or reimplemented? But if that change is there as intended, what would now be the recommended way to configure the player to filter for variants with 2 audio channels? |
@willdharris I think this should be implemented as a restriction and create |
Have you read the FAQ and checked for duplicate open issues?
yes
If the problem is related to FairPlay, have you read the tutorial?
not related
What version of Shaka Player are you using?
4.8.0
Can you reproduce the issue with our latest release version?
yes
Can you reproduce the issue with the latest code from
main
?yes
Are you using the demo app or your own custom app?
custom
If custom app, can you reproduce the issue using our demo app?
yes
What browser and OS are you using?
LG TV WebOS / Chrome 87
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
LG UQ7590PUB 03.34.00
What are the manifest and license server URIs?
https://devstreaming-cdn.apple.com/videos/streaming/examples/bipbop_adv_example_hevc/master.m3u8?93443
What configuration are you using? What is the output of
player.getConfiguration()
?Default config.
What did you do?
On a device that supports surround sound:
preferredAudioChannelCount = 2
which is the default value.What did you expect to happen?
Expected the tracks array to only contain variants with 2 audio channels, as it does in Shaka v4.5 and previous versions.
What actually happened?
The tracks array contains variants of all audio channel counts that are in the manifest.
The text was updated successfully, but these errors were encountered: