Screwed in the field (P2 + FCP) HELP!!!!!!!

[tucklandon]

Here is the scenario:


Final Cut Pro 5.1.4 / Panasonic HVX P2 files:


1) Shot for two days, ingested lots of footage into FCP on laptop (in the field). Using 1 ext 300g
FW drive and another as a backup - no problems


2) Transferred two day footage project file onto Intel Mac (running same FCP) all was peachy, edited all two day stuff


3) At beginning of Day 3 in the field, re-attached FW drive to laptop for that day's shooting - got error message, "can't find this file" or "this file is missing"...all others showed up fine.


4) Ingested some new P2 files a few hours later, closed project file...later (still on laptop) tried to re-open
project file...it loads about 60-70% then - BOOM - "Final Cut Pro has unexpectedly quit". Tried to re-open several times no luck...had to open new project file to be able to ingest newly shot files...after a while the new project files behaved the EXACT same way...ended up having to open 3 new project files to be able to keep workflow going..


5) Trashed prefs twice - no effect / renamed files, projects, drives, left and right - no effect / tried another laptop with same FCP version - same problem occurred / got brand new FW drive for new footage, new laptop - SAME THING HAPPENED


while it appears no footage was lost (all got ingested to drives) FCP has been rendered useless in keeping
a workflow going....and we are nervous about retattaching any of those drives back to the Intel Mac where
the 'base' editing file is

 

[nsoltz]

First of all, make certain that you are running OS X 10.4.9 with FCP 5.1.4. It does not work and play well with 10.4.8. Make certain that you update to 10.4.9 using the downloadable Combo updater (I never update using the delta version from Software Update). Repair permissions on your start up drive.

The other thing you could do is check the directory structure on all drives with Disk First Aid but preferably with Disk Warrior. I think that Disk Warrior is one of those things that should accompany anyone on a remote edit since it can fix any number of directory problems. That is very well what may be the case here if it is not an OS problem.

In any event, could you please post either you solution (or non-solution) as the case may be. Those of us with MacBook Pro's and FCP field editing workflows would benefit.

One more thing-- I have a SATA Express34 card for my MBP and prefer SATA over firewire.

Ned Soltz

 

[tonyfarley]

the firewire drive is too slow.

Tony

 

[wgzn]

i cant imagine slow drive speed alone being the issue. i edit p2 in the field just using the internal boot drive of my old 1.0ghz powerbook g4 all the time with no problems. id bet its a cheap chip/bridge set in your firewire drive.

what brand of drive is it?