Studio One 1.5 feature list- full press release

[redshift factor]

Yeah, Studio One definitely supports FXP/FXB, but I'm asking specifically about Steinberg's new VST3 preset standard, ".vstpreset" which replaces .fxp in Cubase 4 and above. Anyways, I've found a .vstpreset to .fxp converter, called FXTractor, so that is less pressing now.

I have a couple more questions, though.
From what I can gather from the manual, it appears that surround sound is not supported, only stereo. Is this correct?

Also, it appears that unlike Cubase, which has a set number of inserts - 6 pre-fader and 2 post-fader, Studio Ones creates inserts as needed. But is there an upper limit to the number of inserts per channel? Does it have pre and post-fader inserts like Cubase, or just pre-fader?

[aMUSEd]

Yeah, Studio One definitely supports FXP/FXB, but I'm asking specifically about Steinberg's new VST3 preset standard, ".vstpreset" which replaces .fxp in Cubase 4 and above. Anyways, I've found a .vstpreset to .fxp converter, called FXTractor, so that is less pressing now.

Yes .vstpreset is the VST3 file format. Amazing that Studio 1 manages to do what Steinberg fails at (i.e. allow save in vstpreset and/or fxp/b) even though these are their own formats originally.

[koolkeys]

Yeah, Studio One definitely supports FXP/FXB, but I'm asking specifically about Steinberg's new VST3 preset standard, ".vstpreset" which replaces .fxp in Cubase 4 and above. Anyways, I've found a .vstpreset to .fxp converter, called FXTractor, so that is less pressing now.

Yes .vstpreset is the VST3 file format. Amazing that Studio 1 manages to do what Steinberg fails at (i.e. allow save in vstpreset and/or fxp/b) even though these are their own formats originally.

Though Studio One can still only save in .vstpreset format for VST3 plugs and .fxp/b for VST2 plugs. So they aren't interchangeable.

Brent

[aMUSEd]

Yeah, Studio One definitely supports FXP/FXB, but I'm asking specifically about Steinberg's new VST3 preset standard, ".vstpreset" which replaces .fxp in Cubase 4 and above. Anyways, I've found a .vstpreset to .fxp converter, called FXTractor, so that is less pressing now.

Yes .vstpreset is the VST3 file format. Amazing that Studio 1 manages to do what Steinberg fails at (i.e. allow save in vstpreset and/or fxp/b) even though these are their own formats originally.

Though Studio One can still only save in .vstpreset format for VST3 plugs and .fxp/b for VST2 plugs. So they aren't interchangeable.

Brent

They don't need to be interchangeable - anyone using the VST3 version is bound to be using a host that can load them. The problem in Cubase would be if you want to design presets but can't save to a format that is compatible with other hosts (big limitation for us sound designers - though at least there is now a third party converter)

[redshift factor]

Thanks, guys!
So, now that's settled, what about surround sound? Yes or no?
And what's the max number of inserts per channel? Are they all pre-fader?

[LawrenceF]

... what about surround sound? Yes or no?

And what's the max number of inserts per channel? Are they all pre-fader?

You can answer a lot of these questions for yourself by erhmm... trying the demo for a few minutes?

[redshift factor]

... what about surround sound? Yes or no?

And what's the max number of inserts per channel? Are they all pre-fader?

You can answer a lot of these questions for yourself by erhmm... trying the demo for a few minutes?

So you don't know?

[LawrenceF]

So you don't know?

Sure I do, but at some point you need to do your own research.

Full Feature List: If it's not listed there, it probably doesn't have it. http://www.presonus.com/products/Softwa ... twareId=11

(click the "features" tab, anything red will be new in 1.5)

Manual: http://www.presonus.com/media/manuals/s ... manual.pdf

(a pdf search of "surround" comes back empty... do draw conclusions a search for "post-fader" talks about the master channel)

Demo: http://www.presonus.com/demo-studioone/

