![]() |
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#1
|
|||
|
|||
![]()
As of today (never before has this happened) Pro Tools crashes when I open a session located on my Firewire Drive. It doesn't even fully open the session before it crashes. Does anybody know why this is happening? I'm using a 002 on a g4 os X ProTools 6.0.2 Thanks and I appreciate it!
|
#2
|
|||
|
|||
![]()
Do you have PT open first and are then trying to open the session?
Did you have the drive mounted already when you opened PT? What is the status of the drive in the workspace window? Have you checked the drive with somthing like Disk Warrior? can you create a new session on the drive that works? Have you tried importing tracks from the original session into one that works? Will that playback/record? these and other questions....
__________________
He used to cut the grass...he was a very nice boy... |
#3
|
|||
|
|||
![]()
-It happens when I have PT open first, as well as when I double click on the session file.
-It happens when I create a new session. Sometimes the newly created session is corrupt from quitting before it's fully created. -This issue occurs on all PT sessions located on my Lacie. -Sessions located on my internal disk work fine -If I drag a session off my lacie, onto the desktop, and launch it, the session works -The drive was mounted when I opened PT. -Haven't checked the drive with disk warrior, but other files (Documents, mp3s, etc) work when launched from the Lacie. -I imported a file from a Lacie PT session to a session located on my internal drive and the audio file worked in the session Not good: When I open a session from my internal disk, create a new track, set the disk allocation for that track to my Lacie and record, it pops a warning: "Could not complete your request because: Neo Access Error..." Tried recording to my Lacie a second time, in the same fasion, and it just "Unexpectedly Quit" Out of ideas... Any suggestions would be much appreciated! |
#4
|
|||
|
|||
![]()
You didn't install that silverlining software that comes with the Lacie did you? There have also been reports of firewire drives suddenly not being recognized by protools as acceptable volumes (especially after upgrades) and the only fix was to back up the drive and re-format using Apple's disk utility again.
|
#5
|
|||
|
|||
![]()
Nada, no silverlining software for me. I do appreciate the suggestions, anybody got any other ideas?
|
#6
|
|||
|
|||
![]()
The problem doesn't exist in ProTools 5.2.3 on Mac OS 9.2.2. Only OS 10.2.8 Pro Tools 6... Wouldn't it be grand in a world without upgrades......
|
#7
|
||||
|
||||
![]()
Trash the Digidesign database folder on all mounted drives. Then try to open the session again.
__________________
Will Russell Electric Wilburland Studio www.wilburland.com M1MAX Mac Studio OS 12.6, PT2022.12, HDX, D-Command M1 PRO MacBook Pro OS 13.1, PT2022.12, BabyFacePro FS |
#8
|
|||
|
|||
![]()
And it's as simple as that. I didn't even know that folder existed or what it does. Either way, PT is seeing the drive and it's working fine now. I'm in debt. Let me know if you hane any oddball issues that I may have experienced before and could help you with. Thanks everybody for your helpful tips.
Peace, Nathanael |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Protools crashes on opening sessions | Etienne_C | Pro Tools TDM Systems (Mac) | 2 | 07-29-2010 06:31 AM |
OS Crashes when opening protools | schumach | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 2 | 04-25-2008 09:43 AM |
protools crashes while opening | straight cash | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 14 | 01-23-2007 10:04 AM |
ProTools LE 6.4 crashes when opening a session | olguitar | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 1 | 06-07-2004 04:13 PM |
Opening new session crashes Protools | Studiomeijer | Pro Tools TDM Systems (Mac) | 1 | 12-21-2003 04:38 AM |