How to turn an Airwindows effect into a Scriptnode
-
@Christoph-Hart isnt vst2 support officially dropped since cubase13?
-
This post is deleted! -
@Morphoice Yeah, VST2 as a plugin API is dead in the water but this just redirects the VST2 API calls to scriptnode so it's not actually using the VST2 SDK - it basically mimics the API so that you can reuse code that relies on the VST2 SDK.
how do I find it?
It should show up in the
project.xxxnode list. Have you created the C++ template first so that it registers the node file properly? -
@Christoph-Hart got it as a hardcodedfx selection, works like a charm. however turning the value knobs introduces a lot of clicks and pops, very loudly... is there a way to smooth that?
-
@Morphoice unfortunately many airwindows nodes come with not real smoothing. You can try add a smoothed_parameter node.
-
Man you guys got the cheat codes!
Can somebody do a walkthru of this process? -
@Consint ever tried compiling on windows? It all works fine on mac but when I try to make a pc version I get tons of compiler errors upon compiling the DSP network. I have no idea what that means
!C:\HISE\HeatFilter\DspNetworks\Binaries\Source\DspNetwork.h(76,49): error C3203: 'Disintegrate': unspecialized class template can't be used as a template argument for template parameter 'Processors', expected a real type [C:\HISE\HeatFilter\DspNetworks\Binaries\Builds\VisualStudio2022\HeatFilter_DynamicLibrary.vcxproj] -
This post is deleted! -
@Morphoice I have only compiled it on Linux so far.
-
@Consint MSVC seems to be more strict about something in the Airwindows.h which CLANG on mac doesnt bother about.... I know nothing about template resolution so iI'm homping someone familiar with C++ can help...
-
Have you tried asking chat gpt?
If the library is small you can upload the c++ files and the error message and ask gpt to try and find what's wrong.It might fail to find the correct answer. But I find that 70% of issues it can solve. However there is a chance it will give you a bogus answer
-
@griffinboy yeah but it only gives me unhelpful information I already know, the fact that MSVC is more strict about some template resolution. I don't know what that means and how to fix that, neither does GPT in a way that compiles. it just gives me code that produces new problems
-
@Morphoice forget about all the noise - the issue is with your disintegrate network - the compiler thinks it‘s polyphonic but it isn‘t, hence it is missing the voice template parameter that causes the compiler error.
Maybe it‘s best if you send me the disintegrate network as well as the one that is embedding it, might be a false positive with the code generator.
-
@Morphoice I tried it with my plugin and was able to compile it in my Windows 10 VM with Visual Studio 2022 without any problems.
-
@Christoph-Hart sent
-
Is there anyone who can compile more than one AirWindows plugins as Third Party?
I am getting the error
use of undeclared identifier. When I compile these nodes one by one, there is no problem and they work.I am attaching the sample project, when you do Compile DSP Networks as dll it will give this error.
What is my mistake here, or is this a bug?
-
@JulesV I'm not compiling any airwindows stuff but I'm getting constant use of undeclared identifier errors. They all follow on from Use of class template 'project::overdrive' requires template arguments errors.
Could be unrelated
DHPlugins / DC Breaks | Artist / Producer / DJ / Developer
https://dhplugins.com/ | https://dcbreaks.com/
London, UK -
@DanH I noticed something interesting, while almost all AW plugins can be compiled separately, some AW plugins cannot be compiled as multiple dlls in the same project.
For example, Tube2, Huge and Mojo plugins can be used together in a project.
But LeadAmp and FireAmp cannot be used together in a project.
But all of these plugins can be compiled individually.
So it is related to the AW plugin combinations.
-
@JulesV the problem is that each plugin file is expected to be used once per project and there are a few things that you need to modify in order to make this work - it's all very basic C++ stuff.
Look out for the functions in each src/*.cpp file that create the plugin instances or the plugin editors and try to remove them as they aren't needed anyways.
-
@Christoph-Hart Thank you for the suggestion, I will try to edit them.