(install, play, learn how it works and what it can and cannot do and maybe even if you actually like using it or not, which if you don't would make the other stuff irrelevant)

Anything you can't figure out from those things I'll be more than happy to help you with.

[redshift factor]

I'm not going to install the 1.0.2 demo when 1.5 is being released probably sometime this week.

In fact, I probably won't install a demo at all, since I'm going to be upgrading my FireBox to a FireStudio anyways, and I'll get Artist for free with it, and from there, I'll upgrade to Pro for $199 if all goes well.

Switching to Studio One is pretty much a done deal, because it's really the only viable replacement for Cubase 5 (with VST3), and the situation of Cubase maxing out at only 30% load on my i7 is intolerable. Multicore scalability is utter shit on Steinberg products, and I do not hold out any hope that 5.5 is actually going to fix that once and for all. I've been with Cubase since 1997, so this is not a decision I've made arbitrarily.

So right now, I'm more or less in a planning stage, figuring out how I'm going to port all of my current Cubase projects over to Studio One Pro, so I can have a plan in place once I'm ready.

I'm pretty much just waiting on delivery of final Windows 7 drivers for the FireStudio line, which, BTW don't get me started on a rant about PreSonus waiting until Windows 7 was on store shelves before even starting to develop drivers for it..!

BTW, I did search the manual for surround and the maximum number of inserts per channel and came up short, which is why I was looking for confirmation from someone with hands on experience. These are the few things I wasn't able to find a definitive answer on, which is why I'm asking people who would know.

[LawrenceF]

So right now, I'm more or less in a planning stage, figuring out how I'm going to port all of my current Cubase projects over to Studio One Pro, so I can have a plan in place once I'm ready.

It loads Steinberg *.xml archives (and Sequel Projects) directly. It doesn't capture any plugs or instruments from Cubase to S1 though so you'll have to re-load those manually, but it will give you correct placement of any audio/midi.

Good luck.

[redshift factor]

Thanks a lot.
That is some very useful information.
That should make things go pretty quick, then I'll just need to import my plugin settings, which is all sorted out now that .fxb and .vstpreset has been confirmed.

The only real problem area is going to be the lack of proper drum maps.
Honestly that seems like a version 1.0 sort of feature.
I mean, we all use drums, right?

[koolkeys]

Thanks a lot.
That is some very useful information.
That should make things go pretty quick, then I'll just need to import my plugin settings, which is all sorted out now that .fxb and .vstpreset has been confirmed.

The only real problem area is going to be the lack of proper drum maps.
Honestly that seems like a version 1.0 sort of feature.
I mean, we all use drums, right?

Yes, but we don't all use drum maps. In all the years I've used various hosts, I have never once used them.

Many people do, but not everyone. Don't know why it matters. It IS a rather essential feature in the grand scheme of things, but not one that everyone will use(maybe even the majority will use it, though I don't know).

Brent

[redshift factor]

It IS a rather essential feature in the grand scheme of things, but not one that everyone will use(maybe even the majority will use it, though I don't know).

Well, Studio One does ship with Toontrack EZDrummer Lite. With so many drum hit articulations spread out all over the piano roll (and 8 different ways to hit a hi-hat), I would think drum maps are pretty essential for Toontrack products. Same goes for BFD, I'm sure. It's not just being able to name the hits, but also the ability to group drum kit articulations together (and out of chromatic order) that is so useful.

Maybe a simple drum machine style VSTi doesn't need drum maps, but modern virtual drum kit VSTi certainly benefit from them greatly.

[koolkeys]

It IS a rather essential feature in the grand scheme of things, but not one that everyone will use(maybe even the majority will use it, though I don't know).

Well, Studio One does ship with Toontrack EZDrummer Lite. With so many drum hit articulations spread out all over the piano roll (and 8 different ways to hit a hi-hat), I would think drum maps are pretty essential for Toontrack products. Same goes for BFD, I'm sure. It's not just being able to name the hits, but also the ability to group drum kit articulations together (and out of chromatic order) that is so useful.

Maybe a simple drum machine style VSTi doesn't need drum maps, but modern virtual drum kit VSTi certainly benefit from them greatly.

Well, I use BFD2 and have never used a drum map. I use other drum products as well, from Kontakt with Steven Slate Drums to Jamstix to Battery to EZ Drummer(one of the lite versions, the one that came with Virtual Instruments magazine), and others.

I'm not saying they aren't important, or that people don't use them. Just saying that not everyone does, including those like myself who work with complex drum instruments. Can't say that I've ever even had a problem keeping things straight. Then again, I don't typically program drum beats with my mouse, so maybe that's why?

Brent

[redshift factor]

I work in the piano roll editor quite a lot for drums.
Even if I input them by some other means - MIDI controller or e-drums - I still go in and delegate the hits out amongst the various articulations.
I find this to be particularly essential for realistic hi-hats.