For the life of me I cannot get my Mustang LT25 USB to show up as an input in Cubase 12.
Details:
I see it in the Mac OS Monterey System Preferences along with other devices (Blue Yeti, Internal Mic, etc.)
It is selectable and the input is isolated to that device (I verify with the VU meter in the System Prefs panel)
Cubase 11 and Cubase 12 both have the microphone permission granted in System Preferences > Security and Privacy > Microphone.
This is an upgrade from Cubase 11.
So all that seems good but then over in Cubase (Studio > Studio Setup > Audio System | ASIO Driver) it is not listed, but all the other devices are.
Also, and maybe this isn’t how it’s supposed to work, but no matter what I set as the ‘input’ on the OSX side (Yeti or Fender) when I choose ‘built-in’ in Cubase, it stays on the internal Macbook mic.
Make sure Cubase has enabled Mic in the System Preferences, please.
Open macOS System Preferences > Security & Privacy > Privacy > Microphone. Enable Cubase here.
I noted in my original post that this has been enabled but I think I wasn’t very clear about it. I have edited the note now to say “Cubase 11 and Cubase 12 both have the microphone permission granted in System Preferences > Security and Privacy > Microphone.”
It could be that even though both Cubase 11 and Cubase 12 show that the permissions are set in the OS, maybe they aren’t actually in some config somewhere.
Searching the interwebs before posting here I found this cryptic solution, which I did not try yet. And then this super detailed solution, which seems to match mostly what my situation is, but seems pretty heavy handed. I know that the problem in that solution is that Cubase doesn’t show up at all, but if my theory that there is some additional bug in the privacy checkboxes being checked but some config file being out of whack is true then my gut says that forcing a re-evaluation of the permission without the old Cubase 11 version to reference might fix it.
I can imagine that manually testing an update path from 11 to 12 with an OS update in the middle will be lightly tested because of the setup time and execution costs.
