Forum Replies Created
-
AuthorPosts
-
2014/03/23 at 9:56 am #38486
Hi Martin,
The DAW Control app is designed to use the MIDI strips for controlling a DAW. Have you set up the MIDI strips in the Custom Layer?
If you get any conflict with the Input channel faders or Master strips, try disabling the Qu MIDI port in Studio One (leave only the DAW Control virtual ports enabled).
Hope this helps.
2014/03/20 at 11:16 am #38413The other thing is, that I can not playback waves generated with Cubase 7.
Hi Martin,
What version of firmware are you running? V1.31 added support for Broadcast Wave files (BWF chunks) as well as WAVE64 headers. If you are already running V1.31 could you please submit a support ticket here and attach a copy of these Cubase 7 files? That would help us investigate.
Thanks,
Nicola2014/03/20 at 9:25 am #38411Hi Davyd,
You should be able to connect over Ethernet. The reason why we only refer to USB in the pdf is that it’s plug ‘n play and most will use USB for audio anyway.
First, make sure the mixer is set to a static IP address compatible with your computer. By default it is set to DHCP which will not work when connected directly into a computer. For example, set the Qu to 192.168.1.60 and your Mac to 192.168.1.10 or similar, both with subnet 255.255.255.0. In DAW Control, choose TCP/IP. If the mixer is not available in the dropdown box, type in its IP address and tick the Connect box.
Note that the Qu will only support one Network connection. You cannot run DAW Control at the same time as Qu-Pad for example.
Hope this helps.
2014/03/18 at 11:28 am #38345it is wise to reboot the console after the configuration changes
I just want to clarify that the mixer configuration freeze is fixed in V1.40.
If you experience any freeze with V1.40 please submit a ticket to our Support department here and attach your event logs.
2014/03/18 at 11:12 am #38344To clarify, there is no need to install the A&H DAW Control app for USB streaming applications. Qu-16 and Qu-24 are Core Audio compliant on Mac OS X and will appear as an audio and MIDI device without any driver installation. Just plug ‘n play.
The DAW Control app is for, well, DAW control only. That is if you want to control track levels, mutes etc. from the desk MIDI strips.
Rob, when you play stereo files with iTunes, check the settings in Utility / Audio & MIDI as dhak suggested. Select the Qu device and click on ‘Configure speakers’. Set the speakers to the required USB output, for example 21-22 to stream to Qu-16 ST3. On the mixer use the Preamp screen Fn key Source page to patch USB B to ST3. Make sure you have set ‘USB B Streaming’ as the global USB source.
When you have this working, try with Pro Tools. Set the Qu mixer as the Current Engine in Pro Tools Setup / Playback Engine. Make sure your Pro Tools session is running at 48kHz sample rate. Click ‘Setup/I/O…’ and click the ‘Default’ button on the Input, Output and Bus tabs to set everything to the default names and paths in Pro Tools. Remember that audio is returned one-to-one to the input channels. Select track 1, click its ‘Output’ drop down menu under the I/O label in the mixer view, then select Mono output 1. This will feed the Qu-16 Mono ch 1. Use the Preamp screen Source page again to patch USB B to the channel. Repeat for all other tracks.
2014/03/18 at 10:46 am #38343No, we don’t support Aviom mixers with a Qu-16 / Qu-24 and AR2412. The GLD software has a special ‘Aviom’ mode for this.
2014/03/17 at 1:27 pm #38326Hi Mario,
The dSNAKE port on Qu and GLD mixers is not compatible with Aviom devices. We support A-16ii mixers only on the AR2412 Monitor port (when using a GLD) or the MultiOut / MiniMultiOut cards for iLive.
2014/03/07 at 11:07 am #38139This is a known issue, please see here.
2014/03/06 at 2:26 pm #38083is anyone of you attending the Pro Light and Sound in Frankfurt next week?
Sure we are. Léon and I will be there together with representatives from Sales, Marketing and R&D.
2014/03/06 at 2:23 pm #38082V1.4 is now live on our main website here together with updated User Guide and Screen Reference Guide.
Enjoy.
2014/03/06 at 1:09 pm #38079Please use for your personal educational use only.
Audio courtesy of local band Grace Notes.
Not to be distributed.
https://109.203.103.60/tech/Qu-16/AHQU.zip2014/03/06 at 1:03 pm #38078We have a tool in iLive which is exactly what you are asking for – a Scene import with filters 🙂
However you can try this workaround with GLD: open the guest Show and copy a Scene. Open your festival Show again and paste into an empty Scene location. Now either set some Recall Filters for this Scene or some global Scene Safes so that your output patch etc. are not affected when you press Recall.
It’s not ideal as it still requires to jump from one Show to the other, and I believe it’s never been documented – probably needs some more testing! I guess different bus configurations will result in the GLD attempting a ‘best fit’.
Hope this helps.
2014/02/28 at 10:06 am #37969George,
I’ll pass your feedback to our Software team.Re: point 3, be aware that the meters in the Qu-Drive page show playback meters (therefore always fixed to CH1-16 and ST1 on Qu-16) unless you actually arm a recording, that’s when they switch to Recording meters (and follow your USB output patch).
2014/02/28 at 10:00 am #37968You can block the USB Output patch in the Global Filter screen, so that it is not affected by Scene recall.
The reason why Track 17-18 are now set to LR is because they now share the same patch as Qu-Drive Stereo recording. This was necessary in order to accommodate the request for patchable outputs and support of Qu-24.
2014/02/27 at 9:40 am #37951Hi George,
If you’ve just updated to V1.31, note that the Track 17-18 default patching has changed from ST1 to LR. Qu-Drive Stereo recording shares the same patch as Track 17-18. You might need to patch ST1 again from the Setup / Output Patch / USB Audio screen.
If you are recording with a DAW, make sure the DAW is routing back an individual track (not its master bus) to USB 17-18.
Hope this helps.
-
AuthorPosts
