Quad Cortex Distorted and Robotic Playback (when used as Audio Interface)

CorOS Version: 3.1.0

Describe your issue:
When I apply FX to tracks in my DAW (REAPER) recorded with QC, i experience robotic playback/clipping/distortion.

Steps to reproduce your issue:

  1. Record audio into REAPER using Input 1, Input 2, or USB Out 3 (from Grid) using either a guitar with 1/4" instrument cable, or SM57 microphone with standard XLR cable
  2. Apply any combination of FabFilter Pro-C, Pro-Q, or Pro-R
  3. Hit Play on DAW, and experience robotic playback/clipping

I expected this to happen:
When I apply FX on my audio tracks recorded with QC, i expect clean, accurate playback.

I have tried the following things:

  • I have tried changing the buffer size in my DAW as high as possible
  • I have tried lowering the I/O input volume of the relevant inputs on the QC
  • I have tried changing USB cables
  • I have tried changing USB POrts
  • I have tried Toggling Safe Mode in the Audio Driver Settings
  • I have tried monitoring with headphones and speakers

Note that before really messing with all the I/O levels, i was experiencing this issue with no FX loaded on the DAW tracks. I have been using these plugins for years with no issues on my previous audio interface (Axe FX II). That said this seems like an issue in playback with the QC and not an issue with my plugins/DAW.

My full email to neural support:

Hello,

I purchased a brand-new quad cortex from Sweetwater that i received on 3/8/25. I installed Cortex Control and the latest USB Driver from the neural downloads page and connected the unit to my PC which has an i7-14700KF 3.4 GHz processor with 32 GB RAM running Windows 11.

Using the latest version of REAPER as my DAW (monitoring with my headphones and speakers turned off), i selected the ASIO audio driver and Neural DSP USB device option. I set the project sample rate to 48k. I plugged an SM57 mic into Input 2 of the QC with a standard XLR cable.

I selected a blank preset on the QC. After selecting Input 2 as my input for the Grid and setting reasonable levels for input 2 on the I/O page, i was able to hear my voice in my headphones. I even experimented and added a reverb and compression block on the QC grid and everything sounded great. I disabled the QC reverb and compression, reverting back to a blank preset as i had planned to add these effects using fabfilter compression and reverb on a track in my DAW.

I created a new track and selected Input 2 as the track input. I record armed the track with record monitoring enabled. I noticed that if i started to sing loudly into the mic the playback would begin to have distortion/clipping/robotic playback that would “latch” until i either restarted the unit or changed the buffer size in my DAW. I reduced the signal level of input 2 and increased the buffer size in my DAW to the maximum setting and tried again. The results initially seemed better. I recorded a vocal sample. I then tried to apply the Fabfilter reverb and compression, and the distorted playback immediately returned. I have never experienced this issue with these plugins or with any previous audio interfaces.

I was unable to fix the issue with any of the following methods:
1.) Changing the buffer size as high as possible
2.) Reducing input 2 level
3.) Using Input 2 → USB Out 3 (from Grid) with a blank preset
4.) Changing USB cables
5.) Changing USB Ports
6.) Toggling Safe Mode in the Audio Driver Settings
7.) Monitoring via my speakers instead of headphones

Thus, i tried to record some guitars via Input 1 using a 5150 preset i dialed in. There is absolutely no clipping anywhere in the chain. Initially, things were sounding good, until i opened an instance of Fabfilter Pro Q 3 on the track. Immediately, the robotic playback returned on the guitars this time.

My last test was keeping all plugin windows closed and recording to what my ears sounded like a “clean” take with respect to the distortion and clipping issue. I thought i had succeeded in this, because during track and playback the guitars sounded good to my ears. Feeling confident the signal was clean, i then attempted to add the Fab Filter Pro Q and immediately the clipping returned.

I tried the same experiment with the SM57 in input 2, this time applying reverb and compression after tracking what sounded like a “clean” vocal take, and the clipping returned.

Initially i thought there was a problem with just having the plugins open while recording, but it seems like there is an issue with playback when applying these FX post tracking, which is a massive issue for me.

Do you have any suggestions for me? Are there known issues being worked in the audio driver? This problem basically renders my unit useless, as i bought it primarily as an audio interface/recording device.

Please help, i really like everything else about the QC. I dont want to have to return it.

Thanks,
-Rick

Edit:

I did some additional testing with the USB Statistics diagnostics.

