Big Sur

[reflexson]

So I was bored and decided to grab another ssd and give Big Sur a shot(haven’t upgraded since Sierra). To my amazement, everything frickin works. Pro tools 2020.11, fab filter, acoustica, sound toys, trigger, arturia, and everything else I’ve tried just works, and well. My hd native card works. Even my old blue dcommand. What am I missing here? The internet has told me over and over what a bad idea this is. Actually seeing a slight decrease of cpu usage from the same sessions in Sierra.

[falcowe]

That sounds like a freakin' miracle. How stable is it? I would be hesitant to do any serious work on that. But sounds like fun... assuming you like your desktop os to have silly sliders meant for touch devices :0.

[thoughtrecorder]

I took it a step further and installed Pro tools and all of my normal plugins on a new MacBook Pro M1 and to my amazement I was able to mix an entire 19 track session with 8 aux buses without any issues at all. I’ve got Waves plugins, Antares AutoTune, Melodyne and Ozone 9 running as good as I’ve ever seen it. To top it off on my other Mac when exporting audio it went at about 2x with an offline bounce and now I’m seeing 3x...also when bouncing from my 15” MBP it would get so hot I couldn’t even touch the bottom...this new M1 hardly gets warm.

[Darryl Ramm]

I'm curious on the M1 Mac when you create a new track is the track name text in the new track dialog properly visible?

On Big Sur on a 2019 MBP 15" with 2020.11 only the upper part of the name text renders properly in the new track dialog. That's the only issued I've found running 2020.11 on Big Sur.

[reflexson]

Originally Posted by falcowe

That sounds like a freakin' miracle. How stable is it? I would be hesitant to do any serious work on that. But sounds like fun... assuming you like your desktop os to have silly sliders meant for touch devices :0.

It’s been stable so far. No crashes. I’ve been mixing like normal. Haven’t gone back to my Sierra drive yet. Dark mode for pro tools is barf, but everything has been surprisingly stable.

[itsjustmeee123]

This is interesting. I may try it on a backup drive myself and see what happens.

[lancemcv]

I installed on my Mac Pro 5,1 on a separate SSD, installed without issue but can’t install Eucon. Seems to run fine so far.
Get a warning about QuickTime import and bouncing though have not tried it yet.

[thoughtrecorder]

Originally Posted by Darryl Ramm

I'm curious on the M1 Mac when you create a new track is the track name text in the new track dialog properly visible?

On Big Sur on a 2019 MBP 15" with 2020.11 only the upper part of the name text renders properly in the new track dialog. That's the only issued I've found running 2020.11 on Big Sur.

No it appears fine

[itsjustmeee123]

Originally Posted by lancemcv

I installed on my Mac Pro 5,1 on a separate SSD, installed without issue but can’t install Eucon. Seems to run fine so far.
Get a warning about QuickTime import and bouncing though have not tried it yet.

Did you update to EUCON 2020.11? From what I've read in another post here, it's compatible.

[zoff]

Originally Posted by Darryl Ramm

I'm curious on the M1 Mac when you create a new track is the track name text in the new track dialog properly visible?

On Big Sur on a 2019 MBP 15" with 2020.11 only the upper part of the name text renders properly in the new track dialog. That's the only issued I've found running 2020.11 on Big Sur.

I have a 2019 MBP 16"and I don't have the text render problem.