KVR Audio

Sampleconstruct · Post by **Sampleconstruct** » Sat Jul 14, 2012 1:44 am

o0Ampy0o wrote:
Sampleconstruct wrote:Woaaa, this must be one of the most gigantic pad sounds I ever programmed using a vocal scape and a orchestral chord from one of my former soundsets.
http://soundcloud.com/sampleconstruct/g ... p-pro-demo

Sampleconstruct wrote:Here is another new patch: Glass Dreams made with 2 glass samples, one struck and one fingered.
http://soundcloud.com/sampleconstruct/g ... p-pro-demo

Wow! ...this has the potential to produce Omnispheric quality in the right hands......who knows maybe in time the ability to import your own samples in this little inexpensive device will be the straw that breaks the camel's back and lead to a decision in which Spectrasonics opens up Omnisphere? You can only compete by offering more presets as long as you can produce stellar presets before additional features that empower users to do their own thing are needed to take some burden off the software company.

.

I'm sure Spectra would have sold twice as many copies of Omnisphere if they would allow user sample import - I for sure would have bought it by now, just like I bought Padshop Pro yesterday. I have a strong weakness for everything granular and sample based, most VA-based synths just bore me to death these days....

Sampleconstruct · Post by **Sampleconstruct** » Sat Jul 14, 2012 2:03 am

4lb Kitty wrote:Cubase Elements is only $99 USD. Not sure about Euros.

Yeah, but Cubase does not support AU-Plugs, so I'll probably bite the dust and get Studio One. I never wanted a second DAW after having used Logic since version 1 on an ATARI 1040 back in 1987. I only have PT lying around so I can open AVID-audio received from filmmakers but apart from that I never use it.
Studio One here we come...

Vintage73 · Post by **Vintage73** » Sat Jul 14, 2012 2:14 am

I guess that makes sense...sorry.

Sampleconstruct · Post by **Sampleconstruct** » Sat Jul 14, 2012 4:04 am

So I know have Studio One Producer installed and running, I have both versions of Padshop Pro open, I create a patch in the vst3 version, then save it as .vstpreset using Studio Ones Preset Manager, the drag that new preset into the AU-version and export it again as AU-Preset using the Preset Manager.
A bit convoluted but it works and all of that for only $236,81 USD - Jesus....

Now I only have to convert the au-presets I made yesterday manually which will take hours, like in the good old days, maybe even using pencil and paper. I will have Logic and Studio One open at the same time and re-edit each parameter in the vst3 version, great old school fun! No, there has to be another way, let me check...

EDIT:
Nope, that is indeed the only way, I tried using Studio Ones native preset format to get the au presets over into the vst3 version but the vst3 doesn't read those, when you import them nothing happens.
Oh My Steinberg, what have you done here?????

aMUSEd · Post by **aMUSEd** » Sat Jul 14, 2012 8:18 am

fmr wrote:I can't load anything using the built in preset manager, but I can load them using the Import Preset feature in the sample windows. I also managed to create a preset and saving it perfectly as a .vstpreset using the "Export Preset With Sample", then load other presets, and then, using the Import Preset, loading again. This was in Reaper, using the AU version. Strange...

Very - for me the import export button does nothing - if I try and export a preset with sample I get the same dialogue I do with the save button "You cannot save this document with extension ".preset" at the end of the name. The required extension is ".com.steinberg.vst3.preset"." and the file saved has this ridiculous multiple extension. Such a file will not import either with the import button or show in the browser, not even if I rename it as a vstpreset.

aMUSEd · Post by **aMUSEd** » Sat Jul 14, 2012 8:21 am

Sampleconstruct wrote:
4lb Kitty wrote:Cubase Elements is only $99 USD. Not sure about Euros.
Yeah, but Cubase does not support AU-Plugs

oh ffs - about time these companies got off their high horses and worked together more to make life easier for musicians.

Sampleconstruct · Post by **Sampleconstruct** » Sat Jul 14, 2012 8:41 am

Here is a morning patch:
1Finger Pad Split - 2 pads generated from the same huge-chord-sample split across the keyboard.
http://soundcloud.com/sampleconstruct/1 ... adshop-pro

