Opened 6 days ago

Last modified 6 days ago

#7140 new enhancement

minterpolate filter does not work on huge video files

Reported by: kerchroot Owned by:
Priority: wish Component: avfilter
Version: git-master Keywords: minterpolate
Cc: Blocked By:
Blocking: Reproduced by developer: no
Analyzed by developer: no

Description

We are working with virtual reality videos and it is not uncommon for those videos to be bigger than 4096x4095.
Ticket 6795 helped a lot but we have more and more videos in a very high resolution.
Is it possible to remove resolution limits completely from minterpolate filter?
How to reproduce:

% ./ffmpeg [input] -vf minterpolate [output]
ffmpeg version N-45194-g40102a213-static https://johnvansickle.com/ffmpeg/  Copyright (c) 2000-2018 the FFmpeg developers
  built with gcc 6.3.0 (Debian 6.3.0-18+deb9u1) 20170516
...
    Stream #0:0(und): Video: hevc (Main) (hev1 / 0x31766568), yuv420p(tv), 6400x6400, 53472 kb/s, 30 fps, 30 tbr, 90k tbn, 29.97 tbc (default)
...
[Parsed_minterpolate_0 @ 0x74d3640] Failed to configure input pad on Parsed_minterpolate_0d=N/A    
Error reinitializing filters!
Failed to inject frame into filter network: Cannot allocate memory
Error while processing the decoded data for stream #0:1
Conversion failed!

Change History (6)

comment:1 Changed 6 days ago by oromit

The error indicates that your system plain ran out of memory.
I cannot see any frame size limitation in the filter, the limit is your RAM.

comment:2 Changed 6 days ago by kerchroot

See ticket 6795, cehoyos explained the problem.
And this patch: http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=ad73b32d2922f4237405043d19763229aee0e59e
It's not an out of memory problem

comment:3 follow-up: Changed 6 days ago by cehoyos

  • Priority changed from normal to wish
  • Type changed from sponsoring request to enhancement

Any reason you made it as difficult as possible to reproduce for everybody interested in this ticket?

comment:4 in reply to: ↑ 3 Changed 6 days ago by kerchroot

Replying to cehoyos:

Any reason you made it as difficult as possible to reproduce for everybody interested in this ticket?

Yes, this is the same issue as ticket 6795 which was already reported, reproduced, discussed and partially fixed. I thought that it will be a good idea to sponsor this issue complete fix. Sorry for this.

comment:5 follow-up: Changed 6 days ago by richardpl

It is ok to report bug reports, do you still want to sponsor complete fix?

comment:6 in reply to: ↑ 5 Changed 6 days ago by kerchroot

Replying to richardpl:

It is ok to report bug reports, do you still want to sponsor complete fix?

Yes, please email me cto@s3for.me

Note: See TracTickets for help on using tickets.