Flanger in scriptnode
-
@Natanr are you not finding projects created in Scriptnode to be painfully CPU hungry?
I just loaded the snippet you posted and seems to use up a lot of resources (both in HISE on compiled). -
@LeeC @Christoph-Hart Already Mentioned This That Scriptnode Can Go Crazy On CPU, And Also Provided The Idea Of Exporting The Nodes As CPP Custom Modules To Reduce The CPU Usage.
If You Export The Above Example To CPP It'll Drop to Around 3/4 Percent Cpu Usage Instead Of 12/18 Percent.
But Now By Exporting My Fx Plugin, The Custom Node CPP Stop Working Or Somehow Is Inaudible.
It's Like Its On Bypass But It's Not.... -
@Natanr how do use an exported CPP custom node after recompiling HISE?
I'm trying to give this a try... -
@LeeC It's Simple And Reduces The CPU Usage,
But Somehow The Custom node Doesn't Integrate Into The Final FX Plugin Export.In Hise Back End It Works, But No Glory When You Export The Project, Kinda It Gets Bypassed Or Mutes The Module.
@Christoph-Hart Still Waiting For Answer To This, Because My Project Is Now Useless
-
@Natanr shame.
So is the idea behind exporting a CPP custom node to reduce CPU both in HISE and the final compiled plugin (in a DAW)?
Or does it just reduce the CPU in HISE? -
@LeeC I Guess It Should Work With Final Export In Your DAW, Or The Process Come Up A Little Unnecessary.
Some Of Available Nodes"Meta Nodes" Made By Same Export As CPP Trick, And They Work Just Fine With The End Product.
But The Custom Ones Won't Go Anywhere
-
@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?
-
@LeeC @Natan Did you guys get any further with this? I can't even build HISE with custom node location enabled
-
@iamlamprey no unfortunately not.
-
