saveInPreset vs custom prefFile vs what?

[Chazrox]

@d-healey should the knobValue be static value? ie. ALWAYS = 1? or should it always = last saved state? ie, user changes and saves the value as .5 in one preset, should that load as .5 on all presets and next plugin launch....or go back to 1?

[Chazrox]

@ustk @d-healey What about setting Knob1 "defaultValue" on value changes/saves and write/load with JSON. Would that make it persist?

[d.healey]

@Chazrox it does persist for me with the snippet I provided. It should retain the last value it was set to.

[Chazrox]

@d-healey I tested it in Ableton. Value doesn't survive relaunch. Might just be Ableton.

[ustk]

This preset thing drives me crazy...

it work in a minimal example, but same code in the project won't work despite I checked everything I could...

And another strange thing arose, now I removed the initial preset loading, my bypass button is deactivated when a new instance is inserted in DAW. But it initialises normally in Hise, its default value is obviously 1, and it's not set anywhere in code. The project is well saved before export and build folder cleaned... Turning around and around with this lol

[d.healey]

@ustk said in saveInPreset vs custom prefFile vs what?:

it work in a minimal example

Are you saying my snippet is working for you?

[ustk]

@d-healey nope, I should have said only for preset loading, not DAW

[d.healey]

@ustk well that's the first issue to solve. Which daws have you tried? Did you test reaper?

[ustk]

@d-healey It seems I manage to solve it, using your code plus a safety that "protects" the protected parameters CB, and keeping the initial preset loading.

Not sure why the bypass button were always initialising to 0 without the preset load though...

[d.healey]

@ustk said in saveInPreset vs custom prefFile vs what?:

plus a safety that "protects" the protected parameters CB,

Explain please

[ustk]

@d-healey I will, I just discovered an error I've made that might be an happy accident... Need to test further...