KVR Audio

Aiynzahev · Post by **Aiynzahev** » Tue Jun 24, 2014 12:23 am

I am really looking forward to this. Even if it's a let down, I just want to see it!

hibidy · Post by **hibidy** » Tue Jun 24, 2014 6:59 am

That's the KVR spirt!

"even if it sucks, I want it!"

Sorry

JoseC. · Post by **JoseC.** » Tue Jun 24, 2014 8:06 pm

Muziksculp wrote:
JoseC. wrote:
LawrenceF wrote:
hibidy wrote:I remember when that came out. Johnny shot me down in flames when I brought it up over there back then aswell
Yeah.

There's only (technically) six more weeks of summer. Aug 1 is "Autumn / Fall" so ... if they don't announce it pretty soon, it's probably not happening in "the late summer".
Is it not summer until September 21st anymore?
September 21st is the last day of Summer

September 22nd is the first day of Fall/Autumn !

Xactly what I meant

tylerdurden91 · Post by **tylerdurden91** » Sat Jun 28, 2014 2:59 pm

I never advanced past Studio One(aside from free updates for it),as the included sound sets suck and the only real useful features of it for me personally...are using 3rd party freeware,mastering audio tracks and rendering MP3's.

Igro · Post by **Igro** » Sat Jun 28, 2014 8:32 pm

Maybe it's time to put some third-party plugins into S1? Like Cakewalk does. The only S1 plugins that I constantly use are ProEQ (i like it), FreqSpectrum and AmpSim.

The synths are one trick pony. I would like to see some good comps.

hibidy · Post by **hibidy** » Sat Jun 28, 2014 8:44 pm

I don't want it to become bloat.

Compyfox · Post by **Compyfox** » Sun Jun 29, 2014 6:10 pm

Neither do I.
We have a load of outstanding third party plugins on the market already.

What S1 might need, is:
- stability
- support of modern plugin standards (actual working VST3 comes to mind)
- suitable features in the songwriting section (MIDI editing, maybe something like the Chord Track from Cubase)
- similarities to VariAudio (I don't know if Melodyne/ARA is bundled or not) and proper time stretching functions (zplane's Elastique v3 is out by now)
- a pre-filter channel strip module (input gain, phase, LC/HC)
- low CPU/ASIO usage

Don't know at this point how well S1 works on multi-core CPU's or with "bridged" VST plugins (if it has a built in bit bridge). My encounters so far were short.

Who knows what S1 v3 might bring on that behalf. The first steps were already taken into that direction. Now they only need to be pulled off properly. Ideally before everyone else is overhauling their concepts.

trimph1 · Post by **trimph1** » Sun Jun 29, 2014 7:56 pm

S1 is stable here. I've loaded this bugger with plenty of instances of things like synthmadter and some freebie units and actually got no spiking.

SWallace · Post by **SWallace** » Mon Jun 30, 2014 1:52 pm

Compyfox wrote: What S1 might need, is:
- stability
- support of modern plugin standards (actual working VST3 comes to mind)
- suitable features in the songwriting section (MIDI editing, maybe something like the Chord Track from Cubase)
- similarities to VariAudio (I don't know if Melodyne/ARA is bundled or not) and proper time stretching functions (zplane's Elastique v3 is out by now)
- a pre-filter channel strip module (input gain, phase, LC/HC)
- low CPU/ASIO usage

Don't know what version of S1 you are referring to? VST3 has worked fine for me for almost 2 years. Can't speak for others. Melodyne is bundled in the Professional Version. Works like a dream. "Mixtool" plugin on S1 covers the pre-filter needs. CPU usage is good. Could optimize multi-core better. But don't know how much of that is the individual plugin and not the host?

Looking forward to S1v3! A chord track feature would be amazing.

Touch The Universe · Post by **Touch The Universe** » Mon Jun 30, 2014 1:58 pm

has nothing to do with this, but is there an easy way to copy all midi from one instrument to another without having to merge then select all then paste? Couldn't find any videos for this on yt.
Also is there something similar to cubase arranger track?

HobbyCore · Post by **HobbyCore** » Mon Jun 30, 2014 2:06 pm

