Let's Get the OS X P2 Bug Fixed!!!!!

The problem could also be potentially fixed with a firmware update from Panasonic to allow the camera to read OS X Extended formatted P2 cards in addition to the current FAT32(originally developed by MicroSoft for MS-DOS). So rather than fuel the flames- just something to consider if you want this problem fixed. There may be more than one way to fix it...
 
So does this mean there is a known data corruption problem with FAT32 in OSX? If there is, then how come Barry's workflow has never taken a hit? Besides, if there is a problem with FAT32, fixing it would affect a lot more users than just making a few HVX shooters happy.

Otherwise, if there is no FAT32 problem, how would Noah's alternative address the data corruption?

George
 
From my own experience and all the stories I've collected from users, it's a P2 driver bug in OS X, simple as that. OS X has no other problems with FAT32 that I can find.

WORK AROUND
Ok, FCP reports clips being corrupted that actually aren't. Here's a work around. Play the footage in your HVX and capture it live the old fashioned way, via the Log and Capture window. Even with an FS-100, you just set for non-controlable device, and plug the Firewire cable into the DV port of the FS-100. Hit play on the FS, and it'll feed the video into FCP. You'll just have to capture everything at once, the FS won't break the playback up into clips easily.
 
Last edited:
I just stumbled upon this and find it a little disheartening as an HVX will be delivered to me tomorrow and all of my equipment is Mac based.

Earlier I read about an "Apple Approved" P2 method that involved using Disk Utility to create IMG files of the contents of the P2 card. Since this is a bug at the OS level I'm assuming that I still run the risk of data corruption with this method?
 
From what I understand about the disk image, there's some cyclic redundancy checking going on to make sure that it's a bit-for-bit copy. Once you have the disk image, you should be able to import your files flawlessly from then on, if I understand correctly.
 
I've tried the disk image method and still had FCP say some clips were corrupt, and P2 Log imported them fine.

That's one of the problems here, FCP is reporting files are corrupt, when in fact, they aren't.

I actually tried this not too long ago. You take some HVX footage that has some files FCP claims are corrupt. Try P2 Log, says it's corrupted data. These are the files that you've copied to your Mac hard drive (CONTENTS and LASTCLIP.TXT). Copy those from your Mac to a PC and they'll import fine.

I don't see that the Mac is actually damaging anything. It's just reading corrupted data when there really is none.

I'd love to have someone else try my above experment and see if it works for them as well as it worked for me.
 
I believe it is a FCP issue, because while I cannot import the P2 footage with FCP 5.1.2, I can with FCP 5.1.1, and I have them both on the same machine...so the OS and QT are the same versions. The only difference there is the version of FCP.
 
Shane Ross said:
I believe it is a FCP issue, because while I cannot import the P2 footage with FCP 5.1.2, I can with FCP 5.1.1, and I have them both on the same machine...so the OS and QT are the same versions. The only difference there is the version of FCP.
Click to expand...

That's just one of many stories I've collected on this issue. It does in fact happen to folks with 5.1.1, just not on YOUR machine. And it is intermentant, in no way consistant. It happens off and on. I ran 5.1.2 for a month before it began happening to me. And I do know users on 5.1.0 that have had the problem. It's quirkey.

I have also personally had P2 Log report corrupted files that FCP opens just fine!

What I'm trying to figure out now is, are these files REALLY corrupted, or is FCP just reporting them like that?
 
Try playing them elsewhere to see if they're corrupted. If they'll play in the camera, and they'll play in P2 Viewer, then they're not corrupted.
 
Barry_Green said:
Try playing them elsewhere to see if they're corrupted. If they'll play in the camera, and they'll play in P2 Viewer, then they're not corrupted.
Click to expand...

That's my point, I've not had the chance to take what FCP or P2 Log "claims" to be corrupted to any other device. And since it's not every clip on every card, for me, it's not like I have tons of bad files around to test.
 
Just got an advertisement in my email...

P2 Log Pro™ builds on the success of P2 Log™ adding new features for MXF video file repairs, searching native P2 media files and printing. The ability to create new P2 volumes from combined clips makes P2 Log Pro compatible with any P2 enabled editor such as Avid Technology, Inc.

With P2 Log Pro you leave the shoot with confidence the clips you want have been safely transferred to disk” says Dan Montgomery, president of Imagine Products. "The new MXF Repair Wizard is a great utility to help recover damaged P2 Volumes. It's something everyone shooting P2 format should have in their tool kit."

The Repair Wizard locates and copies errant MXF files one-by-one. The result is a new valid P2 Volume of the combined clips.
Click to expand...

If anyone upgrades to this, would be interested to know if perhaps Imagine has created a solution/workaround for this dropped frame/"corruption" hiccup that is happening.

cheers.
 
Just got my HVX this week - with an FS-100.
The second clip I imported off this brand new gear showed the corruption you guys are talking about (a split second "dropout" type of blockiness).

Not good.
Not good at all.

We moved away from tape to get rid of dropouts.
I'm sending this feedback form to Apple right now.

EDITED TO ADD:
Done and done.
Hopefully they listen soon.
(not holding my breath)
 
Last edited:
Barry_Green said:
If you successfully copy the footage off the card with no corruption, then you won't ever have a problem with that footage.
Click to expand...

Not so Barry, If you read my post in the thread you started about this, you will see that I ran into the problem while copying files from one hard drive to another. I had successfully offloaded to a portable bus powered drive with my G4 laptop and they played fine in the import P2 window, then when I copied the files to an external firewire drive on a friends MacPro tower they showed up as corrupt in the import P2 window in FCP.
 
Barry_Green said:
Do macs just have problems with FAT32 devices then?
Click to expand...

Not in my experience. It seems to be pretty isolated to P2. I've only had an HVX since Wednesday, but so far *knock on wood* I haven't seen this corruption offloading on a G4 Powerbook.
 
Macs have no problem with FAT32.

Also, let's keep in mind that often the clips reported as "corrupt" can be read by another application, or PC just fine.

Thus my current question, are Macs REPORTING corrupted files that, in fact, are NOT corrupted at all? That's my very strong suspicion!
 
BenB said:
Macs have no problem with FAT32.

Also, let's keep in mind that often the clips reported as "corrupt" can be read by another application, or PC just fine.

Thus my current question, are Macs REPORTING corrupted files that, in fact, are NOT corrupted at all? That's my very strong suspicion!
Click to expand...

That's my suspition... Maybe try import back to camera not from a Mac but from a decent PC, and see if the dropouts pass back to camera... From what I heard here and elsewere, i believe the glitch has something to do with HDD writting speed vs processor activity- can this cause a conflict while reading a file?
 
You must log in or register to reply here.
Back
Top