Direct channel to matrix routing

Please allow us to route a channel directly to a matrix in stead of forcing us to go through another bus first.

Thanks!

That is only possible on Avantis and DLive, not even SQ, so we have almost zero chance of it on QU range!

1 Like

I personally don’t see the point of artificially dumbing down consoles down like that.
Why should this be an avanits/dlive only feature?
There’s quite enough differentiating features between the lines.
We wanted a small console to use when our Avantis is overkill. We could’ve bought an Avantis solo, or SQ but didn’t want to. The Qu should be ample for those situations.
That they don’t want to spend the time developing a feature because relatively few people want it… that is something I could understand, but since more people use QU and SQ than use Avantis or dLive I feel like there’s no point to the ā€˜this is a premium function only for the premium consoles’ argument.
I’d like to be able to do it, I’m sure others would too.

I’ll have to figure out a way to do what I want with normal mixes in stead or matrices.
That’s too bad because it’s nice to have as much parity in workflow inhow we do things on both consoles.
Would be cool if we could change mixes into matrices too but oh well… :slight_smile:

UPDATE: so just to be able to play a 7.1 movie using the Qu-5, in stead of being able to route those movie channels straight to 8 matrices of the 7.1 PA, I now:

-Left the LR C and Sub matrices as they were, because otherwise it would be a pain to route music, microphones etc. to the LCRS PA part of the system.
-Created 8 mono groups just to be able to send those 8 movie channels cleanly to the LCRS matrices and their individual surround ouputs.
-Perhaps I could forgo the last four groups and use direct outs in stead that follow DCAs etc but sending an input’s direct out straight to an amp set at unity is not something I’m very comfortable doing. Call me oldfashioned :wink:

All in all a lot of hassle and a lot of mixes needlessly spent on a console that has a limited amount of mixes in the frist place, while I can do that much more easily on the Avantis which has ample mixes, without having to needlessly spend any mixes to do so. There’s some irony in that.

So I’d still very much like to be able to:

A. send channels directly to matrices

B. allow mixes to not only be groups or aux, but also be additional matrices

Pretty please.

On a more principle level, and maybe I’m making assumptions here:
Since it seems that you (A&H) take into account with developing your GUI that your pro desks are not only used by pros but also by amateurs, it would be kind of you to also bear in mind that your lower level desk also get used by professionals and not just by amateurs.
I’d like a way to unlock ā€˜pro mode’ on any console from Qu to dLive.
That way you can cater to both amateurs and pros on the same platforms.
You could make your products easy to use and hard to abuse for amateurs, without slowing the workflow of your pros down in the process. Example: 3s touch and hold per channel to enable a 48V. That could be solved in a more efficient way by a simple two handed opperation much like the ā€˜patch’ button safegaurd functionality in the IO window.
Zero need for a 3s press and hold PER channel if you ask me.

Thanks for considering!

You have to remember that although all new ranges of A&H digital mixers use the same XCVI Core structure, the size of the FPGA varies a great deal as you work you way up from CQ to DLive. Ergo there is a finite limit to the functionality that can be built into any particular mixer range. The lack of certain functions is not necessarily a deliberate ā€œdumming downā€ as you refer, but an attempt at making the best use of processing capabilities. Bearing in mind that every possible internal signal route is always active, and just bypassed and a suitable number of dummy clock cycles added to the signal when a particular route is not used, in order to ensure that if you send the same signal to 2 different inputs, route one direct to main LR, and the other via a group, then main LR then a matrix, both will arrive exactly coherent, that involves a great deal of array architecture permanently committed.

1 Like

Of course I understand the larger consoles have more power but that’s mainly represented in channel/bus count

I very much doubt that offering the possibility to route channels directly to the matrices iso going via a bus is going to add substantial processing strain on the engine.

I might be wrong, but I’d be very surprised if that’s the reason.