Muting, Soloing, and the Power Button

Region Mute

Select a region in the Tracks area and invoke Toggle Region Mute (default: ⌃ + M). The region grays out and goes silent. The track is still active, the channel strip is still processing, and any other regions on that track still play. You silenced one block. That’s it.

This is the one you want most of the time while you’re building. You’ve got eight bars of a synth pad and you want to hear the verse without it? Mute the region. You’re comparing two different bass lines you recorded? Mute one, listen to the other. You’re not making a decision about the track. You’re making a decision about a piece of material.

Region mute also shows up in the Inspector. Select a region, look at the region parameters, and you’ll see a Mute checkbox. Same operation, different access point. If you covered Chapter 9 on the Inspector, this should look familiar.

Track Mute

Click the M button on a track header (or in the Mixer). The entire track goes silent. Every region on it, muted. The channel strip is still loaded, still using CPU, still processing — the audio just isn’t reaching the output.

This is a mixing move. You’re listening to the whole song and you want to hear what it sounds like without the rhythm guitar. You’re not evaluating one region against another. You’re evaluating the role of that instrument in the mix.

The difference matters because of when you reach for each one. While you’re constructing a track — arranging blocks, trying ideas, building sections — you’re working at the region level. Region mute lets you audition combinations without disrupting anything about the track itself. Once you’re past the building phase and into mixing or evaluating the arrangement as a whole, track mute makes more sense.

The Power Button

The power button on the channel strip (the small button at the top) does something neither mute does: it turns the channel off entirely. No processing, no CPU usage, no signal flow. The instrument or audio engine for that track shuts down.

Use this when you want to free up system resources. A track with three CPU-heavy plugins that you are not using right now? Power it off. The regions stay, the routing stays, but the processing stops. When you power it back on, everything comes back.

This is not a musical decision. This is a resource management decision. Most of the time, you do not want the power button when you meant mute.

Why the Distinction Matters

When you bounce a project, muted regions are excluded but the track still processes. Powered-off tracks are excluded entirely. Track-muted tracks are silent but still consume CPU. These are different outcomes, and if you’ve been carelessly mixing up all three, you’ll find yourself wondering why a bounce sounds wrong, or why your CPU meter is spiking even though “everything is muted.”

The bigger picture: when you’re building — arranging sections, trying out parts, assembling your architecture — you’re working with blocks. Region-level operations (region mute, region solo) let you manipulate those blocks. When you shift into polishing — balancing levels, evaluating the mix, making decisions about what the song needs — you’re working with tracks. Track-level operations make sense there.

This is the difference between architecture and polishing. Knowing which phase you’re in, and reaching for the right tool for that phase, keeps your session clean.

Solo

Solo is the inverse of mute: instead of silencing one thing, you silence everything except that thing. And just like mute, it operates at two different levels.

Region Solo

Select a region (or several regions) and invoke Toggle Region Solo. Only the selected regions play. Everything else goes quiet. Let go of the selection or toggle it off, and the full mix comes back.

This is indispensable while building. You want to hear just the vocal in bar 17? Select it, solo it. Comparing a piano part against a synth? Select both, solo them together. You’re auditioning material in isolation without touching anything about the tracks themselves.

Track Solo

Click the S button on a track header or in the Mixer. That entire track plays in isolation. Every other track goes silent (unless it’s solo-safe — more on that in a moment).

Track solo is a mixing tool. You’re checking the EQ on a vocal, or listening to a drum bus in isolation, or verifying that a reverb return sounds right. You’re evaluating a track’s contribution to the mix, not comparing individual pieces of content.

Nathan’s Key Command Swap

By default, Logic assigns S and M to track-level solo and mute. That means the keys you’ll reach for instinctively — S for solo, M for mute — trigger the mixing-level operations, not the building-level ones.

That’s backwards for how most people work most of the time. While you’re constructing a song, you’re reaching for region-level operations far more often. The track-level stuff comes later.

The fix: open the Key Commands window (default: ⌥ + K), search for the region-level solo and mute commands — Toggle Region Solo and Toggle Region Mute — and assign them to S and M. Move the track-level commands to something else, or leave them unassigned and access them from the track header buttons when you need them.

This is the kind of customization the Key Commands window exists for. The defaults are a starting point. If they do not match how you actually work, change them.

Solo Modes

Logic has more than one flavor of solo, and the names are confusing. Here is what actually matters.

Solo (Standard / Solo Latch)

Click the S button on a track. That track solos. Click S on another track — now both are soloed. Each solo click latches on, and you accumulate soloed tracks until you un-solo them. This is the default behavior, and it is what you want most of the time, because it lets you build up a combination: solo the kick, then add the snare, then the bass, and listen to the low end together.

Solo Safe

Option-click the S button on a track, or Control-click and choose Solo Safe. The button changes to a striped appearance. That track now stays audible whenever anything else is soloed.

The classic use case: you want to solo individual instruments but always hear the click track, or always hear a reference mix. Set those tracks to solo safe and they will never go silent when you solo something else.

Soloing in the Mixer vs. the Tracks Area

The S button on a track header and the S button on the corresponding channel strip in the Mixer do the same thing — they solo the track. But in the Tracks area, you can also solo individual regions, which is a different operation entirely. The Mixer has no concept of regions. It only knows about channels.

If you are working in the Mixer and soloing, you are always working at the track level. If you are working in the Tracks area, you have access to both levels. This is another reason to stay in the Tracks area during the building phase and save the Mixer for when you are actually mixing.

What to Practice

• Record or import a few tracks with multiple regions each. Practice muting individual regions (region mute) and notice that other regions on the same track still play. Then mute the track itself and confirm that everything on it goes silent.
• Solo a single region in the Tracks area. Then select two regions on different tracks and solo them together. Notice how region solo lets you audition arbitrary combinations of material.
• Find the power button on a channel strip. Turn a track off, watch the CPU meter, turn it back on. Understand that this is a different operation from muting.
• Open the Key Commands window and search for “Region Solo” and “Region Mute.” Consider reassigning them to S and M. Try working with region-level operations as your primary solo/mute for a session and see if it fits your workflow better.
• Set one track to Solo Safe. Solo other tracks and confirm that the solo-safe track always plays through.

Commands in This Chapter