Install “License Support.pkg” at reboot.
#Pro tools 12 pro
Install “Install Pro Tools 12.x.x.pkg” at reboot.So now you have all five components needed to deploy Pro Tools 12. With a few tweaks (specifically lines 4, 6, 11, 12, 17, 20, and 21) this worked brilliantly for Pro Tools 12.Ī copy of the updated script can be found on our GitHub here. It so happens that there’s already a script for Pro Tools 11 that does this. Add new directories in to /Library/Application Support/Avid/Audio for Plugins.Add a Launch Daemon to start it at boot.Add it’s “shoe” tool to the /Library/PrivilegedHelperTools directory.Test deployment complete…but it still wants admin rights on first launch? Add all four to your deployment solution of choice. These all need to be added as ‘postponed’ or ‘on reboot’ installations. A copy of the iLok License Manager installer package (“License Support.pkg”), grabbed from here (yes it’s in a DMG, in a ZIP file).Found in the “Driver Installers” directory. The “Install Avid HD Driver.pkg” installer package.Found in the “Codec Installers” directory. The “Install Avid Codecs LE.pkg” installer package.The “Install Pro Tools 12.x.x.pkg” installer package.So, you’ve downloaded your Pro Tools 12 package from Avid and it looks little like this: Neil Martin of UEL on Mac Admins Slack), who pointed me to the right areas to dig into.Please Note: These notes have been written on the assumption of using an iLok licensing management solution and so doesn’t deal with any licensing models outside of this.Ĭredit where credit is due (aka standing on the shoulders of giants)īefore I start, I have to confess I have pulled most of what I needed from work others have done for Pro Tools 11. This one revolves around turning the Pro Tools 12 installation into something that can be deployed by your Mac deployment / patching solution of choice. Maybe I should start a new series on these 🙂
Again, this is gonna be another one of those “I had to do something for a client and so I thought I’d share” blogs.
0 kommentar(er)
