#Bitwig studio m1 upgrade
#Bitwig studio m1 pro
#Bitwig studio m1 software
#Bitwig studio m1 mac

The newer plugins which were giving my old system a bit of a hard time like soothe for example, work a bit better, but after a few instances in moderate settings still crash my system. It's more like going from Civic to an Acura. With regards to comparing it to my old computer, yes, there is a noticeable difference, but it's not like going from a Honda civic to a Ferrari or even a Porsche.

#Bitwig studio m1 mac

I made a thread when I first got it earlier this year addressing some of my first impressions and covering some of that mac studio m1 max wtf?

#Bitwig studio m1 pro

SHOCKINGLY, it's not really THAAAT much better than my old geezer 3,1 Mac Pro!!!Īlso, compared to friends I know who have imac pro 5ks and trashcan mac pros, it performs around the same, and in some cases, WORSE! Perhaps, I was overexcited? I don't know. Off the bat, it fell way short of my expectations.

#Bitwig studio m1 software

The wait time for 64 gb was too much but I figured with the new SOC the 32gb would be fine (it actually has been better than I thought, even with really large string libraries during production and all types of kontakt etc.) The problem isn't the ram I don't think, but the CPU and how the software coding works with Apple Silicon. Once the Mac Studio came out though, it was the mac mini pro I was waiting for as it had a good price point and better performance and a more reasonable ram amount. I waited for a couple years and didn't jump at the mac mini thinking it was a little too underpowered and had hidden costs such as so many peripheral accessories (not the monitor but pcie for my apogee and HDs). The promise of mac pro level performance at a fraction of the cost was almost too good to be true. The previous high end Intel options such as 2017 imac pro 5k and current mac pro, were crazy expensive and I had considered them a few years down the line (or so I thought whatever would be its equivalent)Īlong comes M1.

#Bitwig studio m1 upgrade

Though it did slow things down a bit so I figured its time to upgrade so I can work without the anxiety and pain of having to do these extra steps. Though the last couple of years with much more cpu intensive plugins coming out, it started to get a little sluggish, though I was still able to make it work with some extra steps (offline bounces, freezing etc.). Had its OS upgraded beyond its official limit and it ran everything fine. Surprisingly it held up quite well and even now it works fine. So up until earlier this year, I was working with a maxed out and upgraded-as-much-as-possible 2008 Mac Pro. Also a lot of using IO for mixing and external midi/midi over USB in combo with software synths and orchestral libraries etc.

I thought it's important to state this because I feel that the context in which this is all used it important, and I happen to have a wide range of things I do which requires a lot of different processes. etc., as well as a decent amount of outboard gear and analog summing. A lot of plugins, including whatever the current standards are, Soothe, etc. etc., as well as a lot of hardware synths and drum machines. For production I use a lot of modern standards, Nexus/Serum/NI kontakt/Spitfire etc. The genres range from more traditional rock/indie rock (so live instruments) to modern electronic based productions (heavy soft synths, plug ins etc). Here is a 5 month thread of a 32gb Mac Studio M1 Max running Logic Pro X and Apogee Symphony IO mk1 TLDR: Don't buy any Apple silicon computer if you do heavy music production/mixing for a few more years until software catches upto hardware.