You happy with Studio One 3?

[nostradamoose]

None of that matters when a user can load up Cubase or DP or Logic and get better performance on the exact same system.

"a user", meaning you. Most people don't have the "issues" you are having in S1. There are plenty of Mac users that are working comfortably and happily inside of S1.

Please try to avoid speaking for everyone when it comes to personal experience that is determined by system specs, user operation and skill level.

Just because you don't like it, had bad experiences or it doesn't work for you, doesn't mean it's S1's fault.

[beatmangler443]

I think sometimes also issues with studio one have to do with some people having an underspec computer or is to old.

Yes, a lot of beginners/non-technically inclined users don't even know the difference between a laptop CPU and a Desktop CPU. They figure that it says i7, i5 or i3 so it must be of equivalent specs, this is more of a marketing trick then anything.

There are a lot of users that make a lot of transpose, pitch, time stretch and other processing changes to tracks without bouncing them. After a while a huge accumulation of these tracks along with Melodyne and events effects start to take their toll on the processor. Because they are asking S1 to keep up with these processed tracks in real time, instead of bouncing them down.

They also like to blame 3rd party plug-in compatibility on S1 crashing, this is probably the biggest issue.

Most of the problems are from Mac users because they have the worst specs for operation. The integrated graphics with lack of memory is only the beginning.

None of that matters when a user can load up Cubase or DP or Logic and get better performance on the exact same system.

If it's giving you those issues why aren't you using the DAW's you mentioned?

[Robert Randolph]

I think sometimes also issues with studio one have to do with some people having an underspec computer or is to old.

Yes, a lot of beginners/non-technically inclined users don't even know the difference between a laptop CPU and a Desktop CPU. They figure that it says i7, i5 or i3 so it must be of equivalent specs, this is more of a marketing trick then anything.

There are a lot of users that make a lot of transpose, pitch, time stretch and other processing changes to tracks without bouncing them. After a while a huge accumulation of these tracks along with Melodyne and events effects start to take their toll on the processor. Because they are asking S1 to keep up with these processed tracks in real time, instead of bouncing them down.

They also like to blame 3rd party plug-in compatibility on S1 crashing, this is probably the biggest issue.

Most of the problems are from Mac users because they have the worst specs for operation. The integrated graphics with lack of memory is only the beginning.

None of that matters when a user can load up Cubase or DP or Logic and get better performance on the exact same system.

If it's giving you those issues why aren't you using the DAW's you mentioned?

