Forum Replies Created
-
AuthorPosts
-
2014/04/30 at 8:19 am #39443
Hi Mike,
– Is your Mac set to a static IP address compatible with the GLD (GLD default is 192.168.1.50) and to the same subnet mask?
– Check Editor and GLD are both running the latest version of software.
– Try switching off WiFi in your Mac. Sometimes it helps.
– If your GLD does not appear in the dropdown box of the Editor Connection window, choose Custom and type in the GLD IP address manually.Hope this helps.
2014/04/29 at 11:00 am #39412You should really contact Tech Support. Please submit a ticket with all the information above to our UK Support team here:
https://allen-heath.helpserve.com/default/2014/04/29 at 10:49 am #39410GLD does send out MIDI messages for fader levels of audio channels. However these are NRPN messages as detailed in the GLD MIDI / TCP specs. Not all DAWs can interpret these messages (as opposed to the standard CC we use for the MIDI strips, which are widely supported), but I believe Logic can!
Install the TCP IP MIDI Driver (not the DAW Control driver) and manually assign the faders to your tracks. You can use the Learn function but you’ll need to tweak with the control settings. Try Unsigned, Multiply by 1.00, and set the Mode to Scaled.
Hope this helps.
2014/04/27 at 2:59 pm #39381Hi,
Where are you based? I’d recommend you contact our local distributor for immediate assistance, but here are a few tips:
– Make sure you have bridged the ACE card ‘Control Network’ port into one of the Network ports, at both the iDR and Surface side.
– Reset the network settings of both rack and Surface by holding down the recessed Reset switch on the CPU (Network) module whilst powering up.
– Check you are running the same firmware version on rack and Surface. If needed, download the latest version from our website and update the devices.
– Try a shorter Cat5e cable if none of the above help. Should this fail too, try connecting the iDR10 Network to the Surface Network (bypassing ACE) – this way you should get full control of the iDR but no local audio.Remember you can always drive the iDR off Editor or MixPad should the Surface still fail to connect.
Should you need clarification on any of the above, check out the iLive training videos on our Youtube channel.
Hope this helps.
2014/04/25 at 8:53 am #39349Hi all,
Where to start.
Yes the buffer size is a key factor in preventing dropouts in the write process, as it compensates for the difference between the rate at which data is transmitted and the rate at which it can be written on the drive. When a USB storage device causes a pause that is longer than the buffer time, a dropout occurs and data is lost. Qu-Drive has a limited buffer when compared to a computer, but as some of you have noticed, one of the V1.4 improvements to Qu-Drive was allocating some extra memory for buffering.
As we cannot reproduce the dropouts with any of our recommended drives, freshly formatted and V1.4 running on the mixer, we can only assume most of the issues reported here are due to mechanical conditions such as vibration. Robbocurry and others have posted about this, and this is what I found on an HGST tech sheet (look at the test results of a hard drive on a shaker in their article!):
One of the greatest hindrances to hard disk performance is vibration. Like a needle on a record, the disk drive’s head must try to follow narrow data tracks in order to read (or write) information. Physical disturbances can throw the head off-track and cause a delay while the actuator repositions it. This eventually has an impact on the hard drive’s input/output performance.
You are also correct in thinking that SSD and flash thumb drives are virtually immune to this problem. However, SSD drives can be prone to other issues such as performance degradation over time as DMAudio has pointed out. As for USB keys, most aren’t fast enough for multitrack recording, hence our reluctance in recommending this medium. Qu-Drive requires a continuous data rate of around 21 Mbit/s when recording multitrack. Unfortunately manufacturers of USB keys typically publish burst (max) write transfer rates, which are of little significance here. Sustained rates are seldom published.
We had good reports of Sandisk Extreme USB keys (available in 16, 32 and 64 GB) and must say this is looking promising here. We need some further testing but we definitely want to include some of these devices in our list of recommended peripherals. However please be aware that another problem common to both SSD and USB keys is the batch variance of memory chipsets used by manufacturers – a device might perform well in our tests, but the same model purchased in the US or six months down the line could show different performance. I guess this is the reason why other pro audio manufacturers have been much vaguer with their recommendations.
Ultimately our list should be taken as a guideline only and you should always test the USB device thoroughly before putting into service.
Hope this helps.
2014/04/23 at 8:24 am #39268Check that audio from iTunes is not going to Channel 1 & 2 on the mixer. If it is, you have to patch the standard OS X stereo output to a different USB out. In Audio MIDI Setup, select the Qu audio device and click Configure Speakers, then assign the stereo output to 21-22 for ST3.
Hope this helps.
2014/04/10 at 8:18 am #38910You can use Waves Multirack Native on a Mac or PC computer for send / return effects (for example Aux 1 -> USB plugin -> ST1 channel) such as reverbs and delays.
Inserting plugins on a channel is not possible I’m afraid, as the channel source is EITHER analogue (local/dSNAKE) OR USB.
Hope this helps.
2014/04/09 at 4:18 pm #38888Hi Rob,
I confirm there is a UI bug but your inserts should work anyway. When you press Apply, the correct routing assignment is made, but the User Interface displays other, unrelated sockets. If you spin again to the correct sockets, you will see the actual assignments displayed below the selection boxes. Another clue that the assignment is in place is the I/O screen.
I have now logged this in our bug tracking system.
Nicola
2014/04/08 at 8:32 am #38839The fader knobs on Qu-16 and Qu-24 are not touch sensitive. Unfortunately this limits their use with DAW automation, as the mixer cannot sense your willingness to overwrite the movement. You can use Write and Read automation modes only I’m afraid – Touch, Latch or similar will not work, as you have noticed.
2014/04/06 at 3:42 pm #38786Sample rate is fixed 48kHz to match the mixer internal processing. Try converting your projects to 48kHz first, then choosing the Qu ASIO interface. Off-line sample rate conversion by a DAW will typically yield better results than on-the-fly conversion anyway.
2014/04/06 at 3:34 pm #38785Hi TB,
None of these options is supported I’m afraid. I’d suggest considering an AR2412 which comes with a dedicated Monitor port.
2014/04/04 at 8:32 am #38719Hi Andy,
Have you updated Mavericks to 10.9.2 and your Qu-16 to V1.4?2014/04/03 at 1:59 pm #38694FX User Libraries are now supported in firmware V1.4.
2014/04/03 at 1:57 pm #38693We are pleased to announce that V1.4 supports USB streaming to/from Windows computers.
2014/03/31 at 12:58 pm #38640Hi Rob,
Have you checked the Qu-24 output assignment in the Setup / Output Patch / USB screen?
-
AuthorPosts
