GNOME Bugzilla – Bug 438940
[rtph263ppay] Support for Segment Fragmentation based on the GOB Headers
Last modified: 2007-05-21 08:58:04 UTC
Where's a patch to add another fragmentation mecasim : Added Property fragmentation-mode as defined below : /* This algorithm assumes the H263+ encoder sends complete frames in each * buffer */ /* With Fragmentation Mode at 0 : * This algorithm implements the Follow-on packets method for packetization. * This assumes low packet loss network. * WIth Fragmentation Mode at 1 : * This algorithm separates large frames at synchronisation points (Segments) (See RFC 2429 This must be used in conjuction with ffenc_h263 with the rtp-payload-size > 0 For the encoder to generate non empty GOB Headers Patch is based on CVS from 16 May 2007 If you decide to allow to patch plz let me commit... :) If you guys know a way to make the read by byte to find the next gob more efficient it would be nice.. that's the one thing I feel uneasy about... I could read 4 bytes at a time but didn't have time to implement this .. and not sure that in this case it would really be more efficient
Created attachment 88301 [details] [review] Patch to implement GOB headers segmentation mecasim
Commited with some changes like making the property an enum and removing // comments. Patch by: Antoine Tremblay <hexa00 at gmail dot com> * gst/rtp/gstrtph263ppay.c: (gst_fragmentation_mode_get_type), (gst_rtp_h263p_pay_class_init), (gst_rtp_h263p_pay_init), (gst_rtp_h263p_pay_set_property), (gst_rtp_h263p_pay_get_property), (gst_rtp_h263p_pay_flush): * gst/rtp/gstrtph263ppay.h: Add new fragmentation mode based on GOB headers. Fixes #438940.