After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 625654 - mpeg2dec gives incorrect timestamps to buffers.
mpeg2dec gives incorrect timestamps to buffers.
Status: RESOLVED INVALID
Product: GStreamer
Classification: Platform
Component: gst-plugins-ugly
unspecified
Other All
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-07-30 12:34 UTC by Vladimir Eremeev
Modified: 2010-12-08 07:05 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Vladimir Eremeev 2010-07-30 12:34:01 UTC
While messing with the reverse playback in MPEG-2 files I was tracing mpegvideoparse and mpeg2dec plugins.
My application builds playbin2 pipeline.

I've put a breakpoint at the line 1040 of the file gstmpeg2dec.c
http://cgit.freedesktop.org/gstreamer/gst-plugins-ugly/tree/ext/mpeg2dec/gstmpeg2dec.c#n1040
where the mpeg2dec plugin pushes the decoded frame downstream.

Then I've discovered an address of the pushed buffer's data and have given this address  to the Bitmap Memory Debugger ( http://www.theycamefromhollywood.com/bmd/ ). The buffer contained a decoded frame in YUV format, and BMD has visualized Y component of it.

Then I've opened the same file in the Elecard Stream Eye and AVIdemux applications and have found the same frame.
Both applications gave another timestamp for it, much earlier.

For example, the first movie frame (I frame) with the timestamp 0:00:00, according to the AVIdemux and the StreamEye, has the timestamp 0:00:01.02, when mpeg2dec pushes it downstream.
Comment 1 Vladimir Eremeev 2010-07-30 13:59:06 UTC
Hmm... 
However, dvbsnoop has shown the same 0:00:01.02 while parsing the same file.
Comment 2 Fabio Durán Verdugo 2010-12-08 02:49:19 UTC
any news for this report?
Comment 3 Vladimir Eremeev 2010-12-08 07:05:14 UTC
It's, probably, not a bug.