[FFmpeg-devel] avisynth as an internal filter, any objections?

[Stefan Oltmanns]

AviSynth (or better VapourSynth) as filter sounds great, but is it possible?
The reason why input plugins (like FFmpegSource2) in
AviSynth/VapourSynth create an index file in a first pass is to allow
frame-accurate random access to the video. Also the exact number of
frames of a clip has to be known, because I could access that property
in VapourSynth.

There is a reverse filter in ffmpeg, but there is a warning to not use
it on long clips, because every frame needs to be buffered, so I don't
think the ffmpeg filter API has the ability to randomly access frames
(that for example wouldn't work with stdin).

But maybe porting some specific filters like QTGMC (which is probably
the best deinterlacer) that don't need that random-access functionality
would be possible.

Best regards
Stefan



Am 18.07.24 um 00:37 schrieb Marth64:
>> LOL,
>> Isn't there demuxer already?
>> Also as filter it would be less useful.
>
> I haven't actually used QTGMC. I have just read of it
> but have not had the time to apply it with VapourSynth.
> But it could be cool.
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".