Each heavyweight function (loading presets, samples, etc) gracefully fades out the audio, suspends the processing and then resumes audio processing. This is a core engine behaviour and you can't do anything about it. Changing this will create audio glitches, incontinuities and crashes.
If they are named well all of the steps except the looping can be done in about 30 seconds using the token parser.
So you're basically paying someone to loop your samples - I would suggest looking into auto loopers like LoopAuditioneer first - because anyone taking the gig is going to be doing that ;)
@ustk I'm indeed still on the latest stable release...
I read it as 4.10 instead of 4.1 so I was convinced I was on the latest version.
I'll compile from the latest develop branch instead and try again.
So what state is the mod matrix actually in?
Do some things work but others don't?
I'd just like to know what to look out for, if the documentation isn't super up to date.
So i got a notarized .pkg working of the .hr files. still need to test more but i got them into the plugin's own per-user app-data folder. Then when the plug-in opens and installs the samples it can also auto-delete the .hr files right after extracting. And no gatekeeper quarantine from macos. Ill have to do the same on pc and create .exe for the .hr files to match. but perhaps this will be best. less confusing for people i imagine?