STUDIO 1 Tip of the week

Anderton has been using the SO Project page for mastering for some time, so it's no surprise that he'd look for another DAW through which to monetize his contributions (you know, the ones the rest of us make for free). Not talking about the initial release; consider the Big Book of SONAR Tips. He cobbled together Vol. 2 after Cakewalk'd the plank. Peeps bought it. Whatever.

JonD

JohnEgan
Otherwise it was somewhat disturbing to read S1 is somewhat behind in multi-core CPU processing use?
 

I've read inklings of this before... Is there a specific (recent) thread where you saw this?

Mostly addressed in SO v3.5. There is still more to do, but it is much, much better than it was.
 
Dan

JonD

JohnEgan
Otherwise it was somewhat disturbing to read S1 is somewhat behind in multi-core CPU processing use?
 

I've read inklings of this before... Is there a specific (recent) thread where you saw this?

 
http://answers.presonus.com/10836/multicore-support-needed-especially-for-multi-instruments
 
 

CPU distribution has been improved in a recent update.  You have to understand too that they distribute CPU usage across tracks and buses. Not wise to say put 6 CPU intensive plugins in a row on a track. Better to send the track to a buss and put some of the more intensive plugins there.
 
With care very large sessions can be easily handled.
 
Maybe you should check this out if you are worried:
 
https://www.youtube.com/w...=5zhXijvtkNc&t=65s

There is also a great feature too when you double click on the little CPU meter down the bottom a large window pops up and shows every plugin and every resource being used and a little bar graph against every one.  Often it is only one or two things that can be chewing things up.  Rendering these things out is super fast in Studio One.
 
When converting midi parts with virtual instruments to audio as well there are options there that allow you to go back at anytime after a complete render.  Virtual instruments are rendered out to audio, the midi file is set aside and muted.  But later with one click you can instantly go back to the Midi file with the virtual instrument again in order to edit the music etc..
 
Mai Tai can be a resource hog but doing simple things like simply altering the ADSR settings so that less voices are overlapping will greatly reduce the amount of CPU it uses.  Choosing your voicing carefully as well really helps.  You don't need 6 voices for example to state a minor 9 chord either.  You can state virtually any chord with a bass note and 3 voices.  It sounds better too. 
 
There are also Mai Tai quality options too which often will sound identical but use less CPU.