I’m seeing a LOT of reports of issues with Cortex Control, so I’ve compiled as much of the pertinent info from this forum on this thread. Please add any observations or solutions you have found.
In some cases, users have reported Support says their issues are due to hardware failure and their units had to be sent in for repair/replacement. Be sure to check w/ Support@NeuralDSP while you’re troubleshooting.
cortex crash reasons;
non-powered hub/dock
multi-monitor setup
too much USB traffic
version mismatch w/ CorOS
bad USB cable
reinstall CoCO
backup/reset/restore QC CorOS
hardware failure, unit requires repair
Here is information from users as to what has helped in their cases:
if I turn on a VPN, the settings open just fine.
However, my account does not display, and I can’t access anything on the cloud, which is probably a result of the VPN itself. Of course, I can access this forum and the Neural websites, but it doesn’t translate to the Control app or the QC getting any information. I can be connected to WiFi on the QC, and the Control app says I’m using the computer’s internet connection, but it has no device account link info at all. But the settings do open and the app doesn’t crash. So it’s something to do with the account settings/link or the internet connection calling that up and failing.
A lot of people have connection problems using some kind of USB dongle, hub, dock, etc. Including myself. Try using a direct connection trough a single cable. Using a USB B to USB C cable connected directly to the QC and my MacBook air m2 fixed my glitchy cortex control connection. Works like a charm now
I was previously using the provided USB-B to USB-A cable alone with an Apple dongle to my M1 MacBook Pro. It would get stuck “Loading Presets”.
I read that a USB-B to C cable would work, and I ordered one. Strangely it works, but only 1 orientation. Sometimes I have to flip the cable around (so much for that reversible connector promise).
Then I found if I had any of my thunderbolt hubs connected (which I use for my external displays, Apollo interface, keyboard/mouse, etc) then it would crash. The QC would still be connected directly. Just the mere presence of another hub seemed to cause issues.
I have identified what happens on both my Macs.
The issue is present only when my BenQ BL 2420-T monitor is plugged in. It doesn’t matter if it is using USB-C (to DisplayPort) or HDMI. The second I plug the cable, the USB connection starts to reset very often, leading to audio drop out, and USBAudioTxFrameSkipped and USBAudioStreamingEPEnabled values start to increase.
The second I unplug the cable, those values stay idle, the USB connection doesn’t reset anymore and audio work perfectly fine.Even if I switch the monitor off using the physical switch behind, if I plug the cable in, USB is screwed.
The only way to be able to plug the cable in without having this glitch is to physically unplug the power cable of the monitor. It is a 3 wires grounded power cable (IEC-C13), so…could it be a ground loop, or a grounding problem to which the QC would be overly sensitive? My Scarlett 2i2 never complained