P2 Import hanging at 4.7GB on FCP

P

Peter Richardson

Well-known member
Hi guys,

I am attempting to import some P2 footage into Final Cut (6.0.6) and the import keeps hanging at 4.7GB. I have tried different clips, different cards, transferred the card data to the drive and attempted to import, and used the P2CMS utility, still no luck.

The drive is aa G-Raid that is formatted as Mac OS Extended, but is not journalled. I have a couple drives that are not journalled and haven't had this problem.

Any guesses as to what is going on?

Thanks!

Peter
 
Are you importing directly or using the "Log and Capture" feature?

Try copying your footage to another drive and use that drive to import again.
 
I am importing using Log and Capture.

Tried copying to another drive and importing from there, but no luck.

I brought the cards to a different computer with 6.0.6 and they imported fine, so it must be something wrong with my machine.

Peter
 
Stupid question, but are you sure you have enough space on your designated capture drive? And, when you say "hang", what exactly do you mean?
 
Yes, I have about 1.6TB's free. By "hang" I mean spinning beachball and when I do force quit, finder tells me that Final Cut is not responding.
 
Yes, meant to write "log and transfer."

I'm going to attempt a transfer directly from my Varicam and see if that helps. Right now I'm using the Panasonic 5-slot P2 card reader.

Peter
 
I've had a problem similar to this earlier this week--my computer sees the cards as "NO NAME" drives on the desktop, but L&T doesn't see the cards at all. Got it to start transferring once, then FCP crashed.

You can also use the tool at the top (Icon is shaped like a cog, directly under the Log and Transfer text when L&T is open), click the dropdown menu from the tool, and choose, 'Add Custom Path', then navigate to the folder that contains the CONTENTS and LAST CLIP. Hopefully your footage will populate the L&T log.
 
Thanks Brad. The L&T sees the cards OK, and will transfer smaller clips, it just hangs on the operation once the clips are longer than a couple minutes.

Peter
 
Peter,
How are your destination drives formatted? Checking a P2 card the media is broken up into 3.9 gig chunks from my HPX-500 so longer clips have to be knitted together in the log and transfer. Some drive formats don't like this. Of course if you where successful doing this to the same array with the other computer than I probably haven't helped.
If you figured it out pleas tell us
 
Daniel Epstein said:
Peter,
How are your destination drives formatted? Checking a P2 card the media is broken up into 3.9 gig chunks from my HPX-500 so longer clips have to be knitted together in the log and transfer. Some drive formats don't like this. Of course if you where successful doing this to the same array with the other computer than I probably haven't helped.
If you figured it out pleas tell us
Click to expand...

Hi Daniel,

They're formatted as Mac OS extended.

What's really strange is I just shot some new footage onto a different card and was able to import it no problem, so perhaps something is wrong with these two cards? But I was able to import the footage from them using a different computer, so that doesn't hold true, either. Very strange.

Peter
 
So my question is what is different about these things? the computer which worked vs the one which didn't, The cards version? Camera is the same? There must be some differences which you can isolate? Was the footage all the same format? HD 1080 etc?. Does the footage from the drive work with the other computer or did you retransfer? You may be surprised by the answer if you can figure it out. Good luck
 
I think I found the problem...

I just recently added another drive -- a 5th G-Raid -- and all the drives are daisy-chained together. At the end of the daisy chain is the P2 card reader (6th in line). Realizing this might be an issue, I tried connecting the P2 card reader directly to my computer via USB, and the transfer completed without a problem. So, I'm guessing there was some sort of issue with daisy-chaining so many FW devices together, though I think the original FW spec is supposed to allow for a very large number of daisy chains.

So that seems to have solved it. Though it is strange that I was able to transfer a different card successfully the other day using the daisy-chained configuration.

Peter
 
Hey Peter,
Glad you seemed to have found a solution. The reason may be difficult to pinpoint but it could be a a random or cyclical conflict with the firewire bus getting busy which the software controlling the card reader getting confused somehow. Just speculation on my part. Using the USB port gives the data a different entrance into the system which might be handled better by the computer.
 
You must log in or register to reply here.
Back
Top