Flanger in scriptnode
-
@Natanr you're right.
I've just tried using a plugin that makes use of a custom (exported) node and it is effectively bypassed when used in a DAW.
I tried using your Flanger snippet as well as Transient Designer project I've been working on and got the same result -
@Natanr ok so I've just realised that although I recompiled HISE and enabled 'Custom Node Location' it wasn't enabled in the 'AutogeneratedProject.jucer' within the 'Binaries' folder of the project. Not to muddy the waters but, could this be related?
-
Attempting this results in a failed build.
"scriptnode::project::Factory::getInstance(scriptnode::DspNetwork*)", referenced from: scriptnode::DspNetwork::DspNetwork(hise::ProcessorWithScriptingContent*, juce::ValueTree, bool) in TransShaper Debug.a(include_hi_scripting_03.o) ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation)
-
In the waiting for a fix, it might work if you unfreeze the custom node before exporting, I haven't tested myself thoughβ¦
-
@ustk Really??? No Way
I'll Try This Right Now -
-
-
@Natanr @ustk yes CPU usage ramps right back up when unfreezing and then exporting.
So to summarise, there's currently no way to use custom node configurations without the high CPU usage (Both in HISE and when exported to DAWs).
The 'Export Node to Location' approach ultimately ends up with said nodes effectively being bypassed when used as AUs/VSTs etc -
@LeeC And @Christoph-Hart Brings No Lights Here
-
@LeeC @Natanr What about standalone export?
-
@ustk I Tried The Instrument, With No Luck
Since It's A Fx Plugin, Standalone Is Somehow Didn't Come To My Attention...Sir, You Think It's A Bug Or A Integration Issue?
-
-
@iamlamprey no unfortunately not.
-
-
@ustk So It Doesn't Work, Right?
-
@Natan Exporting nodes to CPP is currently not working, but Christoph is working on it as part of a whole giant HISE 3.0