Log in
Log in

or
Learning
1 comment

Sidechained Processors Can Give a Variety of Special Effects

How to Get the Pumping Drums Effect with Sidechain Compression

Sidechaining has been around for years; this is the process of using one signal to control another. A couple classic examples are using a kick drum to gate a bass part, or doing de-essing - isolating the high sibilant frequencies from a vocal, and using those to trigger compression so that the sibilants come down in volume.

But in the digital age, we can do a lot more with sidechaining. One of the most popular applications is with dance music, where sidechaining can create the “heavy pumping” electronica drum sound used by artists like Eric Prydz and others.

We’ll describe how to do this with Cakewalk Sonar, although the same principle applies to other programs that allow for sidechaining. Sonar allows sidechaining for several effects, including compression, so that one instrument can control the compression characteristics of another instrument. This offers a variety of effects, including a “pumping” drum sound for multitracked drum parts; we’ll do that by setting up the snare to control compression for all drum tracks.

http://www.harmonycentral.com/servlet/JiveServlet/downloadImage/102–1611–3–11250/256–479/1.jpg

Fig. 1: You’ll need a drum submix bus to create an overall drum sound.

The first step is to create a drum submix bus, and send the drum tracks to it (Fig. 1). We need this submix so the entire drum track can be processed by the sidechained compressor. To create the submix bus, right-click in an empty space in the bus pane and select “Insert Stereo Bus.” To create a send in track view, right-click in a blank space in the track title bar and select “Insert Send.” From the menu that appears, select the send destination. Make sure you feed the bus pre-fader, and turn the individual drum channel faders down so that only the bus contributes the drum sound to the master.

http://www.harmonycentral.com/servlet/JiveServlet/downloadImage/102–1611–3–11251/374–145/2.jpg

Fig. 2: Assign the Drum Submix out to your main stereo output.

You’ll also want to assign the Drum Submix output to your main stereo out (master) bus (Fig. 2).

http://www.harmonycentral.com/servlet/JiveServlet/downloadImage/102–1611–3–11289/450–107/3.jpg

Fig. 3: The Sonitus:Compressor comes with Sonar, and can do sidechaining.

Next up, insert the Sonitus:Compressor (which allows for sidechaining) in the Drum Submix bus’s effects bin (Fig. 3). This will allow for processing the entire drum track.

http://www.harmonycentral.com/servlet/JiveServlet/downloadImage/102–1611–3–11290/391–316/4.jpg

Fig. 4: Use lots of compression!

Now it’s time to program the compressor for really heavy compression – e.g., threshold below –20 and a ratio higher than 10:1. This can definitely add some “squash” as needed; we won’t be adding it all the time, but only when the snare hits. Note that a softer knee compression curve often sounds better than a hard knee for this particular application.

http://www.harmonycentral.com/servlet/JiveServlet/downloadImage/102–1611–3–11291/450–149/5.jpg

Fig. 5: Assigning a bus to the compressor’s sidechain input.

We still need to generate a signal to drive the compressor’s sidechain input, which in this case would be the snare so that the drums “pump” whenever the snare hits. The simplest way is to create another stereo bus, then assign its output to the sidechain input. Now all we have to do is make sure the snare drum feeds this bus.

http://www.harmonycentral.com/servlet/JiveServlet/downloadImage/102–1611–3–11292/450–82/6.jpg

Fig. 6: Use the snare signal to provide the output to the sidechain.

Create a second pre-fader send in the snare track, and assign its out to the bus feeding the sidechain input.

http://www.harmonycentral.com/servlet/JiveServlet/downloadImage/102–1611–3–11293/277–132/7.jpg

Fig. 7: We’re almost there – it’s time to adjust the compressor.

To adjust the compressor, start with the compression attack time set to 0 ms; the drum sound will essentially disappear when the snare hits because the gain is being reduced so much. Gradually increase the attack time to let through more of the initial snare hit, and add a fair amount of release (250–500 ms) to increase the apparent amount of pumping.

And there you have it – the pumping drum sound. May it go over well on the dance floor!


