[KeithJ A&HModerator]

Hi @dhuijberts –

Insert the FX unit you want first in the chain using the Group insert point
Use the second FX unit as ‘Mix -> Return’ being fed from the Group
Route the FX return from the second unit wherever you need it to go

Hope this helps!
Keith.

[KeithJ A&HModerator]

Hi @Ash

As of V1.5.0, you can patch your Talkback, post ‘Talk’ key, directly from the ‘I/O > Outputs > Monitor Out’ screen.
🙂

Cheers!
Keith.

[KeithJ A&HModerator]

Hi @Neil –

As we have explained through the support system, we need to hear from the distributor before Add-ons can be transferred to the new unit.
We have chased up the distributor from our end, as they have asked about the transfer but not yet gone through the process and given us all the information we need to proceed.

Sorry this has taken longer than we’d all like – we have tried to make the process as easy as possible, but with Add-ons being locked to the console, we need to confirm details with the distributor when they actually have the unit in their hands and this is why going through the dealer (which totally makes sense for what is effectively an issue straight out of the box) will add to the time frame.

We will be in touch as soon as we have the info we need.

Thanks,
Keith.

[KeithJ A&HModerator]

@er1cnl – absolutely, hence the comment to imply exactly that!

I wouldn’t say this would never happen, but to repeat…. or echo…. (sorry) from one of the threads linked to:

Presumably you are asking about this because you might expect to be able to tap in a tempo and have repeats match that tempo.
However, the echo uses 3 virtual heads which can be switched on/off in different combinations, each with their own min/max value that you are scaling with the time control.
Therefore, linking tap tempo to, say, the first head would not give you what you might expect with the second and would only make some sense in the modes that include that first head.
The differences in timing between the virtual heads are also a big part of the sound.

Echo is designed to give a smeary, spacey, thick echo effect, not exact tap tempo’d repeats.
The Stereo Tap delay and BBD already have this covered

Cheers,
Keith.

[KeithJ A&HModerator]

Hi @Em

I think some confusion with dSnake and Qu-SB/Qu-Pac is because the I/O sockets on Qu itself are fixed/’hard patched’ (and labelled) but dSnake inputs are patchable so what sometimes helps is to think about the mixer channels (in the core) separately from the input/output sockets.
Then you can think about the 32 input channels in the Qu core which are always there, and you just need to decide which input signal to send to them:
The first 16 input channels can be sourced from local= Qu-SB sockets as numbered, dSnake= digital snake inputs 1-40 or USB= Qu-Drive multitrack 1-16 or USB-B channels 1-16.
The next 16 input channels can be sourced from dSnake= inputs 1-40 or USB= USB-B channels 17-32.

So with an AB168 connected and wanting to use its input sockets 1-16 for input channels 17-32, you need to patch the dSnake inputs 1-16 (the AB168) to input channels 17-32 (in the core) then also switch these channels to ‘dSnake’.
By default, the dSnake input is already double patched, 1-16 > 1-16 and also 1-16 > 17-32. So if you haven’t changed anything else, you can simply switch the input source for 17-32 to be dSnake.

Regarding the N/C, this could either be because you are patching non-connected sockets from dSnake (i.e. input sockets above #16 when you only have 16 connected), there is a firmware update going on (firmware is auto-matched on connection, so if an update is required, it could take a couple of minutes) or there is something wrong with the connection.

If you’re still having issues, just give us a shout using https://support.allen-heath.com 🙂

Cheers!
Keith.

[KeithJ A&HModerator]

Yep, this was discussed a couple of times fairly recently:

FX delay regen

tape echo

(though I appreciate this separate topic may have been created as both of those are in general discussions…)

Cheers,
Keith.

[KeithJ A&HModerator]

@brian

It’s confusing, being that they use the same name, but I think you’re conflating two different types of clock here.

a) Audio clock, clocking, sync, sample rate – there is an internal clock in all digital consoles which is required for digital audio processing and transfer (e.g. console <-> expander or console <-> console).
b) real time clock (RTC), date, time – some of our consoles have an RTC, Qu and SQ do not. The benefits of an RTC are that the date and time could be shown on screen and stored files can be timestamped. The downsides are the need for an internal battery (which will need replacing at some point) and the extra cost.

We looked at the possible system connections along with the importance of clocking/syncing in a live stream here – https://www.facebook.com/112696882086203/videos/262500062266038
But in short, the Qu was never intended to have system<->system connections so it can be used but cannot clock to an external source so must always be the leader.

Cheers,
Keith.

