filter list in avisyth 2.5?

[jonas]

Hi,

I've only read part of all the 2.5 development threads, but if I remeber correctly there is know information about the filter saved in the plugins, so heres's my question:

Is there an internal function that can give a list of all functions loaded with filtername,possible inputs, info about filter and maybe even the filtertype [e.g. source, blends, sourceconvertion, effects]?

This would be really nice if one wanted to write a GUI (adobe premier like) that can do evereything avisynth can (and more).

I have quite a good idea of how I would want it to look, but time [and skill] is a little short for the next weeks to start, but it would be nice to know if its possible.

jonas

[sh0dan]

I just saw yesterday (after uploading the beta) that Belgabor had put up a way to do this in the SourceForge page. I'll have a look at it, and hopefully implement it ASAP!

[Richard Berg]

Belgabor's idea looks like a good stopgap. For an idea of what may be implemented further down the line, check here (http://www.avisynth.org/forum/viewtopic.php?t=6).

[Belgabor]

The thread you gave Richard pretty much sums up what we discussed earlier (about when 2.5 was started). What led me to my patch is the reasoning 'why change the interface when we can use features already present?'. I think global variables are a good way, not necessarily the way I did it. For example we could alternatively use "$PluginCount$" and things like "$Plugin!1!Name$", "$Plugin!1!Param$", "Plugin!1!Info$", ...

(I have to admit the way I did it was pretty selfish, because that way I simply have to pass the exact same string to the scintilla component to get syntax coloring ;))

Edit: Advantage over a COM object is (imo) that you can easily support diffrent avisynth dlls.

Cheers
Belgabor

[jonas]

thanks for the info.
This looks very promissing. It's good to know that this will be implementet. Hope I'll notice as soon as its done

jonas