New Qu Series brochure :new block diagram with firmware 1.7 displayed

Forums Forums Qu Forums Qu general discussions New Qu Series brochure :new block diagram with firmware 1.7 displayed

This topic contains 20 replies, has 10 voices, and was last updated by Profile photo of mervaka mervaka 6 years, 6 months ago.

Viewing 6 posts - 16 through 21 (of 21 total)
  • Author
    Posts
  • #45999
    Profile photo of
    Anonymous

    Firmware 1.7:
    “Are we nearly there yet” says the child in the back seat of the car heading to …. with an ice cream.. waiting waiting patiently

    SO I see from the block diagram you can access matrix outputs on a QU-Pac, only from the AR box, which makes sense of course as there are no physical outputs.
    And also does the other pic show there is a delay for the Alt outputs (from the matrix) as well?
    you need to click on the jpegs to see the whole image

    So will this be the same as for a QU-16?

    #46003
    Profile photo of mervaka
    mervaka
    Participant

    Alt and AES out have always been able to route a matrix source. Any delay would be part of the matrix channel processing. I don’t see anything to suggest otherwise.

    #46004
    Profile photo of
    Anonymous

    Does the QU16 have a matrix already?
    I must have missed something there?
    The way I was reading this is that the Matrix will be available only from the AR box’s on the QU-Pac.
    I’m wondering if the QU-16 will do the same (with firmware 1.7)although from reading further I wonder if the QU16 has the processing power?

    #46005
    Profile photo of cornelius78
    cornelius78
    Participant

    Despite the QuPac having the Qu32 brains, which includes 2x st mtxs, it only has the physical IO of a Qu16, and the physical outputs on the QuPac are already assigned to mix outs and LR, which is why at first glance it seems you can only get mtx outs if you use an AR.

    What I imagine you could do is set up a mtx, dial in the delay, then set either the AES socket or alt out socket to source its signal from the matrix. That way you can get a mtx out using local outputs without an AR (or you could get creative with the pafl bus.) As Mervaka said, the delay you dial in would be part of the mtx processing, not specific to the actual socket. This works on a QuPac because the QuPac has Qu32 brains (which include 2x st mtxs.) It won’t work on a Qu16 because the Qu16 doesn’t have the mtxs to begin with.

    #46006
    Profile photo of
    Anonymous

    yes correct.
    I know the QU16 has no mtxs.
    The info is there in the ‘Getting started guide’ in black and orange.
    I’m hypothesizing.
    old fashioned thinking :+)

    #46011
    Profile photo of mervaka
    mervaka
    Participant

    What I meant to say was you can already route matrices to AES/Alt outs on Qu-24/32. Presence of matrix channels and presence of physical IO are separate issues.

Viewing 6 posts - 16 through 21 (of 21 total)

You must be logged in to reply to this topic.