Anyone else getting tired of the unacceptable amount of bugs in the QC and Cortex Control? Gig today, and there’s no sound coming from my QC on startup (yes I’ve posted/emailed support etc) and Cortex Control constantly crashes so i can’t even back the thing up to my local drive…
I don’t have my QC that long, but no issues so far with it or cortex control works flawlessly.
Bummer that you’re having issues. I’ve been very lucky in 10 months (or so) of ownership. Haven’t updated a single firmware software whatever since I first plugged it in, probably haven’t logged into cortex control in 5 months, and my unit has run flawlessly.
It’s done everything I’ve wanted and more once I get some help/instruction from the fine folks on this forum and learn of new capabilities/routing, etc.
Hope you get yours worked out.
that sounds more like a mechanical failure than a bug. Hope they can get you fixed up.
Sorry you’re having trouble like that.
Did you take the latest CoCo update, on 9/11? Seems like it’s helped some users who were having trouble connecting.
^^^This! May not be the problem @littlespaceman is encountering, but this comment should be helpful to a few of the folks who have updated their firmware but were not aware that you also need to download and install the latest version of the CoCo editor.
No sound at a gig is a nightmare. Hope that gets resolved quickly and is basically a one-off.
Thank you - actually I did update ‘CoCo’ (good abbreviation by the way, easier to type than the full name!) on 9/11 and that actually seemed to make it worse for me.
I know I’m not alone with the ‘no sound’ issue; I’ve created a separate thread for that problem, and a few others have the same issue.
FWIW one of the fixes Support suggested, as a trouble shooting measure, is to select factory preset 1A to see if this fixes the sound problem; it did, but only the first time.
Anyone any idea why selecting that preset would resolve things (albeit not permanently)?
ps, yes, the no-sound at a gig certainly raised the stress levels a bit. That (and a few other things I don’t enjoy about the QC such as aspects of the UI implementation - which you and I have discussed before) made me consider other brand devices for the first time since I’ve owned the QC, and yesterday I ordered a Headrush Core to see what that can do.
I’m sure the ‘grass is greener’ to some degree, and after the honeymoon period there will be things about other units that bug me as well, but as a simple one-stop solution it may do what I need (such as being capable of storing loops/.WAV files permanently) better than the QC. Only time will tell!
My Cortex Control crashes allll the time
Mine doesn’t and I use two different units on two different computers every day. I’m on Windows. Are you using a Mac?
While I have Zero Problems with my QC (while I have, because I am too stupid to get the right In and Outs) my Cortex Control crashes every 5 minutes too. Mac user.
Re-Install, tested different USB Cables, different hubs (My Mac doesn´t have USB A) every 5 - 10 Minutes I have a crash.
I know it’s not common for Macs to do need an ‘uninstallation’ but have you tried deleting/uninstalling CoCo and re-installing clean? Some have reported success from this, but I’m not sure if it’s only for Windows/PC.
And you updated both the QC and CoCo last week?
Thanks, I could give that a try. Yes, I updated both last week.
The problem is that it’s also really inconsistent - sometimes CoCo opens fine, and I can edit the QC using it, sometimes it keeps opening and crashing. But no matter what, I can’t do any backups using it, which means I can’t create any local backups.
I’ve heard the ‘local b’up failure issue’ mentioned a couple times now.
Have you reported that directly? There might be a bug there they need to squash.
Support@neuraldsp.com
I’ll see if I can complete a local b’up. I’ve had trouble in the past with that…
not much help, I know, but I was able to get a local backup to take.
I’m on CorOS 3.0.1 and CoCo 1.1.1
Thank you Xush - I’m on the same firmware, are you using a Mac too?
just finished troubleshooting with a friend on this subject (to no avail)
we’re curious if it’s a Silicon incompatibility. Hopefully we could hear regarding that from other users?
I’m using a much older iMac with no issues. I’ll try connecting my M3 Macbook tonight to see how that compares.
we looked at disk permissions, cable types, etc. I’ll ping him over here.
I’m 85 % sure it’s coincidence.
But when I start CC when I closed it on my second display before. It tries to start on my second display and crashes, or won’t even load after the “Load Presets” marker.
If I drag the CC Window to my main Mac display everything starts fine. Crashes all the time, too. But it starts.
I did a couple of backups via CC on an M1 Mac with no issues.
Only time I ever have problems with CC is when I forget to update to the latest version after a QC update.
When was the last time you did a local backup? Was it with the current versions ( CorOS 3.0.1 and CC v1.1.1)?
Before v3 I think. Haven’t updated to the latest yet
Ok thank you. My gut says CoCo bug in the latest but who knows. I logged it here in the bug reports.