[Bug 730417] rtspt: no timestamp from some rtsp source over tcp

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=730417
  GStreamer | gst-plugins-good | 1.x

--- Comment #11 from Nicola <lists at svrinformatica.it> 2014-07-20 17:12:19 UTC ---
the patch look correct, wireshark show that rtptime go backward too so nothing
wrong with rtsp over tcp, great! 

the problem now is in the muxer (matroskamux),

I receive these buffers:

ts: 23301032087  size: 80480 => this is a keyframe
ts: 23167509865  size: 2399  => this buffer should go with the previous
keyframe not the one above since has a lower timestamp I suppose
ts: 23234265420  size: 508   => this buffer should go with the previous
keyframe not the one above since has a lower timestamp I suppose
ts: 23501332087 size: 4475

saving the file with matroskamux I see something like this:

(fakesink0:sink) (80480 bytes, timestamp: 0:00:23.301000000
(fakesink0:sink) (2399 bytes, timestamp: 0:00:04.204000000 => what????
(fakesink0:sink) (508 bytes, timestamp: 0:00:04.271000000 => what????
(fakesink0:sink) (4475 bytes, timestamp: 0:00:23.501000000

for now my solution, not ideal, is to drop frames that has big negative
timestamp gap using a custom element between the muxer and the filesink,

my pipelines:

rtspsrc ! rtph264depay ! h264parse ! appsink

appsrc ! matroskamux streamable=true ! filesink

to extract the above timestamp from the saved mkv file I use:

filesrc ! matroskademux ! fakesink

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.