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 699804 - wavparse: Messing up timestamps with ADPCM
wavparse: Messing up timestamps with ADPCM
Status: RESOLVED DUPLICATE of bug 636245
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
git master
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-05-07 07:58 UTC by Sebastian Dröge (slomo)
Modified: 2013-05-07 13:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sebastian Dröge (slomo) 2013-05-07 07:58:05 UTC 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697955

http://adi.loris.tv/broken.wav is a WAV file with adpcm. adpcmdec uses GstAudioDecoder and does not do anything with timestamps, but the timestamps end up being bogus in the end. From the log below this seems to be caused by wavparse calculating wrong duration and thus putting wrong timestamps on the buffers

gst-launch-1.0 filesrc location=broken.wav ! wavparse ! identity silent=false ! adpcmdec ! fakesink silent=false -v

/GstPipeline:pipeline0/GstIdentity:identity0: last-message = chain   ******* (identity0:sink) (6144 bytes, dts: none, pts
:0:00:01.462857143, duration: 0:00:00.034829932, offset: 126, offset_end:  129, flags: 00000000 ) 0x7f1754003440
/GstPipeline:pipeline0/GstFakeSink:fakesink0: last-message = chain   ******* (fakesink0:sink) (8144 bytes, dts: none, pts
: 0:00:01.462857143, duration: 0:00:00.046167800, offset: -1, offset_end: -1, flags: 00000000 ) 0x7f1754003110
/GstPipeline:pipeline0/GstFakeSink:fakesink0: last-message = chain   ******* (fakesink0:sink) (8144 bytes, dts: none, pts
: 0:00:01.509024943, duration: 0:00:00.046167801, offset: -1, offset_end: -1, flags: 00000000 ) 0x7f1754003220
/GstPipeline:pipeline0/GstFakeSink:fakesink0: last-message = chain   ******* (fakesink0:sink) (8144 bytes, dts: none, pts: 0:00:01.555192744, duration: 0:00:00.046167800, offset: -1, offset_end: -1, flags: 00000000 ) 0x7f1754003440
/GstPipeline:pipeline0/GstIdentity:identity0: last-message = chain   ******* (identity0:sink) (6144 bytes, dts: none, pts:0:00:01.497687075, duration: 0:00:00.034829932, offset: 129, offset_end:  132, flags: 00000000 ) 0x7f1754003110
/GstPipeline:pipeline0/GstFakeSink:fakesink0: last-message = chain   ******* (fakesink0:sink) (8144 bytes, dts: none, pts: 0:00:01.497687075, duration: 0:00:00.046167800, offset: -1, offset_end: -1, flags: 00000000 ) 0x7f1754003220
/GstPipeline:pipeline0/GstFakeSink:fakesink0: last-message = chain   ******* (fakesink0:sink) (8144 bytes, dts: none, pts: 0:00:01.543854875, duration: 0:00:00.046167801, offset: -1, offset_end: -1, flags: 00000000 ) 0x7f1754003440
/GstPipeline:pipeline0/GstFakeSink:fakesink0: last-message = chain   ******* (fakesink0:sink) (8144 bytes, dts: none, pts: 0:00:01.590022676, duration: 0:00:00.046167800, offset: -1, offset_end: -1, flags: 00000000 ) 0x7f1754003110
Comment 1 Tim-Philipp Müller 2013-05-07 10:55:34 UTC 
Also see bug #636245, which has a patch that likely fixes this.
Comment 2 Sebastian Dröge (slomo) 2013-05-07 13:02:58 UTC 

*** This bug has been marked as a duplicate of bug 636245 ***