Skip to content

jpegparse: Does not passthrough timestamps depending on downstream elements

Submitted by Nicola @drakkan

Link to original bug (#728356)

Description

please test this pipeline:

gst-launch-0.10 -v souphttpsrc location=http://213.251.201.196/anony/mjpg.cgi do-timestamp=true ! jpegparse ! videorate ! image/jpeg,framerate=3/1 ! fakesink silent=false

you'll see:

/GstPipeline:pipeline0/GstFakeSink:fakesink0: last-message = "chain ******* (fakesink0:sink) (8060 bytes, timestamp: 0:00:00.333333333, duration: 0:00:00.333333333, offset: 1, offset_end: 2, flags: 1 ro ) 0x7f33d0025a30"
/GstPipeline:pipeline0/GstFakeSink:fakesink0: last-message = "chain ******* (fakesink0:sink) (8042 bytes, timestamp: 0:00:00.666666666, duration: 0:00:00.333333334, offset: 2, offset_end: 3, flags: 1 ro ) 0x7f33d0025ad0"
/GstPipeline:pipeline0/GstFakeSink:fakesink0: last-message = "chain ******* (fakesink0:sink) (8072 bytes, timestamp: 0:00:01.000000000, duration: 0:00:00.333333333, offset: 3, offset_end: 4, flags: 1 ro ) 0x7f33d0008f30

now the same in 1.0 (today git):

gst-launch-1.0 -vm souphttpsrc location=http://213.251.201.196/anony/mjpg.cgi do-timestamp=true ! jpegparse ! videorate ! image/jpeg,framerate=3/1 ! fakesink silent=false

no buffer arrive to fakesink the logs show these messages:

0:00:04.502834927 4274 0x1678850 WARN videorate gstvideorate.c:1109:gst_video_rate_transform_ip:<videorate0> Got buffer with GST_CLOCK_TIME_NONE timestamp, discarding it
0:00:04.510393982 4274 0x1678850 WARN videorate gstvideorate.c:1109:gst_video_rate_transform_ip:<videorate0> Got buffer with GST_CLOCK_TIME_NONE timestamp, discarding it