2020.3 on Mac Pro 5.1, High Sierra?

[audioluche]

Originally Posted by Farhoof

I just installed High Sierra including the firmware update without any issues on a 5.1 mac pro.

SSD installed on a regular sata port, no spinner needed.
GPU is an old Radeon 5770 (non mac gpu's have issues updating the firmware).
High Sierra downloaded from the app store and run from the Applications folder.

All the info you need is here: https://forums.macrumors.com/threads...hread.2142418/
Pci-e disks don't work. Raid disks don't work. Non mac gpu's don't work. Installing from a usb boot drive doesn't work. 4K displays don't work. Any old high sierra installer doesn't work. Filevault needs to be turned off. Basically what you need is a configuration as sold by Apple in 2010/2012, though I can confirm an SSD works fine as long as it's connected to the standard sata ports.

That's what i've tried. Same video card then you, downloaded from the App store, etc..


I did not work until i tried with a regular drive.
Then, bingo! It worked. And i was able to install it on my SSD drive after that.


So now it's working. Pro Tools 2020.3 on High sierra working just fine
Thanks Padje for the tip

[JFreak]

Good to hear. Now keep that in mind when you eventually upgrade your GPU to Metal compatible and update to Mojave

[Panacci]

Funny, I have a 2009 Mac Pro. I flashed it to5.1 and installed Sierra. I thought that when it is flashed to 5.1 if Sierra works, High Sierra should. The only problem I had was my High Sierra installers were not working because they were out of date and I had to knock the date in my computer for the installer to work. When I did that it loaded fine.

[JFreak]

So it seems there are a bunch of tricks you might need to try to get those flashed 4,1 --> 5,1 cheesegraters to accept another firmware update

[audioluche]

Originally Posted by JFreak

Good to hear. Now keep that in mind when you eventually upgrade your GPU to Metal compatible and update to Mojave

Yep. Thanks for your help Janne!

[JFreak]

No problem

[spoons]

Just adding that my 4,1 to 5,1 flashed Mac pro running Sierra runs 2020.3 with no problems mixing fairly large surround sessions to picture.


Sent from my iPhone using Tapatalk

[innesireinar]

Originally Posted by audioluche

It just wont let me do the install. In fact, I am on a SSD drive.

I'm on a ssd since 4 years. Last year I've upgraded sierra to hs and during the process it asked me to update the firmware. I did it. All worked fine. But maybe (don't remember exactly) it asked me the firmware update when I was still on the usb stick hs installer, because I usually upgrade the OS by formatting the Os disk then do a clean installation.

[nigelpry]

I can also confirm that the High Sierra 10.3.6 clean install, and more recently Mojave 10.14.6 clean install ran without issue, on my cheesegrater 4.1 updated to 5.1 with SSD OS drives (Samsung EVO).

But after the original 4.1 to 5.1 firmware flash, I later replaced the mobo, processors and Ram, to get 2x 6-core 3.46ghz processors, 64gb ram, so it is now seen as a genuine 5.1.

Maybe that makes a difference, or maybe the specific make/model of ssd makes a difference.

Had 2020.3 running for two days now, left on overnight too. Approx 10 mixing across the two day, and about the same trial and error working on template ideas incorporating a basic folder hierarchy to organise things, and updating my track presets.

I’ve shied away from using routing folders for now, because of reported issues going back a while where complex sub routing played havoc with plugin delay compensation where audio goes via multiple paths that each result in different plugin delay total amounts.

I modified my workflow to keep multiple routing paths for audio to a minimum, and above all simple. All audio and instrument tracks are routed directly to my mix buss, with sends on those tracks going to aux track fx busses that then route to the mix buss, and other sends on those tracks going to aux track parallel compression busses that also route to the mix buss.

I avoid aux tracks having sends to other aux tracks because of how many paths with different total delay values a single audio source may end up travelling.

That problem may have been fixed now, I have no idea really, but I haven’t felt the need to back to my previously more complex routing setups. Simple works for me!