> I am trying to use Live555 to implement an RTSP server in our IP camera.
>
> Our H.264 encoder produces NAL units preceded by a 00 00 00 01 start code.
>
> The encoding main thread then writes the NAL units to a linux pipe where they
> can be read by the RTSP Server thread for streaming out
After tracing through there seems to be, dare I say a bug or misleading
testProgram.
The bye handler calls code resulting in Medium::Close. This ends up calling the
destructor on the RTCP class and deletes the fKnowMembers.
The OnReceive is then attempted to be called where it ends up trying to
Hi,
I am trying to use Live555 to implement an RTSP server in our IP camera.
Our H.264 encoder produces NAL units preceded by a 00 00 00 01 start code.
The encoding main thread then writes the NAL units to a linux pipe where
they can be read by the RTSP Server thread for streaming out.
Following your suggestion I got the Bye handlers working better. But I am back
to a situation that may indicate I am doing to much in my handler.
The case in incomingReportHandler1 that handles the BYE falls thru to and tries
to execute onRecieve with the old data. In on receive it tries to acce
Thanks all, the live555 functionality here works fine.
The problem is that ffmpeg requires H264 extradata in avcC format,
which is annoyingly complex to put together. Manning up in
progress...
James
On Thu, Nov 17, 2011 at 10:58 PM, Ross Finlayson wrote:
> Then you will split the
> returned