[KeithJ A&HModerator]

Hi @ppisanchyn

No – ganging is the way to achieve this.
As stereo input channels control both input sockets at once, they should be used with a stereo pair of the same type from the same ‘box’.
For this reason, stereo input channels (and stereo mix external inputs) can only be sourced from an odd/even socket pair.

Cheers,
Keith.

[KeithJ A&HModerator]

@courtcourt

In short, no.
There are ways to create setups using MIDI between systems to have one make changes to the other, but these are not really practical.

The best options here would be to use remote audio racks/boxes (AR2412, AR84 or AB168) or to simply use an iPad running Qu-Pad for full remote, wireless control.

Thanks,
Keith.

[KeithJ A&HModerator]

Hi @courtcourt

There are many similarities but some of the other differences (looking at the additional features on SQ) aside from the 48 input channels and 96kHz processing you mention are:

• Intelligent SLink port for connection to expanders and other systems running dSnake, DX or GigaACE/GX protocols ( https://www.allen-heath.com/everything-io/ )
• I/O port for option cards including Dante, Waves, MADI, SLink
• DEEP processing options (high end modeling processing from dLive) and dynamic/multiband tools – ( https://www.allen-heath.com/key-series/sq/sq-add-on-processing/ )
• Lower latency (<0.7ms from analogue in to analogue out with all processing enabled)
• More output busses, all with stereo/mono options and all 12 mixes can be either group or aux
• Larger, capacitive touchscreen
• Fully customisable patching
• Fully customisable channel strip layout with scribble strips
• More softkeys
• Multi-platform support and offline mode for the SQ-MixPad remote app
• More recording options (48/96kHz and up to 32ch direct to drive)
• Tie Lines
• Dual 24ch AMM’s with option to combine into a single 48ch AMM

Whether or not these make SQ significantly better really depends on your requirements!

Cheers 🙂
Keith.

[KeithJ A&HModerator]

@jimbo1907

Another thing is to ensure that you’re connecting the console to the router as a client, in the same way as you would when connecting a computer.
i.e. connect to a LAN port on the router (often blue), rather than the modem/internet port (often yellow).

If you need further support, you can contact us directly ( https://support.allen-heath.com ) or as you’re in the US, if you wanted to speak to someone on the phone you could contact your distributor AM&S who have a dedicated A&H support team ( https://www.allen-heath.com/dist_type/usa/ ).

Thanks!
Keith.

[KeithJ A&HModerator]

@SparkyAteOneToo

Yes, this is possible and there are many users that we’ve heard from who’ve set this up successfully 🙂
We cannot guarantee that you will be able to do this with all media convertors so would always recommend purchasing from somewhere that will allow returns.
You can find more information on requirements in the following articles:
https://support.allen-heath.com/hc/en-gb/articles/4403304180497-Audio-Networking-Can-I-run-dSNAKE-through-a-network-switch-
https://support.allen-heath.com/hc/en-gb/articles/4403553378449-Audio-Networking-gigaACE-and-DX-networking-VLANs-and-fibre-optics
(note that dSnake and DX are both layer 2 fast ethernet protocols. They have different channel count, sample rate and control messages, but have the same requirements for conversion/switches/fibre)

Thanks!
Keith.

[KeithJ A&HModerator]

Hi @keefus

Sorry to hear this, it’s obviously not the experience we’d wish or expect you to have, nor the experience of most users.
Whilst we do everything we can through the design and development process, and QC every single unit before shipping, things can unfortunately fail.

Anything intermittent and time related can be tricky, but being based in the US, the best thing to do is contact our distributor AM&S (if you haven’t done so already).
They have a dedicated support team and will be able to fully check over your Qu to find out what exactly is going on and put it right.

Thanks,
Keith.

[KeithJ A&HModerator]

@memecode –

The headphone/listen/PFL bus on all ZED mixers is mono and is for checking signals ‘pre-fade’ before adding them to the mix.
Then as you say, with no PFL switches engaged, the headphone output is fed by the stereo main mix instead.

You can see this and all the internal routing in the block diagram here – https://www.allen-heath.com/media/ZEDi-8-Technical-Datasheet.pdf#page=3&zoom=150,-178,761

Thanks,
Keith.

[KeithJ A&HModerator]

@jamesremuscat –

Thanks for working with us on this and for updating the post for anybody else who may run into something similar.
We’ll be looking into it further and although it won’t cause an issue in the majority of cases, it obviously has in yours and will be noted as a bug.

Cheers,
Keith.

[Author]

Posts