Oh, I just re-read the subject line and you seem to be using version 11. I'm not surprised that there are issues. Most beta users are using version 12 and probably don't experience as many issues with OS betas. That said, there are still version 11 betas that come down the pike, although they're much fewer these days. I haven't seen one for a couple of months. I wonder whether version 11 will ever support El Capitan.
Slau On Sep 26, 2015, at 4:40 AM, Kevin Reeves <[email protected]> wrote: > 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 > > -- > You received this message because you are subscribed to the Google Groups > "Pro Tools Accessibility" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
