Is Pro Tools Compatible with OS X Yosemite?
Updated 1/20/2015: Yosemite 10.10.1 is now fully compatible with Pro Tools 11. You must get the latest version 11.3 (See details below:
System Requirements and Compatibility with Pro Tools 11 Software (details)
- Pro Tools 11.3 supports Mac OS X 10.10 & 10.10.1 (Yosemite), 10.9.5 (Mavericks) and 10.8.5 (Mountain Lion)
- Pro Tools 11.3 supports Windows 8, Windows 8.1, Windows 7 and Windows 7 SP1
- Avid Artist, S3, and MCPro Users: EuControl and Workstation are not officially qualified with Yosemite at this time. Upgrading to Yosemite is not recommended yet for use with these products. If using Pro Tools 11.3 with these on Mountain Lion or Mavericks you should install EuControl 3.2 or higher (My Artist Login)
- S6 owners should update to version 1.3 to use Pro Tools 11.3 (Avid Account > My Products > S6 Software Update > Show)
The Read Me file documents important compatibility information, known issues, error messages, issues resolved, etc.
Apple recently released the public beta of OS X Yosemite and I went ahead and decided to test the latest version of Pro Tools and see how it holds up. I tested Pro Tools 11.2 on two Macs - Late 2008 Macbook and Early 2009 8-Core Mac Pro. Let's get to it!
I was very surprised how stable it was running with a fairly large session. The session had over 35 tracks and 40 plugins running. I spent some time recording, mixing and playing back with not a single error on the Mac Pro. The Macbook ran out of CPU power once or twice but that is expected with the lack of power it has. After running the latest version of Mavericks and the Yosemite public preview, it doesn't seem that Yosemite is being much of a memory hog. They are very close! Apple will be cleaning it up and squashing some more bugs so I get the feeling that this will be a better build than Mavericks.
Based on my experience with Yosemite and Pro Tools, I believe Avid should roll out an update that offers full compatibility fairly quickly. As far as Pro Tools 10.3.9 goes, the installer failed to even start due to software requirements (see below).