Help! footage corrupt from HVX $$$ to repair

Z

zimvsdib

New member
I had a small shoot last weekend. I have a 4 GB card and attempted to log and transfer on FCP 6 on an a 2GHZ apple laptop with 1GB ram.
The clip thumbs shows up and i began the log and transfer. Everything looked normal then I got an exclimation point symbol in the status colum in the que window on all the clips. Then the computer had a kernal panic and had me force a shut down. I tried to transfer again but the same thing happened. I figured it was something to do with the computer not having a 7200 rpm drive, so I just mounted the drive and copied the contents of the drive to the computer.
The next 2 P2 transfers i did the same way(mount and transfer contents).
When i got home I log and transfered the footage on my G5 tower, the files from the first transfer gave me the same error!
The other footage was perfect though.
Here are some screen grabs of the FCP window and the footage itself after i imported the .mxf files to FCP. There is green digital noise over the footage and the sound is wierd.

The footage from the first transfer is no longer on the 4GB P2 because i had to shoot more that day.
Is there a was to transfer it back onto the P2 card and repair it or any other solution?
$150 to your paypal if you can save my footage! I hope you tech-heads can give a noobie some help.
-Eric
ps. I thought about uploading the clips but wasn't sure how. It;s around 5GBs.




 
Try the demo of P2 Log or Raylight and see if you can get one of the clips to work ok.
I use Raylight all the time now to work around using Log and Transfer.
 
The Mac has screwed you. If you have the original footage you don't have a problem -- I'd bet a thousand dollars your original footage is absolutely perfect. But if you don't have the original MXFs, or if you've already deleted the original files, you have a huge problem.

NEVER put a P2 card in a Mac, or let a Mac near a P2 card, without it being write-protected. And if you want ultimate safety, don't use a Mac to offload cards at all. Yes, I said it.
 
Hey Barry, thanks for the reply.
I have the "contents" folder including the sub folders containing the MXFs from the P2 on my G5 MAC HD. The file sizes are accurate.

The media on the P2 has been erased though.

Am I screwed? Will taking that contents folder to a PC help?
 
I doubt it'll help -- it's the process of copying the footage off of the card and onto the Mac which can cause the glitching. If you copy it off a Windows system onto an external hard disk, and then plug that drive into the Mac, all is golden. But if you copy directly from the cards onto a Mac, that's where the issue can happen (and it is rare).

So the possibility exists that the MXF files you have on your hard disk are already corrupted. But to find out, try using the trial version of Raylight; it'll let you directly view those files and maybe they're still valid.
 
Okay, I am so distressed at seeing so many users getting screwed over by this issue, I've now posted an official Mac Offloading Policy.

And yes I'm mad, what happened to zimvsdib should never have happened. And yes it was the Mac that did it, and no I really don't give a flying hoot about all the hundreds of users who will want to post a useless comment that says "I use the mac and I've never had a problem." Yeah, well, there's lots of women with breasts who've never had breast cancer -- does that mean breast cancer doesn't exist? Just because there've been people who've played Russian Roulette and lived, does that make it safe? There's too many users who've reported a problem for anyone to tolerate someone saying "it works for me" -- such a response would be useless and in fact insulting to the users who have had their hard work and jobs ruined by some incompatibility in the Mac.

There's a problem and it needs to be dealt with.

Fortunately there is a free way to deal with it. It may mean you Mac users changing your workflow slightly, but if it helps you avoid the fate of the user in this thread, surely it's worth it.

The new thread with the recommended workflow is here:
http://www.dvxuser.com/V6/showthread.php?t=118672
 
I've never had a problem in nearly two years. I also write protect the cards

I'm wondering if the issue is user or operator related because either the OS is writing to the card or not

No idea why it writes to some but not others.

But as Barry points out, it takes a second to flip the switch to red.
 
If you use P2CMS to do the copying, you should be able to have 100% confidence. P2CMS will execute a verification step (assuming you click the appropriate button). I wouldn't have the slightest qualms of using a Mac to offload IF I followed two procedures: always write-protect the card, and use P2CMS to do the actual copying (with the "compare" checkbox selected).
 
Does this issue apply to P2 Store mounted volumes or just P2 cards?

Should we also be following this procedure for the P2 Store?
​
 
Show a little respect... 1)read every word Barry Green says, and 2)don't ever say you've never had a problem with Mac offloads when Barry so clearly explained how stupid that response is.

Granted I'm a noob, not a senior member, but why in the world would anybody respond right after 'The Authority' with such a disrespectful response. It's as if the senior member didn't even read what Barry just said. Noob or not, I understand that Barry doesn't just speak for fun. He's trying to help all of us.
 
Rambos said:
Does this issue apply to P2 Store mounted volumes or just P2 cards?​


Should we also be following this procedure for the P2 Store?​
Click to expand...
You don't have to write-protect the P2 Store, obviously, so that's not an issue. I don't know if the "glitch issue" ever happens from a P2 Store; I've always been of the impression that it's the actual process of copying off of the card (not the P2 Store's hard drive) where the issue occurs.
 
The FS-100 has had lots of issues, primarily in its early days, but we really don't see many complaints about it anymore (and remember, for every complaint you see there's probably 10 or even 100 satisfied users!) Seems like they really got it under control in version 3, and I doubt I've seen a complaint with version 4.

But yes, in version 1 it was quite possible to have glitching and corrpution, so if you're renting an FS-100, be sure to check what firmware version it is. And if it's your own FS-100, upgrade to version 4.
 
You must log in or register to reply here.
Back
Top