-AutoAdjustMacroMappingRange will make it so that when you map a parameter to a macro control, the current value becomes the minimum value of the newly-created mapping (rather than 0). I prefer enabling this option because it streamlines workflow by helping to map macros faster, saving the step of typing in the minimum value when it is already in place.
With -AutoAdjustMacroMappingRangeoff, when mapping a parameter to a macro control, it will always result in a range of “min” to “max”, ragardless of the current position.
Say i want to map a parameter to a macro, and i want it to range specifically from 37 to 127.
With -AutoAdjustMacroMappingRange set to off, i would first have to map the parameter, click “map”, and then edit the minimum value to be 37.
However, with -AutoAdjustMacroMappingRange set to on instead, by mapping it, the minimum value will automatically be set to the current value (in this case 37), while the maximum will default to 127.
For cases where the maximum is meant to be 127, this reduces the mapping process to a single quick step, without even needing to open map mode. Other types of mappings might still require turning on map mode to adjust the values, but will still save a step of action if you map it while the current value matches one of the target values.
The unprocessed screengrab below demonstrates various mapping strategies, depending on what you want the minimums and maximums to be.
. . .
NOTE: i believe that a recent update of Live 10 enables AutoAdjustMacroMappingRange by default, whereas in previous versions it was off unless you enabled it manually. Either way, it’s handy to know that you can change it around when desired. Just remember that if you do change it, you’ll have to restart live for the change to take effect (i think).
“How the heck do i implement this?” you might ask. To answer that and for more swag info about Ableton Live’s mysterious Options.txt, Madeleine Bloom’s series on the topic is highly recommended.
So you’re working on a song and you’ve found a frequency which you want to adjust. Let’s say you want to nudge down 4.4k a little bit to reduce a bit of harshness. Now you ask yourself: what type of EQ should be used?
As time passes by, there becomes more and more dynamic EQ plugins available. Besides, in Ableton, Bitwig, and other DAWs, it’s easy to make any automatable EQ plugin act as dynamic by the use of envelope followers. On the other hand, when using a dynamic EQ plugin, there may be times when you want to use the bands as typical, with no reactivity. So, we have a pretty much open choice of whether to use a static or dynamic EQ on a track we’re working on. So what to do?
Brand new plugins… promotional sales on plugins… they are SO tempting. But do you really need that new compressor plugin that just dropped?
In order to assess which plugin types are lacking in your toolbox, i recommend making a spreadsheet of all the plugins you own by category. You might discover, as i did, that you have such a vast variety of compressor options to choose from, it’s likely that you won’t benefit a whole lot from purchasing any more of them. You also might discover, like me, that you’re somewhat lacking in gate plugins, and could indeed benefit from picking up a few new models. Etc… Continue reading →
True Peak Limiting is a method by which a limiter adjusts for how the digital waveform will be reconstructed by playback systems which can result in actual peak levels above 0dB even when the digital peak level is technically shown at below 0dB.
Basically the way intersample peaks occur is that the quantization points of a digital waveform can at times imply a curve between them which goes up a little bit higher than those actual sample points, resulting in a louder-than-expected actual peak level coming though.
To imagine it, just draw two dots in your mind, and then instead of drawing a straight line between them, draw a slightly curved line. The two dots are at a height of zero, and the curved line connecting them is bumping a little bit above zero. See?
I found some old notes i had taken (for my own reference) about the parameters of Ableton’s Gate audio effect plugin and figured others could use the info as well, so i’ve polished ’em up, expanded on them a bunch, and dropped them here for you.
I’ve found that getting to know exactly how each parameter works with gate plugins leads to attaining desired results exponentially easier, and in particular learning how the more exotic parameters such as lookahead and hysteresis work facilitates sophisticated gate optimization.
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.