Problem with Control Software on Mac OS

Hello,

I bought a QC a few days ago. The Control software works fine on Windows 10, but not on my Mac running Sequoia. I’ve reinstalled it several times and tried different USB ports.

The software launches, but as soon as the QC is connected, it keeps switching back and forth between “connecting to QC” and “loading presets.”

Does anyone have an idea what could be causing this? Or is it because the Control version hasn’t been updated yet?

Best regards

Just to be clear, you’re plugging directly into the USB ports on the Mac? Or are you using a USB hub?

1 Like

Yes Directly in the iMac wirhout hub or anything.

Newest Os on Both devices.

Ensure that you are using the most current version of Cortext Control for your platform etc., worst case send an email to support@neuraldsp.com so they can log your issue(s) and hopefully provide resolution.

1 Like

Current CorOs 3.1.0

The current version of Cortex Control is:
1.2.0 (for CorOS 3.1.0) - Nov 28, 2024

Please ensure you are using that version etc. Thanks!

1 Like

Yes it is 1.2.0
I don’t know what the reason could be.

I hate to ask, but have you restarted the computer, or tried a different cable?

I Love to answer with. Yes 4 cables and multiple restart.

On my old MacBook Pro with Windows, everything works perfectly.

Good Night

Thanks for your reply

damn, was worth a shot! haha

1 Like

I have Cortex Control working without problems on my Hackintosh running the latest version of Sequoia.

1 Like

I tried the Tahoe Beta today and somehow Cortex Control was very stable with it :star_struck:

2 Likes

hi Sargon,
is your Mac an older model that still has USB-A ports or do you have one with USB C ports?
I have a Macbook pro from 2021 and use a cable that has a USB C connector, it works fine with the latest Cortex Control software.

Mac® minimum requirements

  • Intel Core i3 Processor (i3-4130 / i5-2500 or higher)
  • Apple Silicon (M1 or higher)
  • 8GB of RAM or more
  • macOS 11 Big Sur (or higher)

Sorry, I would also guess the cable first, otherwise the only thing I can think of is that there are 2 different installers for Windows and Mac…

Good evening, and thank you for your responses.

I’m using a 21.5-inch iMac from 2019,

I’ve tested both USB-A and USB-C ports,

32 GB of RAM,

Intel processor.

As I mentioned before, I’ve already tested several cables, and they work 100%—unlike my HDMI cables at the moment :joy:

I just accidentally updated to sequoia – but cortex control works fine… Mac PowerBook M2 Max 2023, 64gb, etc…

using a usb-c cable - no adapters - connected to a powered hub - not direct to Mac. The only time I’ve had connection issues with the quad was when using it as an audio interface w/ a 10’ usb cable.
Swapped it out to a 5’ and good to go. I doubt you’ve only tried 10’ USB cables - but just in case - make sure you’re using a reasonably sized cable.

Could also be a Rosetta thing since you’re in an Intel processor…

1 Like

Thanks for the advice. I used the original included cable, among other things. I’m going to wait until the new version of Cortex Control is released

You can request a copy of the early beta from Support@neuraldsp.com
I’ve seen several users say they’ve been provided with an unreleased build that helped.

1 Like

Take a look at this thread: Local Backup on MacBook impossible

Where it stands now based on the testing that I’ve been doing over many months…

  • I have identified a Quad Cortex image (e.g. a backup image) that will cause Cortex Control to fail when doing a local backup. I suspect that the bug that keeps occurring with local backup is more widespread with respect to how Cortex Control reads data from the Quad Cortex
  • I have also identified a Quad Cortex image (e.g. a backup image) that WILL work with Cortex Control for a local backup.

In my extended communication with Neural support, I have offered up those images so that their developers can recreate the issue and hopefully then find the bug in Cortex Control. I have yet to hear back from Neural support (I filled them in on this 4 days ago) to see if/how they want to proceed with getting this bug verified and fixed on their end.

4 Likes