[Live-devel] "no frame!"

[Guillaume Ferry]

Well, it's really simple, the av_parser_parse2 method is being called on  
input buffers, and it will eventually update a variable when sufficient  
data has been received to identify a complete frame.
It works like a charm for me, when receiving videos streamed by live555  
servers.

Glad you found out another trick, anyway :)

Regards,
Guillaume.

Le Fri, 13 Jan 2012 19:42:22 +0100, Menne, Neil <nmenne at dcscorp.com> a  
écrit:

>
> I am in fact talking about the libraries for the underlying parts. In  
> what way was the parser context useful? I’m working on the SPS and PPS  
> stuff, but if >that’s useful for anything, it’d be a worthwhile addition.
>
>
> -Neil
>
>
> From: live-devel-bounces at ns.live555.com  
> [mailto:live-devel-bounces at ns.live555.com] On Behalf Of Guillaume Ferry
> Sent: Thursday, January 12, 2012 2:48 AM
> To: LIVE555 Streaming Media - development & use
> Subject: Re: [Live-devel] "no frame!"
>
>
> When you mention ffmpeg, do you mean the application, or the underlying
> library (libav) ?
> I had the same problematic few years ago, and I found it can be handled
> nicely with a reduced amount of code around avcodec_decode_video.
> I suggest you to have a look on AVCodecParserContext for this matter.
> If you're still stuck, I can even provide you a code sample.
>
>
> Regards,
> Guillaume.
>
>
> Le Wed, 11 Jan 2012 23:53:40 +0100, Menne, Neil <nmenne at dcscorp.com> a  
> écrit:
>>
>>
>> I’m working on my Live555/FFmpeg video player, and I ran into an  
>> interesting problem that has kept me stumped for several days. I am  
>> taking the >>buffer that is delivered to my MediaSink (like the example  
>> in testRTSPClient), and I am passing the buffer and the size to FFmpeg  
>> to decode. It says >>that there is “no frame!” I’m stumped as to why  
>> that is the case when I’m taking the buffer after the  
>> “afterGettingFrame” function is called. I was >>wondering if there was  
>> something else that must be done to that buffer for it to be a true  
>> frame that can be decoded.
>>
>>
>> My first guess is that the decoder needs more information which brings  
>> me to my next question: the SDP description that I’m pulling down  
>> doesn’t >>contain the width/height, so I’m guessing I need to pull that  
>> out of the sprop_parameter_sets; is this the case?
>>
>>
>> My second guess is that there is no frame separator; I noticed that in  
>> one particular file: H264VideoFileSink they prepend a 0x00000001 along  
>> with >>the sprop_parameters. Is this a potential problem?
>>
>>
>> Video is not my expertise, so I’m spending most days reading  
>> anything/everything on these problems, but this one’s got me stuck.
>>
>>
>> -Neil
>>
>>
>> P.S. My video is an H.264 video stream
>>
>>
>>
>>
>
>
>
>
>> --	
>> Guillaume FERRY
> IngénieurTraitement de l'Information et du ContenuTel : 01 39 30 62 09 
> Fax : 01 39 30 62 45ferry at bertin.frhttp://www.bertin.fr 	
>>

>
>
>
>


--  	Guillaume FERRY
Ingénieur
Traitement de l'Information et du Contenu
Tel : 01 39 30 62 09
Fax : 01 39 30 62 45
ferry at bertin.fr
http://www.bertin.fr 	
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20120116/2fcd57ef/attachment.html>