Somebody from Steinberg contacted me this morning very politely saying that none of the problems occured during Betatesting, which seems strange, but he said: Murphy's Law. So they are aware of the issues and will work on them.

aMUSEd · Post by **aMUSEd** » Sat Jul 14, 2012 9:02 am

Sampleconstruct wrote:So I know have Studio One Producer installed and running, I have both versions of Padshop Pro open, I create a patch in the vst3 version, then save it as .vstpreset using Studio Ones Preset Manager, the drag that new preset into the AU-version and export it again as AU-Preset using the Preset Manager.
A bit convoluted but it works and all of that for only $236,81 USD - Jesus....

Now I only have to convert the au-presets I made yesterday manually which will take hours, like in the good old days, maybe even using pencil and paper. I will have Logic and Studio One open at the same time and re-edit each parameter in the vst3 version, great old school fun! No, there has to be another way, let me check...

EDIT:
Nope, that is indeed the only way, I tried using Studio Ones native preset format to get the au presets over into the vst3 version but the vst3 doesn't read those, when you import them nothing happens.
Oh My Steinberg, what have you done here?????

Just a thought - is it saving these presets with the sample?

Sampleconstruct · Post by **Sampleconstruct** » Sat Jul 14, 2012 9:07 am

aMUSEd wrote:
Sampleconstruct wrote:So I know have Studio One Producer installed and running, I have both versions of Padshop Pro open, I create a patch in the vst3 version, then save it as .vstpreset using Studio Ones Preset Manager, the drag that new preset into the AU-version and export it again as AU-Preset using the Preset Manager.
A bit convoluted but it works and all of that for only $236,81 USD - Jesus....

Now I only have to convert the au-presets I made yesterday manually which will take hours, like in the good old days, maybe even using pencil and paper. I will have Logic and Studio One open at the same time and re-edit each parameter in the vst3 version, great old school fun! No, there has to be another way, let me check...

EDIT:
Nope, that is indeed the only way, I tried using Studio Ones native preset format to get the au presets over into the vst3 version but the vst3 doesn't read those, when you import them nothing happens.
Oh My Steinberg, what have you done here?????
Just a thought - is it saving these presets with the sample?

No, just in the native Studio One format. The guy from Steinberg will convert my aus from yesterday he said, as everything is working as it should on his system so I am safe!

Sampleconstruct · Post by **Sampleconstruct** » Sat Jul 14, 2012 9:10 am

Btw, now that I have made the first vst-Presets in Studio One the User folder in the Preset Browser in Padshop/Logic is actually showing it's content, so it's all down to this cryptic wrong format which Padshop is trying to save.

aMUSEd · Post by **aMUSEd** » Sat Jul 14, 2012 9:27 am

Sampleconstruct wrote:
aMUSEd wrote:
Sampleconstruct wrote:So I know have Studio One Producer installed and running, I have both versions of Padshop Pro open, I create a patch in the vst3 version, then save it as .vstpreset using Studio Ones Preset Manager, the drag that new preset into the AU-version and export it again as AU-Preset using the Preset Manager.
A bit convoluted but it works and all of that for only $236,81 USD - Jesus....

Now I only have to convert the au-presets I made yesterday manually which will take hours, like in the good old days, maybe even using pencil and paper. I will have Logic and Studio One open at the same time and re-edit each parameter in the vst3 version, great old school fun! No, there has to be another way, let me check...

EDIT:
Nope, that is indeed the only way, I tried using Studio Ones native preset format to get the au presets over into the vst3 version but the vst3 doesn't read those, when you import them nothing happens.
Oh My Steinberg, what have you done here?????
Just a thought - is it saving these presets with the sample?
No, just in the native Studio One format. The guy from Steinberg will convert my aus from yesterday he said, as everything is working as it should on his system so I am safe!

Why are you doing that? If you have the VST3 available now it does export vstpreset patches correctly with the samples and they will load in the version in Logic. So the aupreset thing is surely unnecessary now anyway except perhaps for the convenience of being able to browse them easier using Logic's own browser.

