Matrix modulation connection is broken in exported plugin
-
@ustk said in Matrix modulation connection is broken in exported plugin:
@Christoph-Hart Are you exporting an FX or INSTRUMENT?
I have the same issue on the exported fx plugin and reported a while ago: https://forum.hise.audio/topic/13977/modulation-matrix-fx-plugin-crashes-in-daw?_=1777946560667
-
@Christoph-Hart Another strange behaviour, I am currently trying with AU export, which is working aside of the current problem we are trying to solve. I guess it's related to MacOS (me) vs Windows (you?)
But that same snippet exported as VST3, and ableton live says:

-
@ustk Could all your problems be related to this juce 8 thing?
-
@David-Healey Perhaps... But I am JUCE 6... Or schizophrenic...


-
@ustk Why is xcode referencing 8.0.3
-
@David-Healey To this day I have no answer for this...
-
@ustk Definitely only got one copy of the source?
-
@David-Healey yes, always had (custom branches but one folder/repo)
Also I just re-aligned develop origin onto upstream to be sure (I had some merge commits because of past manual fork syncing) but no changes regarding the issue and the VST3 crash. -
@David-Healey said in Matrix modulation connection is broken in exported plugin:
@ustk Why is xcode referencing 8.0.3
After analysing everything, AI confirmed Hise is built and running on Juce 6, and it says:
The assertion you hit is most likely thrown by the JUCE-8 plugin's code (in the v8.0.3 message thread), not by HISE's JUCE 6.
Since I am debugging using pluginval which is built on Juce8, that's 99% the origin of XCode reporting Juce8 message thread
-
@ustk yup that's the plugin host telling his version number.
I tried to load your snippet, but the hardcoded FX is empty (of course, I don't have compiled your network) - is it just the
script_fxnetwork in the Script FX that I need to compile?This looks remarkably equivalent to my snippet though (which worked).
-
@Christoph-Hart Yes it an embedded network, very simple, in the scriptFX
What about your snippet that I can test on my side?
And are you on windows or mac? I wonder if the difference can lie there... Especially since I have a straight crash with VST3 while AU, at least, can load