If your server is feeding H.264 NAL units one at a time to a
“H264VideoRTPSink”, via a “H264VideoStreamDiscreteFramer”, then each NAL unit
*must not* begin with a 0x00 0x00 0x01 ‘start code’.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
Ayik
From: live-devel on behalf of Weber,
Patrick
Sent: Thursday, January 18, 2024 9:24 PM
To: live-devel@lists.live555.com
Subject: Re: [Live-devel] H264 all frames corrupted. (Ayik Ahmet)
Could you tell us what you’re using for software encoding
Greetings,
I am having a problem for h264 rtsp streaming. I have implemented my own source
and sub session and it is working properly with frames that are encoded by
hardware encoder. I started using software encoder and my stream is corrupted.
I have tried to change max nal unit size from
> On Jan 18, 2024, at 5:17 AM, Ayik Ahmet wrote:
>
> Greetings,
>
> I am having a problem for h264 rtsp streaming. I have implemented my own
> source and sub session and it is working properly with frames that are
> encoded by hardware encoder. I started using software encoder and my
Could you tell us what you're using for software encoding? If it is FFmpeg, the
packets are made up concatenated NALs; you'll have to break those apart and
send the individual NALs to live555. Otherwise, we'll need more info about your
software encoder.
