[FFmpeg-trac] #10064(undetermined:new): ffmpeg filter error: Picture size is invalid
FFmpeg
trac at avcodec.org
Wed Nov 23 14:02:33 EET 2022
#10064: ffmpeg filter error: Picture size is invalid
-------------------------------------+-------------------------------------
Reporter: Han | Owner: (none)
LiangLiang |
Type: defect | Status: new
Priority: important | Component:
| undetermined
Version: 5.1.2 | Resolution:
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Description changed by Han LiangLiang:
Old description:
> Summary of the bug: ffmpeg: [png @ 0x7f804d005e00] [IMGUTILS @
> 0x7ff7b26715f8] Picture size 96301x5197 is invalid
> How to reproduce:
> {{{
> % ffmpeg -i fuchun01.jpg -i fuchun02.jpg -filter_complex hstack test.png
> ffmpeg 5.1.2
>
> }}}
> fuchun01.jpg and fuchun02.jpg you can find from the attached files.
> After google, I also found the
> https://video.stackexchange.com/questions/28408/how-to-fix-ffmpeg-
> picture-size-32768x16384-is-invalid
> But seems no one create a ticket for this issue, so I create one.
> This feature is impressive as nowdays video switched to 4K, I think more
> and more images would have high resolutions.
> Maybe simple change it int64 could fix this issue?
New description:
Summary of the bug: ffmpeg: [png @ 0x7f804d005e00] [IMGUTILS @
0x7ff7b26715f8] Picture size 96301x5197 is invalid
How to reproduce:
{{{
% ffmpeg -i fuchun01.jpg -i fuchun02.jpg -filter_complex hstack test.png
ffmpeg 5.1.2
}}}
fuchun01.jpg and fuchun02.jpg you need to prepare your self, with a big
resolution of images. I can't upload it from the attach file since they
are too big.
After google, I also found the
https://video.stackexchange.com/questions/28408/how-to-fix-ffmpeg-picture-
size-32768x16384-is-invalid
But seems no one create a ticket for this issue, so I create one.
This feature is impressive as nowdays video switched to 4K, I think more
and more images would have high resolutions.
Maybe simple change it int64 could fix this issue?
--
--
Ticket URL: <https://trac.ffmpeg.org/ticket/10064#comment:1>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list