Cubase on MacOS27?

I’ve heard some people are having issues with Cubase or other MIDI-related things on MacOS27. (NoteOff messages not working I heard..) Anyone taken the plunge here and got Cubase working on OS27?

Just took delivery of a new mac mini and didn’t notice any issues while setting up and testing…live midi to vsts and external synths was working fine and I do use a Nektar controller which was is supposed to have the issue - Unfortunately will be next week now before I have time to do full testing.

If you do get the hanging note issue there’s a workaround posted in this thread. But they released a hotfix for Dorico so assume they’ll get a Cubase update out soon to address it

Recently I bumped into this error with my Axiom Air 32 mini. The workaround is a bit rickety, sometimes it works, sometime does not. Since I am much more inlcined to have a workspace that is not plagued by unnecessary 3rd party midi software than the MacOS 27, I decided to downgrade to Tahoe. Now the setup works as it should.

I do not see this as a negative outcome, there are virtually no part of the OS 27 that I am missing. (so far)

It is an interesting debate who should fix the problem, without the OS 27 Cubase works well, however on OS 27 the Apple stuff I checked (GarageBand/Mainstage) also works fine…who is at fault? Are there any experience with other DAWs that have the same problem? Or is it a Steinberg exclusive?

Been running MacOS 27 since the morning it was released and no lag or any issues here. As always, Cubase just keeps doing its job as its supposed to. Had yesterday off and spent almost the entire day in Cubase 15 playing with my TR-1000. Rock solid.

I have heard similar problems with Logic. I believe it depends on if the DAW implements MIDI 2.0 vs 1.0. Some controllers (midi controllers or keyboards) will trigger the problem because they rely on Note=0 rather than NoteOff. Many do not, it would appear. My PreSonus Faderport is one that does.

Glad to hear that in other respects it seems rock solid. The improved Siri AI on-board is a good reason to want OS27. I hope that Steinberg and/or Apple fix this so that MIDI 2.0 is suitably backward compatible on this point.

Well, I have a NI S88 mk3, an AKAI MPD 26 and an M-Audio Oxygen 61 mk4, all work fine. However the Axiom 32 just do not. Though luck.

Also, the bootup time has become longer again on 27, I have a nostalgy for those Sequoia days when the M4 Mac Mini booted up faster than the monitor attached, so I never saw the apple, just the pine trees :slight_smile:

I’m experiencing the same issue with Cubase Pro 14.

MIDI Pipe temporarily fixed the problem, but it introduced other serious issues. It causes MIDI data to be duplicated with every action, so legato patches behave like long-note patches, and when I record, it creates three MIDI events on top of each other.

At this point, Cubase has become completely unusable for me. I’ve contacted Steinberg for support, but unfortunately, they showed very little willingness to help resolve the issue.

After 20 years of using Cubase, I’ve seriously started considering switching to Logic Pro. It’s incredibly frustrating to reach this point after investing so much time, money, and experience into a DAW, only to be left without a proper solution to such a fundamental problem.

Cubase 14 was replaced a year ago by Cubase 15 and isn’t supported beyond MacOS Sequoia. It wasn’t tested with MacOS 26 and it’s not being tested with MacOS 27 because it’s no longer the current version.

Time to upgrade…

