[Ffmpeg-devel] [ppm @ 0x40415168]picture size invalid (1x0)

Víctor Paesa wzrlpy
Sun Sep 3 10:10:50 CEST 2006


> On Sun, 2006-09-03 at 00:52 +0200, V??ctor Paesa wrote:
>> > [ppm @ 0x40415168]picture size invalid (1x0)bitrate=12291.0kbits/s
>>
>> Some Googling (great tool!) around shows that this is a known problem,
>> that a partial solution was proposed, but rejected, and the submitter is
>> working on a definitive solution.
>>
>> http://article.gmane.org/gmane.comp.video.ffmpeg.devel/33114
>
> Apologies for overlooking this bug report despite some googling. I also
> tried your pnmtopnm approach but it appears that pnmtopnm passes only
> one "white.ppm" through and then exits. So ffmpeg sees only one frame.
> How did it work for you?
>
>> cat white.ppm white.ppm white.ppm | pnmtopnm > white_x_3.ppm
>> ls -l white.ppm white_x_3.ppm
> -rw-r--r--  1 martin users 61455 2006-09-02 22:08 white.ppm
> -rw-r--r--  1 martin users 61455 2006-09-03 08:41 white_x_3.ppm
>> diff white.ppm white_x_3.ppm
>>

Actually, pnmtopnm worked for me in this scenario:

ffmpeg -f image2 -i input.png \
-vhook './ppm.dll pnmtopnm | ffmpeg -v -1 -f image2pipe -vcodec ppm -i -
-f image2pipe -vcodec ppm -' \
-f image2 -y output.png

but, as you have pointed, it is processing just one frame.

> Anyways, I'll be patient and wait for the bugfix. I appreciate your
> work! Regards,
You're welcome, I'm also looking forward the bugfix.

Regards,
V?ctor Paesa




More information about the ffmpeg-devel mailing list