[BaylinkParticipant]

I agree the functionality is important, but that implementation suffers in discoverability; users will try to use the On button to re-unmute the channel, and it will ignore them, and they’ll move on.

Is there any reason why just tapping the On button to turn the channel back on is *un*acceptable? How might that break?

[BaylinkParticipant]

Sure, Keith.

But I think I’ve seen your name, maybe, 4 or 5 times, in the “Reading every thread” I did before I started posting anything.

I’m not sure what your software development cycle is, and perhaps I’m spoiled by spending time in an agile environment most recently, but…

The dirty little secret of gear in which 85% of the capabilities come from software is that *the users know that*, which gives you less maneuvering room in how often things get more capable. And yes, I’ve been a coder for 30 years, and I know that there’s a testing process to go through, too.

Putting this stuff in a system users and potential buyer can see, and doing the prioritization (and vote collecting 🙂 there is an approach that’s been used to good effect in a number of markets. It also allows you to propose the interface a new feature will have and collect comments on that… in a more structured form than this forum. I tried to keep my suggestions separated and clear, but not everyone does.

Thanks for the quick response.

[BaylinkParticipant]

There’s another thread on this; the concensus is “sure, but put in a switch, default OFF; I hate this idea”. 🙂

[BaylinkParticipant]

And now we see why One RFE Per Post is the best approach.

Also: looking to see if anyone already requested that; made much easier by One RFE Per Post.

[BaylinkParticipant]

It’s not.

It’s in the RFE forum, where it belongs. 🙂

[BaylinkParticipant]

And “Make PAFL a selectable source on Matrix Outputs/in Routing” is probably the definition of the other item.

[BaylinkParticipant]

+1

“Allow manual unmuting of a channel muted by a mute group”

Note that group muting *overlays* manual muting; if you group mute a muted channel, then the behavior needs to be defined as to what happens when you unmute-during-group that channel.

On the second point, note that just frobbing the knob one click brings up the screen (or so I’m told); that small an adjustment will rarely be noticeable.

[BaylinkParticipant]

“Please let me know where and how”.

[BaylinkParticipant]

A more useful thing is Sel Follows Cue, IMO.

[BaylinkParticipant]

Let me suggest that this be treated as the more general

“Jump the Big Screen to the appropriate page when the user turns an assignable encoder”, as has been suggested elsewhere; it’s slightly more general.

[BaylinkParticipant]

Hmmm. Someone had suggested reversing the scribble strips, but I hadn’t seen “blink” yet. Another good approach, and even closer to the faders than the Big Screen.

[BaylinkParticipant]

A wee tweak is the sort a Scot makes. 🙂

[BaylinkParticipant]

Yep, I gather from comments from a friend who’s had hands-on that there’s no Master PAFL Release button… which seems a Class 1 glaring oversight to me.

Is it in fact at least possible to assign that function to a softkey?

[BaylinkParticipant]

RQM: You want something like “Blind mode” on an ETC Ion, where you can edit cues and parameters without affecting the live mix.

[BaylinkParticipant]

This is less important on a board, like the SQ, where you can simply move channels around onto strips, as opposed to older boards like the LS9 and x32, where if you want to rearrange channels, you may have to copy to get processing.

[Author]

Posts