Mute / Unmute unexpected behaviour

[gfbrnby]

When I use soundcraftui: MUTE Groupls/ALL/FX: Mute with either my mute group "Mute All" or the MUTE ALL option I can toggle all mutes on and off. When I use soundcraftui: Master channels: Mute to mute a channel I can use the same function to unmute it. However, when I use soundcraftui: MUTE Groupls/ALL/FX: Mute to mute all channels, and then use soundcraftui: Master channels: Mute (with either the unmute or toggle option) to unmute one channel, that channel does not unmute. This is different than if I perform these actions on the mixer itself.

[fmalcher]

Thanks for the report. This topic is a bit difficult indeed. Let me repeat the steps to make sure I got them sorted correctly:

with the Soundcraft web interface:

• enable "Mute all" group
• unmute master channel manually
• channel is not muted
• Mute button has a blue-ish background now

with Companion:

• enable "Mute all" group
• unmute master channel through Master channels: Mute action
• channel is still muted
• Mute button is still red
• expected behavior: Channel unmuted, button blue-ish.

Can you confirm that you're referring to this behavior? @gfbrnby

[fmalcher]

This behavior is related to the forceunmute command. A channel has 3 different mute sources:

• 1.) mute: directly muted, usually through the channel mute button
• 2.) Mute Group: muted through a group, e.g. "Mute All"
• 3.) forceunmute: if set, this overrides mute and groups for this channel

This module only supports (1) and (2) at the moment. The mixer API separates those three ways into different commands. The original web interface acts intelligently such as that it automatically sends forceunmute when the channel is muted by a group.

I can think of three ways to integrate this:

• A) add a separate Master channels: Set Force Unmute action. This will stick close to the API but not to the web interface behavior. Relatively easy to add.
• B) emulate the original behavior of the web interface. This is rather complex to solve: Mute requests must always check whether this channel is muted by a group and must then conditionally send mute or forceunmute.
• C) leave everything as it is 😇

How important is this change to you? If it's just a nice-to-have I'd rather go with (C) first and leave this open until there's some urgent need for this. When we implement it, (B) would be great but (A) would be much easier to build. Looking forward to your ideas!

[gfbrnby]

Thanks for your response. Your description of the behaviour of the web interface and Companion is correct. This is not critical at the moment since we are only using 5 of 12 inputs. I am muting and unmuting each one individually as needed. We will soon be using 8 inputs and eventually 12, at which point having to mute all of them individually so I can unmute them will become onerous and error-prone. I would prefer to be able to select snapshots to select combinations of inputs but, as you mentioned in #42, this isn't available in the current release. BTW, thank you for your work on this Companion module. It will make it possible for non-technical members of our church to operate our A/V equipment my merely pushing buttons on a Stream Deck. Amazing!