**Problem: Certain sessions crash on opening...

[DustySpuds]

Hi,

I have had some trouble lately using PTLE 6.4 on OS X 10.3.9 and an 001 on a DP 1.25ghz G4 w/768 RAM.
Most of the time the systems runs flawlessly, but certain sessions just wont open, PT crashes with the "unexpected quit" dialogue.
Ive tried a few work arounds, like creating a new session and importing all the tracks from the 'broken' one, but as soon as the tracks import, they crash.
Could it be a specific track? or is it a certain audio file?

Any help would be greatly great

thanks

DaVE.

========================================
PTLE 6.4 001 & 6.9 mBox
PowerMacG4 DP1.25ghz and PowerBookG4 867mhz both w/ 768 RAM
"Panther" 10.3.9 on both systems.

[KingFish]

Dave.... it's likely a conflict with Plugin versions... ie... if the session was last saves with an antares Auto-tune v3 inserted, and you are trying to open the session on a system with Auto-tune 4 - the session will unexpectedly Quit on load.

Antares, VST wrapped Instruments, Sampletank 1, or "se" sessions on a sampletank 2 system, are bad for this... I'm sure the list is larger, but of the plugins I own... the above listed are the ones I have a problem with.

Update all plugins you own from the manufacturer's websites... if the problem still occurs once you are fully updated (which unfortunately it likely will)

To find out which plugin it is.... on your desktop... make a temporary folder called PLUGS (or whatever you want)

then... from the root, of your system drive... go to Library/application support/Digidesign/Plug-Ins and drag all of the plugins out of the folder, into the folder on your desktop (PLUGS)

Load the session...... make a list of what plugins are inserted in your session, close Pro-tools, and replace all of the plugins you've moved to your desktop to their original location (Library/application support/Digidesign/Plug-Ins) EXCEPT for the ones, on the list, used in your session.

Load your session, and quit pro-tools, adding one of the plugins at a time.... when PT crashes... you've found the culprit.... you can take the plugin back out of the folder... open the session... remove all instances of the plug, save the session... put the remaining plugins back in the system folder.... and re-insert, configure, and save the plugin in your session, with the current plugin version you have... you shouldn't have any future problems re-opening the session (until you upgrade plugin versions... then... all bet's are off)

Good luck... and tell us which one it was.