Scriptnode is fun!

[A Former User]

@dabdab Thx… with this one I am behind with the ui! Hopefully 2022 will see some releases from me… It’s a long road!
The video was for an Instagram post I made yesterday… Doesn’t have a whole lot to do with the instrument ui and so on… but was fun!

[DabDab]

@ursbollhalder Cheers man. See you soon on the market :)

[Christoph Hart]

Alright, I'm currently trying to improve the user friendliness of the export process to make it even more fun. Let's be honest, HISE will never win the "Most easiest app to use"-award, but this is ridiculous even for my low standards :)

So this is what I've done so far:

1. You don't need the snex_workbench anymore to compile the networks - there's a item in the Export menu in HISE that opens the same dialogue. It requires you to have at least one DSP network in your signal chain when exporting, but there's an error message that will tell you this.
2. There's a command-line option to do that process, so you can call HISE.exe compile_networks -c:Debug and it should do everything for you.
3. It will show which nodes are about to be compiled in the export dialog. After the compilation, you can query the state of the loaded DLL with Tools -> Show DSP Network DLL Info.
4. You should not rely on the workbench like @dustbro suggested anymore - if you choose "Create a network file" in the scriptnode welcome screen, it should create a file-based network that you can export as DLL (just remember to save the network using the save button before hitting the DLL export).
5. I am currently writing unit tests for scriptnode in this repository. This includes also a few test nodes that are compiled and tested against the interpreted node. All the nodes here are supposed to be compileable on macOS and Windows (at least with my setup). If you encounter a DspNetwork that throws a compilation error (or crashes on loading), please post it as issue in this repo, then I will create a test file from it and make sure that it works.

[RCJacH]

I just compiled the newest version of HiSE from the develop branch. However I'm not able to compile to vsti. So I tried creating a new preset and added a sampler with empty samplemap to the master chain and hit export as instrument plugin. After a while, it says

g:\coding\hise\hi_scripting\scripting\hardcoded_modules\arpeggiator.h(47): fatal error C1003: error count exceeds 10
0; stopping compilation (compiling source file ....\JuceLibraryCode\include_hi_scripting_04.cpp)

and fails compilation.

[d.healey]

@rcjach A bit off topic...

How many copies of the HISE source code do you have?

[RCJacH]

@d-healey I removed all but the develop branch before building HiSE.

[d.healey]

@rcjach There might be a bug in the latest version, try rolling back a few commits.

[crd]

@christoph-hart said in Scriptnode is fun!:

5. I am currently writing unit tests for scriptnode in this repository. This includes also a few test nodes that are compiled and tested against the interpreted node. All the nodes here are supposed to be compileable on macOS and Windows (at least with my setup). If you encounter a DspNetwork that throws a compilation error (or crashes on loading), please post it as issue in this repo, then I will create a test file from it and make sure that it works.

I am running in to some issues compiling some Scriptnode patches. Would someone walk me through how to properly post these in the repo Christoph created?

[Christoph Hart]

@crd export the network that doesn't compile as HISE snippet and open an issue here:

Issues · christophhart/scriptnode_testsuite

The testsuite for scriptnode using the SNEX workbench - Issues · christophhart/scriptnode_testsuite

GitHub (github.com)

Perhaps also post the compile error message (in a code block) so that I know what demons to fight...

[crd]

Got it. Thanks

[RCJacH]

@christoph-hart I updated to the latest commit in develop branch and compilation is successful again.

[Dan Korneff]

@christoph-hart doesn't look like Compile DSP networks in latest commit is doing anything. Dll info shows:

{"File": "", "Loaded": false}

[Christoph Hart]

@dustbro Yes, that's one of the glitches of the JUCE migration - the OK button of ALL dialog windows stopped working. It's fixed now...

[Dan Korneff]

@christoph-hart Thank you for the quick fix!

[Lillie]

Thank you ! Great job :)