Okay, maybe I’m going crazy, but after today’s WIN10 update… the issue disappeared for me. I used to get the glitch every few minutes and now I don’t remember having any throughout the whole day.
Edit: nevermind, the issue is still here but it’s not as prevalent
Noooo it did ? sure gonna update today, let you know … That would be a change!
And IT DID, sometimes at teh beginning just a milisecond or so , but that was the case already in the previous version . Well done Microsoft , euh in this case 
I have a late 2015 Mac Pro and I get the same issue. I updated it last night to see if I’d have any luck…none. It’s worse. I hear about half a second of audio and it drops out.
However, my iphone seems to work fine. I use a camera adapter (usb to lightening). I also have luck with my ipad.
I’m only using the interface side of the unit for backing tracks. I haven’t even tried using it for recording.
Any luck? After a week after WIN10 update I can say it’s definitely better, but still present enough that I can’t use it as an interface.
Got a reply from Neural two weeks ago that they’re investigating it and that’s about it.
Yes it was definitely better! But as you say, it’s not usable as an audio interface. We have to wait for Neural to solve this problem. But I must say, for me it is no “show stopper” In teh band is sounds OK , no glitches when only play with the analog inputs.
So update. Glitching continues. The only time I can use the QC as an interface without glitching is when playing games. When gaming it performs solid as a rock. System Specs: Intel i7 6850K, 32gb DDR4 3200, GTX1070, and 2 SSDs.
It may have something to do with power management. Can you try running the game and the music challenge at the same time? It is advisable to leave the game in windowed mode visible on the screen, otherwise an overly smart AI will ruin the test.
Just updated to 1.1. Still getting the USB bit crushing issue when running USB from my Android phone to the QC. The “bit crushing” runs for right at about 25 seconds. …then I get 45 seconds of clear audio. Then 25 seconds of bit crushing. 45 seconds of clear. Repeats. I ran a stopwatch to check the intervals.
Can you try it with another compliant USB device? Android hasn’t played very well with USB audio due to latency issues
All the ones I have are all Android. I may just go get the least costly iOS device to get around this. Assuming iOS doesn’t have this issue. I haven’t really noticed any latency with the Samsung Note 10+. Just the bit crushy noise.
Having the same issue for the first time after updating to CorOS 1.1.0. Anyone heard anything from NDSP on a fix yet? The QC is completely unusable at this point as I now have constant glitching. I literally only get about 4 seconds of normal sound in between constant glitching.
@atljeremy I’m having the exact same issue. I have reported to support and they mentioned that they haven’t been able to reproduce it.
I also contacted support. I just emailed them my system specs as well as something else I just discovered. So, I’ve had the QC for months now (I was in the 2nd round of pre-orders) and have always had it connect to my system through a USB port on my Apple Thunderbolt Display. I’ve never had an issue before COrOS 1.1.0 with this setup. However, to help root cause the issue, I decided to try connecting the QC directly to the computer. After doing that, the issue is completely gone. There is no glitching whatsoever. I moved it back to the Thunderbolt Display USB port and the glitching happens again. So, it seams there’s something going on with CorOS 1.1.0 and external USB (a.k.a. USB hub). I sent all of this to support so we’ll see what they say. At least I’m able to continue using the QC for now though. 
@atljeremy that’s good to know. Unfortunately even connecting directly didn’t work for me and I have a MacBook Pro with only Thunderbolt USB-C ports. So you might be right, it could be related to Thunderbolt. Sad that the QC is not usable for me at the moment :(.
So, it seams there’s something going on with CorOS 1.1.0 and external USB (a.k.a. USB hub).
I had problems using the TB-> USB already at 1.0.2 and correspondingly all glitch-free using the built-in USB ports, even through cascaded USB hubs, so there obviously are some “sensitivity” of protocol issues still going on.
Issues still prevalent here after the 1.1.0 update, I almost think it’s worse now when recording in a DAW. The glitching where it used to be more intermittent is like ‘latching’ now, can record an entire bit crushed sounding track once it engages. Have to manually cycle the buffer size to get it to temporarily stop. Tried on both my laptop and my desktop and confirmed the issue on both computers (Windows 10).
Unfortunately I won’t be direct monitoring from the QC while recording now (DAW monitoring only) just to ensure that I can tell when the glitching starts so I can cycle the buffer size up and back down.
I’m really curious why this would happen, was recording vox in a really light session, and had to retrack al the vox after realizing that everything had been distorting for the recorded audio (had been direct monitoring from the QC with no audio issues)
Still love the QC and have never had these issues while not connected via USB, but I’m struggling a bit to use the QC as an interface.
CorOS Version: 1.0.3
Describe your issue:
When the quad cortex is connected to computer it will after a couple of minutes start to glitch. The audio will be distorted both in the headphones and in the actual recording.
When I reboot the quad cortex, everything works for a couple of minutes but then it occurs again.
I’m having problems with the Windows ASIO driver, too.
I’ve contacted the support and they are working on updates.
Sadley I do not know when the will release an update.
The current CorOS is 1.1.0 - you can see that in Jasons post , too.
If you have problems update first. This is a good thing to do, always,
even if the updated software may have bugs, too, because
no support cares about problems with an outdated software version, as far as I know.
In this case, after updating probably you will experience the current bugs,
so this is “special” as mentioned above as version 1.1.0 is not bug free also.
Hi,
Just a quick word to say that I also have the audio glitches when using the QC as a USB interface with my Windows 10 laptop, no hub, firmware 1.1…
Hi, same here with an updated QC which just arrived.
I’ve contacted the support and they say an update is on the way.
Meanwhile I’ve found some kind of workaround:
Select any other than the QC (in my case RME Hammerfall) as the default sound device for Windows.
Open Reaper (6.33) project configured to get and send audio via QC USB.
Some audio errors will occur.
Open the QC ASIO driver control panel.
Select/Deselect the Save Mode checkbox.
No audio errors any more regardless of the checkbox setting.
(latency with Save Mode selected is higher)
Tested for a couple of minutes only, not for hours, with a buffer size of 32.
This works with ableton live also but it looks like Reaper works better.