Anyone from Neural DSP able to chime in on this?
This thread clearly shows a variety of users with different hardware all experiencing the same issue with the only one common hardware being the Quad Cortex itself.
NDSP devs don’t typically follow these threads. The best method for support is to email support@neuraldsp.com as each issue is supported on a case by case method due to the multiple variables. A larger majority of owners don’t experience the issues. I personally run W10 2015 laptop which has zero issues so the discrepancy is still undetermined. Regardless, please contact support@neuraldsp.com so they can log your issue and hopefully provide resolution.
That is sad to think they are not working on it. Even an update through email saying they are having their tech and software departments looking into it. I am sorry to hear you are having this issue, but happy to read all the support from the community here.
You’ve returned the same unit several times for repair and they are sending the original QC back after repair?
Maybe it’s time for a different approach, as in an entirely new device. I hope your issue is resolved.
1 Like
The support emails provides the same responses and then no further action is done, again, as discussed in this thread- we have all reached out to NDSP for resolution to no avail
I just stopped recording music, what a shame.
Yeah it sounds good and functions for what it’s meant to do (emulate with precision and sonic goodness)
But I can’t record it direct 
1 Like
Hello there !
I take back the thread after a while.
For me it turned out that the issue came from my brand new laptop dell xps i9 64go blablabla. My other sound card had similar issues, the QC was totally OK with other laptops.
But dell support is very very bad and communication is aweful with them.
Good luck to find a solution, if you insist by NDSP maybe they will accept changing you unit.
For me it made a trip to finland, they changed things but I didnt know that the issue was from the laptop…
I am sad for you that you still experience this…
2 Likes
Every single computer I tried ranging from 2011-2022 production years is giving me the same issue.
Now with 3.0.0 it actually signifies the problem and provides an error message when it’s happening
Then crashes and disconnects from the computer
Hello,
I am facing the same issue as demonstrated in the video.
I have a QC since one year and i never had this kind of issue, then i bought a new laptop in windows 11 and the issue started to appear randomly while using the QC as network interface.
I have tried all kind of settings, high/low buffer, increased priority in windows in my DAW and neural dsp driver processes, running DAW in admin etc… Nothing worked.
To me, this is not hardware issue but incompatibility with something in windows 11, since my QC was working fine on my others windows 10 laptops.
I saw on other posts from a few years that using the Asio4All drivers might be a fix. Is it still a fix nowadays ?
Had the same stuff happen to me this week. I contacted support & filed a Crash report. Not much else happened from there on…
This isn’t just a you thing I have the same issue. Thankfully it’s not on my xlr outs but all usb outs do this and it’s incredibly frustrating to record and have this played back and find out it trashed the recording. I’ve noticed changing the sample rate makes it go away for a bit but it always comes back.
1 Like
Are you running PC or MAC? If you are using PC, please ensure you have the current driver installed and some have had success in the past by enabling safe mode on the driver control. Otherwise, please continue to email support@neuraldsp.com so they can log the issue and hopefully work to resolve etc.
I am using a surface book 3 and I have un installed and re installed the latest usb driver.once I get back to my rig I’ll have to verify software version.
I have had issues with usb compatibility on devices before so I figured it was more of a Microsoft surface issue. I have had issues connecting to panels because of un related drivers messing with other interfaces quite often. Like on all surface devices you have to disable Microsoft touch interface and precision touch drivers to be able to connect to a fire panel that uses generic drivers. Odd stuff, but since seeing others running different computers are having issues I may have to dive back into it a bit.
Are you using the OEM power supply or alternate? Also, some have reported issues if using a non-powered hub but that was more towards issues connecting to Cortex Control. Try safe-mode and worst case, reach out to support.
It seems that Nano Cortex users are also facing the same issue.
How many times must this exact issue be brought by individuals before it gets some sort of action?
I’ve stopped recording music because of this issue.
I spent 3k to bring myself at the professional level and I can’t even record it without worrying that my take became corrupted. So I’m back to being a bedroom guitarist, stuck because I can’t elevate myself to the point where I’m marketable… because I can’t record any of it.
See below the only response from any official Neural Support Persons that ACTUALLY did something.
It worked.
Until I restarted my computer.
This should not be standard procedure to get this software to interface, Developers should really be looking into this further and statement would be appreciated
The response:
“
Regarding the noises when using the unit as an interface, please check the CPU affinity of the NeuralDSP driver using the Task Manager and deactivate “Core/CPU 0”. To do that, open the Task Manager, search for the process related to the QC driver, Right-click on it, select “Go to details”, Right-click on it again, select “Set affinity”, and deactivate the first Core, which is probably labeled as “CPU 0”. Finally, press “OK” and close the Task Manager.
Once you have set the affinity, go to the Quad Cortex, Settings > MIDI settings , and set "MIDI over USB " to "Off ". “
That is a really interesting workaround from Neural. Interesting that it worked for you - at first. Have you been able to get it working again since restarting your computer, perhaps with another reboot?
It does work on every fresh boot and affinity set. If I let my computer go to sleep it will happen again on wake but fresh boot each time:
I’ve managed to do a few recordings of ~20-40 minutes at a time with no found issue thus far.
It does seem to be software related then it seems, somehow window is not prioritizing audio streams when dealing with NDSP ASIO.
I’ve not had this issue with any of my previous modellers or interface so not really sure what to do.
There needs to be a permanent fix, this affinity solution I’ve seen suggested for certain games which may imply a workaround for inefficient software development (assumption)
1 Like
Ive had success with app called process lasso to manage my laptop power settings and my audio software priorities etc. I think the real issue i was having was ground loop but with the app i can know my daw, usb asio etc are all high priority for cpu, memory, i/o, etc
What were your settings, and which processes did you edit?
I just tried this and it has been behaving so far. I’m at 128 samples with safe mode off. Of course, every time that I think I fix the issue it comes back, but I’ll update if (hopefully not when) it happens again.
1 Like
Ive had mine return but it was another ground loop issue. Mysetup isnt the most organized at the moment so mine is most likely me bumping cables or power supply etc. Hope youve had luck.