![]() This was the install method where you don’t overwrite all your apps etc, so an upgrade not a clean install.Īs far as I can tell now over a week running Catalina, everything is superb. So then I replaced the original SSD and upgraded that. So with extreme trepidation and caution I cloned the main drive, took it out, replaced it with the clone, and directly installed Catalina onto that drive (this was non-SSD and in fact had errors on it, it was relegated to a back of a back up for emergencies, so I was quite surprised how well it ran!) Everything ran perfectly, all DAWs etc worked really well, again probably smoother overall. 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. ![]() You also get the added benefit of point-release updates that fix new bugs.Hi so firstly I’m very happy with the MacPro running Catalina, and really glad I took the plunge. If you have a MacBook, keep an eye out for the Bluetooth bug that constantly wakes the Mac during sleep-you may need to turn off Bluetooth when you’re not using your laptop.īut if what you’re waiting for is Universal Control, there’s nothing wrong with waiting to upgrade until it is ready. It’s not a massive overhaul over Big Sur, and while there may be some new bugs that get discovered after the final release, as we said, Apple tends to issue patches quickly. If you’re anxious to get your hands on the new features that are ready right now, upgrading to macOS Monterey should be a smooth experience, especially now that version 12.2 is out. ![]() It’s unclear if it has been fixed in recent updates, but it’s always advisable to stay up to date if you’re experiencing issues. Apple has not made a statement about this problem and it doesn’t seem to be isolated to Monterey-macOS Big Sur users are experiencing the same problem. This is likely a memory allocation bug that will be fixed in an OS update. Over a short period of time, the amount of memory allocated adds up and takes up a huge chunk of RAM. Another issue that is being reported is memory leaks, where an app or function doesn’t release the memory it was using in RAM.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |