[GR-PDXParticipant]

Agree.

[GR-PDXParticipant]

I’m naive enough to not understand. What level of control would this offer musicians re. their monitor mix?

[GR-PDXParticipant]

Hi TB,

None of these options is supported I’m afraid. I’d suggest considering an AR2412 which comes with a dedicated Monitor port.

I’m not sure I understand this statement, either. Does this mean the Qu series won’t support the ME-1? It isn’t clear to me how much stuff I’d have to buy if I wanted everyone in a 4 piece band to have their own monitor mix, whether the ME-1s hook up direct to the dsnake port, or what? Are you just saying that the GLD accessory the OP mentioned is not compatible?

[GR-PDXParticipant]

I like the fact that progress is being made, and that at least some of our suggestions are being taken seriously. But yes, I’m disappointed that channel naming on the hardware isn’t done yet. Seems like a real oversight.

[GR-PDXParticipant]

Yeah, I like the progress, and I appreciate the work. Thank you!

[GR-PDXParticipant]

Direct into the balanced 1/4″ line inputs, even if you have enough gain I’d be worried about what the impedance might do to the mic sound.

[GR-PDXParticipant]

Sounds like the needle is jumping out of the groove.

Oh, wait…

I haven’t done extensive recording yet, so I don’t know if my desk has this issue or not. Does there seem to be any pattern of when this happens? Right away, or more than 2 hours in, or…?

[GR-PDXParticipant]

I will say this, dpdan: as I mentioned, I bought based on reputation and sound quality, and I was not disappointed as regards the sound quality. Very nice preamps and processing. Very good sound in spite of being “only” 48kHz sampling. Less stiff sounding to my ears than the Yamaha 01V.

Hopefully with our encouragement and “votes” here in this forum, they will make steady improvements to the firmware.

[GR-PDXParticipant]

Yes, it is what it is in this regard. It seems to be slowly becoming what we were told it would be.

I bought a Qu-16 based in the A&H reputation for excellent sound, and also on some marketing promises that will hopefully be delivered on soon. I was pretty hesitant to get a mixer without naming on each channel, and I would gladly have paid a couple hundred more to have it actually appear on the channel…maybe even giving up the Custom Layer real estate to make room for it, especially if I could link or group faders.

So far, the gigs I’ve done have not been too complex, so this hasn’t been too much of an issue to use magnetic tape and shuffle things around. But channel naming is a convenience that I don’t think I would do without again if I could avoid it.

I bet Chanel naming will be in a future firmware update.

The only way I can think that a firmware update might make this work somewhat would be that
– the QuPad app would also show per-scene channel names and recall them
– there was a special display somewhere (scenes menu and iPad app both?) that would display all the channel names at once for the selected scene
– part of the processing screen also displayed the channel name
– we all learn how to abbreviate even complex things down to five characters

[GR-PDXParticipant]

I don’t really have a preference for how they fix the popping issue, but I’d like to see it fixed. I don’t think a global phantom switch would suffice when the issue is popping during a scene change, would it?

[GR-PDXParticipant]

Thanks for the explanation. I don’t remember seeing any kind of label on the meters signifying “Qu-drive outputs” or something like that, let alone a change in that label as I armed it. If my recollection is accurate, I’ll add that to the usability feedback.

Just as an FYI, we find in user research that changing the primary function on a display like this is difficult to do right, and usually disorienting. We use animations or other cues like color change to help when we have to do so. Something like that could be done while the “Arming…” Message is displaying, for example.

[GR-PDXParticipant]

Ah! That makes sense now, Nicola, as far as why you would patch LR that way.

I’ll see if I can find the global setting that you mention. I really wish routing functions were more co-located. Just sayin’

[GR-PDXParticipant]

I verified that what Nicola pointed out was indeed the issue.

BUT…you almost had me fooled again! Turns out this parameter is also stored with the scene, so when I first tried it I got the same effect because I had changed scenes since I switched that parameter.

The firmware update change this parameter individually for all my scenes, so now all of them will attempt to record a fairly useless stereo mix of the other tracks to 17-18 unless it gets manually changed back.

[GR-PDXParticipant]

I just did some experimenting on my board.

– plugging a dynamic mic in with everything muted doesn’t result in any issues, even when phantom is on that channel.
– plugging in a condenser on a channel with phantom on results in a very loud pop, and literally every channel shows signal clipping as that happens, not just the channel with the mic plugged in. If the master is also muted, it’s minimal.
– turning phantom off and on I with a condenser plugged in results in little sound as long as things are muted.

So the interesting thing is in plugging in a condenser to a phantom-on channel. That is going to create some problems. And it is really odd that every channel is affected.

[GR-PDXParticipant]

So…the other thing, and this is actually related to part of that usability thread:

Presumably that means that 17-18 were recording the main L/R outs? It does not mean that somehow the routing is to have L/R output to those channels?

If that’s right, how would that be helpful in a multitrack situation where presumably you want to do mixdown after the fact? Why did that change from prior firmware versions?

[Author]

Posts