ProTools load problem....

[Lindon]

So does anyone have a workable solution to the ProTools bug, where it fails to load the correct Plugin (saved on compile ) state at start up - and instead loads each control with its default value?

[Dan Korneff]

Here's my hacky solution. I've created a button and label in a hidden Maintenance panel.
Before I export my plugin, I click the InitialState0 button so it's enabled.
When the plugin is first launched in PT, it runs the InitializeState() function and loads a "factory reset" preset and then changes the state of the InitialState0 button so it doesn't run again.

const var InitialStateLabel = Content.getComponent("InitialStateLabel");
const var InitialState0 = Content.getComponent("InitialState0");

inline function InitializeState()
{
	if(InitialState0.getValue() == 1)
	{
		InitialStateLabel.set("text", "");
		Engine.loadUserPreset("Factory Reset.preset");
		InitialStateLabel.set("text", Engine.getCurrentUserPresetName());
		
		InitialState0.setValue(0);
	}


}

ProtoolsParameterFixer.setTimerCallback(function()
{
	InitializeState();
	this.stopTimer();
});

ProtoolsParameterFixer.startTimer(200);

[ustk]

@Dan-Korneff Wouldn't it be enough to simply load the initial preset manually before saving/exporting?
Is this hack just a shortcut against this issue or more?

[Dan Korneff]

@ustk

@ustk said in ProTools load problem....:

@Dan-Korneff Wouldn't it be enough to simply load the initial preset manually before saving/exporting?

Protools ignores the settings you placed at export and instead loads all controls to their default values.

[Lindon]

@ustk said in ProTools load problem....:

@Dan-Korneff Wouldn't it be enough to simply load the initial preset manually before saving/exporting?
Is this hack just a shortcut against this issue or more?

the problem is ProTools wont load your initial preset -Basically ProTools ignores whatever you have set each control == to, and flips every control to its default value. Giving you a mess of a set up, so as Dan has shown you need some way to make ProTools load the first preset as soon as the plug in is loaded...

[Lindon]

@Dan-Korneff Thanks Dan thats the implementation I was thinking of using - ugly as it is...

[Dan Korneff]

@Lindon I came up with this one quickly cause I was in a hurry, and it worked, but I'm sure there's much room for improvement.

[Lindon]

@Dan-Korneff yeah - let me think about it for a bit....

[iamlamprey]

my hacky solution is to tell customers to use a better daw

[d.healey]

@iamlamprey I use a similar solution, I don't provide an AAX

[Christoph Hart]

Is there any valid use case for why the default state of a plugin should be different from the defaultValue property of each UI element? This is nagging me for years because you have to drag around an "init user preset" and restore it everytime you save the project to not mess up the git history.

I'm thinking about adding an Enforce Default State mode that will restore the values of each UI element to the default state defined by the defaultValue property whenever you save or export the project and this would drive-by-fix this annoying Protools problem too.

[d.healey]

I can imagine it's not uncommon to have "safe" default values for the user's benefit when they are tweaking the controls but for your default preset you want different settings.

[Christoph Hart]

@d-healey yeah I think I‘m going through the projects and compare the init state vs the default value, but what if we just add a initValue property that will take precedence over the defaultValue at initialisation so you can customize those controls individually?

[d.healey]

@Christoph-Hart That's good. I think even better would be if we could assign a "default preset" that would also be selected in the preset browser.

[Dan Korneff]

@Christoph-Hart said in ProTools load problem....:

Is there any valid use case for why the default state of a plugin should be different from the defaultValue property of each UI element?

For something like a mixing console, the default value for a fader would be set to 0dB, but that could be way different than the balance you may have dialed in for your default state.

[Dan Korneff]

@Christoph-Hart said in ProTools load problem....:

what if we just add a initValue property that will take precedence over the defaultValue at initialisation so you can customize those controls individually?

Could this be generated automatically from the export state? If you have 100 controls, you'd have to manually verify that the initValue matches the value of your export state. I can't think of a reason why these would ever be different.

[Christoph Hart]

@Dan-Korneff yeah the suggestion of David makes more sense, so I‘d go that route - you will just have to specify a default preset in the settings and it will use this as init state and plugin parameter default state (which solves the Protools issue).

[Lindon]

@Christoph-Hart said in ProTools load problem....:

Is there any valid use case for why the default state of a plugin should be different from the defaultValue property of each UI element? This is nagging me for years because you have to drag around an "init user preset" and restore it everytime you save the project to not mess up the git history.

I'm thinking about adding an Enforce Default State mode that will restore the values of each UI element to the default state defined by the defaultValue property whenever you save or export the project and this would drive-by-fix this annoying Protools problem too.

Actually-if understand this correctly- this would be the exact opposite of fixing the problem. Every control needs a default state - but the plugins init state may well need to be a specific preset (so the user gets a "good" experience straight away).

So if I set the plugin to this init-preset on compile, then every other DAW loads the plugin AND its init-preset state. ProTools loads the plugin and ignores this init-preset state and just sets every control to its default...=== bad,bad,bad PT.

So what we need here is a mechanism to force the load of this init-preset in ProTools.

[Dan Korneff]

@Lindon I think @Christoph-Hart is suggesting that he adds a feature to load a specific preset when you launch your plugin. Like an automatic version of my hack.

[Lindon]

@Dan-Korneff oh well yes if that works in ProFools then great!