[Live-devel] Problem with fMaxSize after signalNewFrame() for live source

[Chmelev, Anton]

Hi,


>> If your encoder "FramedSource" subclass is delivering discrete H.264 NAL units

I was just confused with the fact that MS's encoder outputs multiple NALs with start codes.

I separate them, stripped off start codes, fed them into the H264VideoStreamDiscreteFramer?,and it works!


Thanks!


BR, Anton



________________________________
From: live-devel <live-devel-bounces at ns.live555.com> on behalf of Ross Finlayson <finlayson at live555.com>
Sent: 08 November 2014 4:02 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Problem with fMaxSize after signalNewFrame() for live source

I'm writing an application that encodes screen capture (using MS media foundation h264 encoder) and transmits it via RTSP using liveMedia.

I've written a wrapper for interfacing with the encoder (based on DeviceSource.cpp).
When the encoding starts,  maxFrameSize eventually grows to BANK_SIZE

This implies that (in your "createNewStreamSource()" implementation) you are feeding incoming H.264 NAL units to a " H264VideoStreamFramer".  That is wrong; "H264VideoStreamFramer" is used only when reading a H.264 file as a byte stream.

If your encoder "FramedSource" subclass is delivering discrete H.264 NAL units (i.e., one NAL unit at a time), then you must feed it into a "H264VideoStreamDiscreteFramer", *not* a "H264VideoStreamFramer".  (Also, each NAL unit that you feed into the "H264VideoStreamDiscreteFramer" must *not* begin with a 'start code' (0x00 0x00 0x00 0x01).)


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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20141109/af6f39d1/attachment.html>