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

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...

I am not sure whether it's a FAT32 problem or not but the only instance I have personally seen of the corruption was when I used a friends Macpro to copy from my portable bus powered drive, (that I had successfully transferred P2 files to via my G4 PB), to his G-Drive.
No where did the mac say the files were corrupt, they just showed up in the import P2 window as a mess of pixels. So I then connected his G-drive up to my G4 PB along with the bus powered drive and did the copy again and it worked fine. So to me that indicates a problem at the OS finder level, as it was just copying files from one drive to another. No P2 cards or drivers involved at all.
 
Absolutely fascinating. It'd be wonderful news if this was a generic OS bug rather than a P2-specific bug, because that would *really* light the flame under them to get it fixed!

Please file a bug report with Apple explaining exactly what you did. I wonder if it's FAT32-related after all.
 
I have been saying for a good while now, it's the OS, not FCP. That the files are not actually corrupt, just being reported as such by the OS.

I'm collecting the stories all of you post here about this. I'm actually looking at every one and trying to form my ideas about this based on what's happening to everyone.

Macs have never had any problems with FAT32. Being UNIX based now, FAT32 is a non-issue for OS X. I'd be incredibly shocked if OS X had a FAT32 problem. I have used FAT32 drives for a variety of purposes in the past with Macs, never a problem.

From all the stories I've been collecting, from what I know from my previous career as an IT Engineer, and all my experience with Macs for the last lord knows how many years (since the 8Mhz Mac Plus was cutting edge), it all points to OSX having a problems with P2. I bet you anything it's in that stupid driver you have to install. From what I understand, that driver is an Apple product, as two Panny reps have told me that it'll be a cold day in hell when Panny ever writes a single line of Mac code.

That said, Panny also acknowledges that the majority of HVX200 owners are FCP users, too. So why isn't Panny here telling us something? You'd think they'd want to protect the integrity of their product in the field. Or maybe the HVX is just peanuts to Panny and they just don't care about HVX users? Where are you, Panny? You're not without involvement here! Any Panny reps want to weigh in on this issue? Hello?!

FILL OUT THAT FEEDBACK FOR EACH AND EVERY TIME YOU HAVE A P2 PROBLEM!
http://www.apple.com/feedback/finalcutpro.html
 
Barry_Green said:
Absolutely fascinating. It'd be wonderful news if this was a generic OS bug rather than a P2-specific bug, because that would *really* light the flame under them to get it fixed!

Please file a bug report with Apple explaining exactly what you did. I wonder if it's FAT32-related after all.
Click to expand...

The long post, laying out all the steps I did, that I posted in the thread you started about this, was copied and pasted on the apple feedback page.
 
You must log in or register to reply here.
Back
Top