Closed Bug 1131919 Opened 6 years ago Closed 5 years ago
Properly handle segment discontinuity
We have three conditions that we need to properly handle: 1- No data available, need to wait 2- No data available, it's a discontinuity skip to the next available 3- No data available, it's end of stream. Finish playback Currently, we only properly handle 3). When we reach the end of the buffered range and we search for the next available reader to provide us with more data, we perform a search across all segments and use the best one available. That search is done using a fuzz factor of 125ms. However, should the file be poorly muxed, it can happen that the time gap between two segments is slightly greater. We this happens we wait for more data. As no data is ever going to come, video playback stall (and often either just audio or just video plays) We need to be able to identify between condition 1 and condition 2 properly, ignore the discontinuity and continue playback.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1141333
You need to log in before you can comment on or make changes to this bug.