Hi, I’m having trouble creating V2 captures. I randomly get this error message. I turned off my VPN, closed Discord, closed Steam, unplugged any other USB audio devices from my computer and set the audio drivers to Quad Cortex 1+2. I successfully made 2 captures, and each time I don’t know what changed to make it work but most of the time I get this message. The message appears at the beginning of the training phase, if that can help someone diagnose the problem. Thanks!
Are you using a USB hub? If so, is it powered?
I am not using a hub, I am using the front USB 3.0 port of my PC case. I got things to work better when I switched from the USB 3.0 to the USB 2.0 port next to it. Do I have to plug into a USB 2.0 even if 3.0 is backwards compatible?
Have you tried using one of the USB ports in the rear of your PC chassis? Otherwise it ‘could’ be the Internet is losing signal etc.
1 Like
I am getting the same error, has anyone figured this out?
I have turned every usb device off and anything running in the background.
I noticed that the problem was happening quite randomly, and would sometimes be fixed by unplugging and plugging back the USB cable of the QC, sometimes it would not do anything, and sometimes it would start working on the 3-4th capture attempt.. it’s weird
Make sure you have no ground loop issues. Maybe causing some hum or extra noise that’s disrupting the capture. Try plugging everything in on the same power strip if you haven’t already. And make sure no weird cable issues or metal on the jacks touching each other etc.
Ok, I’ll try that, they are definitely on 2 different plug outlets.
I’ve been able to get the unit to do about 3 captures and then the rest of the time it fails. I’ve completed 1 successful capture and then went back to do a second capture with a tweaked setting and then it fails.
If kemper’s new capture works without issues, this unit is gone.
have you talked to support@neuraldsp.com yet? What did they recommend?
There’s also a limit to how many you can make in a day, but that doesn’t seem like it’d be an issue in your case. I wonder if you’re trying at a high-traffic time of day and it’s not getting thru to the server
1 Like
I had the same issue, I reinstalled the driver and its worked since with no problems