GNOME Bugzilla – Bug 693043
Payloads generated from rtpmp2tpay in gst-1.0 are incompatible with gst-0.10
Last modified: 2013-02-03 15:37:36 UTC
Created attachment 235049 [details] [review] patch file to fix caps for compatibility with rtpmp2tpay v1.x My situation right now encompasses using both 0.10 for legacy clients and 1.0 for our newer clients. Migrating to 1.0 I noticed the rtpmp2tpay-1.0 is incompatible with rtp2tpay-0.10. The pad caps in 1.0 use encoding-name: MP2T, whereas in 0.10 use encoding-name: MP2T-ES. My patch allows you to depay the payloads generated from the 1.0 payloader.
Thanks! commit 83adc3740e2985368980cb58a46c3ab28cc20264 Author: Michael Esemplare <mesempla@kablab.com> Date: Fri Feb 1 17:55:33 2013 -0800 rtpmp2tdepay: fix caps for compatibility with spec and rtpmp2tpay from 1.0 The encoding name is supposed to be MP2T according to RFC 3551 5.7, not MP2T-ES. The payloader in 1.0 was changed to produce that as per the spec, so let's accept the proper encoding-name in addition to the wrong one as well. https://bugzilla.gnome.org/show_bug.cgi?id=693043
Comment on attachment 235049 [details] [review] patch file to fix caps for compatibility with rtpmp2tpay v1.x Committed with minor changes (just merged it into the first caps structure)