GLOBAL CABLE not working in compiled vst
-
Windows 10, Hise develop branch, compiled yesterday
I made a multiband compressor using ScriptNode.
Then i compiled it into Hardcoded Master Fx.
Connected the ui parameters.
Everything works fine, except the Input Level and Gain Reduction meters which are connected using global_cable. They dont work in compiled vst. (but work in hise)Is there some step im missing?
https://forum.hise.audio/topic/8636/ Here is a similar problem, but it wasnt really solved.
When i export vst with uncompiled ScriptNode it errors in daw. (im not sure if thats ok)
I created a simpler project from scratch to test this, but problem remains.
project files: https://drive.google.com/file/d/1yobcCpQLM9ViJJ4I53izSLr5Hc7-OGUy
I even tried compiling "Scriptnode Visualisation 101" snippet, problem remains.
-
@glek I dont think you can use Global Cables (or Global send/receive nodes) inside a compiled ScriptNode ...
-
@Lindon but then why does it work inside hise...
-
@glek I would compile a scriptnode dll in a static position of the parameter range you need. And then in the code editor, I would affect them using the gain reduction of the dynamics module.
-
@glek did you try exporting your plugin with the scriptnode inside, rather than compiling the node into a hardcoded FX?
Works like a charm on my end. I export my nodes without doing the compilation manually and loading it into the hardcodedmasterFX container.
-
@Straticah When i export vst with uncompiled ScriptNode it errors in daw.
But it anyway wont work because it doesnt when i compile "Scriptnode Visualisation 101" snippet
-
@glek yeah the second one did not work on my end either.
but mapping the compressor to a knob that moves did work on my end.
Make sure your scriptnode is set to allow compilation and dont save it before compiling (and delete old ones from HISE Projects\project name\DspNetworks\Networks
-
@Straticah said in GLOBAL CABLE not working in compiled vst:
dont save it before compiling
I don't understand this
if you don't save the scriptnode before compiling it will compile the wrong thing
No?
-
@glek its saved in the project, you just have to save the project as an xml file.
You only have to compile 3rd party dsp nodes inside of scriptnode.
here is an example, i can export this as a vst, no hardcode or dll compiling required
-
@Straticah ok, now i got it working, thank you.
but thats weird anyway
-
@glek no problem, i think its more intuitive than compiling stuff :)
-
@Straticah said in GLOBAL CABLE not working in compiled vst:
You only have to compile 3rd party dsp nodes inside of scriptnode.
Sorry I didn't understand this part of the workflow. I have a scriptnode with a FAUST node connected to two global cables, I can't compile the FX Script otherwise I don't have the global cables in my plugin but I have to compile the node because otherwise I can't use FAUST? So I'm stuck in this limbo?
-
@Mighty23 i dont use FAUST that often but you could compile the faust node - then load it tinto the scriptnoded that has the global cable.
I assume if you export a FAUST project without compiking the node it gives an error?
-
@Straticah said in GLOBAL CABLE not working in compiled vst:
I assume if you export a FAUST project without compiking the node it gives an error?
Usually, I don't get errors if I just compile a Faust node instead of whole ScriptFX. But if the Faust node is linked to other nodes in ScriptFX, I would lose the use of those nodes in the Hardcoded master FX.
Example:
-
@Mighty23 global cables should work in a compiled plugin, but it‘s rarely used so it might be broken. I‘ll check it real quick.
-
Seconded. I didn't post about it bc I assumed I was doing it wrong, but it worked for me uncompiled (previous version of hise) and not compiled.
-
Ah yes, it was in fact not working in the compiled plugin - I somehow missed to call the connection call after compiling the plugin. Should be fixed now.
