-
P2 Log Pro and corruption?
I wonder if you P2 guru’s can help me. I have a team in deep patagonia shooting a documentary on HVX200. I’m the editor, and they’ve run into a problem… unfortunately email is scant and calling on their satellite phone isn’t viable for long troubleshooting conversations. I want to see if anyone knows about this error with what scant info I’ve got!
Apparently they’ve been using P2LogPro to view clips on a daily basis. And sometimes they’re importing footage in Final Cut (to see how clips cut together??) All of a sudden any new FW drive of P2 media won’t import into FCP – it says something like “media corrupted.”
If they go back to older drives FCP can import the P2.
P2LogPro can read the media that FCP says is corrupt. And P2LogPro’s XML transfer function lets FCP import and read the media.
So end of day the Media seems fine. For some reason all the new drives of P2 media they’re shooting won’t Log and Transfer. They’re making duplicate clones of everything, so I’m not worried about failed drives much… But the Producer on set is sweating bullets – they’ve lost media to drive failures before.
Any clues?
I think they have FCP 6.0.2, MacBook Pro. That’s as much as I can figure.
-
4 Replies
-
I’d start by telling them to burn DVD’s of the MXF files…everything in the folder.. need the text file too.
Make sure that the drives they are using are formatted for Mac too.
Jerry
Apple Certified Trainer
Author: “Jerry Hofmann on Final Cut Pro 4” Click here
Dual 2 gig G5, AJA Kona SD, AJA Kona 2, Huge Systems Array UL3D
-
Open the log and transfer preferences and tell them to turn off the ‘remove duplicate frames’ option.
Jeremy
-
thanks guys. I’ll pass it along!
-
I think you might be onto something Jeremy. P2LogPro doesn’t see 24pN correctly – it’s reporting the media as 59.94. And when you us P2Log to export and XML to Final Cut, you’re getting 59.94 media in Final Cut. So it might be blasting out the duplicate frame flags.
Reply to this Discussion! Login or Sign Up