Describe your issue:
CC (Cortex Control) getting stuck again on Loading Presets and/or crashes when QC is turned on.
Steps to reproduce your issue:
Start Cortex Control
Connect Quad Cortex to Mac
Start Quad Cortex
I expected this to happen:
When I do x, I expect y to happen
I have tried the following things:
A not 100% effective workaround is to set the QC to a factory (not user defined) preset and then turn it off. Restart CC. Restart the QC.
This looks very similar to the old CC crashing problem with user defined presets.
The suggested process is that you have CC running and then turn on the QC. This is a more stable startup in my experience than the other way around. When they originally fixed this bug it became stable no matter which order you started things. If you read the CC instructions it specifically implies you should start the QC AFTER CC is running.
huh, that’d be news to me. Where is the suggested procedure described?
I’ve never seen that order recommended. I think the CoCo manual’s wording is a little vague, but it does at least indicate that it ought to be able to open the program even if the QC isn’t connected yet.
Maybe I’ve been doing it wrong all this time, but it always works for me.
Take a look at the CC app instead before you have the QC connected. It states right on the opening page that you should connect the QC and then turn it on. I am sure there are variations and this problem isn’t solved by that in any event.
Like I said - once they corrected the bug last time the order of operations didn’t matter. It also doesn’t matter now - I get crashing either way.
I am experiencing the same phenomenon in my environment. I had this bug before and it was fixed, but it has reappeared in 3.0. Unfortunately, it seems that you have degrade. there was a post about a quality problem with the USB connection, but we were able to address it with a software update, so let’s wait for the release of the corrected version.
Yeah - I think thats correct. It’s the same old bug that somehow cropped up again. They probably know how to fix it and will correct in the next release. Weird that it popped up again but they show a lot of signs of being resource constrained in development - this included.