Can I have 2 instances of Cubase on my Mac -- one native, one Rosetta?

I’m opening a bunch of those old Ashton Gleckman Cubase projects, the ones he shows in his Behind the Scenes series. Since they are so old, I found that it’s best to open them setting Cubase to Rosetta 2, because among other things, that allows them to open in a form as close as possible to the way they were created, in the native architecture at the time.

And that means that the tracks for which he used Kontakt 5 open in that version of Kontakt, and if I happen to have the instrument he used, then the track ends up being exactly the way he did it, or at least close to it.

But when I work on other stuff, I don’t want to use an emulation layer when I paid good money for a Mac Studio. That said, it’s a royal pain to each time open the app in the Finder, right click on it, check the Open in Rosetta option, and then uncheck it when I want to go back to the native version.

So I was thinking of duplicating the full app package and rename it Cubase Rosetta, so I can open one or the other depending on what I need to do. Would this break Cubase in any way, or even make it unstable?

Hi,

Yes, you can do so. Just copy the application and switch the mode for one of the copy (of course I would recommend to rename it respectively).

Just be aware, both of the applications will share the same Preferences folder and files.

I tried this a while ago, and the problem seems to be that even though I name the copy Cubase Rosetta, Cubase files get associated with it, not with the original Cubase app package. Even if I manually set .cpr files to open with the original Cubase, eventually they switch automatically to the Rosetta one.

That’s because regardless of what you rename the outer package container to, the application itself has an internal ID which all your file associations and whatnot are based on. You can rename the container Logic Pro even, it’s still going to take over the file associations for whatever version of Cubase it is, not Logic’s stuff, because it’s coded in the app itself.

At this point, you’ve just really confused your Mac. :smiley:

It’s not just my Mac. It’s everybody I interact with. :joy: