[FFmpeg-trac] #1852(swscale:closed): libswscale can't handle destination widths below 8

[FFmpeg]

#1852: libswscale can't handle destination widths below 8
-------------------------------------+-----------------------------------
             Reporter:  gjdfgh       |                    Owner:
                 Type:  enhancement  |                   Status:  closed
             Priority:  wish         |                Component:  swscale
              Version:  git-master   |               Resolution:  fixed
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  1
Analyzed by developer:  0            |
-------------------------------------+-----------------------------------

Comment (by cehoyos):

 Replying to [comment:9 gjdfgh]:
 > I think people would prefer a libswscale that doesn't blow up on dozens
 of corner cases and sacrifices bug-freeness for uncompromised speed, but
 that's just my opinion. The fact that libswscale suddenly fails when the
 scaling factor is too high is just one example.

 I suspect that libswscale is mostly used for video (or image) input, in
 its default configuration it supports downscaling from 1920x1080 to 32x18
 which I already find hard to imagine as a real-world use-case. (As you
 correctly pointed out, this limitation existed before and after the patch
 that fixed this ticket and is unrelated.)
 Whoever needs higher scaling ratios can easily fix the limitation by
 recompiling FFmpeg.

 If you believe that I am wrong, please suggest that the default gets
 increased, but imo you should at least outline what the use-case might be.
 (Note that there are hundreds of known bugs in the FFmpeg libraries that
 describe if not every-day so at least common use-cases so concentrating on
 true "corner cases" is probably not such a good idea given that man-power
 is the only limiting factor in FFmpeg development.)

 (Otoh, maybe we now have to support downscaling from common camera
 resolutions to X-Face, so my reasoning may be completely wrong.)

-- 
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1852#comment:10>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker