Skip to content

feat(DASH): Change from L3D to non-L3D after the successful playback #8876

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

Merged
merged 11 commits into from
Jul 16, 2025

Conversation

avelad
Copy link
Member

@avelad avelad commented Jul 15, 2025

fastSwitching can be used in case there is a need to start linear playback at very low delay (e.g. shortly after the time the client acquired MPD, initialization segments, and DRM license) or to switch from ad content to main content at an arbitrary point in the stream.

As an example, two representations, join6_540p and join6_1080p, have 6-frame GOPs and are used to start playback at a 6-frame boundary. This enables start-up and fine-grain random access at any 6-frame boundary.

fastSwitching are aligned with the “normal” adaptation set. Asa result, it it is possible to switch between “normal” and fastSwitching variant at any segment sequence boundary.

fastSwitching can be used in case there is a need to start linear playback at very low delay (e.g. shortly after the time the client acquired MPD, initialization segments, and DRM license) or to switch from ad content to main content at an arbitrary point in the stream.

As an example, two representations, join6_540p and join6_1080p, have 6-frame GOPs and are used to start playback at a 6-frame boundary. This enables start-up and fine-grain random access at any 6-frame boundary.

fastSwitching are aligned with the “normal” adaptation set. Asa result, it it is possible to switch between “normal” and fastSwitching variant at any segment sequence boundary.
@avelad avelad added type: bug Something isn't working correctly priority: P2 Smaller impact or easy workaround component: DASH The issue involves the MPEG DASH manifest format labels Jul 15, 2025
@avelad avelad added this to the v4.16 milestone Jul 15, 2025
@avelad
Copy link
Member Author

avelad commented Jul 15, 2025

Everything is tested manually because I don't have any assets I can publicly include in the repo. And livesim2 is still developing the feature, so the test will be added in a later PR. Sorry!

@avelad avelad requested a review from tykus160 July 16, 2025 08:27
@avelad avelad requested a review from tykus160 July 16, 2025 09:44
@avelad avelad requested a review from tykus160 July 16, 2025 10:43
@avelad avelad changed the title fix(DASH): Change from L3D to non-L3D after the successful playback feat(DASH): Change from L3D to non-L3D after the successful playback Jul 16, 2025
@avelad avelad added type: enhancement New feature or request priority: P3 Useful but not urgent and removed type: bug Something isn't working correctly priority: P2 Smaller impact or easy workaround labels Jul 16, 2025
avelad and others added 3 commits July 16, 2025 13:35
@avelad avelad merged commit a7cb005 into shaka-project:main Jul 16, 2025
37 of 47 checks passed
@avelad avelad deleted the l3d branch July 16, 2025 15:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: DASH The issue involves the MPEG DASH manifest format priority: P3 Useful but not urgent type: enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants