Skip to content
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

Low-Latency: Overlap decoding #80

Open
haudiobe opened this issue Jun 3, 2020 · 4 comments
Open

Low-Latency: Overlap decoding #80

haudiobe opened this issue Jun 3, 2020 · 4 comments
Labels
Deferred Deferred for future release/work enhancement

Comments

@haudiobe
Copy link
Member

haudiobe commented Jun 3, 2020

Background: In low-latency case, it may be needed that an existing segment download is terminated and the buffer is overwritten with new media data that overlaps on the same timeline.

CMAF Content: regular content for Audio and Video Profile

Test: Add content segment half way. Append a CMAF header. Add a new CMAF Fragment that overlaps with the timeline of the initial segment

Observation: Clean Switch

@haudiobe
Copy link
Member Author

haudiobe commented Jun 3, 2020

May be two tests:

  • CMAF Header appended
  • CMAF Header not appended
    Also need to exactly define what the overlap can be.

@jpiesing
Copy link

jpiesing commented Jul 3, 2020

I don't completely understand the issue here. Please can you give an example based on (say) 8s DASH segments made up of 2s CMAF chunks. Please remember that reading the data from the network is done by the DASH player. If the DASH player reads in (say) a DASH segment of 4 CMAF chunks and then, for some reason, the last CMAF chunk is to be discarded then the DASH player can just read in more data starting with the last CMAF chunk of that segment. If the 4 CMAF chunks have already been appended to the SourceBuffer then new data can be appended overlapping them.

How does this differ from 8.10 Overlapping Fragments?

@haudiobe
Copy link
Member Author

haudiobe commented Dec 8, 2021

This is a new use cases, that would require new test content as well as a more detailed description. Considered as an enhancements for the future.

@gitwjr
Copy link

gitwjr commented Jan 17, 2023

Deferred.

@gitwjr gitwjr added the Deferred Deferred for future release/work label Jan 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Deferred Deferred for future release/work enhancement
Projects
None yet
Development

No branches or pull requests

3 participants