On Sat, 7 Mar 2015, Martin Storsjö wrote:

Even if this is a guess, it is way better than writing a zero duration
of the last sample in a fragment (because if the duration is zero,
the first sample of the next fragment will have the same timestamp
as the last sample in the previous one).

Since we normally don't require libavformat muxer users to set
the duration field in AVPacket, we probably can't strictly require
it here either, so don't log this as a strict warning, only as info.
---
libavformat/movenc.c | 42 ++++++++++++++++++++++++++++++++++++++++++
libavformat/movenc.h |  1 +
2 files changed, 43 insertions(+)

Opinions? The fact that AVPacket duration is needed for the mov muxer is sad, but hard to overcome. When using the frag_keyframe option for flushing on keyframes, we actually know the next timestamp of that stream so we wouldn't really need this, but we don't know it for all the other streams, so it isn't a complete solution. And it only works for frag_keyframe, not for frag_custom and other setups.

// Martin
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to