I am having a huge problem when using Nano Cortex as an interface. When monitoring music from DAW or youTube to play along i am getting distorted sound and glitches on my headphones. I ve tried on mac and it is ok so I am assuming it is not Nano Cortex but Can’t set it up to work properly. i’ve installed driver and changed buffer size restarting PC etc.
same situation here
1 Like
That hapenned to me aswell when I used an extention USB cord to plug my nano on my PC. Plugging it directly at the bottom of the PC solved the problem entirely for me.
try to use other type C USB cable. mine solve using other usb cable.
I’m having the same issue. I’ve already tried two different cables, I always plug it into the rear USB ports on my PC, in the 3.0 port, and I still keep getting robotic glitch sounds whenever I try to record. I’ve set the buffer size pretty high, but that doesn’t solve it either. It’s really frustrating.
My PC should be more than powerful enough to handle heavy programs, I’ve got a solid setup:
-
Motherboard: MACHINIST X99-RS9
-
CPU: Intel(R) Xeon(R) E5-2670 v3 (12 cores)
-
GPU: AMD Radeon RX 6750 XT (12GB)
-
NVMe Samsung 990 Pro 2TB with Heatsink
-
RAM: 32GB
It should run without any problems, but that’s not what’s happening.
I ran some tests and noticed the following. When using the Nano Cortex on a laptop via USB-C, everything works fine and there are no glitches during recording. On my desktop, however, with Steinberg Cubase Pro version 14.0.32, glitches occur during recording even after a complete clean reinstall using Revo Uninstaller. I also tested with other DAWs on the same desktop, including Avid Pro Tools 12 and Presonus Studio One, and the glitches did not appear there.
This suggests the issue may be related to compatibility between Cubase Pro 14.0.32 and the Nano Cortex, particularly on desktops without native USB-C connections. A firmware or driver update focused on improving compatibility with Steinberg Cubase Pro could potentially resolve the problem.
Hi guys. I’m experiencing audio issues when using NC as an audio interface.
I’m connected straight through USB-C to my laptop (latest Win11), set up Reaper in 48K and 1024 samples and monitoring directly through the NC headphone jack.
Tracks are not monitored in Reaper, only NC.
But the issue even get’s recorded. Also tested with Audacity with the same results.
I’m uploading a sample. Tried checking different USB cables (USB-A to USB-C) with the same resutls.
I have to keep using my HX Stomp since it’s more reliable as an audio interface.
Any ideas/suggestions?
Nano audio issues.zip (1.2 MB)
not sure if this will work for the Nano, but user Thilo reported this fixed that issue with his Quad.
Also, make sure your DAW is running a 48kHz sample rate if you’re not using a standalone.
I had that issue for years and could not get rid of it until lately. Definitely no hardware issue! So if someone has the same problem, this might be the solution for you as well:
When on Windows 11, the priority of the NeuralDSP ASIO process is set to “normal” by default. I noticed by chance that the same ASIO process of my Focusrite Interface is set to “real-time” by default. And here is the solution: Just set the priority of the Quad Cortex’s process to real-time and the robotic sounds are gone (for me). You can do that in the task manager, just right click on the running ASIO driver tool, show more details and on the next screen right-click again. Then set priority to real-time. Never ever had the problem again and before the QC was completely unusable as an Audio Interface.
It seems to be a Windows specific problem of the drivers, never heard of it for Mac users.”
Have you tried lowering your sample size? It could be your specific setup may not have the resources to support the higher sample of 1024. If what @xush posted above doesn’t resolve your issues, please feel free to email support@neuraldsp.com to log your issue and hopefully provide a quick resolution.
I was apparently able to sort it out by trying different cables and sample configs.
I still need to test it with more tracks to see if the audio “glitch” doesn’t return.
Regards.
1 Like