[Mfk0815Participant]

YOu are right USB support is not very handy on A&H consoles in general.
First of all you have to know do not use ‘repair disk’ on windows after formatting the USB drive with the console.
I personally have only some audio files on the stick I use for checking the sound system. all other audio files I play from an external source (PC/iPod/smartphone…). for the get in music I use most of the time a cheap Lenovo tablet. This is far more useful than the USB audio function on any desk and therefore also more useful that what is provided on the dLive.

[Mfk0815Participant]

I am using a SQ6 with the dante card for live sound engineering and recording.
I would say that the quality of the preamps is more than good enough for recording purpose. If you have sound problems you would have it from the environmental situation rather than from the preamps.
Will there be people who are not satisfied with the SQ preamp? Sure, but because the choice of the „right“ preamp is a mythical holy grail stuff, this is true for any given preamp. Fact is for me that preamps in the most existing digital mixers or audiointerfaces are good enough for recording.
Second, you can use the four jack inputs, these are line inputs without mic preamps.
But if sou want to exchange all mic preampsby others maybe the SQ is not the right choice and you better go the audiointerface route.

[Mfk0815Participant]

You can use the same input on more than one channel but they all share the same gain. but every channel also have an individual digital trim which can be used to adjust the internal channel gain. The rest opf the hannel processing (Preamp, Gate EQ, Compressor and routing) is then individual for each channel which uses that single input.

[Mfk0815Participant]

Hello Keith
Thank you for the clarification. But would it be possible to add also the information of how much additional latency we have to expect when using the Stageboxes? There are some rumours about the latency of the SRC when using the dSnake devices and also when using the DX Hub. That also would be helpful to make the right decision.

Thanks
Klaus

[Mfk0815Participant]

+1

[Mfk0815Participant]

This is for sure a beta for a paid app since the payments are part of David‘s income. But the price for the android versions of his mixing apps is fair and worth every cent.

[Mfk0815Participant]

+1

[Mfk0815Participant]

Having a common time basis on all used devices during a show is always a bonus. Even if it is not that important how to implement such feature it is always a good idea to use an existing solution like NTP, which is now standard across all OS platforms, than reinventing the sqare wheel by creating a new mechanism.
So my vote also goes to (X)NTP.

[Mfk0815Participant]

Hmm, Brian, you did not mentioned why you are struggling with the X32. So maybe you now exchange one product by another just to see you will have the same issues. For me personally the Qu was never an option to replace the X32.
If you want to replace the X32 you should go the SQ route. It become now more and more a competitive product to replace the X32 or M32, even if there are still some open points on the comparsion chart. Ok, there is no rack only version available for the SQ but probably you will like the possibilty to use a hardware surface once when the Wifi breaks down. And the SQ comes with remote apps for IOS and Android.

BTW: Mixingstation for QU is developed by the same guy as Mixingstation for X32. So, even if the feature set is not the same, both apps shares the same intellectual DNA.

Regards

[Mfk0815Participant]

Short anser: no.
They both ‚talk‘ a different network protocol. You can use the DX168 only with dLive and SQ. And you can use the QU-SB with the stageboxes AR2412,AR804 and AB168 or, when you do not use stageboxes on the QU, you can connect the QU to the SQ.
The SQ can ,talk‘ different protocols via SLink but always one per SLink-connector at any given time (there is a SLink card available to add an extra SLink connector).

[Mfk0815Participant]

last Saturday I missed a de-esser desperately. I had an male singer with significant S’s. At the end I fixed the issue somehow with the channel compressor and the keyfilter. A ducking gate would be in that case the better solution but is also not available on the SQ:-(

[Mfk0815Participant]

In my dayjob I am software developer. So I have some insider knowledge on how development is done today. In the past most developers coming from other engineering disciplines, because IT was not or less educated in those days but they have a lot of knowledge about the so called businessdomain (in our case audio engineering and mixing desks) Today we have a lot of well educated software developer. But those developers only know a lot of software development but less or nothing about the business domain. So they can implement a particular feature but do not look over the edge of the plate. On the past this was done by the developerbased on his deep knowledge of the background of this feature. So what can be done? Either educate the developers in the business domain, use a test team with deep knowledge of the domain or letthe users do that job for you. I cannot exactly say which one is done at A&H, I just hope that it is not the third option only;-)

But on the other hand people tends to forget how long firmware improvements lasts also for other consoles. For instance the jump from 1.0.x to the well filled package of 2.x lasts round about 18 month for the X32. For other consoles its more or less the same. So A&H still have the good chace to surprise us.

[Mfk0815Participant]

Hmm, in my opinion the SQ is a real great device. Good size, good audio and, asfar as i can it say, also a good architecure (with some weakness e.g. the USB design). Also allot of the basic software stuff is fine. But it seems that a lot of little things are not thought to the end. An example is the missing mono matrix. Or, we now got with the new update the possibility to assign also some FX parameters to the soft rotaries, which is a great idea. But why is there no possibilty to assign name and color for that. Now you can read FXtime or FXAmnt on the display and all of them are colored magenta. This cannot be the big issue to implement this but it helps the user a lot.
Or why can we now assign the PAFL bus to any physical output but there is no possibility to control the output level? Ok, you can use the listen bus which level can be controlled. But only in a sub, sub page of the Setup or when you change the Masterfader mode. Why not a assignable fader for both, the layers as well as the soft rotaries? Little missing things which complicates the workflow of the users.

BTW. I do notthink that the SQ is good for a theater, even if there would be a mono matrix. The scene system is only rudimentary implemented and not helpful for theatrical work. But thats another story.

[Mfk0815Participant]

I also did not find a solution for the PAFL output. But you can use the Listen bus together with the listen bus mode of the Main fader. On the listen bus you hear the same as on the PAFL but its level can be controlled.
I would love to have dedicated faders for PAFL and listen bus which are assignable to fader layers as well as on soft rotaries.

[Mfk0815Participant]

With V1.3 you can use the Softrotaries to control a time parameter and on some fx types also a second parameter. The value is displayed while you change it or when you use the view button. See new manual on page 57 which parameters for the different fx types can be assigned to the soft rotaries.
Now the soft rotaries become more and mor useful. A custom label and color would make it even more useful.

[Author]

Posts