BURNT HOUSE / CUBASE PRO 16 / MIX ROUTING
Routing is one of those parts of a mix that can either make everything easier or create a confusing maze. Groups, buses and FX returns are not there to make a session look professional. They are there to give you control over related sounds, manage shared processing and make the signal path understandable.
Understand the channel types
An audio or instrument track contains the source. A group channel receives several tracks so they can be processed or controlled together. An FX channel hosts shared effects such as reverbs and delays. A bus is a routing destination or submix path; in Cubase, group channels commonly perform this role. The exact layout depends on the production.
Build groups around musical families
A practical starting point is drums, bass, music and vocals. Route related tracks to these groups, then route the groups to the main mix output or a dedicated mix bus. A dense electronic production may need separate kick, percussion and drum groups; a small acoustic session may need very little grouping.
Why group processing can help
Group processing can make several sounds behave as a coherent unit. Gentle bus compression may help a drum section move together. EQ can shape the overall tone of a group. Saturation can add density. But group processing should not hide problems on individual tracks. If one snare is too loud, fix the snare before compressing the whole drum bus harder.
Set up FX returns
Use FX channels for shared reverbs and delays. Insert the effect on the FX channel, set it to fully wet where appropriate and control the amount from each source’s send. Name the returns by function, such as Short Room, Plate, Tempo Delay or Long Texture. Avoid making several nearly identical returns unless they serve a distinct purpose.
Use parallel processing carefully
Parallel compression blends a heavily processed version with the original. It can add density while retaining transients, but phase, latency and level relationships matter. Start with a clear purpose and blend quietly. Compare at matched loudness rather than assuming louder means better.
Expanded send capacity in Cubase 16
Cubase 16 increases the number of audio sends available per channel to sixteen. That gives complex sessions more flexibility for multiple FX destinations, parallel paths and sidechain routing. Most tracks do not need sixteen active sends. Keep the list short, named and intentional so the extra capacity does not become visual clutter.
Sidechain routing
Sidechain signals can trigger compressors, gates and other processors without being heard as part of the main signal. A kick can trigger bass compression; a vocal can trigger a subtle reduction in a synth bus. Make sure the sidechain source and destination are correct, and listen for the effect in the full arrangement.
Keep the master path simple
Route your main groups clearly to the stereo output or mix bus. Avoid accidental double routing and check that reference tracks bypass the processing you intend to compare. Keep print tracks separate and make sure they are not feeding back into the mix path.
Routing checklist
- Every source has a clear output destination.
- Groups represent useful musical families.
- FX returns are named by function.
- Parallel paths are level-matched and checked for phase issues.
- Sidechain sources and destinations are documented.
- Reference and print tracks are routed safely.
Continue with our guides to automation, session organisation and low-end mixing and our Cubase Pro 16 session-template guide.
Design a routing map before building the mixer
Before creating channels, sketch the signal path on paper or in the project notes. A straightforward electronic session might send individual drum tracks to a Drum Group, bass tracks to a Bass Group, instruments to a Music Group and lead vocals to a Vocal Group. Those groups then feed the main mix output. Shared reverbs and delays sit on FX channels and receive signal through sends. This map makes it easier to spot accidental double routing and understand where processing is taking place.
Do not create a group simply because a professional template contains one. If two tracks need different processing and never need to move together, grouping them may add complexity without adding control. Conversely, a group becomes valuable when you regularly adjust the family as a unit, want shared processing or need a convenient stem output.
Gain staging through groups
When several tracks feed a group, their combined level can be much higher than any individual channel. Check the group input and output meters rather than assuming that each source being below zero guarantees plenty of headroom. If the group is clipping, find the cause: too many overlapping sources, excessive insert gain, a hot send return or an unnecessary level boost. Lowering the group fader after a clipped insert does not repair distortion that has already happened earlier in the path.
Use bus compression for a defined musical reason. A small amount of gain reduction can help a drum family move together, but heavy compression may flatten transients or make cymbals pump. Compare bypassed and processed versions at matched loudness. If the bus processor is solving a problem created by one track, fix that track first.
FX returns: shared space, controlled depth
Shared effects can make separate instruments feel as though they belong in the same environment. A short room can add cohesion to drums, a plate can support a vocal and a tempo delay can create rhythmic movement. Name each return by its purpose and set the effect to fully wet when it is being used as a send effect. Then use the source sends to decide how much of each sound enters the effect.
Listen to the return on its own to identify noise, harshness or unwanted low frequencies, but make final decisions in the full mix. Filtering the return can keep reverb from clouding the low end. Automating a send can make the effect appear only at the end of a phrase. Keep an eye on feedback paths: a return should not accidentally feed itself or another return in a way that creates an uncontrolled loop.
Parallel processing and sidechains
A parallel path gives you a processed version alongside the original. This can add density, sustain or colour while retaining some of the source’s transient detail. The blend is critical. Start with the parallel channel muted, bring it up gradually and check polarity, latency compensation and phase interaction. If the sound becomes thinner when the parallel path is added, investigate alignment before changing EQ.
Sidechain routing is different: one signal controls a processor on another signal. A kick can trigger gain reduction on a bass channel, or a vocal can create a small pocket in a synth bus. Set the detector input deliberately and listen for the movement. A pumping effect may be a creative choice, but for clarity the reduction can be subtle and timed to the arrangement.
Prepare stems and references safely
Make a clear distinction between the main mix path, reference tracks and print tracks. Reference audio should not pass through the processing you are trying to compare. Print tracks should not feed back into the mix bus while recording. If you deliver stems, agree whether they should include shared effects, bus processing and automation, then document the choice. A stem set that does not recreate the approved mix can cause confusion later.
Routing fault-finding checklist
- Trace one signal from source to output and confirm every destination.
- Check for duplicate outputs or unintended sends.
- Mute groups and returns one at a time to identify unexpected signal paths.
- Confirm sidechain inputs are assigned to the intended detector.
- Check that reference and print tracks are excluded from unintended processing.
- Save a clean routing version before major restructuring.
A well-designed mixer is easy to understand at a glance. The purpose of routing is not complexity; it is to make the musical decisions easier to repeat, revise and deliver.
