You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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?
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
The text was updated successfully, but these errors were encountered: