-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
fix: Fix legacy codec support by rewriting codec metadata #4858
Conversation
Incremental code coverage: 83.33% |
e91a141
to
81e7274
Compare
I'm going to need more information to review this. Is there an associated issue filed? Why is this more correct than what we did before? |
@joeyparrish It's because other code will use the codecs from shaka-player/lib/media/media_source_engine.js Lines 348 to 376 in 15232dd
|
Feel free to try the test stream: https://cdn3.wowza.com/2/THFDbHhHVUJJVC9k/MEg5MFJH/hls/v7l2kt3h/playlist.m3u8 |
So basically, I just store the converted correct formatted codecs for further use. |
Thanks. As a tip for next time, that all would have been useful information to include in code comments or the PR description. |
Based on your explanation, I took the liberty of writing a PR description (now for the commit log, but would have been helpful for reviewers), as well as code comments (which will be helpful for future readers of that code to avoid "cleaning up" and reverting your change). Even better would have been to add a regression test, in case this logic is some day replaced in rewrite without preserving all the details. |
@joeyparrish Thanks, Sorry for the inconvenience . |
I'll merge this once the test pass is complete. (Or the other maintainers can do it if I'm too slow.) |
No problem. I hope the explanations are helpful, and that you'll continue to contribute to Shaka Player. We appreciate your contribution! |
This fixes legacy codec support by rewriting the codec metadata in the Stream objects. After capability checking, the converted codec information will be used. Co-authored-by: Joey Parrish <[email protected]>
This fixes legacy codec support by rewriting the codec metadata in the Stream objects. After capability checking, the converted codec information will be used. Co-authored-by: Joey Parrish <[email protected]>
We have a failing test case on Tizen since this was merged: https://github.com/shaka-project/shaka-player/actions/runs/3854362680/jobs/6568932949 |
This test started failing on Tizen after PR shaka-project#4858.
This test started failing on Tizen after PR #4858, which updates codecs in manifest metadata any time they are rewritten. Since ac-3 is rewritten as ec-3 on Tizen, that caused this test case covering ac-3 to start failing (because the codec says ec-3 by the end of the test).
This test started failing on Tizen after PR #4858, which updates codecs in manifest metadata any time they are rewritten. Since ac-3 is rewritten as ec-3 on Tizen, that caused this test case covering ac-3 to start failing (because the codec says ec-3 by the end of the test).
This test started failing on Tizen after PR #4858, which updates codecs in manifest metadata any time they are rewritten. Since ac-3 is rewritten as ec-3 on Tizen, that caused this test case covering ac-3 to start failing (because the codec says ec-3 by the end of the test).
This fixes legacy codec support by rewriting the codec metadata in the Stream objects. After capability checking, the converted codec information will be used. Co-authored-by: Joey Parrish <[email protected]>
This test started failing on Tizen after PR #4858, which updates codecs in manifest metadata any time they are rewritten. Since ac-3 is rewritten as ec-3 on Tizen, that caused this test case covering ac-3 to start failing (because the codec says ec-3 by the end of the test).
This fixes legacy codec support by rewriting the codec metadata in the Stream objects. After capability checking, the converted codec information will be used. Co-authored-by: Joey Parrish <[email protected]>
This test started failing on Tizen after PR #4858, which updates codecs in manifest metadata any time they are rewritten. Since ac-3 is rewritten as ec-3 on Tizen, that caused this test case covering ac-3 to start failing (because the codec says ec-3 by the end of the test).
…ect#4858) This fixes legacy codec support by rewriting the codec metadata in the Stream objects. After capability checking, the converted codec information will be used. Co-authored-by: Joey Parrish <[email protected]>
This fixes legacy codec support by rewriting the codec metadata in the Stream objects. After capability checking, the converted codec information will be used.