Presets with third party plugins

[Number6]

Long shot...

I'm probably just imaging this, I thought it worked before, but here is a third party plugin and Presets don't appear on the drop down (see red arrow). Obviously they work within the plugin itself.
Is this standard behaviour for third party plugins? Is it just Studio Pro only, is there any way to get it to work?

Thanks....

 

[BobF]

Standard behavior. The SP8 presets will only show presets created at that level. Presets within/provided with 3rd party plugs are managed via the plug-in

 

[Number6]

Standard behavior. The SP8 presets will only show presets created at that level. Presets within/provided with 3rd party plugs are managed via the plug-in

Thanks. So no way to create our own I assume, and no workarounds. Proprietary only. Maybe I was thinking about other DAWs that did something similar (or maybe I was imaging it).

 

[BobF]

Thanks. So no way to create our own I assume, and no workarounds. Proprietary only. Maybe I was thinking about other DAWs that did something similar (or maybe I was imaging it).

I don't understand how this is limiting

 

[Number6]

I don't understand how this is limiting

Well for instance Atom controllers (and no doubt these new Fender additions) select presets via this method.

Otherwise why offer this facility at all? It obviously has some use.

 

[ptheisen]

I may not be understanding the question, but, you CAN create your own SP presets specific to each individual plugin or instrument. You can name them, save them, organize them in folders, etc. Then select/recall them via any method that accesses the SP presets that the red arrow in the OP's image is pointing to. This functionality is revealed by clicking on the little icon that looks like a page with a folded upper right corner to the left of the previous/next preset arrows.

Some plugins have their own preset functionality which is totally separate and not accessed the same way. Other plugins install their presets in the vstplugin format and put them in a place that SP "knows" about so those are available via the SP preset functionality without any user work required. But if the plugin doesn't do that, or if you want to add to what is there, you can create your own.

 

[Vocalpoint]

Well for instance Atom controllers (and no doubt these new Fender additions) select presets via this method.

Otherwise why offer this facility at all? It obviously has some use.

This facility is for Presonus/Fender "in-box" plugins to provide a baseline to a user when adding an ATOM controller to a Studio One/Studio Pro install.

Do note - there is no requirement in the real world to need/use/buy any third party plugin. The ATOM focuses on it's own backyard and controls it by design.

Third parties do their thing their way - can't win em all.

VP

 

[Number6]

Wow it's almost like you are part of the development team, thanks for letting me know about Fenders "by design" policy that of course would never ever change. No point in asking for them to reconsider or change things in the future, you already explained it to me. Sorry silly me.

 

[Vocalpoint]

Wow it's almost like you are part of the development team, thanks for letting me know about Fenders "by design" policy that of course would never ever change. No point in asking for them to reconsider or change things in the future, you already explained it to me. Sorry silly me.

Just answered your question bro.

Have zero knowledge on the DEV team or what they will (or will not) do regarding this item or anything else quite frankly.

If you want to get bent out of shape about this - that’s on you to manage.

VP

 

[BobF]

Wow it's almost like you are part of the development team, thanks for letting me know about Fenders "by design" policy that of course would never ever change. No point in asking for them to reconsider or change things in the future, you already explained it to me. Sorry silly me.

This is what a Feature Request is for; a change to existing, or new functionality.

 

[Vocalpoint]

This is what a Feature Request is for; a change to existing, or new functionality.

This.

VP

 

[Number6]

I made the mistake of thinking this was another thread so deleted my last post. Apols for that.

"thanks for letting me know about Fenders "by design" policy that of course would never ever change.

I'm pretty much spelling a feature request here aren't I in that statement. Can't see how that would be interpreted in any other way. I'm using obvious sarcasm in response to the previous post.

BTW:

"This facility is for Presonus/Fender "in-box" plugins to provide a baseline to a user when adding an ATOM controller to a Studio One/Studio Pro install."

I have no idea what this means "to provide a baseline to a user" - Huh?, or indeed which person from Fender supplied you this information.

"Do note - there is no requirement in the real world to need/use/buy any third party plugin. The ATOM focuses on it's own backyard and controls it by design."

Again meaningless especially when it's a feature request, and none of that statement came from Fenders mouth. And yet Studio Pro does support hosting third party plugins "by design".

"Have zero knowledge on the DEV team or what they will (or will not) do regarding this item or anything else quite frankly.*

Exactly my point. Unless you are part of the team "By design" or telling us what the intention is, isn't our place.

But yes, absolutely a feature request.