Thursday, February 27, 2025
Tuesday, February 25, 2025
Monday, February 24, 2025
Cubase Pro: Mix Mastering With Multiband Tools
Voxengo’s CurveEQ plug‑in, bundled with Cubase Pro, allows you to compare the EQ spectrum of your mix with that of a reference track.
We explore how Cubase’s multiband tools can help you master your own mixes.
In April 2021, I described a simple, single‑band signal chain for DIY mastering in Cubase. The approach followed the principles outlined by Ian Shepherd in his SOS Mastering Essentials video series (https://sosm.ag/mastering-essentials), and used stock plug‑ins that are available to all users of Cubase 11 Pro, Artist and Elements, as well as a couple of third‑party freebie metering plug‑ins. As mentioned in that article, though, Cubase Pro also boasts an impressive collection of multiband processors — so in this article, I’ll consider the pros and cons of using these powerful tools for our DIY mastering signal chain. To accompany the article, I’ve prepared a number of audio examples, which you’ll find in the 'Audio Examples' box.
Join The (Multi)Band
In my previous article, I followed Ian’s keep‑it‑simple approach and used a signal chain comprising Cubase’s StudioEQ, Compressor and Limiter plug‑ins. I also placed an instance of Brickwall Limiter at the end of the chain, just to catch any stray peaks, and used freebie VU and loudness meters to monitor the final level of my in‑progress master.
For my multiband signal chain, I substituted StudioEQ for Frequency 2 and Compressor for Multiband Compressor, added instances of Imager (for stereo image adjustments) and Quadrafuzz 2 (for saturation), and kept Limiter and Brickwall Limiter in place. For comparing the spectral content of my master with my reference, I used Voxengo’s CurveEQ, which is bundled with Cubase Pro. SuperVision provided loudness metering alongside Klanghelm’s VU Meter (my favourite third‑party option).
Compare The EQ
As in the April 2021 column, my first step was to use my VU meter and SuperVision’s Loudness module to adjust the channel gain in the Channel Settings dialogue, aiming to get the level of my raw mix to average/peak levels around 2‑3 dB below Ian’s suggested final targets (‑11dB on my VU meter and ‑10 LUFS for short‑term loudness).
I then used CurveEQ to compare the overall spectral balance of my as‑yet unprocessed mix and a reference track I’d chosen. Inserted on any track, this plug‑in can capture an EQ spectrum of the audio that’s passing through; this spectrum can then be loaded into another instance of the plug‑in, allowing direct comparison between two (or more) signals. CurveEQ can also calculate an EQ curve that makes the signal (in this case, my track) match the EQ spectrum of a reference track. I did not actually use CurveEQ to apply any EQ changes — Instead, I made my EQ moves manually using Frequency 2 — but it is a useful visual guide if you wish to nudge your own track in the direction of a reference.
In this case, comparing the frequency curves encouraged me to experiment with small boosts centred at 60Hz, 2kHz and 7kHz, while also applying small cuts at 125Hz, 1kHz and above 10kHz. I also applied high‑ and low‑pass filters to tidy up the extreme ends of the frequency range. In keeping with Ian’s advice, the changes were subtle but, to my ears at least, they both added weight and brought clarity to the mix, and I retained these EQ settings as the foundation for my subsequent multiband experiments.
Two-band Approach: Multiband Compressor + Quadrafuzz 2
The majority of Pro 11’s multiband plug‑ins offer four bands of processing. The new Imager plug‑in allows you to specify exactly how many bands you wish to use but in the older Multiband Compressor and Quadrafuzz 2, you cannot completely remove the unwanted bands; you can only disable them. Starting with a two‑band approach, my Multiband Compressor and Quadrafuzz 2 settings are shown in the screenshot. In an ideal world, I’d have the same band configuration as in Imager, with a low band and a high band, split at around 200Hz. As it is, the two ‘unwanted’ bands in both plug‑ins have been centred in the low‑mids and made as narrow as the GUIs permit. It’s a modest, pragmatic workaround, but there is therefore a narrow frequency range between about 200 and 300 Hz that isn’t being processed in this configuration.
The settings used for the key plug‑ins in my two‑band DIY mastering signal chain.
To arrive at the settings shown, I adopted the same approach as in the Cubase Techniques April 2021 article, but on each of the bands. So, for example, for the compression, I set moderate attack (20ms) and ratio (2:1) values and then simply dialled in the threshold until each band was applying a maximum of 3‑4 dB of compression. For Quadrafuzz 2, I soloed each band, selected the gentle Tube mode (Tape worked equally well when I tried it) and increased the Drive control until the effect was clearly audible, before gradually dialling it back; I wanted to ‘hear’ the effect but without it being too obvious. I used the two Imager bands to narrow the stereo image below and gently widen it above 200Hz, and also checked for mono playback compatibility. Finally, I used identical settings for the Limiter and Brickwall Limiter plug‑ins as in the April 2021 article.
In comparison to the unmastered mix, this two‑band mastered version is louder, but even with the perceived levels matched it seems to have a punchier low end, less muddy mids, a crisper high end and slightly greater stereo width. The differences are subtle, which hopefully suggests the processing hasn’t been overdone, but to my ears at least they seem beneficial: the two‑band mastered mix has more impact.
Three, Four, Testing
If we start by sticking to the same keep‑it‑simple principle, moving up from two bands to three or four doesn’t involve much more than deciding what crossover points to use and configuring the required settings within Multiband Compressor, Imager and Quadrafuzz 2 for the new bands. For my three‑band version, I used crossovers at 200Hz and 5kHz, while for the four‑band version the values were 200Hz, 2kHz and 10kHz.
More bands means greater control over fine details, provided you can avoid abusing the processing power available!
Whether the differences are audible in a specific case or not, in principle, splitting our compression across more independent bands ought to produce a smoother overall result, as each band is focused on, and only triggered by, a narrower range of frequencies. Peaks in the low mids should not, for example, trigger compression in the high mids, or vice versa. That said, there’s nothing to stop you making further adjustments in the different bands: you might, for example, experiment with higher compression ratios in your low band (for tighter control of the bass levels) or low mids (for keeping the mud at bay) if you feel your mix requires it.
However, using more bands for Imager and Quadrafuzz 2 is only really necessary if you wish to make use of different settings in the additional bands. I’ve done this with both plug‑ins, applying gradually more stereo widening in each of the mid/high‑frequency bands in Imager and, in general, applying a little more saturation in the lowest and highest bands than within the midrange in Quadrafuzz 2. Used in this conservative fashion, these extra bands feel to me like I’ve got just that little bit of extra control over details and the amount of ‘mastering fairy dust’.
If you wish, you can easily construct alternative mastering chains using some of the other plug‑ins bundled with Cubase Pro 11, but applying the same principles. For example, you could use an instance of Squasher to provide your multiband dynamics processing, or use Frequency 2’s dynamic EQ options to combine multiband EQ and compression in a single plug‑in. Just for fun, I’ve included audio examples based on both those approaches, but I’ll leave a detailed discussion of those tools for another day.
Mixed Up Mixes
So, what’s my own takeaway from this little experiment? First, while sensible (ie. subtle) single‑band mastering in Cubase Elements and upwards can easily give a solid mix a good nudge forwards, I think the benefits of multiband mastering are obvious. This might simply be the ability to control the dynamics of your low end more firmly, without squashing your mids and highs. But the option to add different degrees of stereo width and saturation sweetening to your high‑mids and highs provides useful additional control over the end result. And while you can do the same thing with third‑party tools, Cubase Pro 11 users have plenty of scope on this front using just their DAW’s stock plug‑in collection.
Do note, though, as Ian Shepherd makes clear in the SOS videos, that less is generally more at any single stage in your processing chain. It’s easy to get lost wandering through the options presented to you when working with more bands, and thus to take your mix backwards rather than forwards. You must focus on what the material needs, not simply what your tools can do to it! Bear in mind, too, that splitting audio into frequency bands introduces phase shift which may be audible, especially when you do it repeatedly.
Finally, don’t forget to audition the audio examples. As a small twist, I’ve randomised the order of the multiband mastered examples so that, if you want, you can audition them ‘blind’. After you’ve decided which you think is most effective, check the small print at the end of the audio file description for the running order!
Saturday, February 22, 2025
Friday, February 21, 2025
Cubase 11 Sound Design
StepFilter might not be the most powerful filter plug‑in ever created, but its step‑based pattern sequencer opens up some very interesting creative possibilities.
Want to create your own signature sounds? Cubase makes sound design easy.
There’s something very satisfying about making music with sounds you’ve designed yourself, and Cubase provides plenty of options to explore on this front. It’s a big topic, and I’ll consider two different angles in successive workshops: this time, I’ll transform a live audio input source into something more ‘synthetic’; and next month I’ll look at ways you can create playable instruments from a simple, single sample. In both cases, I’ll provide audio examples to illustrate the text, and you’ll find this month’s below or at https://sosm.ag/cubase-1221 with full captions.
Before we start, check your audio buffer size (in the Studio menu, select the Studio Setup panel and, via the Audio System section, open your audio interface’s Control Panel). This needs to be set low enough that real‑time monitoring through a plug‑in chain feels responsive, but not so low as to cause clicks and pops. Second, engage the Monitor button for the audio track you’ll use for your audio input. You may need to disable direct monitoring on your audio interface too, so that you are monitoring only the audio being processed in Cubase.
Sustain
You can process any live audio input through a Cubase plug‑in chain, but let’s start with something simple: transforming some sustained DI electric guitar chords into something that sounds more like a rhythmic synth. Sonically, an unprocessed guitar DI signal can sound pretty uninspiring. One problem may be a lack of sustain, in which case a useful first processing stage might be compression. In my example, I used (or rather abused!) Cubase’s Tube Compressor. With a fast attack, slow release and high ratio, the compressor quickly reduces the initial transients in the audio input while the slow release makes the sustained portion of the sound appear louder. As our aim is something synth‑like, we can think of this compressed DI guitar as our synth’s ‘oscillator’.
StepFilter & MidiGate Rhythm
Some filtering might be a good next step and StepFilter is a good starting point. This plug‑in offers the usual cutoff and resonance options but the main attraction is its step‑based pattern control of these parameters — this makes it super‑easy to add filter movement in real‑time. As shown in the screenshot, I programmed a cutoff pattern that includes some steps with zero values, essentially closing the filter. This chops the sustained guitar chords to create a rhythmic feel and adjusting the Glide control determines the strength of that rhythmic effect.
Many synth filters and filter plug‑ins include a drive control to spice things up a bit, and while StepFilter doesn’t you can insert one of Cubase’s distortion plug‑ins somewhere in your chain. I plumped for Distortion, and inserted it before StepFilter. With suitably high Boost and intermediate Feedback settings, this can generate a nice ‘growl’, without sounding too much like a distorted guitar amp. For Pro and Artist users, Distroyer could provide similar results while offering more options.
MidiGate lets you superimpose complex rhythmic patterns upon your live audio signal.A more adventurous option for creating a rhythmic feel is to use MidiGate. Essentially, this is a noise gate that’s keyed by MIDI notes, rather than by the audio signal exceeding a threshold and it thus requires some configuration — but it’s well worth it! First, set StepFilter’s Cutoff and Resonance patterns to provide a continuous sweep (rather than rhythmic pattern) for the filter. Then insert MidiGate just before StepFilter. To trigger the gate you must create a MIDI track and route it’s MIDI note data to MidiGate’s MIDI input. You can then use the MIDI notes on this track to open and close the gate rhythmically. The notes can be from MIDI loops, recorded parts or a live input, but if you already have a MIDI drum track or bass track in your production, elements copied from these (try the hi‑hat or kick/snare) will often work particularly well, instantly locking the rhythm of your designed sound to other elements in the production.
The screenshot shows my MidiGate settings, which force the gate to open and close quickly. Note that because the three lower controls are all set to zero, the pitch of the MIDI note has no influence on the gate’s attack/release time and the note velocity doesn’t influence the volume of the sound passing through. But these controls are definitely worth experimenting with at some point.
Retrologue 2 Side-chain
Although StepFilter can be very effective, Pro and Artist users have a more powerful option still: Retrologue 2’s filter. Retrologue 2’s side‑chain input can receive audio from another track, and this could be a ‘live’ audio input if you wish. This audio is passed through Retrologue’s filter and effects sections and if you disable all of its oscillators, you’ll hear only this Retrologue‑processed audio.
There are a couple of ways to route audio from your ‘live input’ audio track to Retrologue’s side‑chain. In this case, having enabled Retrologue’s side‑chain, an Input level control appeared in Retrologue’s Oscillator Mix panel. I then routed my audio track’s output directly to Retrologue’s side‑chain using the MixConsole’s Routing panel. This means my live audio input is first processed by the audio track’s plug‑ins (for example, my instance of Tube Compressor) before being sent to Retrologue.
My audio input track has been routed (top left of the screen) directly to Retrologue’s side‑chain input, so that I can apply the synth’s filter and effects processing to the sound.
Retrologue’s filter has plenty to offer: there are over 20 filter shapes, a filter envelope and a choice of distortion types. However, as with MidiGate, for Retrologue’s audio engine to be ‘active’ it must be triggered by incoming MIDI notes — even if all the synth’s oscillators are disabled. Your Retrologue track therefore needs a MIDI clip containing some MIDI note data. The upside of this requirement is that the MIDI note data can serve several functions...
First, the timing and lengths of the notes can be used to impose a rhythmic feel upon your live audio input; a single long note will allow you to hear your audio exactly as you play it, while a series of shorter notes will impart their timing on the performance. Second, some fun can be had with the pitch and velocity of your MIDI notes, which can influence both the filter’s Key Follow control and the velocity sensitivity of the filter and amp envelopes. The audio examples include a number of different MIDI note configurations that illustrate just some of the possibilities, from letting your audio dictate the dynamics (using long MIDI notes), through syncopated staccato patterns (short MIDI notes) and to pseudo‑reversed notes (using a slow attack time in the Amplifier ADSR), but you can get very creative with this.
If enabled, Retrologue’s Arpeggiator features provide yet more rhythmic and modulation options. In the final screenshot, the Vel(ocity) lane is being used to create a rhythmic pattern and control the volume of each step, while I’ve set the first two Controller lanes to change the filter’s Cutoff and Resonance values. The tempo of the pattern (and, therefore, the speed at which your audio is modulated) is locked to your host tempo but can be adjusted with the Tempo Scale setting.
Once your audio has been routed into Retrologue 2, you can exploit the Arp page options to inject some rhythm and movement into your sound.
More Processing
As with the sound engines built into most virtual synths, the processing options don’t stop at the filter; you can deploy a whole array of ambience, modulation and other effects to further enhance your sound. Cubase’s Stereo Delay, available in Elements, is a good starting point but the less conventional Multitap Delay (Pro and Artist) and ModMachine delay (Pro only) both offer something a little less conventional and they’re well worth experimenting with. When using Retrologue 2’s filter, the full suite of Retrologue’s effects panel is available including the suitably experimental Resonator section. I’ve included a number of examples of what’s possible in terms of ‘post‑filter’ processing in the audio examples.
Having built a processing signal‑chain for transforming your live audio input, make sure you save the configuration using either the Track or Insert rack preset systems (whichever works best for your particular configuration); when you want to try it with your didgeridoo as opposed to that DI’ed electric guitar, you’ll be ready to go in a flash.
Of course, you might also like to build a fully playable instrument or two from just a sample of that didgeridoo, and if you check back next month I’ll offer you some more ideas.
Published December 2021
Thursday, February 20, 2025
Wednesday, February 19, 2025
Cubase Pro: Take Control Of Your Stereo Image
Imager: up to four bands of stereo width control for Pro and Artist users.
We show you how to take full control of your stereo image with Cubase’s powerful bundled plug‑in suite..
Cubase has long included stock plug‑ins for manipulating the stereo image and they all have a role to play, as I’ll explain, but the recently added Imager is particularly interesting. It allows you to process up to four different frequency bands and, as is so often the case with multiband processors, it’s a powerful tool that’s capable of great results in the right context — but it’s also fairly easy to screw things up if you don’t know what you’re doing! In this article, I’ll work through a few examples that show you what Imager has to offer, while noting some of the potential pitfalls. You’ll find some audio files to accompany each example on the SOS website at https://sosm.ag/cubase-1021.