HLS variant wrongly guessed as video (it is audio)
See original GitHub issueHave you read the FAQ and checked for duplicate open issues? yes
What version of Shaka Player are you using? 2.5.0-beta3
Can you reproduce the issue with our latest release version? yes
Can you reproduce the issue with the latest code from master?
yes
Are you using the demo app or your own custom app? demo app
If custom app, can you reproduce the issue using our demo app?
What browser and OS are you using? Mac with Chrome and Safari
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
What are the manifest and license server URIs? sent via email
What did you do?
load manifest in demo app
What did you expect to happen? content play with video and audio
What actually happened? only audio is playing no video
apparently the “guess audio” / “guess video” part of the code is not working for our manifest it wrongly guess that an audio only variant is a video variant as a side effect, when choosing best codec, it removes all the video codec and only keep mp4a audio ones
maybe our manifest dont respect best practice i don’t know
thanks
Issue Analytics
- State:
- Created 4 years ago
- Comments:13 (13 by maintainers)

Top Related StackOverflow Question
@fadomire we will be investing resources in HLS in our 2.7 release. Our initial implementation has grown old and if I remember correctly was only meant to cover the core elements of HLS, not all. The best way to get the spec-issue resolved, will be to file an issue citing the part of the spec that we are not respecting. This will make it easier for us to allocate resources to. In this case, I would actually suggest that you file it as a feature request since it would be extending our implementation to include an additional spec detail.
As for skipping variants, I would suggest that you open another issue that focuses on that. If you can host a copy of your manifest with the Audiodescription uris included and file a bug saying that variants are being skipped, we will be more able to dedicate resources to investigating that issue.
Closing due to inactivity. If this is still an issue for you or if you have further questions, you can ask us to reopen or have the bot reopen it by including
@shaka-bot reopenin a comment.