> On Feb 25, 2023, at 4:40 AM, Firdaus.Muhammad > <firdaus.muham...@isapsolution.com> wrote: > > For latest HEVC stream camera, the data will look like this > Nal Remark > 32 VPS > 33 SPS > 34 PPS > 39 Prefix > 19 I-Frame (1/3 size) > 19 I-Frame (1/3 size) > 19 I-Frame (1/3 size) > 39 Prefix > 1 P-Frame (1/3 size) > 1 P-Frame (1/3 size) > 1 P-Frame (1/3 size) > …. > 39 Prefix > 1 P-Frame (1/3 size) > 1 P-Frame (1/3 size) > 1 P-Frame (1/3 size) > That’s where I tried to merge the fragmented frames before sending it to the > decoder.
Are these "1/3 size" ‘frames’ individual NAL units - i.e., ’slices’? If so, then it is your responsibility (as a RTSP client) to decode them, or to do whatever is necessary to get your decoder to accept them. This is outside the scope of this mailing list. If, however, these "1/3 size" ‘frames’ are *not* individual NAL units, but are instead fragments of a single NAL unit, then your server is not compliant with the H.265 RTP payload format (because if it were compliant, then the LIVE555 RTSP client would be delivering these to you as single NAL units. In this case, you would need to contact the manufacturer of your server, telling them to fix it. (Again, this would be your responsibility; outside the scope of this mailing list.) Ross Finlayson Live Networks, Inc. http://www.live555.com/ _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
