Flanger in scriptnode
-
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