gst-plugins-bad: avtp: error on gst_avtp_src_start:<avtpsrc0> Failed to open socket: Operation not permitted

[John Rama]

Desounza,

>> Now question is does talker really need to set M bit ?
> 
> Well, IEEE 1722-2016, Annex F (Protocol Implementation Conformance
> Statement), Table F.12, Item H.264-4 says that, *yes*, the talker
> really need to set the M bit...
>
Oh, Yes. It's described so. I did not notice that.
Thank you for pointing out.

>>
>> IEEE1722 section "8.5.2.4 M field" says 
>>> The M field shall be set according to RFC6184, Section 5.1.
>>
>> And RFC6184, Section 5.1 says 
>> https://tools.ietf.org/html/rfc6184
>>
>>> Marker bit (M): 1 bit
>>> Set for the very last packet of the access unit indicated by the
>>> RTP timestamp, in line with the normal use of the M bit in video
>>> formats, to allow an efficient playout buffer handling.
>>>  Decoders MAY use this bit as
>>>  an early indication of the last packet of an access unit but MUST
>>>  NOT rely on this property.
>>
>> So this implies that it would be great if we can add the feature to the CVF plugin 
>> to support the stream without M bit field set.
> 
> One source of inspiration here could be the 
> gst-plugins-good/gstrtph264depay.c:gst_rtp_h264_depay_handle_nal() - it
> has some code to guess where M should be. Look for "marker".

Yes, I have already noticed this code, and seems not so hard to implement.
I'll update this post if I could make some progress here.

Anyway, thank you so much for your help !!
Really appreciated.

John