[FFmpeg-trac] #8114(undetermined:closed): Make minterpolate process higher resolution videos
FFmpeg
trac at avcodec.org
Fri Sep 6 23:28:06 EEST 2019
#8114: Make minterpolate process higher resolution videos
-------------------------------------+-------------------------------------
Reporter: deovr | Owner:
Type: defect | Status: closed
Priority: normal | Component:
| undetermined
Version: unspecified | Resolution: duplicate
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by cehoyos):
Replying to [comment:4 Gyan]:
> The ffmpeg memory allocation functions will not allocate more than
INT_MAX bytes (2^31-1).
>
> Two of the data structures in minterpolate hit that limit at around
4096x4095. It is unlikely that the limit will be raised.
I thought it would make sense to raise the limit under some conditions ...
> So, the other possible way is to refactor those data structures into
separate arrays, say, one per N rows, and allocate each separately. And
then adapt the filter to work with this new arrangement.
>
> One possible workaround with the current filter is to divide each frame
into partitions. Crop to each partition, with some padding added as per
the search radius. Perform minterpolate, crop to remove padding. And then
stack the results together. This could get very slow, so do it one
partition per command, save to lossless or HQ codec and then stitch those.
... especially since afaict, all this would not help on 32bit systems
(where above limit cannot be raised significantly).
--
Ticket URL: <https://trac.ffmpeg.org/ticket/8114#comment:5>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list