#PROTOOLS 12 6117 DAE UPDATE#
I also have a lot of $$ invested in those plug-ins and obviously want to keep using them.Īt this point I'm trying to separate Avid issues from Waves issues and hope that the announced PT 12.4 update might resolve some of these stability issues.
Starting 12.8.1, I was able to use the 'n' key and that's how I found out PT was attempting to use the CUBASE Generic ASIO driver. I uninstalled 12.8.2 and installed 12.8.1 (after doing the 'Trasher' utility thing). Uninstalling all of my Waves plug-ins seems to resolve the AAE 6 issue for me, but then I'm still faced with AAE -9173 and ProTools.exe hanging, forcing me to use Ctrl+Alt+Del and then reboot. Pressing the 'n' key while starting PT 12.8.2 was just not working - don't know why. I did try the Acronis drive monitor someone else had recommended and that shows no signs of errors or potential issues with my 7200 rpm drive. I can close the session and reopen to move forward until the next error. I started using the disk cache feature and that seems to improve overall performance, although I will still get AAE 6 when opening the session and the audio is being cached to disk. I've since updated to PT 12, added more RAM and switched to an MBOX 3, which is on the list of supported interfaces.ĪAE 6 still occurs frequently during playback, when dragging a clip onto an open track in the edit window or just trying to select an audio clip on the timeline. Details were posted on that separate thread. I first got AAE 6 while still running PT 11. They're stable, solid, and these days can be had for very little on the used market.
#PROTOOLS 12 6117 DAE PRO#
I don't believe in this yearly update of a major operating system and personally, I'd rather keep older Pro Tools rigs going just to get the job done. I'll be quite pissed once it is longer supported. Mountain Lion rocked, still rocks and I hope it will for some time. Then again, neither is El Capitan, since I first tried building up a new rig for that before discovering that many of my plugins weren't supported and don't work (Plugin Alliance, namely, which is a huge one for me). My Yosemite partition was running great otherwise, and all other apps were fine, so I suspect that Yosemite is not a great Operating System for Pro Tools. With over 350 plugin licenses, settings and sample libraries to reinstall, it wasn't something I enjoyed.but I will say, I have not had a single AAE message since doing it. I eventually formatted the entire mix rig, and reinstalled Mountain Lion and every app from scratch - something I really wasn't looking forward to doing, and that eventually took me over 5 days to completely straighten out. My audio was running off an internal SSD drive on a 2012 Macbook Pro and it made absolutely no sense. Ya know, I was on Yosemite for a few months and these dumb AAE errors got worse and worse.
0 kommentar(er)
