On Sun, 8 Jun 2014, Luca Barbato wrote:
On 19/05/14 00:28, Luca Barbato wrote:
Well, sure we can parse the #EXT-X_DISCONTINUITY marker, but what actual
effect does this have on receiving those streams? Setting
c->first_packet doesn't really do anything (it only makes sure we
recheck the discard flags immediately).
I'm not sure if I had been lucky or not, but hls w/out this patch gets
royally confused when you scramble segments, with it it behaves as expected.
What one might want to do, though, is to make sure we don't compare
timestamps from one variant from before the discontinuity to timestamps
from another one - however I think that's not much of an issue right now
either since we enforce returning packets according to segment sequence
number before we check the timestamps themselves.
I thought setting first packet would take care of it (since surprisingly
the testcase I created worked fine that way), I'll try to figure out if
it was just a lucky situation for some reasons.
People using this patch report it solves their problem... Can we look at
it together?
I can have a look if you can provide a sample where it does make a
difference.
// Martin
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
