Preset MIDI Learn doesn't load in compiled plugin

[tomekslesicki]

Ok, so I've just finished MIDI-mapping everything on the interface to CCs. It works fine after the file is loaded in HISE but when I export the vst, I need to load the preset for the mappings to work. It doesn't seem to load the mappings on first plugin load.

I remember reading somewhere that I might need to load the preset in HISE before export and I did it but it doesn't help.

[d.healey]

Yes this is a problem I have faced too. @Christoph-Hart We really need the option to set a default preset, this would solve this issue and several other issues, some of which there are workarounds for. One in particular is even if we save/export with what we want as our "default" preset it doesn't highlight it in the preset browser so the user may not be aware that a particular preset is loaded at all.

[tomekslesicki]

I can live without the default preset if it’s super-hard to implement, but it would be lovely if the midi mappings worked. I know I can script them in but that doesn’t work well with Logic’s non-realtime bounce and some automation artifacts start showing up. So I have to use the midi mapping instead but it doesn’t work on init...

[Christoph Hart]

Yeah it‘s more likely that I fix the midi mapping and let you set a default preset as file just for displaying.

[tomekslesicki]

@Christoph-Hart said in Preset MIDI Learn doesn't load in compiled plugin:

Yeah it‘s more likely that I fix the midi mapping and let you set a default preset as file just for displaying.

That would be awesome! When would you say we can expect this?

[Christoph Hart]

@tomekslesicki said in Preset MIDI Learn doesn't load in compiled plugin:

That would be awesome! When would you say we can expect this?

Wasn't too hard :)

- fixed MIDI mappings not being initialised in the compiled plugin · christophhart/HISE@060a887

The open source framework for sample based instruments - - fixed MIDI mappings not being initialised in the compiled plugin · christophhart/HISE@060a887

GitHub (github.com)

[tomekslesicki]

Awesome stuff! Thank you!

[tomekslesicki]

Hey @Christoph-Hart, I'm working on AAX versions of the plugins now and it seems like there's a problem with loading the initial preset in ProTools. All slider values look kind of random on init:

When I load the preset again, they load just fine:

These are not default slider values either.

Help!

[tomekslesicki]

Here's a lead: if the sliders are not set to be plugin parameters, the instrument loads fine.

[d.healey]

@tomekslesicki Could it be that the DAW overrides the default?

[tomekslesicki]

@d-healey that would be my guess, too. @Christoph-Hart ?

[Christoph Hart]

Ah yes, I think I remember that was a Protools special:

Initial loading values of GUI elements in aax when plugin is opened....

There is an issue with AAX fx plugin initial loading settings. Normally initial loading settings of GUI elements in the exported VST and AU plugins (in host)...

Forum (forum.hise.audio)

TLDR: Make sure that the defaultValue property match the value in your initial preset.

[tomekslesicki]

Ok, I experimented with this further and it seems like the only thing that helps is to disable 'is plugin parameter' for the sliders on AAX plugins. defaultValue doesn't help much.