[WaihekeSoundieParticipant]

Thanks for the suggestion.. re-plugged.. was going to reformat.. but this time it can see the file and now it works..? On the 8th go it finally found the file and installed it…

It takes over 1 min from plugging in a Segate 1TB Expansion laptop HDrive (USB powered) into the USB port to the OS advising that the drive is available and displaying back capacity stats.. does everyone experience this long a delay?

It won’t read my Toshiba 4gb stick at all and I notice that it won’t power one of my portable drives from the USB power properly either..

But YAH– 1.4 is loaded and I love the new interface features and of course Windows DAW integration. Windows integration is great especially since I’m having drop outs on small projects with QU16 ->Reaper64 on Mavericks 🙁 Posted elsewhere on that.

Thanks dev team for 1.4 🙂

[WaihekeSoundieParticipant]

Yeh– think I get you.
Locking the customer layer means that the only layer you can use is the custom layer. I realise now that this is useful if you have mapped all the faders you need right now for your show (or recording) to the custom layer — In this scenario, freezing to just the custom layer means you simply can’t adjust in the wrong layer. Actually that is quite cool.

Mind you, mixing live I find I’m much more likely to adjust a fader in the wrong MIX than in the wrong LAYER but nothing to be done abut this that I can see– it is just practice and discipline–
Changed a monitor MIX setting. All done ? –> Immediately revert to LR!!
Another one? All Done ? –> Immediately revert to LR!!

If anybody else has any tips about this– would be appreciated 🙂
Andy

[WaihekeSoundieParticipant]

Well it does pretty much what I experienced.. if you click it on the only layer you can work is the custom layer– clicking to switch to the returns layer or the channels layer does nothing. Can’t quite figure why you would want this though– but I’m only slowly getting to grips with the custom layer..
Can some one explain the use case for this button?
Thanks

[WaihekeSoundieParticipant]

Sorry– yes.. I just found it and it was set on.. page 43 explains
(my bad.. RTFM)
Many thanks.
I do love my QU 16.. 🙂

[WaihekeSoundieParticipant]

I did read somewhere that there was a hardware fix to the bang when plugging / unplugging with PP engaged.. but would mean sending back to UK (from NZ) and who would pay? Is there a policy or precedent for this?

But regarding the loud pops on switching scenes when PP turned On or Off — I will know to set mute groups with global filters before scene changes when I can but it won’t suit every case I’m sure..
So I would be keen to hear more on this..

[WaihekeSoundieParticipant]

Thanks for confirming it is not just my unit that has this lag.
The huge pop on plugging / unplugging when phantom engaged can be fixed with a H/W return to base eh. That sounds like a bit of a mission though. Has it been establish whether A&H pay for the return? Think they prob should but is there a precedent?

Andy

[WaihekeSoundieParticipant]

Totally stoked that I see Windows streaming will be supported– that is really , really good news for a guy who does live and studio work.. makes it a really flexible useful product 🙂 THANK YOU !!

[WaihekeSoundieParticipant]

Umm..yeh ugh.. to England from NZ? Would this be covered under warranty and the return cost covered by the dealer / A&H?
I just purchased mine like 3 weeks ago…

[WaihekeSoundieParticipant]

Can see why you might suggest that but I might say that on my desk there is a considerable lag between the PP turning on /off and the pair of voltage spikes.. turning off it is seconds before the first spike- perhaps 3 secs.
Maybe my new QU has a h/w fault?

[WaihekeSoundieParticipant]

Yeh, but I had 17 multi-instrumentalists in 5 acts and drums– (about 40 channels on an analog desk) and all wanted to be soundchecked– 40 into 16 is a lot of channel re-use– scenes totally came into their own for this 🙂

Course you can’t really stop the fiddle player plugging into the Banjo DI or the main vocalist taking mic 4 instead of 3 because the bass player has suddenly decided to have a wee sing. But scenes totally helped:)

[WaihekeSoundieParticipant]

Well the way this worked out for me was 5 acts unknown to me turned up for sound checks. Band 3 about 1/2 way through sound check turned out needed a bunch of phantom for their drums on channels not used in any prior band scene so phantom gets set and band 5 later swapped out a passive DI on a channel I had for Acc guitar in Band 1 with a DI requiring phantom on same channel so I engaged phantom in that scene too. As the bands came on things get unplugged and re-plugged and I increment the scenes. Happens.

Quietly next time 🙂

[WaihekeSoundieParticipant]

Yes, I see that now but I might say that there seem to be a couple of issues here:
a) horribly loud pops when a mic is physically connected / disconnected with PP on;
b) lesser pops and hiss (depending on channel gain) when I turn PP on and off (with mic connected or not).

There seemed some debate whether these issues are fixed at 1.31. They are not (on my desk anyway).

And what I found (first time out and rather publically) is that b) above can happen when you change scenes. That caught me out. So you need to mute PP channels that are on in the leaving scene OR being turned on by the new scene. So apply an across the board mute group and keep the mutes safe with filters on during scene changes if you have any PP on anywhere.

This is prob what everyone does anyway but I’m a total newbie to digital mixers and these things just aren’t written down.

I should say that I LOVE my QU 16.. it is really cool balance of features and simplicity and it sounds fantastic 🙂

[WaihekeSoundieParticipant]

Actually what I have noticed is that whenever I turn on or turn off the phantom power there is a delayed spike, a loud hiss and then an other delayed spike.. it almost pushes the level into the red.. you can see it in the meter but not hear it if the mute is on.

I have also noticed that if I connect or disconnect a mic to a channel with phantom on I get a huge spike whether muted or not…
I am running v1.31

Guess my learnings are
a) don’t connect or disconnect mics unless phantom is off
b) always mute before turning phantom on or off

Note: Because a scene change can turn phantom on and off
c) before you scene change make sure that you mute all channels affected by phantom- (a mute group on all channels (except your continuity channels)) does well BUT
d) also note you have to set a Global Filters to retain your mutes and your mute group masters otherwise the new scene may remove them as it switches and big pop again.

Bit fiddly but seems to work for me.
Appols – this prob should have gone in the troubleshooting section eh..

[Author]

Posts