Problem transferring HVX files that have been "spanned" over 2 P2 cards. Help!

M

Melody

New member
Problem transferring HVX files that have been "spanned" over 2 P2 cards. Help!

I have been shooting on the HVX200 for a few months and recently came across a problem. I logged and transferred two full P2 cards, and one long clip is spanned across both cards. For some reason, the footage isn't transferring correctly at all. The file looks fine when I play it in the log and transfer window (and in the camera), but once I import it into final cut it is completely gray, except for the very beginning of the clip which shows the first few frames broken up into squares, then it goes gray.
Does anyone know what the problem might be? Is there another way to import this one clip without doing the standard "import" function? It seems that something is going wrong during the transfer, although all the other clips from both cards imported with no probelm.
I tried it several times, with the same results each time. The clip is about 10 min. long.
Any suggestions would be greatly appreciated.
Thanks!
 
My suggestion is a frequent one, but rarely taken except by those who really want to improve their productivity: ditch the FCP log & transfer window entirely, and get raylight instead. It'll fix all FCP import problems, it'll cut down your disk space requirements in half, and it even avoids the bug that FCP 6.0.2 introduced where any Quicktimes you'd imported prior to upgrading don't now work!

I wouldn't use the Mac/FCP without Raylight.
 
INteresting point Barry and along the lines of a problem I have been suffering today. Worked as a steadicam operator yesterday on feature being shot in the UK. Dowloaded the footage to a laptop, then networked it accross to the Apple once I got home. I made sure I copied across the Lastclip.txt file and made a seperate folder for each P2 card.

Using the log and transfer import system in FCP had me almost crapping myself as the footage failed to import. Just nothing happened. I thought the files might have been corrupt and was thinking that I must have made some type of findemental error and ballsed it up. I was wondering what the hell I was going to tell the director!

but a few monutes later it decided to work! God knows what the problem was. but it seems very unreliable and gave me grey hairs. Must be a bug in the system somehwere I am sure.

I will check out Raylight.
 
Thanks for the tip Barry. I will look into Raylight, I would love something that helps eliminate gliches in the transfer. But until then, do you have any ideas and/or short term solutions that will help me get this one clip into FCP. I am under a tight deadline and I just need to get this clip in and edited, then I can focus on a longer term solution. It is extremely frustrating, expecially when I can't figure out why it is happening!
 
Hopefully some Mac users will chime in. I think the FCP importer is the root cause behind probably 90% of all user frustration with P2 and I think the sooner you get away from it the better off you'll be.
 
success!

success!

I bought Raylight and was finally able to open the problem file. Thanks for the tip! I will be using Raylight from now on.
But now that I'm here, can you answer a basic question for me? What is the primary difference between XML and MXV, and does it matter which format the clips are in during the edit.
thanks, again.
 
I don't know is mine is a related problem or not but I'd appreciate any suggestions. I was on a shoot yesterday and had to do an emergency transfer from one of my P2 cards to a portable firewire in order to free up space. I didn't realize it at the time but the FW drive was nearly full. I thought the card was fully transferred but today when I tried to transfer from the FW into my main drives using the FCP Log and Transfer I found that FCP crashes whenever I start to load those files in. I have over 14gb in the corrupt file so at least most of my footage should be there but I can't access it. I'd buy Raylight and use that instead but it's my understanding that it doesn't work with an Intel Xeon mac. Any suggestions?

thanks,
JD
 
You must log in or register to reply here.
Back
Top