[gstreamer-bugs] [Bug 460274] New: FFmpeg buffer duration issues
GStreamer (bugzilla.gnome.org)
bugzilla-daemon at bugzilla.gnome.org
Wed Jul 25 08:28:00 PDT 2007
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
http://bugzilla.gnome.org/show_bug.cgi?id=460274
GStreamer | gst-ffmpeg | Ver: HEAD CVS
Summary: FFmpeg buffer duration issues
Product: GStreamer
Version: HEAD CVS
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: gst-ffmpeg
AssignedTo: gstreamer-bugs at lists.sourceforge.net
ReportedBy: julien at moutte.net
QAContact: gstreamer-bugs at lists.sourceforge.net
GNOME version: Unspecified
GNOME milestone: Unspecified
2 different issues :
1) When an ffmpeg demuxer receives a buffer duration of 0 it should set it to
CLOCK_TIME_NONE.
2) When an ffmpeg video decoder receives a buffer with CLOCK_TIME_NONE duration
it calculates the duration with the framerate. There is a check for a 1000/1
framerate which is the ffmpeg default to indicate "unknown framerate" but that
check is only applied against the codec context, not the framerate obtained
from the caps. So when using an ffmpeg demuxer together with an ffmpeg video
decoder and buffer duration are CLOCK_TIME_NONE it will by default calculate
the duration to 1 millisecond when it should stay CLOCK_TIME_NONE.
--
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=460274.
More information about the Gstreamer-bugs
mailing list