Working With Automation
I find in general that there are usually 2 school’s of thought when it comes to automation, or more specifically - when it comes to recording / writing automation. Those who like to draw everything in perfectly, and those who prefer to record it in using a controller, or at the very least using a mouse.
I myself, am comfortable doing either method, but usually prefer to get some sort of hands on control whenever possible.
But have you ever felt like the result of your record pass isn’t quite what you performed?
Too Many Nodes - or Not Enough?
If you are part of the camp that likes to record in your automation manually using a controller of some sort, I’m almost certain that at some point you may have found yourself in either one of these 2 situations:
The automation has too many unnecessary nodes (breakpoints)
The automation doesn’t reflect the exact performance that was recorded! ie: It doesn’t have enough.
As most of you know - I come from a Pro Tools background, and in Pro Tools, we had a preference that allowed us to deal with this scenario that gave the user the option to “thin out” the automation at varying levels after each pass.
In case you weren’t aware - this is actually something that was recently added to Studio One in one of the final updates to Studio One Version 3’s life cycle.
In this video I demonstrate the recently added "Reduction Level" setting in PreSonus Studio One's Automation preferences. More specifically, what it's meant for - and when (and why) to use it.
And as always, if you enjoy this content, please - Share, Subscribe, and hit that like button. :)
Cheers, Marcus
