Scriptnode is fun!

[UrsBollhalder]

I had a serious HISE development relapse yesterday that got completely out of hand... I ended up neck-deep in scriptnode, mangling field recordings, modulating delay times with bleeding eyeballs around midnight!

https://drive.google.com/file/d/1mmzSlaRIV0AQCnrd4kKMybXCe8CpRQVZ/view?usp=sharing

This is the HISE-only version:

https://drive.google.com/file/d/1zT1-2JnBmhpbd5lKz8KF-RWPSBew6Igv/view?usp=sharing

Thanks to @Christoph-Hart for providing us with such an amazing tool!

[Matt_SF]

Agreeing with @UrsBollhalder, I'm so happy @Christoph-Hart implemented this system into HISE. I so love the scriptnode system ! Keep upgrading it Christoph, thank you very much

[DanH]

@matt_sf Has anyone managed to compile a script fx succesfully yet?!

[d.healey]

@danh If you mean scriptnode network in the Workbench, then yes.

[Matt_SF]

@danh on windows yes (when the workbench is in a good mood) / macOs nope.

@d-healey linux only or other platforms ?

[d.healey]

@matt_sf Only tested on GNU/Linux

[DanH]

@matt_sf hmm, maybe I'll try on windows then, hopefully that is transferable to osx if successful

[Dan Korneff]

I have finally successfully exported! It's a pretty fussy system.... I've had to rebuild chains many times because they'd randomly stop compiling C++. It also might be picky about file names? It also doesn't like when you start DSP in HISE and then continue building in Workbench. You really have to do everything in the workbench, then move it to HISE

[UrsBollhalder]

@dustbro Oh oh... That doesn't sound good to my ears... I already feel some painful and time-consuming rewrites coming up... I hope somebody makes a video soon... going through the compilation process... I can patch stuff together alright, but I am fairly lost when it. comes to compiling this thing.

[Dan Korneff]

@ursbollhalder I'll post something soon for ya

[UrsBollhalder]

@dustbro That'd be great! Thx!

[DanH]

@dustbro How do you move it to HISE after the workbench? As in, when you create a Script FX in HISE, how do you load the compiled chain into it?

[Dan Korneff]

@danh First, I create a project in HISE, then close it. Open workbench and load your project folder. Create new dsp. Then when you add a scriptFX in HISE, your new dsp network will be available.

[DabDab]

@ursbollhalder Nice man.. Where is the GUI/Plugins interface. I am curious to see it. Nice work dude

[UrsBollhalder]

@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.