@David-Healey Im on vs 2026 by the way

Thank you guys!

@David-Healey yeah that would be a problem. But A hise project folder with hise in the name will not be deleted, that would be nuts. It looks for all HISE Standalone.jucer files and walks the folder hierarchy up to the HISE root.

I know Oli Larking the dev of iPlug. He's worked very hard on this over the years. Awesome dood. He is day job is at Ableton and he's mostly working on it by himself....

P

@David-Healey said in Changing Sample Start Mod:

@ulrik said in Changing Sample Start Mod:

But the sample map xml files are also changed when saving the project, if I open the maps in a text editor I can see the changes are made

Aha I misunderstood. So it's autosaving them, hmm that's unexpected.

Yes indeed it is.

@ulrik said in Changing Sample Start Mod:

So if I understand right, it doesn't matter as long as it's referring to the right ch1

Needs testing in a compiled plugin.

Ok I have tested it in a stand alone, and that works fine

@ulrik said in Changing Sample Start Mod:

The user can change all samples in range between 0 - 5000 smpl, that is already fixed

In that case I would just use sample start mod and a constant modulator or set the start offset in the note on callback, rather than changing the sample properties at run time.

Yes I have been thinking in that direction as well, but I also have a script that already make use of the SampleStartMod, so that will add up to the Sample Start setting I guess.
But I think it would be the best way to use Sample Start Mod for this purpose as well

Thank you David for the feedback, it's much appreciated!

@dannytaurus I like it, looks smooth

@ustk
@Orvillain
I noticed that Christoph has joined the conversation, so I'll hold back now to avoid causing any confusion. :-)

@Christoph-Hart said in Shoutout: Azure Trusted Signing:

I used a self-signed certificate to sign the AAX plugin

I've just setup Azure signing for my upcoming packaging course and have been following various guides online - all of which seem to be slightly wrong or confusing.

For AAX signing if you're following the Koala DSP guide it has a whole setup thing about using a python and batch script. Ignore that, go to the PACE documentation and look-up the --explicitsigningoptions flag, it includes an example. Just copy that and you're good to go.

It's important to put quotes around all file paths and if you have nested file paths you'll need to escape the quotes on the inner paths (\"mypath\").

@David-Healey bummer...

I opened a thread regarding the problem I mentioned above:

https://forum.hise.audio/topic/14273/clock-synced-arpeggiator-daw-sync-makes-first-tick-off-grid

It contains videos and snippets; I don't know if anyone has managed to fix this yet.

@Ben-Catman more than one button with the same param name? Check using Export>validate plugin parameters

Yes, on Windows ASIO is not multiclient. On MacOS, CoreAudio is multiclient. Thought this was common knowledge??

Again in reference to my earlier RME comment, what they do is handle everything in TotalMix for you. You just tell it which outputs you want to feed through to the WDM driver. I like this solution because it is a permanent wiring. Sorry, I know this doesn't help if you don't have an RME card!

@Lindon said in Custom browser - custom preset file format???:

@Orvillain this all seems massively complicated for preset saving and loading, what does the existing prest management and a custom tag based browser on the front of it not give you?

Ultimately it isn't just about preset saving and loading.

They want full customization of the preset data model. They want each preset to have an associated image. They want to be able to import and export presets along with sample content at the same time. Which means I need full path control over the samples when saving. They want rich meta-data based browsing and on the fly searching. When saving a preset, they want to be able to specify various tags and descriptors, and it makes sense to store that stuff directly into the xml. There's probably more they want, but off the top of my head that's all I remember.

Everything they're asking for seems to involve deeper control over the load and save mechanics. But it's actually not that complicated. I'm essentially overriding the HISE automatic system, with a manual system. I'm capturing nearly everything that HISE captures automatically in a single call to UserPresetHandler.createObjectForSaveInPresetComponents() - everything else is custom.

Unless I'm missing something, there's a lot that the stock preset management system doesn't give you.

After spending a fair amount of time trying things out and reading the API, I'm fairly sure I have a decent grasp of how it all works now. There are also pre and post callbacks for loading and there's a post callback for saving too, which I'm going to need to tell the system to refresh the list of presets; or to update the external database, which is probably going to be required too.

Tried this — native HISE on Win ARM64 is a pain. VS ARM toolchain works if you patch JUCE and tweak CMake, but VST3s crash unless you strip x64-only intrinsics. x64 emulation on Win11 ARM is way more stable. Linux ARM / Pi is basically DIY hell for plugins, engine only.

@DanSound Guess I need to create a sequencer instead of using arpeggiator 🤖

@Phelan-Kane Hi Meta Function,

I’m encountering a compatibility issue between Max 9 / RNBO 1.4.2 and HISE 4.1 (Developer Branch).

Current Status:

RNBO 1.3.3 patches (Max 8) work and show up in the Scriptnode project list.

RNBO 1.4.2 patches (Max 9) are created by the HISE wizard but stay invisible in the workspace.

Individual compilation in Xcode fails with 23 errors.

Errors indicate missing members in the C++ class: createParameters, prepare, process, and reset.

It seems the HISE C++ wrapper doesn't recognize the new RNBO 1.4.2 class structure. Have you found a workaround for Max 9, or are you still using RNBO 1.3.3 for HISE integration?