How to turn an Airwindows effect into a Scriptnode

[Morphoice]

@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...

[griffinboy]

@Morphoice

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

[Morphoice]

@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

[Christoph Hart]

@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.

[Consint]

@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.

[Morphoice]

@Christoph-Hart sent

[JulesV]

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?

AWAmp.zip

[DanH]

@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

[JulesV]

@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.

[Christoph Hart]

@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.

[JulesV]

@Christoph-Hart Thank you for the suggestion, I will try to edit them.