I’m not fully versed in Mac compatibility issues, I’m on Win10, so I can’t help in this fashion. What I can say is that there is a work-around for the issue. It isn’t convenient, but it allows one to continue work.
Rather than directly opening up a Cubase 13, or older, session. Import the session into a new Cubase 14 session. This appears to resolve whatever causes the issue to show up.
There was hope that the recent maintenance update would resolve this issue, but there seems to be something significantly different about the MIDI remote implementation in 14 that is not at all compatible with the data stored in 13 and older sessions.
If a Cubase 13 session is opened in Cubase 14, and a control surface gets borked, I advise immediately closing the session before saving or before autosave can happen. If the session is saved, then the session will remain cursed.
hahaha…just realized it’s the wizoo guys. I have embracer in Cubase 6.5 so I took a quick look at its gui.
Yeah, it was the wizoo guys so copying the dll etc to test with Jbridge in Cubendo14 failed of course. Those guys were pretty intense about protection as I remember.
I dunno…even though Avid and InMusic gobbled up wizoo years ago, maybe embracer is somehow still existing within all the stuff Kellegg (or whatever his name was) brought out under the current A.I.R umbrella.
Oh well, as long as an elicenser works, one could run Cubase 6.5 on a pc slaved to a Cubendo 14 pc and route Embracer midi/audio to/from. I can’t see using it, but I guess some guys really liked that one…or need it in terms of recreating old projects.
Maybe the A.I.R guys would consider a back-to-2000 legacy reissue of their ancient stuff, ported to 64bit or unprotected or whatever.
You can also copy the Embracer DLL to your Cubase 8.5 (32-bit) folder and it will still work. That’s the most recent version of Cubase that will run the old Steinberg VSTi’s.
Good idea.
Of course, another far less elegant option is to just bounce a rough mix and open it up in the older version of Cubase we need in order to work on an Embracer part, etc.
Oddly, that option hadn’t occurred to me when I was working recently. This doesn’t work so well on MAC unless you have an old machine that opens up 32-bit programs, though. But on Windows, it works fine… that is, at least on my old Windows 10 machine with hardware circa 2008. Does this work on a modern Windows 11 machine?