Why why why cannot I not name the mute groups? Please add this feature!
Because you have 24 dca’s that you can name instead. I’d rather have extra dcas instead of namable mute groups.
What? There’s certainly functional overlap, but DCAs do not “exist” to be nameable mute groups. Asking to implement names for mute groups is totally reasonable.
Okay, but nowhere is it suggested that having nameable mute groups needs to come at the expense of DCAs. If you’d like to have more than 24 DCAs, submit a feature suggestion to that effect.
Just because we don’t see a need for a feature in our particular use case doesn’t mean we need to shoot down the suggestion. If you want to offer workarounds or help educate a user when they might not be aware of an existing solution, that’s fine. But that’s not how your response reads, in my opinion.
2 Likes
What I mean is that I would rather see development resources focused on expanding existing functionality than creating new functionality with the same purpose. We already have a working system that is able to do the task that is requested, so why spend valuable development resources on changing another to into the same thing. Merging would be a better solution.
I hear you. Software engineering resources are limited, but the allocation of those is ultimately up to Allen&Heath. The voting system in the forums is the most direct way to express demand for a feature.
But regardless of the community support a feature request might have, the engineering teams at Allen&Heath will assess the technical effort required to implement and whether or not the feature fits within the company’s vision for the product.
However, none of those are reasons that should prevent users from requesting things that they believe would make the product better.
4 Likes
Those of us who ran analog desks for most of our engineering careers are probably using tape and markers to label our mute groups on the soft keys?
Yep, I’ve got board tape down the side of the soft keys and along the layer buttons for the banks. Messy, but until A&H brings out a desk with OLED displays buttons for softkeys its my best solution.
+1 I voted for dLive, but the same goes for Avantis. (The older Qu and Sq versions allow this). Using DCAs is indeed possible, but since the Mute Groups function is already integrated, being able to name them would be a plus.
(On a small console like the Avantis Solo, I often don’t assign mute groups to softkeys but only to the screen, and it would be convenient not to have to go to the assignment page if I’m unsure).