Steinberg releases Retrologue and Padshop Pro for VST & AU

[fmr]

Something occured to me: You are using it in Logic, therefore, you are using the AU version. Didi you check if the folder Padshop creted has the factory presets listed as VSTpresets and not aupresets?
bacause, if it is like other plug-ins, either they use their own format, or, when they use the common formats, AU versions cannot load Vstpresets and vice-versa. I will try using it inside a VST host to see if I can create VSTpresets

[aMUSEd]

That's a possibility. However Steiberg certainly are not providing Padshop presets in aupreset format. tbh I hope this is not the case - I'm getting very fed up with this ridiculous duality of preset formats, developers should be using formats that can be opened in any hosts, not forcing people to create 2 different sets of presets all the time.

[fmr]

That's a possibility. However Steiberg certainly are not providing Padshop presets in aupreset format. tbh I hope this is not the case - I'm getting very fed up with this ridiculous duality of preset formats, developers should be using formats that can be opened in any hosts, not forcing people to create 2 different sets of presets all the time.

2 different sets? You are forgeting RTAS, and the new AAX, and RE, etc. This plug-in world is becoming nuts. Definitely, the only way is for each manufacturer to develop it's own format. Of course, I would like something like XML based or something. I believe it could be done that way.

[Borealis]

Can someone shed some light on the Preset Browser in Padshop Pro? I saved several of my own presets but they don't show up in the Browser, there is no downward arrow to unfold the User folder. Also the "Import Preset" function in the sample window doesn't work.
Also I noticed that when I save my own presets the ending in the name is not .vstpreset like in the Factory stuff but it has some gigantic name with vst3.steinberg.com.whatever - can this be correct?
This is in Logic 9.1.7 on a Mac Pro.
So all my presets from this morning are actually useless so far as I can't recall them. All I can do is to save stuff in the .aupreset format but than I won't be able to share my sounds with Non-Mac users.
Anybody?

Hi Simon, glad to see you here and that we're all digging Padshop. I'm having the same problem with saving presets, the only thing I can add is that it seems strange that the samples associated with my preset are available under the User Samples drop down menu (along with the obligatory down arrow). Odd, hope they fix it soon.

Borealis

[Sampleconstruct]

Something occured to me: You are using it in Logic, therefore, you are using the AU version. Didi you check if the folder Padshop creted has the factory presets listed as VSTpresets and not aupresets?
bacause, if it is like other plug-ins, either they use their own format, or, when they use the common formats, AU versions cannot load Vstpresets and vice-versa. I will try using it inside a VST host to see if I can create VSTpresets

That's the first thing I checked, all factory content comes in .vstprest format and I can load these patches via the Padshop Browser, although it's fiddly as one has to click 2 times on the name of a preset and hope that the preset will load, another Browser issue. Logic is obviously saving stuff (or trying to save) in vst3-format which Padshop can't seem to read in it's current state as a AU-Plug-In.
Confusingly obsolete time-wasting crap really....

[Sampleconstruct]

Can someone shed some light on the Preset Browser in Padshop Pro? I saved several of my own presets but they don't show up in the Browser, there is no downward arrow to unfold the User folder. Also the "Import Preset" function in the sample window doesn't work.
Also I noticed that when I save my own presets the ending in the name is not .vstpreset like in the Factory stuff but it has some gigantic name with vst3.steinberg.com.whatever - can this be correct?
This is in Logic 9.1.7 on a Mac Pro.
So all my presets from this morning are actually useless so far as I can't recall them. All I can do is to save stuff in the .aupreset format but than I won't be able to share my sounds with Non-Mac users.
Anybody?

Hi Simon, glad to see you here and that we're all digging Padshop. I'm having the same problem with saving presets, the only thing I can add is that it seems strange that the samples associated with my preset are available under the User Samples drop down menu (along with the obligatory down arrow). Odd, hope they fix it soon.

Borealis

Hi Ben, yeah the samples are getting saved right after you drag and drop them into Padshop. Also when exporting consolidated patches to wherever one wants to, the samples get saved, but the saved preset-format is not compatible.

