Become a member
Become a member
Continuer avec Google

or
Log in
Log in
Se connecter avec Google

or
learning

The traps of automation - Glitches and clicks

A guide to mixing music - Part 118

Today I'll write the second part of our brief compilation of the most common mistakes and issues when dealing with automation.

View other articles in this series...

Die Hard

Apart from the issues related to routing, another very common problem seems to be the frequent appearance of glitches or clicks as a consequence of automation. This phenomenon arises mainly in two situations: The first one is when two automation events happen at the exact same time, which is visually represented with a vertical line in your automation curve. This means that the automated parameter goes from one value to the other in a discontinuous way. The more significant the value jump, the riskier it is for artifacts to happen. A textbook case is the automation of the volume fader going from 0dB to -∞ right at the middle of an audio file. This would equate to cutting off the waveform just like that, without a fade out and with the obvious result of a click.

There are two ways to solve this: try to space a bit the automation points so the transition between values is more progressive. Or make the abrupt changes when the track in question is completely silent.

Automation glitches

The second situation is linked to the first one in a way and has to do with the automation of settings that only toggle between two states, like the mute button of a track or the bypass of a plug-in. As explained above, the change between values is quite radical, which can result in some sort of artifact. But in this case you can't simply create a fade out, given the toggle nature of such parameters. The good news is that if your DAW and plug-ins are well-conceived, you shouldn't have any issues. The bad news is that if that's not the case there isn't much you can do about it. The best thing you can do is look for an alternative solution to get the desired result. For instance, you could make a quick fade in rather than using the Mute button, or if the plug-in features a dry/wet parameter automate it instead of using the bypass switch. And if there is absolutely no other option, you could always go more radical and render the track in question with the automation and then manually do away with the click using the tools available in your DAW (scissors, trim, fade, etc.).

And to finish this article, one last remark. Don't forget that the whole idea of automating something is that later on you won't need to have your hands on it. This doesn't mean you can't modify it afterwards, but that might prove to be a bit more complicated than directly altering the parameter with the mouse, for example, the Trim automation mode or even deactivating the automation reading. If you were asking yourself why hadn't I dealt with automation earlier, now you know!

Next time I'll give you some last recommendations regarding automation.

← Previous article in this series:
The traps of automation - Part 1
Next article in this series:
Last advice on automation - Part 1 →
  • John Kelly 7 posts
    John Kelly
    New AFfiliate
    Posted on 02/27/2017 at 17:27:27
    Great lesson here.
  • Nantho Valentine 336 posts
    Nantho Valentine
    Author
    Posted on 03/01/2017 at 08:37:28
    Thanks ;)

Vous souhaitez réagir à cet article ?

Log in
Become a member
cookies

We are using cookies!

Yes, Audiofanzine is using cookies. Since the last thing that we want is disturbing your diet with too much fat or too much sugar, you'll be glad to learn that we made them ourselves with fresh, organic and fair ingredients, and with a perfect nutritional balance. What this means is that the data we store in them is used to enhance your use of our website as well as improve your user experience on our pages (learn more). To configure your cookie preferences, click here.

We did not wait for a law to make us respect our members and visitors' privacy. The cookies that we use are only meant to improve your experience on our website.

Our cookies

Cookies not subject to consent

These are cookies that guarantee the proper functioning of Audiofanzine and allow its optimization. The website cannot function properly without these cookies.

Website preferences

We store your preferences so that you do not have to re-enter them every time your come back (forums options, dark or light theme, classifieds filter, standard or buzz news, newsletters popups...).

Log in

This one makes sure you don't have to re-enter your credentials every time you visit Audiofanzine.

Analytics

This data allows us to understand the use that our visitors make of our website in an attempt to improve it.

Advertising

This information allows us to show you personalized advertisements thanks to which Audiofanzine is financed. By unchecking this box you will still have advertisements but they may be less interesting :)

We did not wait for a law to make us respect our members and visitors' privacy. The cookies that we use are only meant to improve your experience on our website.

Our cookies

Cookies not subject to consent

These are cookies that guarantee the proper functioning of Audiofanzine and allow its optimization. The website cannot function properly without these cookies.

Website preferences

We store your preferences so that you do not have to re-enter them every time your come back (forums options, dark or light theme, classifieds filter, standard or buzz news, newsletters popups...).

Log in

This one makes sure you don't have to re-enter your credentials every time you visit Audiofanzine.

Analytics

This data allows us to understand the use that our visitors make of our website in an attempt to improve it.

Advertising

This information allows us to show you personalized advertisements thanks to which Audiofanzine is financed. By unchecking this box you will still have advertisements but they may be less interesting :)


You can find more details on data protection in our privacy policy.