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

Qu Qu General Discussions
1

Hi,
I have reading interesting something in the qu series brochure update (since Qu-pac annonce) :
The block diagram indicate 1.7 firmware version, for now I can see the ducker fonction will be present for inputs and group masters.
If you see an other difference…

link to the brohure

2

Hi Flo,

Well spotted. There is also a paragraph in the brochure about the upcoming Channel Ducker, scheduled for v1.7 release sometime in March subject to test.

3

March - yummy :wink:

I’ll look forward to April ('cos I’m a pessimist and would rather be pleasantly surprised)

4

Wil the ducker also come to the gld?

It is very silent there after 1.42

Richard

5

the ducker would be helpful on all the A&H consoles

6

errm - what is a channel ducker?

7

Dynamic processing (gate/compressor) which reduces the volume of a signal when the trigger signal exceeds a specified level.

Often shown as a gate option.

A normal gate is shown on the graph as a triangle truncated on the left, so very low volumes produce zero output, then normal behaviour is resumed above that level.

A ducking gate is truncated on the right, very high levels get turned off.

One use we make at church is to have the vocal FX channel ducked by the “vocal boost” mix, which boosts the vocalists signal to the loop and foyer mixes for when they start speaking (as opposed to singing).

8

Thank you nicola for the information ! Waiting next month for the new features coming with 1.7

9

aha, thanks for the explanation XAP Bob

10

Hi to all.
@nicola, there a release date for the new firmaware?. I have some problems with the 1.6 than 1.5 do not have. please.
Greetings from Argentina!!

11

We are still on track for release before the end of the month.

Andres, if you are experiencing problems with V1.6 please contact our local distributor for assistance or open a Support ticket.

12 

   _                             .-.
  / )  .-.    ___          __   (   )
 ( (  (   ) .'___)        (__'-._) (
  \ '._) (,'.'               '.     '-.
   '.      /  "\               '    -. '.
     )    /   \ \   .-.   ,'.   )  (  ',_)    _
   .'    (     \ \ (   \ . .' .'    )    .-. ( \
  (  .''. '.    \ \|  .' .' ,',--, /    (   ) ) )
   \ \   ', :    \    .-'  ( (  ( (     _) (,' /
    \ \   : :    )  / _     ' .  \ \  ,'      /
  ,' ,'   : ;   /  /,' '.   /.'  / / ( (\    (
  '.'      "   (    .-'. \       ''   \_)\    \
                \  |    \ \__             )    )
              ___\ |     \___;           /  , /
             /  ___)                    (  ( (
  PN         '.'                         ) ;) ;
                                        (_/(_/
13

Thanks for the reponse @nicola!

14

nice dancing bob. :+)

15

Unfortunately I can’t claim it as my own :wink:

16

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?

17

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.

18

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?

19

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.

20

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 :+)