Modulation Matrix FX plugin crashes in DAW
-
Did you have any success using the new Modulation Matrix system on the fx plugins?
I loaded it to the Hardcoded module. It works in Hise but exported fx plugin crashes. Maybe the Global Modulator causes this?
-
No crashes in my plugin no. If you're getting a crash, the initial idea I'd suggest is to check for deferenced or null pointers. Are you trying to access any variables, functions, or namespaces that exist when you're in HISE standalone, that might not exist in the compiled plugin??
Using the Builder API can be a cause of plugin crashes too.
-
@Orvillain Are you using the current commit?
Is there a tickbox or something else I need to set in the project settings?I used this preprocessor definitions:
HISE_NUM_SCRIPTNODE_FX_MODS=8 HISE_NUM_POLYPHONIC_SCRIPTNODE_FX_MODS=0 HISE_NUM_SCRIPTNODE_SYNTH_MODS=0 NUM_HARDCODED_FX_MODS=8 NUM_HARDCODED_POLY_FX_MODS=0 NUM_HARDCODED_SYNTH_MODS=0 -
My project is setup for this:
HISE_NUM_SCRIPTNODE_FX_MODS=32 HISE_NUM_POLYPHONIC_SCRIPTNODE_FX_MODS=32 NUM_HARDCODED_FX_MODS=32 NUM_HARDCODED_POLY_FX_MODS=32 ENABLE_ALL_PEAK_METERS=1 JUCE_LOG_ASSERTIONS=1If you're going to be using hardcoded modulators, then you're definitely going to want to activate some of the mods. Saying that, I don't think having them set to zero would cause a crash. Would just cause modulation to not work.
If you're using a hardcoded module, are you initialising the SlotFX properly when your plugin loads? I'm not 100% certain, but if you're not ensuring the slot actually has the effect and then you're trying to map modulation to it at any point, that could cause a null pointer and a crash.