[aMUSEd]

It's not just Logic - I'm getting that same dialogue saying you cannot save the document with the extension "preset" and forcing me to save it with a ridiculous preset.com.steinberg.vst.preset extension in other au hosts too - obviously borked.

[Sampleconstruct]

In case someone needs fresh Padshop presets, here is a pre-order page for my upcoming soundset.

[aMUSEd]

Cool - I'll definitely be up for these.

[aMUSEd]

Whatever it is saving they are not even vstpresets - I just tried importing one into the VST3 version in Studio One and it said "this is not a padshop file". I suspect now that it is saving aupresets but just trying to give them the wrong format name - so annoying though that we could end up having two different sets of banks for the same plugin emerging but no ability to use both in the same version. This is why formats like u-he's h2p or NI's former ksd are so much saner - make once, load everywhere.

[Sampleconstruct]

Whatever it is saving they are not even vstpresets - I just tried importing one into the VST3 version in Studio One and it said "this is not a padshop file". I suspect now that it is saving aupresets but just trying to give them the wrong format name - so annoying though that we could end up having two different sets of banks for the same plugin emerging but no ability to use both in the same version. This is why formats like u-he's h2p or NI's former ksd are so much saner - make once, load everywhere.

Woaaa, gruesome! So for now I will only announce my set for Mac users then, as I can't know if I will finally be able to convert them to vst-format somehow, that totally sucks!

[aMUSEd]

Yeah, also it looks like it might be worth just tediously going through the factory bank and converting it all to aupresets one afternoon. At least then it will have manageable presets - unlike the current situation.


hmm wonder if it's scriptable?

[aMUSEd]

Yeah, also it looks like it might be worth just tediously going through the factory bank and converting it all to aupresets one afternoon. At least then it will have manageable presets - unlike the current situation.


hmm wonder if it's scriptable?

OK I'm doing this now - boring but necessary. I'll see if it's possible for me to make the factory presets available to anyone that wants them, for obvious reasons I can't do that for the Zero Gravity bank though I will make them for myself in time.

[aMUSEd]

Whatever it is saving they are not even vstpresets - I just tried importing one into the VST3 version in Studio One and it said "this is not a padshop file". I suspect now that it is saving aupresets but just trying to give them the wrong format name - so annoying though that we could end up having two different sets of banks for the same plugin emerging but no ability to use both in the same version. This is why formats like u-he's h2p or NI's former ksd are so much saner - make once, load everywhere.

Woaaa, gruesome! So for now I will only announce my set for Mac users then, as I can't know if I will finally be able to convert them to vst-format somehow, that totally sucks!

Do you have a way to get hold of Studio One or Cubase for a while? It seems easy enough (just tedious) to convert from vstpreset to aupreset in Logic, just not the other way.

[Sampleconstruct]

Whatever it is saving they are not even vstpresets - I just tried importing one into the VST3 version in Studio One and it said "this is not a padshop file". I suspect now that it is saving aupresets but just trying to give them the wrong format name - so annoying though that we could end up having two different sets of banks for the same plugin emerging but no ability to use both in the same version. This is why formats like u-he's h2p or NI's former ksd are so much saner - make once, load everywhere.

Woaaa, gruesome! So for now I will only announce my set for Mac users then, as I can't know if I will finally be able to convert them to vst-format somehow, that totally sucks!

Do you have a way to get hold of Studio One or Cubase for a while? It seems easy enough (just tedious) to convert from vstpreset to aupreset in Logic, just not the other way.

I have the demo of Studio One installed, time has run out though. Maybe I should just buy a licence tomorrow - but I thought you said that even in Studio One the preset saving doesn't work as it should or did I get you wrong?
But all the patches I did today would only be in au and not in vst and I don't want to start from scratch, hmmmmm

EDIT: I reread your post above, so I got it wrong - importing the odd vst3 format saved in Logic does not open in Studio One/Padshop, but saving inside Studio One/Padshop will work fine?