You're free to go to my blog and find out. I've already written quite a lot about it. (Hint: I don't talk about CPU issues, I wonder why?)

[Robert Randolph]

None of that matters when a user can load up Cubase or DP or Logic and get better performance on the exact same system.

"a user", meaning you. Most people don't have the "issues" you are having in S1. There are plenty of Mac users that are working comfortably and happily inside of S1.

Please try to avoid speaking for everyone when it comes to personal experience that is determined by system specs, user operation and skill level.

Just because you don't like it, had bad experiences or it doesn't work for you, doesn't mean it's S1's fault.

I suggest googling something like "Studio One Mac CPU". Maybe throw in the word 'spike', or leave out the word 'Mac'.

I don't even have this issue, but it's certainly a problem that is unique to a single user (nor is universal).

I am somewhat confused how you seem to think that by saying "a user", that I'm referring to all users or to myself even. Perhaps some language barrier is getting in the way or something.

[beatmangler443]

I think sometimes also issues with studio one have to do with some people having an underspec computer or is to old.

Yes, a lot of beginners/non-technically inclined users don't even know the difference between a laptop CPU and a Desktop CPU. They figure that it says i7, i5 or i3 so it must be of equivalent specs, this is more of a marketing trick then anything.

There are a lot of users that make a lot of transpose, pitch, time stretch and other processing changes to tracks without bouncing them. After a while a huge accumulation of these tracks along with Melodyne and events effects start to take their toll on the processor. Because they are asking S1 to keep up with these processed tracks in real time, instead of bouncing them down.

They also like to blame 3rd party plug-in compatibility on S1 crashing, this is probably the biggest issue.

Most of the problems are from Mac users because they have the worst specs for operation. The integrated graphics with lack of memory is only the beginning.

None of that matters when a user can load up Cubase or DP or Logic and get better performance on the exact same system.

If it's giving you those issues why aren't you using the DAW's you mentioned?

You're free to go to my blog and find out. I've already written quite a lot about it. (Hint: I don't talk about CPU issues, I wonder why?)

No thanks.

[kevvvvv]

Robert Randolph

So could you folks that are unhappy with Studio One's midi give me 5 specific things that you find problematic with it?

Not unhappy.

Quite the opposite.

But there's always room for improvement.

What's been Presonus' reaction when you've written to them with your complaints?

Are they warm or dismissive towards what you've been saying?

[nostradamoose]

You're free to go to my blog and find out. I've already written quite a lot about it.

Seems like a radical step to be taken to express your personal experiences with a piece of software.

If better performance over another piece of software was the only determining factor, we'd all be using something light weight like Reaper, but that's just not the case.

The DAW of choice should offer you a comfortable and cohesive environment that has a work flow that fits with the user's creative process.

Performance can simply be increased by techniques of bouncing/freezing tracks and using efficiently programmed plug-ins, adding DSP hardware or upgrading your system.

There are a lot of users out there that don't really understand how much real time processing is going on under the hood of these extremely technical applications.

[Robert Randolph]

You're free to go to my blog and find out. I've already written quite a lot about it. (Hint: I don't talk about CPU issues, I wonder why?)

No thanks.

I'm glad I didn't take the time to reply here then. You're disinterest in people responding to questions you ask has been noted.

Robert Randolph

So could you folks that are unhappy with Studio One's midi give me 5 specific things that you find problematic with it?

Not unhappy.

Quite the opposite.

But there's always room for improvement.

What's been Presonus' reaction when you've written to them with your complaints?

Are they warm or dismissive towards what you've been saying?

Someone from Presonus actually had contacted me directly a couple months ago and helped me out with some things that I was having trouble with. The contact was made purely based on some of the blog posts I had written (and this was before it was linked in my signature).

Then 2 updates came out that resolved both bugs and workflow issues I had complained about. Particularly v3.3 being notable. I doubt I'm the only influence on this, but it is nice to think that maybe I made a small difference.

There are most certainly people there that care.

I've been using S1 actively since V2 (and I've owned it since Day 1), and at this point it's comprehensible that I could almost happily use it for all my work.

If you're interested, I do cover some of my thoughts recently here: http://admiralbumblebee.com/music/2016/ ... xtend.html

P.S. No, my blog isn't just about S1. Every month I take one habit or non-habit and I reverse it. I stick to doing 1 specific thing for 1 month. For 3 months I did all the work I could possibly manage in a different DAW that I primarily use. I wrote about those experiences on my blog. Studio One was probably the most well-documented.

[kevvvvv]

Robert Randolph

I doubt I'm the only influence on this, but it is nice to think that maybe I made a small difference.

You probably do make a difference.

There's always one curmudgeon in the vanguard of generating change, and the rest of us all need you and a handful of similarly committed others for this.

I couldn't do it, cos I'm generally too pleased with what I've got, and buy in heavily to nostradamoose's comment about a comfortable and cohesive environment that has a work flow that fits with the user's creative process.

But soldier on and be damned. Presonus prob know you better than you think because you're consistent in what you say

[kevvvvv]

btw all

presonus have just this minute issued a new crossgrade offer to get people to migrate to S1 Pro

info here https://shop.presonus.com/products/soft ... Crossgrade

[nIGhT-SoN]

Studio One is quite bad at using multiple cores, especially on virtual instruments. I just did a test using Serum in S1 and Bitwig. S1 uses only first core and I get really fast to drop outs with pads. Bitwig on the other hand it splits the load evenly on all cores and I can play that pad very easily with like 50% cpu load.

[Guenon]

The DAW of choice should offer you a comfortable and cohesive environment that has a work flow that fits with the user's creative process.

I agree. In that sense, when the CPU performance of a DAW (or any tool of such importance) is bad, it might be outweighed by the actual functionality and user experience it offers. Then it's a case of a successful compromise. However, it's quite lucky if one finds a comfortable and cohesive experience that fits one's creative process, in a DAW that also performs very well !

[beatmangler443]

Gotta give presonus some slack. Still haven't been around that long. Look how long how long it took them to fix the disc overload and cpu spikes.

[c_voltage]

I forgot to say, also in v2 was useful RAM and latency meters always on main panel. In v3 latency meter was moved to perfomance subscreen, what is quite inconvenient for control it in realtime, and RAM meter was removed at all (i understand that it 64 bit, but I do not find it logical, considering size of some kontakt instruments for example).
Of course, all this is not as critical, but it was more comfortable.

[Guenon]

Gotta give presonus some slack. Still haven't been around that long.

It's kind of like that, but it's also the image they want to build upon. The development started as a student thesis in 1999. In 2004, an overhaul began, to bring it onto a new codebase. In 2006 it was made the property of an official company (KristalLabs) which had associations to Cubase and Nuendo through a co-founder. Then, in 2009 that company became "Presonus Software", and the product was named Studio One.

http://www.kristallabs.com/

In what ever way one wants to look at it, they have been around long enough not to be a "new underdog" anymore. Comparable to the length of Ableton Live's history, for example.