@DabDab try deleting the DLL in your project and try again.

@d-healey nope sounds like an easy addition (adding a new mode to the drop down menu)

Now restart hise, and you will be able to use the Node:

Yes. it should read now:

Now press OK and you will be able to use the node

It's the small details :)

@griffinboy HISE will use the NUM_POLYPHONIC_VOICES constant to create a fix amount of voices (default is 256 I think) and then use the default HISE voice management system to allocate / start / steal the voices.

If you set the voice count to be less than the maximum voices using the scripting API, it will just ignore the voices that are allocated above this amount.

@d-healey Alright, this is implemented now.

• sustain pedals are now correctly supported - it 100% mimics the behaviour of the voice stopping logic now
• the sample will never jump back in time to the release offset - if the sample has already played the release trail, it just continues playing at the current position.
• you have a Sampler.setAllowReleaseStart() function that accepts an event ID for per event setting (or -1 for globally enabling / disabling the feature).

Let me know if you find other quirks. The goal is to get this usable in real projects, so don't be shy :)

@d-healey nope this are all good suggestions - I‘ll add a script API method to disable release triggers per voice using the event ID - this should be enough for most of your feature requests, the other things are minor issues that I can fix easily.

@Fortune oopsies, the build script didn't handle spaces well (and it was particularly annoying to get the command line arguments properly escaped) when using the internal child process for the compiler.

Anyways, it's fixed now (and the weird popup shouldn't appear on macOS). Can you try again?

Are networks marked as Allow compilation now automatically compiled on export,

Nope, but almost. On compilation the ScriptFX modules are replaced with their hardcoded counterpart so we're 80% there. What's missing is that if there is no DLL present at all (or the DLL was never exported manually once before), it won't create the C++ files for the networks that will be included in the plugin export.

I've added this step now too in the compilation process although I'm hitting a few issues with hardcoded FX not being initialised correctly if there is no DLL present.

I'll sort this out and then commit it, but this will make it very convenient - you actually do not have to bother at all about compiling scriptnode networks anymore and it will be all taken care of at plugin export - unless you want to compile the DLLs before to see that state during development.

@Fortune windows or macOS?

@d-healey Are you reading past the array? what if buf[i].length - j < 5000?

I will add a tool that allows you to automatically convert a script FX into a hardcoded FX module

Alright that's also implemented:

This operation is also performed whenever you export your project through the new compilation dialog so it's guaranteed to never use a ScriptFX with a compiled network in a compiled plugin!

I figured out it's due to nested networks being removed; or at least refusing to load as nodes.

There's no way to add nested networks anymore and the entire Project tab is missing from the Node Browser.

Alright, that was only happening if you don't have a compiled DLL present - I've fixed that now to show dummy nodes that you can click on in order to compile the DLL - this should also work without restarting HISE now.

Feel free to check it out, I've also spent a few hours changing the UX of the entire compile process to be within the HISE window now so it won't spawn a console and block the UI.

Spaces in the middle should be supported, but checking for spaces at the beginning and end didn't cross my mind. I'll add this as sanity check...

@aaronventure haha I would love to be as funny as this, but in this case my old keyboard with the defect d key pranked me one last time... but damn that's a solid joke.

@JulesV I pushed the preliminary work I had on my mobile rig but it‘s not usable as it is. I‘ll need to do a few more performance tests and cleanup.

@aaronventure yeah I might have been a bit too ambitious with the cleanup.

What is gone now is the ability to freeze / unfreeze nodes as well as to run the compiled root network from a script FX - this was a complete mess on the implementation side and probably caused the script FX to crash in a compiled plugin. I will add a tool that allows you to automatically convert a script FX into a hardcoded FX module as this is a major gap in the development UX right now but this makes everything more predictable and stable in the long run.

I also removed the ability to load uncompiled networks as a node (so nesting of uncompiled networks is not possible anymore). However I probably need to roll back this change as it was too intrusive.

@tomekslesicki multimics are grouped into a single voice so this shouldn't affect the functionality.

So basically it breaks with 8 RR groups?

@tomekslesicki hmm, works here, I did exactly that and it correctly plays always the two notes. Have you checked the exact steps to reproduce on your end? Maybe it breaks with more groups etc...

@aaronventure said in Close Welcome Screen with ESC:

restarting HISE after compiling networks

well, I might have news for you there soon...

@aaronventure what do you want to achieve with the macro automation? I'd rather expand the command line functionality for automatable tasks...