On November 17, 2014 4:43:25 PM EET, Derek Buitenhuis <[email protected]> wrote: >On 11/17/2014 2:39 PM, Martin Storsjö wrote: >> Not technically, no, but given the way Chrome currently treats >segments >> that don't start with a keyframe it's probably desireable. > >Read: Chrome is broken / non-conformant. > >> Also we'd currently have a small gap or overlap of frames between >segments >> in different tracks if we cut all segments at once, since streams >without >> b-frames would have a few frames belonging to the previous segment at >the >> start of the next segment (since their dts is higher than dts in >streams >> with b-frames). > >Right OK. > >I'm just thinking it might not be desirable to make such cutting >completely >impossible with libavformat (it's required in some use cases). That's >all.
Yeah, it doesn't make anything impossible - this segmenter is mostly a reference example on how to do segmenting of the output from our mp4 muxer - if you want to do something fancy you should be using the mp4 muxer directly and segment it yourself. I've tried to make sure that what's in the mp4 muxer shouldn't be limiting such usecases. (With the dash segmenter, you can't do cutting at anything else than keyframes right now either, this just fixes misbehaviour in certain corner cases.) // Martin _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
