UNDO - Swap Scriptnode FX w/ Dlls

[Chazrox]

After we compile with this option... can we go back to an editable Scripnode Module? Lets say I compile and swap it out and I forgot to add a parameter and want to go back inside...how do I do that?

Compiling with this replaces the scriptnode network and I'd like to go back into it somehow.

Thank You

[David Healey]

@Chazrox said in UNDO - Swap Scriptnode FX w/ Dlls:

After we compile with this option

Where are you seeing that option?

[Chazrox]

@David-Healey When selecting 'Compile networks'

[David Healey]

@Chazrox This one?

[Chazrox]

@David-Healey Yes.

[David Healey]

@Chazrox Weird, I don't see that dialog. I thought the swap option had been removed. Are you using the latest version of HISE develop?

[Chazrox]

@David-Healey Im on 4.9.2

[Chazrox]

@David-Healey

[David Healey]

@Chazrox Interesting, must have only been removed on Linux or something. To answer your original question you can still edit them, but to do so you need to add a separate scriptfx to your project and open the xml.

It's not a great workflow. In previous versions of HISE there was a little button to switch between the compiled and uncompiled version, it would be nice if that was brought back.

[Chazrox]

@David-Healey Ok. Im trying to see what the safest approach is because I tested one and couldnt figure out how to go back and im scared to compile the rest now. lol.

[ustk]

@David-Healey yep I confirm it's still there on mac last commit.
And I agree the workflow can only be better, so much time we spend going back and forth between networks and DLLs...

[Chazrox]

@ustk Im just starting to see how this is gonna go. Im trying to think of the safest workflow. Is there anything I should be aware of that one would only know from experience?

[Chazrox]

@David-Healey said in UNDO - Swap Scriptnode FX w/ Dlls:

you need to add a separate scriptfx to your project and open the xml.

Any material I can reference on how to do this?

[David Healey]

@Chazrox You already know how to do that, it's how you created the network in the first place ;)

[ustk]

@Chazrox I tried to simplify my workflow like this, and it meets @David-Healey advice:

• I create as much scriptFX as I need, and start to develop the network up to something working very well
• Then I export the DLLs, and place them in HarcodedFXs (for this I have never used that automatic tickbox thing as I always feared it...)
• I remove the scriptFXs and just create one at the top of the tree to hot load networks I want to tweak more.
• Then I just rebuild the DLLs.
• when exporting the project I just delete that latent ScriptFX

[Chazrox]

@ustk I just need to ask one question.

I have a SNEX loaded a couple containers deep in a scriptnode. There are other nodes around it that have parameters exposed to the outer container as well. Will these be repopulated when rebuilding the dll again? This is the part that im afraid of. Is it compiling the SNEX only or is it compiling the entire scriptnode and its content? Is this what 'Allow Compilation' flag is for? If I untick that option on all scriptnodeFX containers except one, will the 'Compile Networks' function ignore those networks?

That was def more than one question. lol. Sorry and Thank You!

[ustk]

@Chazrox said in UNDO - Swap Scriptnode FX w/ Dlls:

Will these be repopulated when rebuilding the dll again?

If I understand the question, yes

you can compile nodes, or nodes + networks. So you can keep a network as is (not use the dll) but load a compiled node inside it (snex, faust, c++, etc...)

'Allow Compilation' flag is just for the network itself.

in the end you can have:

• an interpreted network with interpreted nodes
• an interpreted network with compiled nodes
• an compiled network with compiled nodes

[Chazrox]

@ustk Ok I think im understanding. Thank you.