Restoring properties with DAW session

[whoopsydoodle]

I've been playing around with this trying to find a solution for global settings. Things like oversampling. What I would like is:

• When a new instance of the plugin is loaded, these controls load according to a global settings json file which I set on user control of the knob
• Unless! It's a session being recalled where that knob has already been set by the user.

So when the user clicks off something like oversampling, it will apply to that instance and any new ones loaded, unless an instance is being recalled from a saved session. I absolutely can't have it breaking recall by changing the sound when a user reloads a project.

Unfortunately the .isInternalPresetLoad() method seems to not work well for this. First the settings blink. For a split second it loads the value saved in the preset and it both visually and audibly jumps to that setting for a moment before jumping back to what it was before the preset load.

And second if a user quickly changes presets this method fails after a few clicks. I suspect it has to do with the system trying to load a next preset before it's completed things and set the finished flag. The result is that after a few rapid "next preset" clicks, my control loads the value saved in preset instead of maintaining the prior value as it's supposed to.

[clevername27]

@whoopsydoodle If i understand you correctly, I posted the code to do this a couple weeks ago.

[whoopsydoodle]

@clevername27 link? would love to give it a try

[clevername27]

@whoopsydoodle I tried to find it, but there is no "advanced search" that I can find for the forum. You'd want to search by user (me) and then maybe "file". Perhaps there is a way to do that I do not know of.

[David Healey]

@clevername27 said in Restoring properties with DAW session:

there is no "advanced search"

Search bar at the top, hit enter.

[clevername27]

@d-healey Thank you, appreciated — I can't find stuff, often, with that interface. I meant something like this, which includes options on which keywords must be found, and such.

[David Healey]

@clevername27 said in Restoring properties with DAW session:

I can't find stuff, often, with that interface

It does provide all of those features, the interface is just different.

Search in forum = category
Entire post = In titles and posts
etc.

[clevername27]

@d-healey How do I specify phrases that must be found?

[David Healey]

@clevername27 Wrap it in quotes

[clevername27]

@d-healey So it does, cheers (clicking the gear icon).

[David Healey]

@clevername27 said in Restoring properties with DAW session:

clicking the gear icon

Yeah I just noticed that too :)

[clevername27]

@whoopsydoodle @d-healey Here, then…

https://forum.hise.audio/topic/11384/user-preference-system?_=1742308745595

[cassettedeath]

@David-Healey Would there be any way to make it so that the values don't update visually every time you change a preset?

In my case the button opens a panel and it’s quite abrupt seeing it open and close every preset change. Could this be to do with where the code is placed?

It’s a trade off between the option to say, browse presets without turning off the arp every time or the unaesthetic UI value jump.

[David Healey]

@cassettedeath Remind me what this thread's about again, I'm too lazy to read through

[cassettedeath]

@David-Healey Restoring values in a daw session without the save in preset flag

[David Healey]

@cassettedeath What is the solution that was provided that you're currently using but isn't working as you expect? Do you have a simple snippet?

[cassettedeath]

@David-Healey Snippet ```
code_text

const uph = Engine.createUserPresetHandler();

const var Knob1 = Content.getComponent("Knob1");

reg knobValue;

uph.setPreCallback(function(presetData)
{
	 if (!uph.isInternalPresetLoad())
	 	knobValue = Knob1.getValue();
});

uph.setPostCallback(function(presetFile)
{
	 if (!uph.isInternalPresetLoad())
	 	Knob1.setValue(knobValue);
});

[David Healey]

@cassettedeath Is the goal to keep the leave the panel's open/closed state unchanged between preset changes?

[cassettedeath]

@David-Healey yes that would be good

I suppose the values have to jump from what’s saved in the preset to the previous value?

[David Healey]

@cassettedeath Is there a reason you need to save the button value in the preset at all?