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

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

[Roger Pack]

Hi all, just wondering, if I were to write a libavfilter that
basically "called out" to avisynth and had it process stuff, would
there be any ideological pushback, or would it possibly be accepted?
Cheers!
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

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

[Michael Niedermayer]

[-- Attachment #1.1: Type: text/plain, Size: 663 bytes --]

On Tue, Jul 16, 2024 at 07:04:40PM -0600, Roger Pack wrote:
> Hi all, just wondering, if I were to write a libavfilter that
> basically "called out" to avisynth and had it process stuff, would
> there be any ideological pushback, or would it possibly be accepted?
> Cheers!

If this would allow people to develop filters that users could use
without the need for approval by a 3rd party then i think thats a
good idea.

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

"Nothing to hide" only works if the folks in power share the values of
you and everyone you know entirely and always will -- Tom Scott


[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

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

[Kacper Michajlow]

On Wed, 17 Jul 2024 at 03:21, Roger Pack <rogerdpack2@gmail.com> wrote:
>
> Hi all, just wondering, if I were to write a libavfilter that
> basically "called out" to avisynth and had it process stuff, would
> there be any ideological pushback, or would it possibly be accepted?
> Cheers!

Have you considered VapourSynth instead? AviSynth days of glory are long over.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

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

[Marth64]

I think this could enable use of the highly regarded,
QTGMC deinterlacer which sounds appealing to me
(+1 for VapourSynth instead).
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

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

[Paul B Mahol]

On Thu, Jul 18, 2024 at 12:30 AM Marth64 <marth64@proxyid.net> wrote:

> I think this could enable use of the highly regarded,
> QTGMC deinterlacer which sounds appealing to me
> (+1 for VapourSynth instead).
>

LOL,
Isn't there demuxer already?
Also as filter it would be less useful.



> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
>
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

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

[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@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

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

[Stefan Oltmanns via ffmpeg-devel]

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@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

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

[Michael Niedermayer]

[-- Attachment #1.1: Type: text/plain, Size: 2208 bytes --]

On Thu, Jul 18, 2024 at 12:21:11PM +0200, Stefan Oltmanns via ffmpeg-devel wrote:
> 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.

Maybe but i think that solves the wrong problem.

Porting everything into libavfilter while few of the authors/creators/innovators
want to work or maintain the code inside libavfilter doesnt scale.

What does scale is giving the final power about each module to
the authors/creators/innovators that created that module.
This can be inside libavfilter as it is now with a system closer to the linux kernel
This can be with a plugin system where the code is outside our control
This can be in another filter API/ABI that we support

The fundamental problem i see is whoever wants to make the decissions will
have to also do the work maintaining the code or pay someone to do it.
So the cheapest and easiest is to give up the power and let the individuals
who wrote and care about the individual filters, decoders, ... maintain them
as they see fit.
Thats not going to magically make everyone maintain their filter in libavfilter
but it would attract more filters and developers. I certainly would be more
interrested in writing more filters if i _know_ i wont have to argue with
anyone about anything.

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Everything should be made as simple as possible, but not simpler.
-- Albert Einstein

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

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

[Roger Pack]

On Thu, Jul 18, 2024 at 6:16 AM Stefan Oltmanns via ffmpeg-devel
<ffmpeg-devel@ffmpeg.org> wrote:
>
> 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.

Yeah that's a good question, wonder how vsrawsource does it...
related: https://forum.videohelp.com/threads/404486-Ffmpeg-piped-as-source-to-avisynth
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".