Hello
After a few exchanges with Ndsp support, they asked me to return the unit for further inspections.
I did try to to make a fresh install of windows 11 and same issue. As you again, the occurence is random and it may come in 1min as 1 hour.
I tried with a QC of a friend and I did not experience the glitches. With friends QC nothing, when I plugged mine glitches occured after 2min…
Maybe the problem comes from the unit itself.
I will tell you what happen next !
Exact same problem for me with Linux, where I never had any problem for >10 years with 4 different usb sound cards.
It can’t be a hardware problem, or a driver problem on th OS side.
There is clearly a serious bug in the software inside the QC in the way it handles the usb connection.
NeuralDSP should stop telling people to return units or buy other cables.
I have seen that it can depend on which power supply unit is connected to the QC. I used a different one than the one provided by NDSP, and my USB was unusable. I saw that it somehow interfered with other equipment (a display) that was connected to the same power outlet. It got better connecting it to a different power outlet but not perfect.
Then I went back to using the power brick provided by NDSP, and it got a lot better, BUT when this particular display was connected to the same power outlet, I still had some USB failures. The only way I found to get my USB connection usable is simply to not use this particular display.
I can’t figure out if it is a hardware flaw, or a bad USB interferences handling on the software side though, but there is definitely something fishy in how the QC handles USB.
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.
I have been in contact with NDSP support. I performed myself all the testing, I provided them all the videos and pictures that show evidence of the problem.
After a while, they just stopped answering. I am not sure if either they have no clue about what the problem is, is if they are knit really interested in solving it.
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.
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
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…
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 ?
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.
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 ". “
