ProTools load problem....

[gorangrooves]

Here:
https://forum.hise.audio/post/57305

[Dan Korneff]

@gorangrooves but didn't this change the default values of the parameters?

[Lindon]

@Dan-Korneff said in ProTools load problem....:

@gorangrooves but didn't this change the default values of the parameters?

yeah - this == bad.

[Christoph Hart]

Alright, I've pushed something that should take care of this problem. You can now define a relative path in the Project settings to a user preset file (from the user preset directory) (DefaultUserPreset) that will be embedded into the binary and loaded as default state. Once you've done this, this preset is being loaded everytime you save or export the project. It will also return the value stored in the preset as default value for the plugin parameter which should hopefully fix this Protools issue once and for all.

What I haven't done yet is to make this the selected preset on init, but that's something for another day :)

Let me know if that helped.

[gorangrooves]

@Christoph-Hart I guess, this will only work for those who utilize presets in their plugins.

@Dan-Korneff Yes, it sets the "default values" of parameters to that what you set on your GUI as the default state of your plugin. Isn't that the objective?
If I set a slider to a value of 0.5 on the GUI to be loaded when a user opens up the plugin, why would I want the default value of that slider to be anything different from that?
Basically, you make your adjustments for the controls on the GUI to be what you want them to be in every DAW, and the little script sets the default values for those controls to the same values.

The secondary script on the page I pointed to, gets the Pro Tools to recall those values if one slider moves to a value we know it should not be on load.

@Lindon What's bad?

All I can tell you is that I have implemented this, and it works perfectly.

[d.healey]

@d-healey said in ProTools load problem....:

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

@Christoph-Hart I guess, this will only work for those who utilize presets in their plugins.

You can just add a preset for the purpose of having a default preset. You don't need to use them for any other reason if you don't want to.

Isn't that the objective?

Nope. The idea is to have the controls on the UI appear in a particular state when the plugin is initialized. That state does not necessarily match the default values you want for your controls.

[d.healey]

This post is deleted!

[gorangrooves]

@d-healey My plugins have presets, so I am good.

So, what would you want the component default values for if not for when a plugin is loaded?

[d.healey]

@gorangrooves We have posted some scenarios where this is useful further up the thread.

The default values are used when the user double clicks a knob to reset it. That doesn't mean you want it at that position with the initial instance of the plugin.

[d.healey]

Pro-Tools support might not be a problem soon https://www.reuters.com/technology/space/media-editing-software-vendor-avid-explores-sale-sources-2023-05-24/ :)

[gorangrooves]

@d-healey I see.
I personally would want the double-click to bring the knob value to what is set on the GUI on the initial plugin instance. So, for me, it still makes sense to match the two.

[d.healey]

@gorangrooves Yeah me too for most of my instruments, but it depends on the plugin. Someone posted a good example above. When you have a mixer you want the default (double click) to be 0dB but you want the initial state of your plugin to have a good balanced mix so the faders probably won't all be at 0dB.