ljefe I use phantom live when recording, but it is not on during playback, which is when the issue appears.
I think the issue may be resolved. I have an NVIDIA GeForce GTX 560 Ti. What I did was disable all the NVIDIA High Definition Audio instances in device manager, I do not think that fixed it, but then I updated the Intel Chipset drivers and the problem has not resurfaced since then. So far so good.
FrankieFender, that’s an interesting observation. I wonder if the issues experienced by folks could be a conflict between sound card drivers (onboard vs. Qu). Could it also be differences in sample rates between the onboard card and the Qu somehow coming into conflict?
The wav files themselves are damaged, so not a playback issue. I tried opening them on a different machine (I typically record on a MBP, but copy to a Windows workstation to mix in the studio) and in a different audio app (Audacity) and the “beep/bloop” was still there.
There’s literally no discernible audio left in the wav, even though the wave peaks look fairly normal (a bit truncated here and there, but it looks like a kick pattern on the kick wav, etc.).
I have the same problem. The pops and clicks and random noises are on the actual recordings. It really bums me out that such great and pricey gear has issues like that.
on my Samsung Laptop (i7, 8GB, Win10) no USB 3 port is usable with Audio.
Only the USB2 port works.
And it doesn’t matter wich audio driver or wich audio interface i’m using.
Had similiar issues on different machines from time to time.
Most of them related to the USB or Firewire ports.
I like how nobody comes back to share how they solved this issue. I am also having this problem. Does anyone have a solution to this? It’s driving me nuts. Playback streaming via usb from my Windows Computer.
I fixed the issue on my PC by disabling XHCI in the usb settings in the BIOS.
I’m having the same issues while streaming from USB-B to an Icecast-server with a raspberry.
Yesterday I received the following answer from A&H support (within a day, by the way. Very quick reaction!)
We are sorry to hear you are experiencing trouble with your QU24 console.
The issue you are experiencing is actually down to Intel(R) USB 3.0 eXtensible Host Controller on your computer or laptop. the QU mixer has a USB 2 interface and Intel ‘broke’ compatibility with the real time streaming protocol when they implemented this driver that deals with USB 3.0 ports.
We have been in contact with Intel, but they currently have no interest in fixing it. our software team have been looking in to this to see if there is any permanent solution we can create at our end, but this is currently ongoing.
Depending on which platform you are using there are some work around that work for some customers.
With a Mac, the only way to update or change this driver is with a full system update, and I have had feedback from a couple of users who found that updating to macOS Sierra resolved the issue.
With PC’s, you are able to update or change these host drivers independently. Some manufacturers have more recent USB host controller drivers available which ‘improve compatibility’ with USB devices. I would recommend seeing if there are any more recent drivers available for any system where you see this problem.
However, if that doesn’t work, another work around at the moment is to disable the xHCI driver using ‘Uninstall a program’ in the control panel.
This has been found to solve the issue, though it also removes USB 3.0 functionality.
Please let us know how you get on, or if there is anything else we can assist you with.
I’m not sure if there’s such an Intel host controller inside, but I’ve stopped trying to solve is in this way. I bought a Behringer UCA 202 USB soundcard to convert an analogue mix to USB and that solved the issue. It’s not the nicest solution, but it works.
Congratulaion, welcome to the club I’m not alone and you just inherited a brick!!!
Buy a new computer made with AMD part like I did and you will be fine.
I just got a follow up from Intel and here is what they want… since apparently it is not Q&H problems… there is no problem with your console as I was told.
FROM INTEL support after I offered them to do whatever they need to get more info about the issue:
"I have gotten the research done to find out what is required to create the logs for this matter.
It would be required to purchase hardware devices and download the software form the vendor to perform the validation test to get the log files. Customer can consultant vendor for further information.
For hardware required please visit: Test Solutions for USB4, Thunderbolt, USB 3.2, USB Type-C and Power Delivery-Teledyne Lecroy
Since the current OS is Windows 10*, and the USB 2.0 driver is native driver which means it comes from Microsoft, so if this is an driver issue, customer needs to get support from MS for a solution.
I understand it may be tricky to proceed with the tests, but in case you are able to, it would be great.
"
They want me to buy a very rare hardware that is probably more expensive than my laptop to start with, this is a joke and the joke is on us.
I did found the solution to the problem.
Buy a new computer with AMD part, that’s exactly what Intel suggested me to do…
It did fixed my issue…
Hi stevelogik,
Yeah the topic got split…sorry I didn’t post a link in this thread…I posted in other places, it seemed like this problem had several manifestations though…I am glad you finally got your’s resolved!
I wish this was the solution for all, I know I would have been ^&8% if I ended up not getting it to work. Love this board, but really sucked leaving work to continue work on something I should have been playing with 
TritonX,
What AMD did you purchase?
Maybe could start a SOLUTION Thread we can chime in on…If you have a good working system, maybe we can inform others of good configurations?
Actually that protocol analyzer…yeah when I saw you post that I laughed so hard…
That’s funny, Originally I was looking to see if I could find an analyzer to look for drop-out.
I did use a software analyzer to poke a bit when I was looking into this…
not as capable as doing hardware in-line…but…(within a normal person’s budget…plus I couldn’t find one at work…haha)
reading through Intel errata and manuals while falling asleep to repetitive USB data…and then NOISE…SMH…it helped me a little finally point the finger.
The middle finger Intel! haha
-s
I purchased a MSI A68MH motherboard, a cheap 4.1 GHZ AMD CPU (not the cheapest but close, forgot which one) to go with it. 8 GB of 1666MHZ, a 256GB SSD and the rest (case, PSU, HDD, monitor) I already had at home. All that for less than 500$.
It’s not as good and fast as the Intel laptop I planned to use but it’s still perfectly usable and had no issue recording with it in 2-3 weeks of usage.
I wouldn’t call buying another computer “A SOLUTION”. When I made the joke to the Intel support guy he told me, " I’m happy you found a solution", replied with "I think you didn’t get the joke… Joking aside, while not very useful, I have nothing to say against the guy who I was in contact with for the support. I have the impression he really tried to make a follow up and solve my issue but since it would require a rewrite of their drivers his bosses weren’t really willing to go that way…
Probably that there is no issues with other Intel chipsets but screw them …
For the record ! I did buy a USB 3 PCIE express card. Ok - it was only 25 bucks. I hoped that i would have a exclusive USB card /port solution to get lower latency. (Because other USB ports are used for Keyboard, Mouse, NI Maschine, USB Midi controllers and so on.)
Guess what - the Qu Pac does not work with this pci express card.
The card is a fresno logic card.
Should have bought this one:
https://www.amazon.com/StarTech-com-Express-Profile-Speed-PEXUSB4DP/dp/B002RL8V7E/ref=sr_1_4?ie=UTF8&qid=1505520370&sr=8-4&keywords=usb+2.0+pci+express
As i have still usb 2.0 ports on my pc, i will move the current devices that does not stream audo to the new usb 3.0, and give the usb 2.0 exclusive to the qu pac.
But its nevertheless annoying
The usb 3.0 should be correctly backward compatible.
Yes, it’s annoying, but that’s IT for you… if it doesn’t break the mainstream case who cares about full compatability
So Allen & Heath,
At this point wouldn’t it seem like a good idea to just write a driver to read the raw Layer2 audio stream of the dSnake.
Instead of USB, hell go Ethernet…why not?
Quick fix, maybe just change the order…USB for MIDI, dSnake for Audio??
-s
No good if you use dSnake and USB… but I’d quite like to be able to play/record over dSnake
Hey all, what is the current status with this?
I have just recently bought a QU32 and in the process of rearranging things in my studio to fit the new desk in. I was hoping, actually part of the main reason of buying the QU32, to record directly into my DAW, but reading this I am getting a little concerned on if I made the right choice. I was looking to pick up an Imac in the next few weeks to run as a DAW using Sonar/Ableton for multitrack recording, has the electrical noise issue been sorted? I know there is a fix with disabling the AHCI on PC, but that isn’t possible on the iMAC.
If it hasn’t been sorted then I suppose I will have to have a look at getting another PC built instead…not ideal, was hoping to make the switch for it’s better audio/midi handling, but if needs be n all that.
There’s no solution in the hardware of A&H. If you read the full post you will see that this is quite an actual topic. My solution was to solve it with a separate Behringer USB soundcard. No issues since.
Just the thing I was hoping to avoid by buying this mixer >.< I already have an MOTU 828mk3 and a couple of Behringer ADA8200’s but was hoping to move away from those. I really hope A&H get on to fixing this issue via firmware update or something…but then I know how some companies can be.
I’m still in communication with Intel support since A&H points the responsibility to them.
After cursing at them a few time the support guy finally seems to try hard to help me(us). I made them a explanatory video and gave them a hardware report and I’m waiting for a follow up…