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 581703 - rtph263pay rtp numbers not continuous
rtph263pay rtp numbers not continuous
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
git master
Other All
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-05-07 08:06 UTC by Marc Leeman
Modified: 2010-11-01 17:30 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
warnings on missing sequence numbers (8.20 KB, application/octet-stream)
2009-05-07 08:08 UTC, Marc Leeman
Details

Description Marc Leeman 2009-05-07 08:06:56 UTC
Please describe the problem:
when using rtph263pay; the RTP sequence numbers are not continuous as captured on the sending machine.

Steps to reproduce:
1. gst-launch udpsrc multicast-group=226.255.0.55 port=6000 caps="application/x-rtp,clock-rate=(int)90000" ! gstrtpjitterbuffer ! gstrtpptdemux ! rtph263depay ! queue2 ! rtph263pay pt=34 ! tee name=d d. ! queue2 ! udpsink host=226.226.226.123 port=6000 d. ! queue2 ! gdppay ! filesink location=h263pay-rtp.log


Actual results:
see wireshark and gdp dump with logging of missing packets. Capture is done on the sending machine, so no network issues can carete this that I know of.

Expected results:
rtp packets in sequence

Does this happen every time?
yes

Other information:
see wireshark and gdp dump with logging of missing packets. Capture is done on the sending machine, so no network issues can carete this that I know of.
Comment 1 Marc Leeman 2009-05-07 08:08:39 UTC
Created attachment 134173 [details]
warnings on missing sequence numbers
Comment 2 Marc Leeman 2009-05-07 08:13:12 UTC
wireshark dump (including encoder input and gstreamer output):
http://crichton.homelinux.org/~marc/downloads/h263_wireshark_rtph263pay_dump.cap.gz

gdp dump before sending
http://crichton.homelinux.org/~marc/downloads/
h263pay-rtp.gdp.log.gz
Comment 3 Wim Taymans 2009-06-03 14:55:35 UTC
The only reason I can see is that the payloader would reuse and modify buffers after it pushed them out, modifying the seqnum of the buffer downstream. That would be bad and it's not possible to quickly see this from the code...
Comment 4 Marc Leeman 2010-10-22 14:58:02 UTC
Haven't seent this anymore in the last year.