![]() ![]() This time, I (also) removed the Waves LinEQ's (3 of them). I reverted Windows 7 system back to it's current state (backup I made at january 10)įirst I thought it was Nugen VisLM because I could open about 7 sessions problem-free after removing that insert.īut then it happened again. I hope I don't bother people by keeping updates here but maybe it's helpful for others out there. Or have found a new DAW I'm willing to learn. I'll be shift-opening and re-opening from now on, to see if that "fixes" the issue until I have a new system in half a year or so. After shift-opening something resets itself somehow. (I could't enable the plugins after shift-opening).Ģ. I saved as new file, opened it again (withoud shift) and all plugins where active again and working. So I tried Albee's tip, holding the shift key down, and the session indeed opened without crashing. So unfortunately my prediction came true and all has been for nothing.Ī year ago I worked with the exact same template, the exact same plugins, same routing, same video codec (avid) etc. I could work for two days without problems until now. Copy licenses from ilok2 back to ilok1 (that was used at backup point). Restore system from a disk image from june 2015. Re-insert old graphics card that was used at backup point (a system disk image) Thank you Albee, that's very useful information I have one other theory and that is that one of the Windows updates did something that Avid does not like. Now I need to find out what the cause is. It just happened with yet another session so now I'm quite confident that it's triggered by Pro Tools and nothing in the session could change that. But I wouldn't be surprised if even THAT does not solve the problem. Oh thank you Avid, you've been so supportive to your clients (that is sarcasm). And if I do I also am forced to buy new hardware and ALL plugins new since everything is now AAX. I have plans to upgrade to Mac Pro and PT12 but want to wait for the new Mac since the current is 2+ years old. Pro Tools 10 latest (also happened with previous pt10 version so at first I thought the update solved it), Windows 7, M-audio Delta 1010. With everything I do I hold my breath, hoping that Pro Tools won't crash again. But it's a matter of time before it happens again. ![]() After that I can open the project again without problems. The only thing that TEMPORARILY solves the problem is using the 'Rapair' function of the uninstaller (thank god for that). I gave up on trying other things as I have to WORK and DELIVER. Importing the session data does not help (also crashes at import, from any of the versions or backups) Opening older versions does not help (those also crash while previously they have been re-opened without problems) The only cause I can think of is that OMF files delivered from the latest Adobe Premiere (on a Mac) have something in them that makes it happen. I haven't made any changes to the system. This happened now with 3 projects in the past month, it's something new. I start Pro Tools, open the project and BOOM! Pro Tools manages to freeze the complete system (no other software I know does that).Īny other project will open fine. The next day I am asked to make some changes, no problem. I have seen several topics about this problem but none seem identical.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |