@HISEnberg @David-Healey Yup that works! I get it now. I've been compiling like a mad man lol
Posts
-
RE: How do I port DspNetworks ---> NewProject file ?posted in Scripting
-
RE: How do I port DspNetworks ---> NewProject file ?posted in Scripting
@David-Healey Ok. Thanks. Im still making sense of these networks tbh. I guess thats not hard to do if need be. The part im trying to avoid is creating all the parameter knobs in a new project when I want to use an effect in a new project. Am I overlooking something here?
-
How do I port DspNetworks ---> NewProject file ?posted in Scripting
I've noticed that when I compile a dspnetwork to dll, it creates these files in my project folder and im assuming this 'TestNodeA.h' is the file that is loaded into a Hardcoded Master FX module...

Can I just add these files to a new projects 'AdditionalSourceCode' folder and have my 'TestNodeA' be available in a Hardcoded Fx slot?
What is the proper way to do this?
Or do I have to compile a new dsp from within the NewProject ?
-
RE: Dsp network wont compile: // <--Changed to more relevant title :)posted in Scripting
FIXED!!!!!!


@David-Healey @HISEnberg @dannytaurus OMG! A Year of trying and it was a stale template file....I wanna cry. lol
Finally made it to this window:

and compiled dll successfully !

-
RE: Dsp network wont compile: // <--Changed to more relevant title :)posted in Scripting
Claude told me to quit already but I kept going lol. I really want to fix this. It gave me a "High Signal Report" in hopes that someone here can read it and help because its Claude is literally telling me to go to sleep lmaoo
Here's what it gave me:
HISE 4.9.2 on macOS Sequoia 15.2 / Apple Silicon
Crash in compileNetworksToDll, even with empty project + bare core.gainStack trace shows crash inside createAllNodesOnce() iterating
TemplateNodeFactory. Recurses 4 levels deep into nested containers,
then NodeContainer::nodeAddedOrRemoved calls getNodeForValueTree
which returns nullptr. Register x21 = 0x0 at crash site, attempting
ldr from null in getNodeForValueTree+108.The bug is not in user projects — createAllNodesOnce instantiates
HISE's built-in templates and one references a child node not in
the factory. Reproduces 100% with completely empty project.Built ReleaseWithFaust from develop branch commit 6446c4ab6 with
HISE_INCLUDE_FAUST=1, HISE_INCLUDE_FAUST_JIT=1, HISE_FAUST_USE_LLVM_JIT=1,
USE_BACKEND=1, HISE_INCLUDE_SNEX=1.Need to know: which preprocessor flag combination makes
TemplateNodeFactory register a node whose child template is missing
from the build? -
RE: Dsp network wont compile: // <--Changed to more relevant title :)posted in Scripting
@dannytaurus I havent tried that yet! Im not sure how to use it honestly. Im gonna watch a video and see whats up. Thanks!
-
RE: Dsp network wont compile: // <--Changed to more relevant title :)posted in Scripting
Is this the expected folder structure for having just created a new dsp network file? Is there anything missing here?

-
RE: Dsp network wont compile: // <--Changed to more relevant title :)posted in Scripting
Claude has completely given up on me. lol I've tried everything a few times over. Claude keeps telling me to wait for Christoph to save me
. -
RE: Dsp network wont compile: // <--Changed to more relevant title :)posted in Scripting
I just tried a to fix with Claude and this is its response:

Does that mean im screwed? lol
The new HISE build is working great aside from not being able to compile networks still...Something is really screwed up over here.
-
RE: Dsp network wont compile: // <--Changed to more relevant title :)posted in Scripting
Is there any difference in creating a node with these two options?

Im trying both to see what works but still same result.
-
RE: Dsp network wont compile: // <--Changed to more relevant title :)posted in Scripting
@HISEnberg I just found Davids updated video regarding sdk's. Im going to continue trying. Thank you.
***UPDATE:
My test project will compile and export as an FX plugin but still its just not compiling my networks to dll.
-
RE: Dsp network wont compile: // <--Changed to more relevant title :)posted in Scripting
@David-Healey In my new hise build, I cant find the setup wizard that lets me extract the sdk's and I noticed in settings "Setup Wizard = 1" . Does that mean its already setup by default?
-
RE: Dsp network wont compile: // <--Changed to more relevant title :)posted in Scripting
@HISEnberg Just letting you know, I tried changing the name to my folder and still get the error/crash.
-
RE: Dsp network wont compile: // <--Changed to more relevant title :)posted in Scripting
update from Claude reading latest crash report:

I dont think its a HISE bug but maybe something here is telling of something else?
-
RE: Dsp network wont compile: // <--Changed to more relevant title :)posted in Scripting
Do I need to set this?

-
RE: Dsp network wont compile: // <--Changed to more relevant title :)posted in Scripting
@HISEnberg No worries I really appreciate it. Im down to try that. If I just change the name of the folder will that mess up any of my projects in it? Is this also the case for naming conventions in general? Project names and node names?
-
RE: Dsp network wont compile: // <--Changed to more relevant title :)posted in Scripting
I really appreciate all the help on this from you guys because Im out of my league at this point.
-
RE: Dsp network wont compile: // <--Changed to more relevant title :)posted in Scripting
@HISEnberg just tried that. Still this error.

