[fxkParticipant]

It’s like choosing a mate – people are pretty well set in their ways long before you meet them. So many people get into a relationship and turn the other into a “project” to meet their needs. That never works.

Buying into a console line hoping that some new release will give the things one dreams of is as futile as getting into a relationship as a project.

We’ve all dreamed of the QU with off-line editor, downward expanders, the ability to daisy chain consoles, use the QU-SB as a stagebox, and the list goes on. Don’t hold your breath. Remember, software updates either fix problems, or offers new features. One is needed, the other is not. Both cost money, yet we expect A&H and others to improve the software gratis. Good way to lose a company. Although many of those things are on my wish list, I still can put a decent show together using a QU series mixer as is.

The QU is what it is. If you need something else, buy something else.

As far as EOL…
EOL happens when the whiz-kids can produce something for a market segment that outperforms the current product at a cheaper production cost.

EOL is about repair and support, or lack thereof.

[fxkParticipant]

Mea clupa! I missed the point in the thread where the CRC had been unraveled.
Please put my comments in the file “rambling of idiots”.

[fxkParticipant]

By A&H’s thunderous silence, and their apparent unwillingness to part with the CRC algorithm that is needed by one who has the rest of an editor figured out, I’d guess the answer is nah. The QU is what the QU is – and it will never have an off-line editor, much to my chagrin. Really, how old is the platform now? I’m not saying they’re not busy, but there has been opportunity after opportunity that have passed.
(sigh)

[fxkParticipant]

Yeah… If you’re that close (I’ll assume you are) it is absolute evidence A&H have no intention of either providing help, or to allow a QU editor in the wild, or EVER provide an editor. They know how it’s done, they’ve “had plenty of time” to develop their own, and we’ll NEVER see one – even as an extra cost option.

If I could afford to sell my early QU16 (with the fixable phantom-pop problem, a defect they corrected on later versions, that they say I have to pay for), and my AB168 without taking a bath, I’d dump A&H in a heartbeat, though I do love the console itself.

If nothing else, when asked (over and over) they had have come clean and definitively said “Never Ever!, I may have had some respect left for them. Lying by omission is still lying.

Shame on A&H. For lying about the editor, and trying to stick me with the bill for the phantom-pop fix.

[fxkParticipant]

Maybe switch to a “special scene” that has phantom off, then switch to the preset scene with phantom.

Lately, I’ve been using the AB168 digital snake – and with the snake connected, no problem at all.
Of course, when I go back to analog snake, I get caught with my pants down (figuratively). They also suggest turning phantom off, then back on after patch. How long would that take with the built in delay to turn phantom on or off…

Personally I believe this is a despicable way to treat their customers – “yeah, we got a fix, but you have to pay for it. Tough beans to the early adopters.

That, and the refusal of A&H to provide an offline editor puts me in a position where I would like to get a QPac, but I fear that would be just throwing good money after bad. I got a really good deal on the AB168, so I’m kind of stuck – selling off and buying something else with digital snake, and an offline editor financially does not make sense.

Heck, someone here on the board says he’s developed an offline editor, but can’t figure how the checksum works. Maybe it’s wishful thinking, and maybe I should be more skeptical, but it would be nice if A&H would consult with this guy and test and help out.

Makes me wish I had bought Soundcraft.

[fxkParticipant]

XYZ – I have both an iPad gen 3 (first wth RETINA) and an iPad Air 2. The newer is somewhat more responsive, but not significantly. It may be placebo effect or it may be real.

I worked as a custodian when young and say some industrial-strength cleaners as well. I know many people’s hands sweat when hot or under pressure. I sweat everywhere (profusely) except my hands and feet.

[XAP]Bob – Good thought – I’m an internal heat generator that has no match. Gloves are basically a no-go. I can’t wear golf gloves. Rarely do I wear gloves in winter. Never work gloves. Only when motorcycling can I wear gloves where winds over 35mph is enough to keep my hands cool enough to stave off the swelling. I tried the soft-tipped stylus, and recognition is better, but they drag on the screen surface. Maybe something like finger picks with a hard-plastic stylus. Had some of those that fit on the end of a pencil. Need to look for them.

