- Messages
- 6,551
Puke react!
A not quite as scientific as I'd like DAW CPU usage comparison
- Thread starter Orvillain
- Start date
- Messages
- 6,551
Reaper 7.0 default theme:
There are sooooooo many problems with this in my opinion. It's borderline abusive.
Studio One default look:
And with the meter bridge and small channels:
Everything is pretty clear. No weird alignment issues, buttons don't jump around randomly based on the size of the track headers. The mixer gives you professional features like ... erm... dB markers on the meters... because why would you ever not want that... There's loads of small workflow-y things that a screenshot cannot convey. Like selecting multiple tracks and inserting the same effect onto each one of them all in one quick motion.
Studio One has very very nice workflow.
Cubase Pro 13:
And the mixer:
And colourising the channels:
This is probably my favourite software mixer across any package out there. The meters are super clear and readable, very informative. Being able to hide away stuff you don't need at any given time, just makes the whole thing a joy to use.
Reaper just doesn't even compete with Studio One and Cubase, in my honest opinion. It has so many workflow niggles, look and feel mistakes, and on the whole as a software package, it just sort of .... I feel like it hates the user and wants me to die.
There are sooooooo many problems with this in my opinion. It's borderline abusive.
Studio One default look:
And with the meter bridge and small channels:
Everything is pretty clear. No weird alignment issues, buttons don't jump around randomly based on the size of the track headers. The mixer gives you professional features like ... erm... dB markers on the meters... because why would you ever not want that... There's loads of small workflow-y things that a screenshot cannot convey. Like selecting multiple tracks and inserting the same effect onto each one of them all in one quick motion.
Studio One has very very nice workflow.
Cubase Pro 13:
And the mixer:
And colourising the channels:
This is probably my favourite software mixer across any package out there. The meters are super clear and readable, very informative. Being able to hide away stuff you don't need at any given time, just makes the whole thing a joy to use.
Reaper just doesn't even compete with Studio One and Cubase, in my honest opinion. It has so many workflow niggles, look and feel mistakes, and on the whole as a software package, it just sort of .... I feel like it hates the user and wants me to die.
- Messages
- 6,778
Not sure what you mean? I use Studio One (6) but haven't experienced anything weird with Native.
TheTrueZoltan!
Shredder
- Messages
- 1,825
Activate low latency („Z“) monitoring on the track that has Helix Native on it, play guitar and then tweak some settings in the plugin. You should not hear any changes to the sound as long as Z is engaged. This behavior has been confirmed by a lot of users.
I think your test is comparing different performance tradeoff schemes in different DAWs when it is difficult to know if you're comparing apples to apples. It's hard to compare performance when ultimately the only metric that really matters is: how much processing can you do before getting dropouts?
SillyOctpuss
Shredder
- Messages
- 1,941
Seeing as someone else resurrected the thread. Did you make the move to Cubase and have you stuck with it?
- Messages
- 1,661
Something you can do to help with "glitching in the audio / sucking too much processing power" when doing a session with a huge number of tracks is "freeze" select tracks with plugins on them to lower the processing power draw.
Pretty sure most DAWs have this "freeze" capability. All "freeze" does is process the specific track with the plugins applied and temporarily create a (most likely) .WAV file; ready to go. Obviously, playing a straight-up .WAV file is much less processor intense versus playing a .WAV and processing the plugins over it.
If you need to tweak the track, just "unfreeze", tweak, then "refreeze" when done.
Pretty sure most DAWs have this "freeze" capability. All "freeze" does is process the specific track with the plugins applied and temporarily create a (most likely) .WAV file; ready to go. Obviously, playing a straight-up .WAV file is much less processor intense versus playing a .WAV and processing the plugins over it.
If you need to tweak the track, just "unfreeze", tweak, then "refreeze" when done.
