Wouldn't it be great to support OFX ?

[morsa]

I mean, seeing that AVIsynth is suffering a big overhaul for the upcoming 3.0 branch, I thought it could be a good idea to follow this route and implemte support for this API:

http://openfx.sourceforge.net/

http://openfx.sourceforge.net/Documentation/ofxProgrammingReference.html

Maybe both structures can co-exist, or even the required avisynth extebsions could be added to the official OFX API.

Who knows. I'll be waiting for you to tell me how stupid I am :)

Cheers..

[Zarxrax]

If I understand correctly what this is, I don't really think it would be feasible to implement into avisynth. This seems to be designed for high end effects applications such as After Effects, Boris, and the likes. These kinds of things rely heavily on a GUI interface, and the ability to add keyframes. In an environment such as Avisynth, I can't see something like this really being of much use.

[TheFluff]

That would mean actually implementing Avisynth3 first, which at the present rate (http://avisynth2.svn.sourceforge.net/viewvc/avisynth2/) (zero commits since last time someone built vaporware ideas on it) will not happen anytime before 2030, if ever. A Unix port f 2.6 is more likely to happen than Avisynth3 ever being released.

[Mug Funky]

personally i'd like to see some avisynth stuff ported to OFX too...

MVtools denoising for example :)

yes, self interest at work here - Scratch supports openFX as a post-process, but there's not much out there for OFX that i'd want to use. motion-compensated de-spotting would be first on my list... it takes weeks doing it manually.

[Prettz]

That would mean actually implementing Avisynth3 first, which at the present rate (http://avisynth2.svn.sourceforge.net/viewvc/avisynth2/) (zero commits since last time someone built vaporware ideas on it) will not happen anytime before 2030, if ever.
Oh dear.

I think I'm more committed than ever to join in avs 3.0 development. This situation is unacceptable. Now I just need to find the free time... :\