@Christoph-Hart said in Airwindows again:
I actually wrote a VST2Node wrapper at one point where you could just drop vanilla VST2 codes in the third party folder (I've reverse-engineered the VST2 API calls into scriptnode callbacks) and it worked with most of the AirWindows effects, but then I lost this file because it was deleted when I exported the DLL again.
Oh, bummer. I would have loved to have this one.
As for why do I need Airwindows and believe they're useful, well... once I manage to implement them myself, you will know. ;)