aMUSEd · Post by **aMUSEd** » Sat Jul 14, 2012 9:29 am

Sampleconstruct wrote:
aMUSEd wrote:
Sampleconstruct wrote:So I know have Studio One Producer installed and running, I have both versions of Padshop Pro open, I create a patch in the vst3 version, then save it as .vstpreset using Studio Ones Preset Manager, the drag that new preset into the AU-version and export it again as AU-Preset using the Preset Manager.
A bit convoluted but it works and all of that for only $236,81 USD - Jesus....

Now I only have to convert the au-presets I made yesterday manually which will take hours, like in the good old days, maybe even using pencil and paper. I will have Logic and Studio One open at the same time and re-edit each parameter in the vst3 version, great old school fun! No, there has to be another way, let me check...

EDIT:
Nope, that is indeed the only way, I tried using Studio Ones native preset format to get the au presets over into the vst3 version but the vst3 doesn't read those, when you import them nothing happens.
Oh My Steinberg, what have you done here?????
Just a thought - is it saving these presets with the sample?
No, just in the native Studio One format. The guy from Steinberg will convert my aus from yesterday he said, as everything is working as it should on his system so I am safe!

They still haven't got back to me

Since they are talking to you would you mind letting them know that I've converted the entire Factory bank now into aupresets if they want them - I presume they wouldn't be happy for me to just post them here

aMUSEd · Post by **aMUSEd** » Sat Jul 14, 2012 9:35 am

Sampleconstruct wrote:Btw, now that I have made the first vst-Presets in Studio One the User folder in the Preset Browser in Padshop/Logic is actually showing it's content, so it's all down to this cryptic wrong format which Padshop is trying to save.

Yes they do show - but unless you are using the built-in "save preset with samples" export it's possible they are not doing that

Sampleconstruct · Post by **Sampleconstruct** » Sat Jul 14, 2012 9:42 am

aMUSEd wrote:
Sampleconstruct wrote:
aMUSEd wrote:
Sampleconstruct wrote:So I know have Studio One Producer installed and running, I have both versions of Padshop Pro open, I create a patch in the vst3 version, then save it as .vstpreset using Studio Ones Preset Manager, the drag that new preset into the AU-version and export it again as AU-Preset using the Preset Manager.
A bit convoluted but it works and all of that for only $236,81 USD - Jesus....

Now I only have to convert the au-presets I made yesterday manually which will take hours, like in the good old days, maybe even using pencil and paper. I will have Logic and Studio One open at the same time and re-edit each parameter in the vst3 version, great old school fun! No, there has to be another way, let me check...

EDIT:
Nope, that is indeed the only way, I tried using Studio Ones native preset format to get the au presets over into the vst3 version but the vst3 doesn't read those, when you import them nothing happens.
Oh My Steinberg, what have you done here?????
Just a thought - is it saving these presets with the sample?
No, just in the native Studio One format. The guy from Steinberg will convert my aus from yesterday he said, as everything is working as it should on his system so I am safe!
Why are you doing that? If you have the VST3 available now it does export vstpreset patches correctly with the samples and they will load in the version in Logic. So the aupreset thing is surely unnecessary now anyway except perhaps for the convenience of being able to browse them easier using Logic's own browser.

The samples are saved into the user folder User/Documents/Steinberg/Padshop/Samples/User Samples as soon as you drop them into Padshop so there is no need to resave them. Sample Path issues will occur later

I'm just saving the aus inside Tsudio One because I can - LOL, but you're right I can do that right in the end when everything is finished. I was just proud of my new DAW which can use both Plug-In formats like every other DAW on this planet should do.

aMUSEd · Post by **aMUSEd** » Sat Jul 14, 2012 9:46 am

Sampleconstruct wrote:I was just proud of my new DAW which can use both Plug-In formats like every other DAW on this planet should do.

Amen! Although even then an AU will only save aupresets and VST3 will only save vstpresets - it would be nice if it would also load any format but I suppose that is too much to expect.

Steinberg releases Retrologue and Padshop Pro for VST & AU