Originally published by Harmony Central.  Reprinted with permission.

  • darkhorizon 3 posts
    darkhorizon
    New AFfiliate
    Posted on 06/01/2012 at 21:42:05
    Lovely article. If only you could explain the same principle to Nuendo users. I know the principle is the same but I need step by step guidance with pictures. I could play all positions of a mixolydian b7 scale and run minor 9ths add 13 arpeggios but music technology is too much for me! (maybe less playing and more manuals?). In any case, thank you for the article!

Would you like to comment this 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 and show you personalised ads (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. Example: cookies that help you stay logged in from page to page or that help customizing your usage of the website (dark mode or filters).
Audience analysis (Google Analytics)
We are using Google Analytics in order to better understand the use that our visitors make of our website in an attempt to improve it.
Advertising (Google Ads)
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 are using Google Ad Manager to display part of our ads, or tools integrated to our own CMS for the rest. We are likely to display advertisements from our own platform, from Google Advertising Products or from Adform.
Marketing (Meta Pixel)

On our websites, we use the Meta Pixel. The Meta Pixel is a remarketing pixel implemented on our websites that allows us to target you directly via the Meta Network by serving ads to visitors of our websites when they visit the social networks Facebook and Instagram. The meta pixel are code snippets which are able to identify your browser type via the browser ID - the individual fingerprint of your browser - and to recognise that you have visited our websites and what exactly you have looked at on our websites. When you visit our websites, the pixel establishes a direct connection to Meta's servers. Meta is able to identify you by your browser ID, as this is linked to other data about you stored by Meta on your Facebook or Instagram user account. Meta then delivers individualised ads from us on Facebook or on Instagram that are tailored to your needs.

We ourselves are not in a position to identify you personally via the meta pixel, as apart from your browser ID no other data is stored with us via the pixel.

For more information about the Meta Pixel, the details of data processing via this service and Meta's privacy policy, please visit Meta Privacy Policy - How Meta collects and uses user data for Facebook and Meta Privacy Policy - How Meta collects and uses user data for Instagram.

Meta Platforms Ireland Ltd. is a subsidiary of Meta Platforms, Inc. based in the USA. It cannot be ruled out that your data collected by Facebook will also be transmitted to the USA.


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. The website cannot function properly without these cookies. Examples: cookies that help you stay logged in from page to page or that help customizing your usage of the website (dark mode or filters).

Audience analysis (Google Analytics)

We are using Google Analytics in order to better understand the use that our visitors make of our website in an attempt to improve it. When this parameter is activated, no personal information is sent to Google and the IP addresses are anonymized.

Advertising (Google Ads)

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 are using Google Ad Manager to display part of our ads, or tools integrated to our own CMS for the rest. We are likely to display advertisements from our own platform, from Google Advertising Products or from Adform.

Marketing (Meta Pixel)

On our websites, we use the Meta Pixel. The Meta Pixel is a remarketing pixel implemented on our websites that allows us to target you directly via the Meta Network by serving ads to visitors of our websites when they visit the social networks Facebook and Instagram. The meta pixel are code snippets which are able to identify your browser type via the browser ID - the individual fingerprint of your browser - and to recognise that you have visited our websites and what exactly you have looked at on our websites. When you visit our websites, the pixel establishes a direct connection to Meta's servers. Meta is able to identify you by your browser ID, as this is linked to other data about you stored by Meta on your Facebook or Instagram user account. Meta then delivers individualised ads from us on Facebook or on Instagram that are tailored to your needs.

We ourselves are not in a position to identify you personally via the meta pixel, as apart from your browser ID no other data is stored with us via the pixel.

For more information about the Meta Pixel, the details of data processing via this service and Meta's privacy policy, please visit Meta Privacy Policy - How Meta collects and uses user data for Facebook and Meta Privacy Policy - How Meta collects and uses user data for Instagram.

Meta Platforms Ireland Ltd. is a subsidiary of Meta Platforms, Inc. based in the USA. It cannot be ruled out that your data collected by Facebook will also be transmitted to the USA.


You can find more details on data protection in our privacy policy.
You can also find information about how Google uses personal data by following this link.