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 609408 - [mpegpsdemux] Produces wrong timestamps
[mpegpsdemux] Produces wrong timestamps
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
0.10.x
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 609520 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-02-09 12:04 UTC by Miguel Angel Cabrera Moya
Modified: 2012-06-18 16:37 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Miguel Angel Cabrera Moya 2010-02-09 12:04:38 UTC
I have a file saved from a IP camera through http using wget.

It plays fine with mplayer but not with GStreamer.

Receiving the live stream with GStreamer have the same effect than playing it from a file.
Comment 1 Miguel Angel Cabrera Moya 2010-02-09 13:02:43 UTC
The file exceeds 1MB and cannot be attached, here it is in megaupload.

http://www.megaupload.com/?d=SBT0HFEP
Comment 2 Sebastian Dröge (slomo) 2010-02-09 13:59:14 UTC
Seems to be a problem with mpegpsdemux, it produces incorrect timestamps:

/GstPipeline:pipeline0/GstFakeSink:fakesink0: last-message = "event   ******* E (type: 102, GstEventNewsegment, update=(boolean)false, rate=(double)1, applied-rate=(double)1, format=(GstFormat)GST_FORMAT_TIME, start=(gint64)73257000000000, stop=(gint64)-1, position=(gint64)57109740300000;) 0x1120b80"
Setting pipeline to PLAYING ...
New clock: GstSystemClock
/GstPipeline:pipeline0/GstFakeSink:fakesink0: last-message = "chain   ******* < ( 8192 bytes, timestamp: 20:20:57.000000000, duration: none, offset: -1, offset_end: -1, flags: 33) 0x7f66800011c0"
/GstPipeline:pipeline0/GstFakeSink:fakesink0: last-message = "chain   ******* < ( 8192 bytes, timestamp: none, duration: none, offset: -1, offset_end: -1, flags: 1) 0x7f66800012c0"
/GstPipeline:pipeline0/GstFakeSink:fakesink0: last-message = "chain   ******* < ( 7764 bytes, timestamp: none, duration: none, offset: -1, offset_end: -1, flags: 1) 0x7f66800013c0"
/GstPipeline:pipeline0/GstFakeSink:fakesink0: last-message = "chain   ******* < ( 5168 bytes, timestamp: 4:29:07.339700000, duration: none, offset: -1, offset_end: -1, flags: 1) 0x7f66800011c0"
/GstPipeline:pipeline0/GstFakeSink:fakesink0: last-message = "chain   ******* < ( 5172 bytes, timestamp: 4:29:07.379700000, duration: none, offset: -1, offset_end: -1, flags: 1) 0x10cb6c0"

ffdec_h264 then drops all frames except the ones without timestamps because they're before the configured segment.
Comment 3 Edward Hervey 2010-06-17 08:38:48 UTC
*** Bug 609520 has been marked as a duplicate of this bug. ***
Comment 4 Edward Hervey 2010-06-17 08:39:21 UTC
ffdemux_mpeg shows the same timestamp errors.
Comment 5 Tim-Philipp Müller 2012-03-07 23:50:35 UTC
Does anyone still have this file?
Comment 6 Akhil Laddha 2012-06-18 16:37:29 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!