Quote:
Originally Posted by MysteryX
Here's an idea for a new feature. Someone wrote AvsFilterNet to allow writing plugins in .NET. One issue is that the .NET plugin must be loaded by AvsFilterNet which is not practical for the user. A .NET library can't be loaded directly by AviSynth.
Could AviSynth+ natively provide an interface for .NET plugins?
|
First of all, .NET really wouldn't simplify stuff too much. Plugins rarely contain anything but the most trivial code and C++ is perfectly fine for that these days.
Second, I see no reason why something like AvsFilterNet couldn't just autoload other plugins on its own. What's the point of moving something like this into the core?