Are Plug-in Settings Preferences Global?

[skylar_battles]

I couldn't find this specified in the manual either so I figured someone here would know for certain.

When clicking on the context menu in the preset section of a plug-in window there are the options within settings preferences for "Set Plug-in Default To" and "Save Plug-in Settings To."

These both seem to global but I can't find anything specifying that. It seems like the "Set Plug-in Default To" would be problematic as a global setting because then you wouldn't be able to choose when you'd like to use factory settings vs. user settings if it applies across the entire application.

[albee1952]

"Set Plug-in Default To" means that any given plugin will default to any preset you have saved(whether a stock preset, or one you create) as long as you have that plugin set to default to a user preset(another menu option if you dig deeper)

"Save Plug-in Settings To." Now I am not positive on this and am not at my rig right now, so take this with a grain of salt. USUALLY, you "Save Plug-in Settings" as a preset(like, I have favorite EQ settings for bass drum and BGV's, or favorite reverb settings which I want those plugins to default to when I add them). Having said that, if it really is"Save Plug-in Settings To" then I'm not quite sure if that is different, though it may be that you can decide WHERE to save settings(vs the default plugin settings folder). I'll watch this thread to see if someone else has a deeper understanding on this

[skylar_battles]

Hmmm so tell me if this is correct...

So after recalling a preset regardless if it was provided by the plug-in developer or custom made by the user and selecting "Set As User Default", and also selecting "Set Plug-in Default to" -> "User setting, then next time you add that plugin is will load the desired preset?

Then would any plug-ins without a designated preset by using "Set As User Default" just default to the factory default?

Some of my confusion with this has to do with when I tried to set up a default preset in the Drum Sampler "Sitala". I noticed when I was creating an new preset to be recalled that I had to create a separate one for the Mono and Stereo versions of the plugin which didn't make sense to me. Upon trying to get it working as desired, I somehow lost the Mono version of the plug-in. Troubleshot with the developer to no avail. It seemed like the plug-in needed separate presets for the different Widths while the settings in the dropdown we are discussing might be global.

Since GrooveCell for example also has a default preset with sounds loaded into it, it could be good to save an empty kit to build on, but now I'm nervous about losing or messing up plug-ins without fully understanding this process.

"Save Plug-in Settings To" I'm less concerned about because as far as I understand, using the root settings folder seems safer so you can recall that setting in any session as compared to choosing the session folder option. Would love to learn more about this though as well!

[docric]

Originally Posted by skylar_battles

"Save Plug-in Settings To" ... using the root settings folder seems safer so you can recall that setting in any session as compared to choosing the session folder option...

That's correct.
If you have created presets you love for a plug-in & want access to them for various sessions, then "saving plug-in settings to" the ROOT level folder does that.
Personally, I keep this set to "session folder" mostly, bc I just want to save the "Bass Eq" (or whatever) settings for that specific session to use.

[skylar_battles]

I still have some confusion about this.

Is the correct procedure to set a preset to be recalled upon opening a plugin as follows?

1. Adjust settings to make desired preset
2. Click "Save settings As…" in the preset context menu and name your preset
3. Click "Change Settings Preferences" to in the preset context menu and change to from "Factory Default" to "User Setting" if not already set that way
4. Click "Set as user default" in the preset context menu

My thought now is that "Set Plug-in Default To" and "Save Plug-in Settings To" are global as they are defined under "Settings Preferences" (plural) but I'm still not 100% certain.

Also in the past, I've had behavior when I follow the procedure I mentioned for a stereo plugin, the setting I've set up won't recall on a mono instance of that same plugin. Is it to be expected to have to do the same procedure for every width of the plugin for the same preset you want to save as a default or could that behavior be the result of a bug?

[smurfyou]

That is correct. Works for me, and seems to apply to every format. Maybe certain plugins like Sitala aren't respecting that? I haven't used it since I went Silicon native... need to install it, I really liked it.

[skylar_battles]

Thanks for clarifying that for me. It's a great plugin but I lost a bunch of work either because of trying to do the procedure I mentioned to the mono version of the plugin, or when updating to 2024.3. One of these things seemingly caused the mono version to go missing as I discuss in this thread.

Could you let me know if you try it you are able to use the mono version or only have the stereo version accessible in Pro Tools? I really tried to troubleshoot with the developer and couldn't solve it so I had to stop using the plugin unfortunately. The mono version is far preferable for me because you can use mono pan on mono AUX tracks when using multi-output from the plugin.

[smurfyou]

I see it is a paid plugin now, which is cool and I think it's worth it. (But I can't buy it at the moment).

I did install it and it is available as mono. Because it's unregistered I can't access the multi-out config though.

[skylar_battles]

I really appreciate you taking the time to do that and letting me know!

What version of Pro Tools are you using? I presumably lost it on 2023.12 when I updated or because of trying to set up the plugin presets under the same name for the mono and stereo versions of the plugin. I'd really love to find a way to get it back if possible as it's hard to beat! Any troubleshooting ideas you'd recommend? Sorry to change the thread subject but I suppose it's related if it caused me to lose a plugin!

[smurfyou]

I'm on 2023.9

Have you tried clearing the plugin cache?