@ustk

var PluginParameterGroupNames = ["Sampler", "Synth", "etc"];

@Christoph-Hart

Can I sanity check this:

namespace PluginUserPresetHandling { const UserPresetHandler = Engine.createUserPresetHandler(); inline function onPresetSave() { Console.print("onPresetSave triggered"); } inline function onPresetLoad(obj) { Console.print("onPresetLoad triggered"); } inline function preLoadCallback() { Console.print("preLoadCallback triggered"); } inline function postLoadCallback() { Console.print("postLoadCallback triggered"); } inline function postSaveCallback() { Console.print("postSaveCallback triggered"); } inline function init() { UserPresetHandler.setUseCustomUserPresetModel(onPresetLoad, onPresetSave, false); UserPresetHandler.setPreCallback(preLoadCallback); UserPresetHandler.setPostCallback(postLoadCallback); UserPresetHandler.setPostSaveCallback(postSaveCallback); } }

In what order are these called, and which ones are synchronous versus asynchronous??

@David-Healey Thought so, cheers Dave!

@dannytaurus You could just make a Script Time Variant Modulator and blend between 3 oscillators directly in the network. But yeah, a wavetable should be a fun exercise!

@Christoph-Hart Wouldn't cause a corruption in XML. So far as I know, it is perfectly legal to do so. I've used parenthesis in parameter id's for ages and not had any errors in xml files like what @HISEnberg is reporting.

@ulrik are you parsing dodgy data from somewhere?? Because grouping numbers and text strings like that into a single array seems like a poor design.

@Orvillain So that one more confirmation toward the extra_mod connection not being effective... @Christoph-Hart?

@Oriah-Beats Does your client have an old CPU?

@duma That's the Create a New Project Dialog

2a25cb76-8c74-4b52-a277-286118da1974-image.png

To open an existing project go to the File menu.

@duma said in Exporting problems:

how do i downgrade from visual studio 2026 to 2022

Like I said above, uninstall VS26 and install VS22

@lightningpig said in Missing Projucer in tools folder (and other issues I ran into that may or may not be caused by me using Projucer standalone separately):

could we get David on this im kinda lost lol whats happening

Go through my free HISE bootcamp course, it explains everything: https://audiodevschool.com/courses/hise-bootcamp/

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!

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