Soundcheck

Do it on the X32 · Step 13

DCA & mute groups

Why am I doing this?

DCAs let one fader control a whole group of channels. Mute groups let one button silence a set of channels at once. Together they're what makes a busy service manageable with two hands. The full explanation → Guide, Step 13

The short version

Already know the drill?
  1. Assign channels to a DCA to ride a whole group on one fader
  2. Assign channels to a mute group to kill a set with one button
  3. Suggested DCAs: Drums, Bass, Guitars, Keys/Pads, Vocals, Speaking, Tracks
  4. Suggested mute: "everything but the speaking mic" for the sermon
  5. Save the scene

DCAs vs. mute groups — what's the difference?

Easy to mix up. They're different tools:

DCA = level. Mute group = on/off. That's the whole distinction.

DCAs — the setup

You get 8 DCAs. The goal is to control the whole service from a handful of faders instead of chasing 32. A worship-friendly layout:

DCAChannels
1 — Drumskit / e-drums
2 — Bassbass
3 — Guitarselectric + acoustic
4 — Keys / Padskeys, synths, pads
5 — Worship Vocalsleader + backing vocals
6 — Speakingpastor, lectern, MC
7 — Tracksplayback, loops
8 — spareFX returns, or whatever your team needs

Now the whole band comes down on one fader when the pastor stands up, vocals ride as a group, and you're never hunting.

To assign: hold the DCA's SELECT and press SELECT on each channel you want in it (or use the DCA group setup on screen). Put the channel's assignment in Our Setup so every volunteer builds the same layout.

Mute groups — the setup

You get 6 mute groups. They're for killing a set of channels instantly and reliably. The ones worth having:

Build the ones that match your service's shape. Service flow → walks through when each gets used.

⚠ One caution

Know exactly what's in a mute group before you rely on it live. A "sermon" mute group that accidentally includes the pastor's mic is a very public failure. Test it deliberately before you trust it.

Step by step

  1. Plan the groups

    using the layouts above and Our Setup.

  2. Assign DCAs.

    Hold the target DCA SELECT, then tap SELECT on each channel for that group. Repeat per DCA.

  3. Assign mute groups.

    Enter mute-group assign mode (there's a dedicated control / on-screen page), pick the mute group, and select the channels it should silence.

  4. Label the DCA faders.

    Name them just like channels — "Band," "Vocals," "Speaking." An unlabeled DCA defeats the point.

  5. Test every group.

    Press each mute group and confirm exactly the right things go quiet. Move each DCA and confirm the right channels follow. Do this before the service.

  6. Save the scene.

What good looks like

CheckShould be
DCAsgrouped by role, labeled
Whole banddroppable on one fader for the sermon
Mute groupscontents known and tested
Sermon muteleaves the speaking mic live, kills the rest
Layoutmatches Our Setup, same every week
Scenesaved

If it goes wrong

A DCA fader isn't controlling a channel.
That channel isn't assigned to it. Re-check the assignment.
I muted the group but something's still live.
It's not in that mute group — or it's in a different group you didn't press. Check the membership.
The pastor's mic died when I hit the sermon mute.
The speaking mic is wrongly included in that mute group. Fix it, then test again before next week.
A channel won't come up no matter what.
Check three things: its own fader, its DCA fader, and whether a mute group is holding it down. Any one can be the culprit — a channel is only as up as the lowest thing controlling it.
Everything's muted and I can't find why.
Look for a lit mute-group button. It's easy to leave one engaged.