Ableton Forum

Is there a way to mute or unmute all tracks at the same time? I have keys mapped to specific track's mute buttons to change mute status and I'm using a Midi Keystroke app to engage mute or unmute on groups of tracks, but I cant find a way to mute all tracks regardless of their current mute status.

Basically what I'm trying to do is solo groups of tracks while others are muted. Then switch to solo another group (possibly containing some of the same tracks as the first group)

What I'm looking for is a mute all tracks button that I can assign to a keyboard shortcut so I can include it in a midiStroke keystroke macro.

You might be able to get that effect using the A/B crossfader. And/Or use sends to group tracks together, and sends within sends etc. on crossfaders.

Putting buttons on A/B fader assignments can result in toggles from A to B to A to B...

I thought of using the A/B crossfader, but i need to have much more than two groups.

group to sends, set track's outputs to Sends Only and mute/unmute the sends

This is a good solution for grouping the tracks, but it still requires two separate keystrokes for switching groups. One key press to deactivate the current group and another to engage another group. I want to do this in one stroke. Is it possible?

Not sure if this will help or not. I haven't messed with Live 6 yet but I have heard that you can assign multiple midi commands to one controller. Assuming this is true, you could put the "utility" plug in on each channel and assign all the mute buttons from the "utility" plug in to one button. And if you want to mute groups, you could do the same thing. Assign a group of mute buttons to one controller and another group to another controller. Make sense?

The multi-assign feature in Live 6 would definitely help the cause, but unless there is some kind of "Mute All" button there doesn't seem to be a way to switch groups (containing similar tracks) in one stroke. Creating macros with midiStroke basically substitutes for the Live6 multi assign functionality.

I may have to spill the beans on what I'm trying to devise in Live before this thread really starts getting confusing.

Is it too late for Live 6 feature requests?