There are not many controls for digital plugins where i prefer stepped options as opposed to continuous values, but the Q factor of EQ slopes is one of those that generally i do. Not really sure why i prefer them that way; i suppose there are a few reasons.
Regardless, i made myself (and you!) up a nifty spreadsheet of “Go-To Q Values”, based on logarithmic steps between the basic Q value(0.70607) and the minimum or maximum ranges. These Q values are optimized for Ableton Live’s EQ Eight, but can be applied to most any parametric EQ, when you want no-brainer go-to Q values to fall back on.
Just disable VST plugins during times in tracks when they are not being used.
Automate the nifty device activator (aka “on/off switch“) of a device (or a rack of devices) to shut off during times of silence. Set the automation to switch on a little bit before audio starts, and to turn back off a bit after the audio is completely silent again.
Have you ever wanted to use Ableton live just to drop a bunch of tracks into session view and have them play randomly like a shuffle playlist in a media player?
Natively, you could always use follow actions for each clip to trigger random other clips after a set number of bars. However, this only works with warped clips. What if we want the next clip to trigger once the one currently playing ends, regardless of how long it is?
A nice solution (assuming you have MaxForLive) is to use the Follow CLIP device from Isotonik Studios. Simply place your group of adjacent clips together on a track in Session View, drop Follow onto the track, select the options shown below, and hit play on the first track you want to launch. As soon as the track ends, it randomly selects and starts playing another one in the batch. Woohoo!
There’s some ambiguity between the terms gain, level, and trim. In general, they are used interchangeably. But sometimes they are different; for example, guitar amps often have both gain and level controls.
I won’t attempt to provide the ultimate absolute definitive official definitions of those terms. I’ll just tell you how i tend to use them. Continue reading →
So this one is super simple, but definitely helpful as a workflow enhancer. Applies to any VST-capable DAW.
It’s always annoying when bringing one plugin GUI into focus obscures another GUI and then you have to shuffle things about.
This tip applies when you have too many plugins open to fit them all onscreen without overlapping or when you’re not sure how many more plugins you might need to add in a project; it’s not needed when you have few plugins and enough screen space to comfortably them fit all.
So there’s this issue with fading between chains in a rack in Ableton Live which i haven’t heard much mention of. Perhaps you’ve noticed it?
Say you have a rack with two chains, let’s call them “A” and “B“.
Starting to Set Up our Chains
Using the Zone Editors in the Chain Selector Editor of the rack, we’ll place A on the left (full at 0), fading out the other direction. Vice versa for B, placing it on the right (full at 127) and fading out towards the left.
A … fades to B
Now let’s map the Chain Select Ruler to the first Macro.
Macro Control to Fade between A and B
Macro 1 will now give us a nifty fader knob between whatever processing we place on chain A versus whatever we place on chain B.
Kind of like every human being has a height value, every audio clip has a peak level value. So what can we do with that information, beyond knowing that going above 0dB usually isn’t advised? In our eternal quest for ultimate audio quality, the inclination can be inherent to record loudly—as close to 0dB—as possible, and thereafter maintain that peak level. We fear that by mixing with track levels that are too quiet, we might be losing fidelity, some harmonic detail in the saturation floor or something.
While it is true that recording analog signals as loudly as possible without signal clipping to begin with will indeed minimize noise floor, the benefits reaped by maximizing peak level for individual tracks tapers off as you get closer to zero. At what peak level are audio sources louder than they really need to be? At what level are they too quiet, that they might need to be boosted excessively later? Using an algorithm based on the energy of how sounds stack together, i devised a set of go-to ranges for peak levels based on track counts. Since peak levels can vary fairly wildly based on content, you are given minimums and maximums (instead of single target values). Juicy details ahead…Continue reading →