Kevin Reeves
unread,Sep 26, 2015, 4:40:56 AM9/26/15Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Pro Tools Access
Hey folks.
I upgraded one of my machines to the El Capitan Beta.
As a rule, I never upgrade a mission critical machine to a beta or release that is not yet documented to work with Pro Tools, or other mission critical software.
However, it came to my attention that El Capitan was much snappier in regards to voiceover performance, and I desperately needed that kind of speed, as the latest version of Mavericks was laggy and throwing up busy signals left and right.
With all of that said, I upgraded knowing full well that Pro Tools could break, and I have a laptop capable of letting me get all of my work done, if that were to happen.
Well, allow me to warn you, El Capitan breaks pro tools in some weird ways that will put you at work stoppage.
1. Importing audio gives you this error.
Could not complete the Import Audio command because Assertion in "/Volumes/Development/151228/ProTools/NewFileLibs/Cfd/MacBuild/../MacOS/Cfd_ImportAudioDialogMacOS.mm", line 559.
2. You can not arm tracks with either the mouse, voiceover commands, or using the Shift R command while in the tracks list.
3. You can not instantiate any plugs what so ever. When you press enter, VO space, VO Shift space, or mouse click on any plug.
When you return to the mix window after performing any of these actions, the slot you tried to put the plug on remains empty.
I skimmed a thread on the DUC, and others were having the problem with importing audio, while others were reporting no problems at all. So, YMMV, but you have been severely warned.
None of the above findings are complaints, whines, etc. I knew full well that this could happen, and have a backup machine to start using immediately.
I just want to let you all know what the deal is.
I’m sure avid will release a compatibility update soon, and I imagine that this is potentially old news to the beta team. I just thought you all should know.
Kevin