[Dick ReesParticipant]

I’m sorry to say that this scheme of yours is very impractical, theoretically unsound (pun not intended, but a good one) and poses potential operational problems for the actual engineer(s).

I would certainly not want anyone on my crew mucking about on the network during a live show. That would be a firing offense.

[Dick ReesParticipant]

1. The app/console interface is not what you imagine it to be.

2. Even if it works as you not so correctly assume, observing console manipulations/adjustments without knowing the reason for any changes is not likely to give you much real information. You’d have to know the WHY behind the action for context.

[Dick ReesParticipant]

Gary…

Good call. That did cross my mind.

[Dick ReesParticipant]

See pages 27 and 58 in the user manual.

[Dick ReesParticipant]

Oops…

I’ve been mixing remotely for so long I didn’t notice the channel naming option on the console. My bad.

Try what Bear said. Save the scene prior to shut-down, recall the scene after powering up. Works for me.

[Dick ReesParticipant]

I assume you’re naming the channel in the QuPad app. That app has no memory as such and the console itself has no way to name the channels, so the app cannot receive info that the console cannot provide. End the session, stop the connection and you’ll have to re-label in the app.

You can always put some old-fashioned board tape on the console itself.

[Dick ReesParticipant]

Custom layer might look like this:

Attachments:

You must be logged in to view attached files.

[Dick ReesParticipant]

Example:

Gtr routed via Grp 1/2, dobro routed via Grp 3/4, other routed via Grp 5/6, all fed from a single incoming channel. You now have effectively split the incoming signal 3 ways and can EQ/process them separately as you desired.

Set up your channels on a Custom layer. Assign the channel to each Group and un-assign the channel from the Main bus to avoid double-busing.

[Dick ReesParticipant]

There are several solutions or work-arounds, but the first thing you need to do is slow down, collect yourself and realize that it WILL work…just not as you desire/think/imagine. OK…

1. Route the channel to the main mix via groups, EQ as required using the group processing rather than channel processing.

2. Physically split the signal at the board using a couple of FXLR x 2 MXLR cables:

https://www.audiopile.net/YFMM

There are more possibilities, but less elegant. For now, I’d go with splitting 3 ways using group routing.

Good luck. Don’t panic.

[Dick ReesParticipant]

It seems like you are saying “yes” to over-writing the scene. When you do that you will have only one scene…or perhaps two identical scenes, those being the second scene.

[Dick ReesParticipant]

RTFM: Group or DCA, not linking (limited to 2adjacent channels)

Attachments:

You must be logged in to view attached files.

[Dick ReesParticipant]

Section 11.12, p. 70 of the User Manual.

[Dick ReesParticipant]

You may be able to do what you want with User Scenes.

Page 50 in the manual.

Attachments:

You must be logged in to view attached files.

[Dick ReesParticipant]

My point is it wouldn’t take much to put a little more code in there to get some add’l recording functionality

It’s not that simple.

[Dick ReesParticipant]

Boy was I surprised at how limited the recording functionality is on the QU-16. I’ve been using a cheap Tascam Portastudio ($400) for years that I can record tracks and come back and add layers on the unit hoping to add audio quality but that functionality doesn’t exist in the QU-16 ($2.3K, yes sounds far superior, but…). It may be more of a live mixer but I’d think they could put a little more code in there to at least go back over and re-record sections of a song/arrangement…

Soooo…

How’s your Tascam work for live sound mixing?

[Author]

Posts