![]() ![]() The Mac Pro was running Mojave (I’d upgraded the graphics to do that a while back). So this made me wary of trying it with the MacPro in the Studio, until I saw the spec needed for C12. I haven’t stress tested it but it way outperforms the other DAWs, so at least I do have a DAW on the MB, and I also have a partition I can boot into High Sierra if needs be. However, it’s interesting to note that Cubase 11, and then this week 12, runs absolutely fine. ![]() This didn’t bother me as I don’t use the Macbook for audio so much, maybe a bit of editing. Crackling audio with anything above a basic few tracks. However, I discovered that when I ran audio apps, Studio One & Mixbus 32C, I got reduced performance. At first I was extremely impressed, everything ran very smoothly, apart from a grey background to the menu bar, as the graphics on this model are not metal compatible. ![]() It did and so then I installed onto the main SSD drive of the Macbook (Late 2011, 2.8GhZ dual core i7, 8gb ram). Then, following dosdude’s video to the letter I installed to an external drive first, to be sure it would run. I started with the MacBook which was running High Sierra, made a clone of the hard-drive first. The reason I did the Catalina patch was a/ on my MacBook so I could run Dorico 4 (and by good fortune it seems, C12) and on the studio MacPro 5.1 so that I could run Cubase 12. Here is what I did to calm my worries about messing up my system which was running very well. On the Macbook not so positive but read on. Even though I may yet buy a Mac Mini M1, for portability and future proofing reasons. Hi so firstly I’m very happy with the MacPro running Catalina, and really glad I took the plunge. ![]()
0 Comments
Leave a Reply. |