FYI @Mehran , on another forum I hear that Logic users have EXACTLY the same problems - its a difference in the definition of “backward compatibility” between how Apple and Microsoft are treating MIDI 2.0 in their recent releases, as I understand it. And: I’ve heard nothing about a patch for it on Logic, whereas elsewhere on this forum ( macOS 27 input via midi keyboard result in hanging note - #95 by Ulf ) Steinberg have kindly told us the patch is in 15.0.40 and is imminent… I hope this makes you feel a bit better about your investment in Steinberg :slight_smile: But @Monotremata is correct, you are running a version not compatible with latest MacOS and it is time to upgrade to something! HTH. All DAWs are good - but not all DAWs are as feature rich as Cubase.

MacOS 27.2 is out, could somebody be so kind to test whether the hanging notes problem has been solved from Apple’s side? I understand that from Steinberg the fix will only come for C15 users, which, I think, is a shame. I do not wish to upgrade, as there isn’t a single function that I would consider as a worthy addition for C15, but that is my problem. However, if Logic is plagued with the same issue (GarageBand and MainStage are not), then Apple could have done something…which is not fixing Logic but fixing the operation system. (hopefully.)

Not sure what’s out there for macOS, but if there’s any sort of MIDI patchbay or translation software, you could have it translate your keyboard’s Note On, Velocity 0 to a regular Note Off message and that would presumably fix this problem.

There’s no problem translating MIDI 1.0 Note Off to MIDI 2.0 Note Off.

Pete
Microsoft

Thanks Pete, but earlier I tried with MidiPipe and it wasn’t up to the standard. anyway, using 3rd party midi apps were always a no-go to me, even back in the days of the Midi Ox.

I would gladly stay wth Tahoe or even go back to Sequoia, the only disturbing thing is the nice long list of solved security issues for the 27.2, that suggests me that I may not be safe without the 27.2 update.

Oh Great, mistakely installed the latest MacOS. Now I can’t open Download Assistant. Well, my fault of course but hello there upstairs and bring us something good, please.

Just install rosetta and it should be fine.

The latest Download Assistant is a universal binary…

But it won’t update without Rosetta…Possibly a direct download of the new one might work though I saw someone else post they still got asked to install rosetta during install. Maybe to uninstall the old version first??

I have not seen any cubase problems yet. But a lot of plugins have issues with installer even with rosetta installed. (And 27.2 is the last version with rosetta support).

I did the update to macOS 27.2, and it didn’t solve the problem. But I have great news: I fixed the issue!

I use Cubase 14.0.41 Pro, and my macOS is 27.2.

The problem was caused by any MIDI controller that sends “Note On with Velocity 0” to the OS instead of “Note Off”.

I had already tried MIDI Pipe, but although it solved part of the problem, it caused some other issues that made it unusable.

How did I fix it? I simply asked ChatGPT to write some code to convert MIDI “Note On with Velocity 0” messages into MIDI “Note Off” messages. Then I used Xcode to compile the code and create a proper macOS application. I set it to run on startup, and it works like a charm!

I can confirm that I now have zero issues. It literally works completely normally.

I believe that if Steinberg wanted to provide us with a hotfix, it would only take a couple of minutes of their engineers’ time. But instead, they told me that Cubase 14 is no longer supported and that I should pay for the upgrade to Cubase 15.

I don’t need the new features in Cubase 15, but the company still wants me to pay for an upgrade instead of fixing the problem.

Steinberg should consider that I’m using Cubase 14, not Cubase 4! Cubase 14 was released less than two years ago. How can they give up on their software so soon and push us to pay for an upgrade? It’s really not nice.

This issue is not a simple malfunction or a minor bug. It fundamentally makes Cubase unusable. They should provide their customers with a hotfix instead of pushing them to pay for an upgrade.

Anyway, I’ve opened my heart here. I’ve been a Steinberg customer for almost 20 years, and now I’m really disappointed in them.

I’m literally thinking about switching to Logic after all these years.

I also tested Ableton Live 12 Lite, and it works perfectly fine on macOS 27 from day one, with no need for my ChatGPT converter app.

I hope this information can be helpful to others facing the same problem.

@AlanP @Monotremata

FWIW, when a product goes out of support in most companies, the entire CI/CD pipeline for it gets taken down at the same time to open up capacity for the next release.

I can’t speak for Steinberg, so I’ll explain ours. I can’t ship any features for Windows 10, or Windows 11 24h2 and below, because the branches that can actually build them are now gone. Those branches are critical as they also handle all the localization for the close to 100 languages we support, and then the specialized versions of Windows required for certain export markets. Sometimes, as in the case of Windows 10, the branches end up over in a different servicing org, which can’t do any feature updates, and can only provide very specific fixes, at significant cost, but we’re a huge company, much larger than any DAW company, so we can do that when necessary.

So while it only took you a few minutes, you’re likely looking at tons of time (and server capacity) to do something like that at a company like Steinberg, just to spin back up the old CI/CD. And don’t forget, you only had to support your one OS in your one language in your one region. And you probably didn’t code-sign it.

Building with AI for this kind of thing is great for individual use, but it gives non-developers a an overly simplistic view of the actual level of effort to create, service, and support real software delivered to the broad public.

Pete
Microsoft