SWallace wrote:
Compyfox wrote: What S1 might need, is:
- stability
- support of modern plugin standards (actual working VST3 comes to mind)
- suitable features in the songwriting section (MIDI editing, maybe something like the Chord Track from Cubase)
- similarities to VariAudio (I don't know if Melodyne/ARA is bundled or not) and proper time stretching functions (zplane's Elastique v3 is out by now)
- a pre-filter channel strip module (input gain, phase, LC/HC)
- low CPU/ASIO usage
Don't know what version of S1 you are referring to? VST3 has worked fine for me for almost 2 years. Can't speak for others. Melodyne is bundled in the Professional Version. Works like a dream. "Mixtool" plugin on S1 covers the pre-filter needs. CPU usage is good. Could optimize multi-core better. But don't know how much of that is the individual plugin and not the host?

Looking forward to S1v3! A chord track feature would be amazing.

Studio One's VST3 implementation is incomplete. You can use VST3 plugins, but you can not make use of everything the VST3 format has to offer.

CPU usage is not good on OS X. I've seen a few Windows benchmarks comparing Studio One with cubase, pro tools, samplitude, reaper etc.. and Studio One is usually in the middle of the pack. On OS X it often runs 60% less efficient than the next least efficient DAW. Really pitiful.

HobbyCore · Post by **HobbyCore** » Mon Jun 30, 2014 2:12 pm

mysticvibes wrote:has nothing to do with this, but is there an easy way to copy all midi from one instrument to another without having to merge then select all then paste? Couldn't find any videos for this on yt.

I don't understand why you have to merge. Select all on track, then alt/option-drag or copy/paste.

You could also duplicate the midi track and then route the duplicate to your instrument of choice.

mysticvibes wrote: Also is there something similar to cubase arranger track?

The project page is the closest that you will get in Studio One, and it's not very close.

Tracktion's edit clips, Reason's Blocks and Digital Performer's chunks are quite similar though.

dr4kan · Post by **dr4kan** » Mon Jun 30, 2014 2:16 pm

HobbyCore wrote: CPU usage is not good on OS X. I've seen a few Windows benchmarks comparing Studio One with cubase, pro tools, samplitude, reaper etc.. and Studio One is usually in the middle of the pack. On OS X it often runs 60% less efficient than the next least efficient DAW. Really pitiful.

probably not good on your OSX. Here I have S1, Cubase 7.5 and Logic X and S1 more CPU friendly than Cubase. Just Logic X performs (slightly) better.

Touch The Universe · Post by **Touch The Universe** » Mon Jun 30, 2014 2:22 pm

Thanks so much Hobby Core, that is exactly what I was looking for. Studio One is becoming my favorite DAW lately and impressed with the things you can do with it and its ease. Peace~Tim

HobbyCore · Post by **HobbyCore** » Mon Jun 30, 2014 2:28 pm

dr4kan wrote:
HobbyCore wrote: CPU usage is not good on OS X. I've seen a few Windows benchmarks comparing Studio One with cubase, pro tools, samplitude, reaper etc.. and Studio One is usually in the middle of the pack. On OS X it often runs 60% less efficient than the next least efficient DAW. Really pitiful.
probably not good on your OSX. Here I have S1, Cubase 7.5 and Logic X and S1 more CPU friendly than Cubase. Just Logic X performs (slightly) better.

Note that I referenced benchmarks, not my own testing. You can see a representative benchmark here http://www.dawbench.com/win7-v-osx-5.htm

You could do a formal test yourself with the projects listed here http://www.dawbench.com/benchmarks.htm . Now, to reference my own testing, Studio One 2.6.2 is still significantly less efficient than every other DAW that I've tested on OS X (I was unable to test Cubase, but I did manually duplicate the project for Digital Performer). I did this within the last 3 weeks on a brand new i7 iMac with a fresh install of Mavericks.

It's also worth considering the anecdotal data. A lot of people have complained about Studio One's poor performance on OS X relative to other DAWs. This thread alone demonstrates that.

Note that these discussions hinge around how much load before a DAW shows an error (buffer underrun or similar). NOT how much cpu usage is reported. Studio One may show cpu usage on par with other DAWs, but it begins to error at much lower loads, lower buffer sizes and with fewer plugin instances.

Studio One 3?