Re: [AVTCORE] [payload] Clarifying the H.265 RTP payload format specification's text on when to set the RTP "M" bit

[Ross Finlayson <[e-mail]>]

On Aug 26, 2013, at 9:50 PM, "Wang, Ye-Kui" <[e-mail]> wrote:

> Hi Ross,
>  
> Sorry for a slow response. I started to edit this draft today, and have included the following note after the semantics of the M bit:
>  
> Informative note: The content of a NAL unit does not tell whether or not the NAL unit is the last NAL unit, in decoding order, of an access unit.  An RTP sender implementation may obtain this information from the video encoder.  If, however, the implementation cannot obtain this information directly from the encoder, e.g., when the stream was pre-encoded, and also there is no timestamp allocated for each NAL unit, then the sender implementation can inspect subsequent NAL units in decoding order to determine whether or not the NAL unit is the last NAL unit of an access unit as follows.  A NAL unit naluX is the last NAL unit of an access unit if the next VCL NAL unit naluY in decoding order has the high-order bit of the first byte after its NAL unit header equal to 1, and all NAL units between naluX and naluY, when present, have nal_unit_type in the range of 32 to 35, inclusive, equal to 39, in the range of 41 to 44, inclusive, or in the range of 48 to 55, inclusive.
>  
> Would you be fine with this wording?

Yes, this looks good to me.


Ross Finlayson
Live Networks, Inc.
http://www.live555.com/