[fxkParticipant]

As far as “sensitivity” on the QU app…
I read this to mean “what the heck do I have to do to get the iPad surface to respond to my finger!”

I’m one of the “lucky” few where the iPad (any iDevice, Android, etc) is unsure if I’m actually alive and touched it’s surface. Maybe it’s dry hands, but I have trouble with capacitive surfaces in general. OK…

That being said, the Soundcraft app recognizes me immediately and is super responsive always. The Yamaha apps and QSC Touchmix apps are quite decent, with very few “retries” ever. The Touchmix app even allows multi-touch so I can grab a couple faders at once and make adjustments.

Then there’s the QU app. Folks around me see me practically pounding on the screen to get it to recognize my touch. Moving a fader is bad, but selecting a channel is VERY hit-or-miss. Mostly miss. It seem at least 50% slower than on other apps just because it will not recognize my touch. I guess there’s a way in IOS API to dial up or down screen sensitivity – I wish A&H would dial the sensitivity up (or a user configuration). I do understand about guarding against accidental touches, but this, for me, is ridiculous.

And QUery me this – Most mixer apps select the channel when the fader is grabbed. Why is that a separate function (fader move vs channel select) in the QU app? What possible use does that enable? Mostly mixing on the cafe’s Touchmix which does auto select anytime the channel is touched, the QU method really causes me to make errors – change the volume on one channel, then reach for the PEQ only to find that another channel is QUeued up in the channel strip.

frank

[fxkParticipant]

Flash the blue LED Mix Buttons as selected, and SEL button flashed at reduced brightness when anything but LR is selected.

[fxkParticipant]

I agree. The current setup (console AND iPad app) are far from intuitive.

[fxkParticipant]

QSC Touchmix has a decent implementation I’d like to see adopted by A&H.
The normal 4-band PEQ plus a separate shelving buttons (High and Low) and a separate variable High-Pass/Variable Low Pass Low Pass w/button all right there on the PEQ screen. No looking around, no twisting an encoder or slider (iPad app) to get to shelving or filters.

[fxkParticipant]

Hmmm… going to have to look at QuControl to see if that is an option. Good thinking.

[fxkParticipant]

Good observation, PEJ. One could go the “crude” route – pull the lamp plug before shutting the mixer down. Not pretty, but effective.

[fxkParticipant]

Good, solid debugging techniques, PEJ. One change, test, move on.

[fxkParticipant]

Moderator,
Are you saying that dSnake can be run through a switch successfully? If on a switch, then in theory one could use the switch to create a monitor split?

[fxkParticipant]

Welcome to the space between the rock and hard place where I live.

I am unlucky enough to have one of the early QU16 mixers that exhibit phantom pop pulse on all channels, muted or not. (reared its ugly head with latest version of the firmware) So don’t hot plug phantom, but make it a royal PITA to turn it off. There is an “optional” fix that is outside of warranty for my mixer for which A&H will not pay…

I wrote A&H about phantom pop even when muted and was chastised by both A&H and this community for not turning phantom power off before connecting or disconnecting an input.

Consider a open mic or festival situation where one is changing stages once every 15 minutes or every hour. Going through channel by channel and doing the long-hold phantom off really eats into the changeover times. (needless to see my fat fingers cover the button AND INDICATOR making it all that more a pain) Saving a scene with phantom for the various acts is a plus, but only if one can kill the phantom in-between.

Two options:
1. Being able to assign phantom on-off to the select key would allow a FAST way that could easily be incorporated into a fast workflow.

2. Assigning a assignable button to global phantom on/off would be a great fix. Global off, global on based on channel configuration.

One or the other, please, if it is INSISTED that the archaic practice of killing phantom when reassigning inputs between stage changes.

Yeah, there are workarounds. Use the AB168, where hot plugging the phantom does not cause the pop. Load a generic scene that has all phantom turned off and then load the desired scene (hope no one os on an announce mic during the two scene switching)

frank

[Author]

Posts