SOLVED
Even though the Focusrite drivers were up to date (as was Focusrite Control SW), I reinstalled the same versions and voila: Cubase is happy again/seeing the Focusrite! Weird, but so much better than having to uninstall/reinstall Cubase fresh, etc.! Thx to everyone who chimed in to try and help!
==============================================================
Hey all- I recently upgraded to a Mac Mini M4 Pro. Cubase (currently on most recent 14.0.2) has been seeing my Focusrite Clarett 8PreX AOK, but suddenly today when I loaded Cubase (tested on various projects), the Focusrite I/O is nowhere to be found (not listed as an option in Studio setup, projects load with missing I/O pop up, etc.). All other apps (Apple Music, FL Studio, Mac OS Sound settings, etc.) are seeing and utilizing the Focusrite with no issues. I did a reinstall (not a full uninstall) to no avail, have rebooted multiple times, etc. The mic privacy settings are enabled for Cubase as well. I’m befuddled (and dead in the water in terms of being able to use Cubase). Any ideas? Thanks!!
Larry
What Focusrite driver version are you using ?
Current one is Focusrite Control (v3.20.0)
Strange that you say the Focusrite shows in everything BUT Cubase 14
What does Focusrite Control show when you try running Cubase, does it show the Hardware is Connected ?
Which version of the Mac OS are you using ?
I’m running Sequoia 15.3.2 on a MacBook Pro M2 Max and Cubase 14 Pro Version 14.0.10 build 144. I won’t update the Cubase version until it’s been out for a while, I see too many problems posted from users with the latest version.
I’m assuming you are NOT running Rosetta mode.
1 Like
Hey Paul- thanks for the reply. Latest Focusrite drivers and version of Focusrite control SW. This I know for sure bc I updated everything a few weeks ago as part of the migration to the new Mac. OS is latest Sequoia and yes, on most recent Cubase release 14.0.2. Everything was working fine on these versions until today. Focusrite Control detects the hardware, looks fine (which makes sense since FL Studio, Apple Music, Mac OS sounds prefs, etc are all seeing the Focusrite and working fine).
The only other thing I can think of is to try using Cubase Pro 14.0.10 instead of v 14.2
I’ve been stung before by updating the Cubase version and then having strange problems which were resolved by rolling back to the previous version.
The fact that you said everything was working fine until today though is weird.
Sorry I can’t help 
Hope you manage to solve this soon !
You could try resetting Cubase’s preferences, maybe something got glitched. Go to ~/Library/Preferences/Cubase and move that folder to your desktop. When you open Cubase again, it’ll create a fresh one. It might help clear whatever’s causing the problem.
Also, go back into Studio > Studio Setup and make sure the right ASIO driver is selected under VST Audio System. Sometimes Cubase defaults to something else, especially after updates.
I know you’re on the latest Focusrite Control, but maybe try uninstalling it, rebooting your Mac, and reinstalling it anyway? Just to be sure the software isn’t having some weird issue with Cubase.
Also, check the security settings for Cubase in System Preferences > Security & Privacy. Even though you’ve got permissions set, sometimes things get reset after updates.
Finally, if nothing else works, try creating a new Cubase project and see if the Focusrite shows up there. If it does, there might be something in your old project causing the issue.
1 Like
Thanks so much for chiming in, Paul! I may go that route, or might just do a full uninstall/reinstall if it gets that far. May also for grins just reinstall the Focusrite stuff, but logic doesn’t support that at the moment. 
Thanks so much for chiming in; I had reset prefs too (should have noted that in my OP). Turns out although the Focusrite driver was current (as was Focusrite control) and all other audio SW was recognizing it, I reinstalled both and Cubase is happy again! Odd, but not complaining! Thanks again!
Weird but that’s the way computers are sometimes, no logic to the way things happen, thanks for posting that you solved it.
