CorOS Version: 3.0.1
** Cortex Control Version:** 1.1.1
Describe your issue:
When I start creating a new a local backup (on Mac), Cortex Control goes into a disconnect-connect loop. Finally the backup is timing out. Backup cannot be created.
I also updated to the latest versions 3.1.0 and 1.2.0
Local backup works fine on Macbook pro M1/macOS 15.1.1
And by the way the former problems with starting up Cortex Control are gone.
Also updated to latest versions (CorOS 3.1.0 and CoCo 1.2.0) and everything’s working as expected on my M2 Mac Mini (going through a powered USB 3.0 Ugreen hub), including local backups. Random crashes seem to be gone too.
Up to date on CorOS and CoCo. Still no local backup on mac. Even tried another mac and had the same issue so its gotta be related to the QC itself. I might try a factory reset but I really don’t want to without a local backup.
User RudyTardy reports this fix today:
" if CoCo won’t make local backups on Mac: take it off the full disk access list, clean uninstall with app cleaner and then reinstall."
I’m also having issues with creating a local Backup. I’m Running Mac OS Sequoia 15.3.1.
With Apple silicon M1Pro.
QC is CorOS 3.1.0 / Cortex Control 1.2.0.
I’ve contacted support and they weren’t able to figure out how to correct the issue.
I’ve tried multiple things like a full uninstall and reinstall of Cortex Control.
I’ve tried enabling full disk access to the CC app.
Cloud Backup seems to work fine but I cannot create a local backup without having the CC app crash and send an error message.
Let’s hope the Dev team at Neural figure out the issue.
It’s a pretty basic function but I do believe it’s a must have feature to be able to save all the time spent on building and tweaking your tones.
Hey folks, just a follow up on the local backup issue.
This afternoon I’ve tried once again (just for fun) to create a new local backup of the QC.
It worked !
Out of the blue I was able to successfully save a local Backup.
The size of the .json file is also showing a different size in MB than the older local backup that I wasn’t sure were successfully working.
So far so good.
Local backup on the Mac has NEVER worked for me. I have been going back and forth with Neural support for many months… I have tried two different Mac Laptops (a MacBook Pro and a MacBook Air). I have tried different USB cables. I have tried the productions build and at least two developer builds. NOTHING WORKS.
It seems that a significant number of people are having issues with local backups on Macs. Local backup is one of the primary features for Cortex Control, yet it still does not work!!!
I think I have an idea of what might be causing the local backups to fail.
I found that a specific Quad Cortex image was able to be backed up locally. This happened after getting my QC back from Neural support. However, the local backup worked only two times! It seems that once I made some minor tweaks to my configuration (ex. changed some preset settings and perhaps some global input/output levels) then the local backups failed once again with the “connect the usb” messages.
I got a NEW QC and downloaded my last backup to the cloud. Then I tried to do a local back, and it FAILED. I then loaded the one local backup that had previously worked, and then used that image to make another local back - that WORKED.
So, I have tested local backups with a few different QC and I also tested running Cortex Control on two different MacBooks (one a MacBook Pro and the other a MacBook Air). Cortex Control repeatedly fails in all scenarios.
I suspect that there is a bug in Cortex Control and that is has to do with how it is reading data from the Quad Cortex. I suspect that there either Cortex Control gets stuck/blocked somehow and/or there is a memory overflow issue.
Given that I have 1)a backup image that WILL work for local backup and 2)a cloud backup that will NOT work for local backups. It seems that Neural support has the appropriate test data to reproduce this bug. I have sent this information to Neural support, and I am waiting to hear back from them. I am hopeful that if their develops test the local backups using these known datasets, that they should be able to identify the bug in Cortex Control and finally get local backups working. One thing I will note - I’m not sure if others have seen this, but I have seen Cortex Control do the how “connect usb” thing when just trying to change preset via Cortex Control. SO, perhaps there is a more general bug in Cortex Control e.g. not just related to doing local backups BUT whenever reading the data from the Quad Cortex, there may be some issue where data is not read correctly. This would account for the behavior (“connect usb”) that I have seen in Cortex Control for both local backups as well as other times when the “connect usb” message pops up…