With an SM57 plugged into Input 2, monitoring on my headphones, with a blank preset, and with Input 2 routed into a track in REAPER that is record armed with record monitoring enabled and also has the FabFilter plugins instantiated; I yell into the microphone until i experience the audio transition into robotic playback. The USBAudioRdWrDistanceAverage turns red. After i see this occur, playback becomes robotic in my DAW on the audio track until i change the buffer size.

It seems like the USBAudioRdWrDistanceAverage variable is reducing to a low number when this happens, although i have seen it turn red and be as high as 500. It looks like it is also turning red periodically on the diagnostic page even when i just let the unit sit without passing audio in or out of it.

Additionally, i noticed that when the tracks recorded with the QC are experiencing the latched robotic playback, i am able to playback other tracks that were recorded with my axe FX II that have FabFilter Pro-Q on them within the same project with no issues!

Have you seen this thread discussing similar issues solved by a different driver?

I usually suspect sample rate mismatches with these kinds of issues, but you’re sure you’re working with 48kHz? Isn’t the Axe FX 96kHz?

1 Like

I tried the most recent asio4all driver today with a larger buffer size than mentioned above and still had the robotic playback and distortion. I am positive my project is set to 48k. Can’t remember what the axe fx sample rate was but never had a problem with it.

there have been many troubleshooting posts regarding the interface issues- hopefully one of them somewhere might offer a solution for you. I’ve never had the issue myself on Mac so I’m not sure what else to suggest, other than getting in touch with Support@Neuraldsp.com - they’ll have you repeat a lot of the steps you’ve already tried but they might be the only ones who can get you up and running glitch-free

I have read every related post I can find and also emailed support. Some recommendations helped for a little but nothing has solved it indefinitely.

I tried to factory reset today and that also didn’t work. I have a usb b to usb c cable coming tomorrow that I’m going to try.

I fixed this by rebuying the interface I sold when getting the QC. NDSP support didn’t do anything other then forwarding my reports and the going silent over and over again.

I had the same problem with a recent PC (I7 13620H , 32Gb Ram, Win 11)

Several factor can affect the ASIO drivers, poor implementation is one thing, but the most frequent factor is system ‘optimizations’ (both at hardware and software level) that interfere with the ASIO driver buffers, producing robotic sounds.

One good starting point is : How to optimize your PC for the Stage - download FREE e-book - Gig PerformerÂŽ
On this site, you’ll find a PDF / EPUB / MOBI ebook that contains a LOT of resources to optimize a Windows 10/11 machine for Audio Production.

Most modern machines come with several power consumption optimizations that throttle the CPU when the workload is not high, but it has the side effect to cause instability in real-time activities (like audio processing at low latency) , so you must disable those ‘optimizations’, both in the BIOS and at the Windows level.
Some windows optimizations are not easily accessible and could cause side-effects, but it’s worth the pain of tweaking…

‘Latency Monitor’ ( Resplendence Software - LatencyMon: suitability checker for real-time audio and other tasks ) is the baseline utility to check your system perf and can be used to determine if a tweak has a positive or negative effect on latency.

It takes some time one some machine (I had to disable ‘CPU Parking’ , and so on…) but in the end you can have a perfectly usable system for Audio Production…

3 Likes

Thanks for the suggestions and resources. I’ll give some of the recommendations in the E Book a try and let you know how things go!

The QC is very picky when it comes to USB Cables. Get a short high quality USB Cable. I had the same Issues till i changed my cables.

Make sure you don’t have a ground loop. Can easily happen esp if using pedals and pedal supply in conjunction with QC power and usb cable connected to laptop and it’s power supply. Unplug everyrhing and if possible plug everything into same power strip.

Hi, I had this exact problem. Nothing helped. I sent it back to NDSP for warranty repair after a short email discussion with NDSP and after a month it came back and it was fixed.
I recommend doing the same.
It is definitely a hardware issue that cannot be fixed by you.

I have tried four different cables, one of which was USB-C and none of them fixed my issue

I just replied to their initial customer support email with my demonstration video of the issue. Im glad you were able to get yours fixed, i hope they can do the same for me because i have spent many hours trying every suggestion i can find on this forum and nothing has worked for me.

I´ve had similar issues. The solution, for me, was to connect a c type usb cable to a micro usb adaptor. Fortunately my pc has one port for micro usb…
Wish you luck!