Yep,i have been saying this for a few months here,people want to crucify me for stating the facts.
I can do 1/5 of things with S1 that i can do with cubendo.
I do heavy projects,200-300 tracks,a lot of reverbs,plugins,50+ groups,dozens of buses,automation.
Honestly id be mad as hell if i bought S1 and got a daw that is not fully developed,doesnt deserve to be called pro.
In this regard Reaper is a much wiser choice for serious producers on a budget,especially power users.

 

Last edited by a moderator: May 28, 2016

Well, I guess Steve Winwood is not a VSTi power user. As I can see on his screen, James Towler have to deal with audio files only, and audio files doesn't require much CPU resources.

 

Not a valid argument.
When power users like tom holkenborg switch to s1 i may take a listen.
No one in the movie scoring industry uses s1.

 

Memetest86: made with all 10 test types, this means more or less 5 hours.....no intel here, ATI radeon HD2600, never had any issue with SO 2.6
Intel chipset is Z87, Intel(R) Management Engine Interface V9.5.14.1724 for Windows 7/8/8.1 32bit & 64bit
No pops or cracks when CPU load is at 50%, only the AM hanging ater some time

By the way....I rendered some Omnisphere 2 tracks (as I told before I found a strange automation in one or two of these, created by omnisphere itself, I think - I didn'do anything further - panning them to only one side), also rendered some izotope fx, and now the project seems to work

Finally: it's really strange that very few people complain about bad CPU management at presonus forums.......maybe they are not professional

 

Last edited: May 28, 2016

Not for power users?
Video:
Stevie Winwoods house engineer moved over to Studio One from Pro Tools

 

Cool!

 

I have noticed that the CPU meter seems to jump a lot higher, a lot faster than it does in Live. For instance, I'll run several instances of Omnisphere, some of them multis, usually two or three Serum and Harmor. FX chains on every drum sample/synth. For FX I use a lot of Soundtoys. etc. etc. And I really almost never think about CPU in Live. I have a quad core i5 - which is obviously not top of the line anymore but is solid enough. My CPU in Live almost never goes above 50%

In Studio One I can get to 30-40% easily just by mixing a vocal project with a bunch of tracks. However, I read somewhere that this is because Studio One's CPU meter functions differently. Someone said something to the effect of, it measures the thread or core (or whatver, I'm not especially computer literate) with the largest load on it and displays that. I've never experienced any actual adverse effects from Studio One's ostensible CPU management problems.

I'm not really defending it. Just curious, because I've heard about memory leaks and such, but none of it seems to affect me. And S1 never ever crashes on me except when I was trying out some early AudioUTOPiA releases that by necessity could not be adequately tested.

 

PreSonus Studio One 3 PRO v3.2.2.37876 Should anyone require it. Again please accept my apologies if im not supposed to post links etc. I will not do anymore if it becomes apparent that i shouldnt be doing it, i simply want to share and give people the opportunity to experience software before shelling out sometimes hundreds of pounds/dollars etc for it. Thanks x

No Links Allowed To Warez

 

Last edited by a moderator: May 30, 2016

Nice, so you chimed in just to push your upload of Team R2R's work...
@Deejay1210

 

For normal projects S1 is perfectly ok,most people shouldnt notice anything out of ordinary.
People who do film scoring,sound design,large projects should test it before buying.

 

 

Last edited: Jun 2, 2016

You expected to be welcomed like a savior, while it was apparent that you were acting against a rule you knew perfectly well.
And now that little paltry revenge...
Keep your toys for yourself, we've already enough tools to achieve every of our projects until the end of time.

 

Friend of mine made a little experiment according to CPU load with different DAWs in their latest versions (on Macbook Pro 2012, 2 GHz i7, 16 GB RAM, SSD HDD, OS X 10.9.5). As you can see - the CPU performance on Studio 1 3.2.2 is really really weak :-( I love that DAW - but it isn't for bigger projects (without using UAD cards etc). It was really simple audio session with one audio region with 4 plugins on it and few automations. Try to compare the CPU load of Studio One and Reaper (in other words "the worse one" vs "the best one" in this test). Come on Presonus - wake up! That's a shame.

Studio One:



Cubase:



Pro Tools:



Logic:



Reaper:

 

Last edited: Jun 2, 2016

Von_Steyr: As i read, are you the owner of the full version of Studio One? If yes, do you think it's possible to repost my post at official presonus studio one forum? I'm the demo user only and there are the restrictions for writing feedbacks. Thanks a lot

 

Mate, your effort is really appreciated, but believe me, they know, they know it. The problem, I think, is that to have a dynamic CPU allocation (or any other ****ing trick to optimize its load) probably requires a deeeper sw rewriting.........
They could at least make something to avoid that freezed sw didn't require to wait hour to unlock the PC or a full restart
By the way, are we sure that these CPU load meters are all working in the same way giving comparable results?

 

Last edited: Jun 2, 2016

As Pereira said,they are perfectly aware of what they have developed,they know.
They are adding more and more features,while suffocating the cpu even more,the console shaper can fuck you up before you even start properly.
People are now waking up and realizing something is not right.

 

Last edited by a moderator: Jun 2, 2016

Studio one has a fast workflow, so does have any other daw. But unlike others S1 is easy to learn because the workflow is logical. This is 'my' observation however I stand corrected. There is no doubt and without slightest hesitation I can say it is a CPU hog. I have been using it since it came out so it's not that I have installed it just yesterday. I go mad when I see memory leakage and CPU performance. I bang my head when it freezes at the height of my projects. I have to painstakingly create sub-projects like A, B, C,...of the same project. But I still love the quick(est) workflow it provides. I have done A/B of it with Reaper. Reaper loads vsts' like breeze, consumes less CPU, up and running like lightening power. However it requires a lot of learning which is time consuming for me (bad on my part). I am willing to put my time in learning Cubase instead when I would buy it. However, Reaper is a beast which has to be trained by you; a mighty daw that could be modified to death. Alas the workflow, routings, deep midi functions are not as conventional as Cubase or S1 has to offer which is again a not so good point (for me).

OP you might be having some hard time ahead checking plugins one by one unfortunately. Sometimes back I had quickquak reverb installed and loaded which caused S1 to behave half of what you have stated until I found it and completely got rid of it. Also clean the cache (ccleaner), as well as old projects (delete or move them to other place) to let S1 make a new imprint. See how it goes.

 

Last edited: Jun 4, 2016

I'm really into Logic (and partially into Studio One) – hitting the 100 % of CPU performance meter means no realtime playback in both DAWs. The Logic's CPU load is aprox. 10 % on that picture vs. 78 % with using of Studio One - a big big difference there. It's impossible to recreate any 30–40+ % CPU load Logic's project within Studio One, that's pity .... i've been logic user since version 3 (many years ago), i know it well, but it's impossible to rely on it in many cases :-( So - i'm looking for something better (in most aspects) but it's hard as i see

 

Hmmm we are nasty hateful pricks you say? Read your post again.

 

Don't get too sensitive and as you have stated in your posts that you were not aware of the rules is fair enough on your part. Welcome aboard!

Guys don't be judgemental from just one post of someone. Give some benefit of doubt at least.