-
Notifications
You must be signed in to change notification settings - Fork 425
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 calculate timestamp offset for each segment #1451
Merged
dzianis-dashkevich
merged 5 commits into
main
from
fix-calculate-timestamp-offset-for-each-segment
Nov 28, 2023
Merged
Fix calculate timestamp offset for each segment #1451
dzianis-dashkevich
merged 5 commits into
main
from
fix-calculate-timestamp-offset-for-each-segment
Nov 28, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #1451 +/- ##
==========================================
+ Coverage 86.14% 86.18% +0.03%
==========================================
Files 42 42
Lines 10618 10624 +6
Branches 2447 2449 +2
==========================================
+ Hits 9147 9156 +9
+ Misses 1471 1468 -3 ☔ View full report in Codecov by Sentry. |
adrums86
approved these changes
Nov 28, 2023
dzianis-dashkevich
deleted the
fix-calculate-timestamp-offset-for-each-segment
branch
November 28, 2023 17:40
dzianis-dashkevich
added a commit
that referenced
this pull request
Dec 4, 2023
…rEachSegment and remove replaceSegmentsUntil (#1457) * Revert "fix: check for transmuxer for vtt-segment-loader (#1452)" This reverts commit b4dd748. * Revert "fix: fix several issues with calculate timestamp offset for each segment (#1451)" This reverts commit 3bbc6ef. * Revert "fix: replaceSegmentsUntil flag resetting too early (#1444)" This reverts commit af39ba5. * Revert "fix: prevent wrapping in resetMainLoaderReplaceSegments (#1439)" This reverts commit 719b7f4. * Revert "feat: Add feature flag to calculate timestampOffset for each segment to handle streams with corrupted pts or dts timestamps (#1426)" This reverts commit 2355ddc. * Revert "fix: fastQualityChange refactor (#1414)" This reverts commit 4590bdd. * cherry-pick: use transmuxer time info instead of probeTs * feat: sync controller media sequence strategy (#1458) * feat: add media sequence sync strategy * fix: fix current media sequence increment * chore: update logs * feat: use exact segment match in sync-controller * fix: fix race condition for a fast quality switch * chore: add additional logs for choose next request * feat: force timestamp after resync * chore: fix or skip tests * Update src/segment-loader.js Co-authored-by: Walter Seymour <walterseymour15@gmail.com> --------- Co-authored-by: Dzianis Dashkevich <ddashkevich@brightcove.com> Co-authored-by: Walter Seymour <walterseymour15@gmail.com> --------- Co-authored-by: Dzianis Dashkevich <ddashkevich@brightcove.com> Co-authored-by: Walter Seymour <walterseymour15@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.