-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
feat(cea): Add CEA parser for TS #4697
Conversation
Incremental code coverage: 97.52% |
5fc363d
to
fa1276f
Compare
fa1276f
to
2976dd7
Compare
0c08990
to
7b0e83f
Compare
Related to PR shaka-project#4697
Related to PR #4697 This will help us ensure we're not changing parsing outputs by accident.
# Conflicts: # test/media/media_source_engine_integration.js
This completes the TS StreamGenerator and updates test expectations to match. With this, we get realistic simulated TS streams, which will be important as a baseline for replacing mux.js with our own TS parser. See also PR shaka-project#4697
This completes the TS StreamGenerator and updates test expectations to match. With this, we get realistic simulated TS streams, which will be important as a baseline for replacing mux.js with our own TS parser. See also PR shaka-project#4697
Includes #4739, but still isn't quite passing tests. I fixed two edge cases (one in TS parser, one in CEA decoder) that got the new parser's output aligned on timestamps... but I'm still seeing one edge case left. In the test where we append segment 0 only, we see the first cue come in at time 0.067 - 0.734, but when we append segment 2, then segment 0, that same cue for segment 0 comes in at time 0.767 - 4.972 (which is the same time as the old parser output). |
This exercise led to some bugs discovered, and the new test coverage shows that my changes to clarify the NALU parser did not break anything. |
This completes the TS StreamGenerator and updates test expectations to match. With this, we get realistic simulated TS streams, which will be important as a baseline for replacing mux.js with our own TS parser. See also PR #4697
So the problem is just when the first segment is added and with the first timestampOffset. After investigating the problem is in our CEA parser, I will continue investigating. |
Related to PR #4697 This will help us ensure we're not changing parsing outputs by accident.
This completes the TS StreamGenerator and updates test expectations to match. With this, we get realistic simulated TS streams, which will be important as a baseline for replacing mux.js with our own TS parser. See also PR #4697
Related to PR #4697 This will help us ensure we're not changing parsing outputs by accident.
This completes the TS StreamGenerator and updates test expectations to match. With this, we get realistic simulated TS streams, which will be important as a baseline for replacing mux.js with our own TS parser. See also PR #4697
Closes shaka-project#3674 Co-authored-by: Joey Parrish <[email protected]>
Closes #3674