>
>
> Date: Tue, 29 Nov 2011 20:30:36 +
> From: Jeff Shanab
> To: LIVE555 Streaming Media - development & use
>
> Subject: Re: [Live-devel] Passing H.264 RTP stream to hardware decode
> Message-ID:
><
> 615fd77639372542bf647f5ebaa2dbc
Sorry for the bad subject!
>
> Date: Tue, 29 Nov 2011 10:08:32 -0800
> From: Ross Finlayson
> To: LIVE555 Streaming Media - development & use
>
> Subject: Re: [Live-devel] Passing H.264 RTP stream to hardware decode
> Message-ID: <6634fb8c-1025-47c9-8
ppy.
From: live-devel-boun...@ns.live555.com
[mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson
Sent: Tuesday, November 29, 2011 12:09 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Passing H.264 RTP stream to hardware decode
I am working on pa
> I am working on parsing H264 too. A RTP H264 stream
> I found that it is a common approach of decoders (hard and soft) to request
> an entire AU (or frame).
> However, the code in live is parsing the streams at NAL-by-NAL basis.
If you're talking about *receiving* H.264/RTP streams, then the on
Hello,
I am working on parsing H264 too. A RTP H264 stream
I found that it is a common approach of decoders (hard and soft) to request
an entire AU (or frame).
However, the code in live is parsing the streams at NAL-by-NAL basis. At
the (file) sink every NAL is appended to a file with an start_cod
