@David-Healey said in Moonbase:

if you then reexport from HISE the juicer file will be recreated and your changes overwritten, that's probably the issue you were running into

yes i believe this was the issue.
but im also wondering if i somehow screwed up changing over from 6 to 8.

@Anhuarcin It could be possible that there are code paths generated for runtime dispatch, so that if the CPU detection shows AVX support, then it will branch to use that - I can imagine that IPP does stuff like that to squeeze out performance.

@JulesV My solution is to use a flag. If the plugin is being initialized, load a specific preset that has my settings. if the plugin isn't being initialized, it doesn't do anything special.

@Daanyoo I just tried to reproduce it on a empty project on WIN, it worked there and all of the sudden it worked in the regular project as well... I am so confused haha

But at least its fixed, thank you guys for your help!!

@dannytaurus @Oli-Ullmann @ustk thank you all for the help, all your suggestions work great!

@ustk yeah ill just hide it.

I was gonna have it as part of the interface for the user to see cpu and ram usage, but its not really necessary.

@Bart Wow, that interface is wild! 😮 😂

The synth I'm building is the start of a series, so I'm designing a layout that will work with all of them. Each one will have a couple of unique controls, so they all look slightly different but obviously from the same family.

@Lindon I've used iLok on 4 of my plugins. Just wrapping, not fusion. Totally doable, but you'll be editing the HISE source to implant the code.

I would also like to throw my hat into the ring. :-)

I have spent most of my professional life as a composer for film, TV, and advertising. My clients include German TV stations as well as Bugatti Automobiles, Porsche, Nivea, and many more. I have also been involved in several gold and platinum chart productions.

Since 2022, I have released a few Kontakt libraries, and for the past 2.5 years, I have been working intensively with HISE. I am currently finishing my first plug-in. For this, I created all the graphics in HISE and also worked with Max and RNBO export and import in HISE. In addition, I have extensively studied the new HISE modulation system.

There are certainly some more experienced programmers than me in this post, which is why my unique selling point is probably that I have many years of experience in professional music production and sound design.

I look forward to working on projects together! :-)

@David-Healey thanks for this post! :-)

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

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

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