Abeleton shows An error about a plugin I Compiled with the Latest Commit

[d.healey]

@ILIAM Are you compiling the network before compiling the plugin and inserting it as a hardcoded effect, or just compiling the plugin?

[ILIAM]

@d-healey said in Abeleton shows An error about a plugin I Compiled with the Latest Commit:

13 minutes ago

@ILIAM Are you compiling the network before compiling the pl

Just compiling the plugin, the network above has only 3 nodes, 1 timer, 1 MinMax, and 1 Bipolar.
I 100/100% sure the error is because of the Timer node ( set to Random )

[d.healey]

@ILIAM I'm not getting a crash here with your test snippet when loaded into an empty project and compiled as a VST3. I'm able to load it in both Ardour and Carla.

[ILIAM]

@d-healey Strange, Which Commit?
And also what VS? for Windows?

[d.healey]

@ILIAM Latest commit from 2 days ago. I haven't tested on Windows, I'm using Linux.

[ILIAM]

@d-healey Compiling A VST3 Right now

[ILIAM]

@d-healey
The error is still there—no way to get rid of it.

I created a new project, only imported the UI (no callbacks), and rebuilt the networks from scratch—same error.
I even tried using previous commits, but no luck.

Could this possibly be coming from Projucer or the VS version?

[ILIAM]

@d-healey Also, have there been any recent changes to the HISE build process—like new flags or extra definitions—needed for using Global Modulators?

[d.healey]

@ILIAM said in Abeleton shows An error about a plugin I Compiled with the Latest Commit:

Could this possibly be coming from Projucer or the VS version?

Only if you've customised something.

@ILIAM said in Abeleton shows An error about a plugin I Compiled with the Latest Commit:

Also, have there been any recent changes to the HISE build process—like new flags or extra definitions—needed for using Global Modulators?

I didn't have to do anything special when I tested.

Are you able to test on another computer or with a virtual machine?

[ILIAM]

@d-healey Is there a way to completely reset all settings and make Projucer 100% clean?
I suspect something might be hidden in Projucer—are there any folders I should delete to ensure a truly clean build?

[ILIAM]

@d-healey For FX plugins, do we need to add or remove anything new in the build process?

[d.healey]

@ILIAM said in Abeleton shows An error about a plugin I Compiled with the Latest Commit:

@d-healey Is there a way to completely reset all settings and make Projucer 100% clean?
I suspect something might be hidden in Projucer—are there any folders I should delete to ensure a truly clean build?

There will be an app data folder on your system for Projucer, you can delete that.

@ILIAM said in Abeleton shows An error about a plugin I Compiled with the Latest Commit:

@d-healey For FX plugins, do we need to add or remove anything new in the build process?

Nope