CorOS Version: 2.3.1
Cortex Control Version 1.0.1
Since the latest version, it has become unusable because just opening it makes my PC fans go crazy and I cannot do anything when it is open. I’m using Windows 10.
1 Like
I’ve never had this issue or seen any other complaints about it. Have you opened task manager to verify that CC is the culprit?
I get pretty high power usage as well. Not sure if it’s something new or was always happening though.
The same thing happens to me with MacOS
same issue here with MacOS 14.4.1 (M1 Pro chip) and the same CorOS & Control Version with you. My laptop runs hot because of it.
I found the installer for version 1.0.0 of the CC, and the problem is gone. On my desktop, version 1.0.1 uses 8% of the CPU, while version 1.0.0 uses only 0.5-1%. On the laptop I mentioned in my previous post, the CPU usage drops from 60% to 5%. It’s a fairly old laptop. Now I can hear the reverb trail and not the PC fans, and version 1.0.0 doesn’t crash much more than version 1.0.1.
Same here! Fans go crazy on my W10 laptop!
Agreed. I go into my Task Manager (Windows) and set it to Efficiency Mode, but shouldn’t have to. It’s been a resource hog this version. My fans go crazy, too.
1.0.1 has 16%-25% CPU usage.
Uninstalling it and re-installing 1.0.0 brought it down to 2%
Are there any improvements in 1.0.1 that I will be missing? I can’t run 1.0,1 until they fix the CPU glitch.
CorOS 2.3.1
Window 10 64.
Nearly 5 months without some kind of hotfix… pretty unaccettable, i hope they fix this with the 3.0.0 update
2 Likes
Wow. 5 months? That is odd.
I am new QC user, I am well within my return period. How is the rest of the support from Neural? I have a couple connection issues and emails without replies yet.
I am in the USA.
If you haven’t tried reinstalling v1.0.1 again recently, it would be worth confirming your initial test results and there is always the chance that the second install might fix something that was problematic the first time. Might even have been a Windows update in the interim that fixed the issue. Maybe that new CrowdStrike update 
Also occurs to me that, although they haven’t mentioned it, there could be a CoCo update when the 3.0 firmware rolls out at the end of the month.
3 Likes
Cheers. Cloudstrike only affected those who used cloudstrike.
And it made zero difference re-installling it. I just uninstalled 1.0.0 and reinstalled 1.0.1 and same results. Here are the screen shots (only one per post allowed for me)
It’s a pretty serious CPU hit/glitch and It may sway me from being a neural user. 5 months is a really liong time for this. It sounds great, but it is a bit risky with the lack of support I have been reading about.
I think they are slow, maybe because of the 3.0.0 update, but updates have been really slow compared to the competition. The QC itself sounds amazing, so i keep it, and using cortex 1.0.0 made no difference for me.
Reinstalling changed nothing, i think it’s a problem all windows 10 cortex control have: basically unusable for me, fans go louder with cortex than when gaming
Probably not the issue but wondering if anyone has tested turning off or pausing their antivirus program while running CoCo. They can sometimes cause some resource thrashing. Looks like the task manager is indicating CoCo as the culprit though.
I have an M1 Max Mac Studio and the CC is taking 99,2% of the CPU…crazy.
The second app that uses more CPU takes 4,3% 
Edit: When the QC is shutdown, the cortex Control takes 1,2%.
There will be a new CoCo version for 3.0 because of the need to “know” about / be able to handle the added blocks and functionalities. 
If we are lucky they also fixed some bugs like this one.
3 Likes
Cortex Control 1.1.0. with CorOS 3.0.0 fixed this issue for me, even if not stated in bug fixes