Hi,
Does it work for you in the Disabled Preferences? Do you get the MIDI data into Cubase?
1 Like
Hi,
Great! This picture shows, the system knows about the MIDI Device. It has been used. But itās not active/connected at this moment.
Could you maybe try another USB Port and or USB cable, please?
You can also try to execute the following command to delete the MIDI preference files:
rm -r ~/Library/Preferences/com.apple.audio.AudioMIDISetup.plist
After executing the command, restart your Mac to apply the changes.
I donāt know where to find disabled preferences, I can only get audio with local control on, if it is off, there is no signal
I donāt think disablong preferences would work for your issue. On your side, itās on the system level, not in Cubase.
You can try to execute the following command in Terminal to delete the MIDI preference files:
rm -r ~/Library/Preferences/com.apple.audio.AudioMIDISetup.plist
After executing the command, restart your Mac to apply the changes.
Iāll look up where I can find the terminal setting (Iām a lifelong PC user - Iām new to Apple which has me puzzled many times, like today).
Iāve done that but no change. its beginning to look like an Apple issue and so Iāll give them a call later this week.
Once I have it resolved, Iāll let you know.
Many thanks again,
Robert
1 Like
-Akai keyboard doesnāt work in either disabled pref.-startup or normal mode (but it has worked sometimes in Cubase and always in other daws, while in Seqouia)
-Arturia keylab ess. worked in disabled pref. mode and also in normal mode (but not when disconnected and reconnected again in same session; and similarly this Ā«sometimes it works at startup and sometimes notĀ» has been situation all along in Seqouia. As with Akai, never any issues in Garageband, Performer Lite nor Zenbeats)
Hi,
This is different. Cubase has an auto-detection mechanism. It should recognize a MIDI Device that becomes connected while the program is running. However, this might not work 100% of the time.
So the save way is to always first plug in and switch the MIDI Device On first and then start Cubase.
Of course, it would be great to know when it worked and what was different, when it worked and when it didnāt.
Hello Martin,
Following up on my query, Apple very kindly looked at my MacBook remotely - it was concluded that the Yamaha Steinberg USB driver 3.1.7 is perhaps not compatible with Sequoia at the moment for the CP88 and was referred to Yamaha.
I chatted to Yamaha technical support in the UK and one solution may well be a temporary roll back of the operating system from Sequoia to Sonoma.
However, Iāll just wait for the next USB driver update from Yamaha and record the CP88 as audio in Cubase when required and use my Komplete Kontrol keyboard for all other Cubase interactions.
Once again, many thanks for your efforts in assisting me.
Regards,
Robert
Hi Robert,
Iām sorry for this result. I hope, you will receive the driver update soon.
Itās hard to say when it works and not, Iāve tried a lot of different things but notice no pattern. Default situation is that itās not working (alas, little to build a pattern from) the last half a year or so, partly given up but hoping someday it will run as normal again.
I most often (try to) start up Cubase after restart or full shut down of OS and except that to be sufficient.
Nevertheless, your willingness to help is much appreciated! Thank you.
The last several attempts fresh Cubase start after restart/shutdown neither keyboards did work either in disabled pref.-mode or normal mode.
Hi,
Do you still see the devices in the Sutdio Setup > MIDI Ports Setup, please?
Yes, I check every time.
Hello again Martin,
I hope you are well.
Have heard any information on when the midi driver 3.1.7 will be updated?
I met with the Apple support team in Trafford Centre Manchester and they advised not to relax the security settings on my MacBook Pro as this would immediately expose it to hackers.
Many thanks and regards,
Robert
Hi, you may consider having them clarify the scope of this advice. From a general security posture perspective, yes, the default security setting of āFull Securityā for Apple-only DriverKit and legacy kext signatures is the most secure. The reality of the development model for modern audio equipment is that the migration to DriverKit from kernel-mode kexts is slow and painful. Even today, if you want to use an RME or UAD interface, you must relax your security posture. For those two developers, itās even worse as you must allow unsigned kexts, even though they BOTH are code-signing vendors for Apple. I have an opinion about that, but it doesnāt matter.
Where it may matter for you is that even with relaxed security requirements, an attacker would ALREADY require root to your system to install a malicious kext. So they already have to be root to get root. Further, after a reboot, you would STILL have to go in and manually approve the unsigned kext extension for it to run. So the actual scope of vulnerability is limited here. The ārealā risk is that you just download some kext from the internet, install it with Admin approval, then go back and explicitly allow it run after install. You seem FAR too astute (based on the manner in which to phrase and respond to questions) to fall for something like that 
Your teamās comment of āimmediately expose it to hackersā isnāt exactly correct.
It will be some time before developers ācatch upā to the new restrictions for driverkit deployment. Iāve been having to accommodate UAD for years now in this regard - literally. When I recently got a new RME interface, it too required āreduced securityā to run.
I only say all this to let you now that if you are going to wait for devs to catch up, youāll probably be doing it for quite some time. If you practice even the most basic security, you should be unaffected. Even if you mistakenly install a malicious kext, it canāt run without you saying so. It may be worth it to you to get back to making music with current software drivers and OS patches; just giving you my buck-o-five.
1 Like
Thank you for your most informative reply to my query and kind words. Iām afraid I am rather risk averse even to the point of all emails received that arenāt from a contact going immediately to junk for sorting and review.
Iāll have another chat to Apple support when next in Trafford Centre but in the meantime, as my Korg and Native Instruments equipment work fine with Sequoia, I can probably wait for an update and use my CP88 for audio only for the specific sounds I need from it.
Again, your detailed response is most appreciated, thank you.
Robert
1 Like
Sounds like an informed and reasonable response based on requirements and dependences. One of my favorite things
An example of ārisk managementā at its finest! Have a good one!