If your data stream arrives as a continuous buffer (its not easy to tell where NALs start/end) use H264VideoStreamFramer, if your NALs are separated & delivered one by one, use the H264VideoStreamDiscreteFramer. You can cull the startcodes from the NALs easily enough.
James On Fri, Nov 18, 2011 at 6:07 PM, David J Myers <david.my...@panogenics.com> wrote: > 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. > > > > My questions are:- > > 1. Is the linux pipe method a good enough mechanism for getting the > data to the server? Has anyone else done this? > > 2. Which H264 framer class do I need? The new > H264VideoStreamDiscreteFramer class doesn’t seem right because I have these > start codes on each NAL unit. If I base a new class on > H264VideoStreamFramer, do I need to remove the start codes? > > 3. What else does the framer class need to do? Is there an example of > this anywhere? > > > > Thanks and regards > > David > > > > _______________________________________________ > live-devel mailing list > live-devel@lists.live555.com > http://lists.live555.com/mailman/listinfo/live-devel > > _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
