Hi, thanks for the message. I updated shortly after but the problem persisted. As long as it is a common error that everyone experiences, at least I know that it is being worked on. If it was a problem only I had, then this would be a different story entirely hehe. Thanks 
Iāve installed and tested the ASIO4ALL driver 2.15 beta 2.
The support suggested this to ādetermine if the driver is playing a role in this scenarioā.
So far it works just fine.
ā
I have this audio glitch issue all the time since I upgraded to core 1.1.0. It never happened before. I experience this with all audio when using the QC as an audio interface - in my DAW (Logic Pro x), youtube, iTunes, Spotify - everything. This renders my QC unusable as an audio interface for my MacBook Pro (from mid 2020, OS 10.15.7). I have logged a support ticket with NeuralDSP, provided some details and even trialled a patchā¦nothing is fixing this. When I use my Audient iD4 as an audio interface, it works flawlesslyā¦
I have to wait patiently for a fix, but this is very annoying.
I was just using my QC via USB on my W10 computer.
I had a YouTube video playing while I was messing around with a patch (I think I wanted to add a splitter), and I had some audio glitches.
I had monitors in my ear, so it wasnāt a pleasant experienceā¦
Hi, does this mean that there is somehow a way to run the QC with project samplerates at 44.1?
Iāve run my QC the last few months on my Mac Mini as an aggregated audio interface with an RME UCX interface. The UCX is the clock master running at 44.1 kHz and the QC syncs without any problems (no glitches or anyting). However if the QC is the only interface or acts as clock master then 48 kHz is the only option.
Running at 44.1 kHz is not officially supported by NDSP - maybe Iām just lucky - but as I said, no issues whatsoever.
Same issue for me when connecting my android mobile through USB for playback. Bits crushing after around 25s.
By the way itās working well with a win 10 computer and up to date driver. Issue is only with android from my side.
Any news about it guys ?
Hmmm so i am not really familiar with aggregated device stuff, but does that mean that there is a workaround where just having another audiocard controlling the sample rate then that would work? Without using said audiocard?
I am trying to find a workaround to see how my computer acts with qc at 44.1.
On a Mac itās easy to set up an aggergated device - and yes you can utilize just the QC analog I/O without using the analog I/O of the other card! A note though - RME have very good drivers for their cards and as I said, I might be lucky to have the right combination of gear. I havenāt really experimented - I just tried to connect as described and āit just worksā 
If on a Mac, you could try to make an aggregate with the internal sound card and the QC (add the internal first), set the internal as clock master at 44.1kHz
and try if you get that to work.
I have been struggling with using the Quad Cortex as an audiocard. The audio directly from the QC has never been an issue though. The issue is that the audio recorded into my daw has crackles, stutter, bitcrush / heavy distorted phasing coming from it and it is hearable through the direct monitoring. When I hook up the QC it initially works fine for a couple of minutes but then the problems occure.
The unit starts sounding like a robot and the sound changes drastically, turning it into a noisemachine. The sound is basically like putting a bitcrusher on the signal chain.
The only thing that āresetsā, back to normal sound is when I restart it, unplug and plug the device back in the computer or if I press the āsafe modeā off and on again. This only remedies the situation for about a couple of seconds to a couple of minutes before the issue returns.
I tried with a Focusrite Scarlett 2i2 3rd gen and it can run perfectly on 48khz and 98khz down to 64 samplerate, so the computer is more than fine for this type of use.
Computer specs:
Huawei Matebook X Pro
16 gb ram
1 tb m2 drive
Latest Windows
I have tried:
-
Increase buffer size, to see if glitches go away/become less frequent, I have tried increasing samplerate to 2000 and the problem persists
-
Avoid any USB hubs . If any adapter is required (such us USB-C) make sure that good quality parts are used.
-
Make sure the DAW is not forcing a sample rate other than 48KHz .
-
Disconnect any other potentially conflicting hardware.
-
Change USB ports.
-
Try a different cable (shorter if possible as well).
-
Move cable away from interference sources.
-
I tried it on a mac, same thing
-
I ried plugging it in and out and the issue disappears for a couple of seconds before it returns
-
I tried in a Cubase project with nothing on it and with a preset without any blocks in the QC
-
I have tried having the QC as the main audio on the computer and not having it as the main audio.
-
Reinstalled driver several times
-
Tried Asio4All on the computer and that also works flawlessly
-
Switching inputs and outputs, only the usb outputs seems to be the issue.
I am not sure what I am missing, but the QC is so amazing when it works that it is so sad that it is unusable as an audiocard. I am hoping someone has had that same issue and that there is some kind of compatibility fix that clears the whole thing right up.
Cheers
Jahn
1 Like
I had the same issue, everything exactly as you describe it. I read in some other thread that disabling the āsafe modeā helps with some pc audio issues.
Did you try that, yet? I didnāt have the time yet, but will try this later.
Iām using Reaper on Windows by the way.
1 Like
Can confirm. Turning off Safe Mode in the driver fixes the issue.
Putting in my 2 cents, I also get audio glitches when playing normal music through spotify, etc. (even with āsafe modeā turned off). This seems to happen every few minutes for a few seconds. Specs are fine so shouldnāt be an issue. Havenāt recorded yet, quite scared lol.
Yeah i tried it, it resets and goes back to normal but it only lasts a couple of seconds.
Though progress has been made in understanding what this is:
It seems that it is a driver issue with Neural DSP. I suspect that something in the driver stresses the system to overload, because everytime the noise comes, it is because of a Ā«peakĀ», in performance, though it doesnt go away when the peak goes away. That peak in performance never happens with any other drivers.
I therefore tried using asio4all and there is no peak, no overload in the performance meter and when it peaks because of the usual stuff like to many plugins for example, it glitches like a normal interface and goes back to normal when the stress from the overload has passed. Instead of lasting until a hard reset.
Use asio4all until NDSP can update their driver. That is my take from this.
It does so for me as well, but just until the next Ā«uncalled forĀ», overload of the performance meter.
If the driver stresses the system somehow, safe mode fixes it, but only the few seconds before the driver stresses the system again.
I can reproduce this exactly as you say. Also nothing helps but using Asio4All, so thatās what Iāll stick with for now.
I reported this to support@neuraldsp.com referencing this thread. Hopefully they will manage to put out a fix in the near future.
Me too. I never saw myself using asio4all, but here I amā¦
I hope Neural DSP can fix this soon. Nothing like driving a Lamborghini with Mazda engineā¦
I tried running plugins in reaper last night and what a disaster. Glitches all the time and then never stops. They really need to fix this otherwise itās largely unusable for the home / recording musician. It also makes me wonder why itās been an issue for so long and is so problematic given you can get a simple interface for like $100 which works flawlessly and this thing has the most advanced tech with AI built into it and glitches at the first sight of an Mp3.
I also think a useful suggestion is having a mode to use the QC as an interface in standby mode without it having to run a preset simultaneously. Just seems like a waste when youāre just playing music from your computer that the unit is running a preset at the same time and in fully functioning mode. It should still be useable as a normal interface when in standby mode I think.
2 Likes
I thought 512 is fairly high latency though? I donāt think there is a sweet spot per se, it really comes down to what the AI can handle. The fact there are glitches when peaking just playing normal apps on the pc and having to stick with a 512 buffer size with latency I donāt think is really good enough. It was glitching out on a track with very little going on in the DAW vst wise as well. It seems from the posts above there is definitely an issue. I think my only solution is to run it into my other interface for now and hopefully they update.
Also are you supposed to match the sample rate in the DAW to 48000? I did this anyway but just checking what the differences are between the sample rate in the DAW and sample rate on the interface itself.
I was finally able to fix mine on Windows 10 PC trying to use USB ->QC ā Speakers. I started getting USB glitches on my Focusrite (although the Focusrite glitches were pops/static and not the bitcrushed sounds from the QC). Led me to find LatencyMon which pointed to my storahci driver causing huge DPC runtimes. Had to use Snappy Driver Installer since Windows updates and other drivers from my motherboardās website were not fixing the issue. Alot of other people with DPC issues see them on USB port drivers and Network drivers as well.
Once my drivers were updated all my audio glitches went away.