Apple and it's P2 super bugs!

bbalser

bbalser

Veteran
http://www.apple.com/feedback/finalcutpro.html

I'm on the war path (literally, I'm Cherokee, and I'm pissed) with my beloved Apple now. The bugs in Macs trying to handle P2 data is just getting ridiculous.

PLEASE if you use FCP go to the above URL and let Apple know how bad it is and how very upset we are, ASAP! It is the most sure fire way to get Apple to move their ass!

IMHO, from trying to trouble shoot this with others, and now having the problem myself, I'm convinced it's the P2 Driver for the Mac.

Bear in mind a huge chunk of the HVX200 market are FCP users, and the overwhelming majority of FS-100 market are FCP users. Make a noise!!!!!!
 
Same as everyone else:
All clips play fine in the P2 import window. When added to the import queue, randomly they get the red stop sign icon with an exclimation point in it. Unknown Error, can't import.

Tried same batch with P2 Log, and NONE of the clips will import, and the error message it gives names a clip very different from the one FCP has problems with.

After trying to troubleshoot this with many users for some time now, and now that I finally have the problem, IMHO it's Apple's P2 driver. It makes no difference if you're ingeting from a P2 card in a card slot, from the camera, from a P2 Store, or from an FS-100, the problem is the same.

Search these forums, there's lots of these reports. Barry even has a thread he started dedicated to trying to figure this out.

OH, and that's not even getting into how in camera, often only one P2 card shows up in the Finder when both have data on them. This is also a problem when using a P2 Store. I can only conclude that it's in Apple's P2 driver.
 
I haven't seen this, yet. On neither P2 nor Firestore.
(Praying that this will stay the case!)

But more often than not, I'm copying the P2 files to the mac prior to import into FCP.


Is there a workflow connection?
Could it have to do with how OSX (or rather FCPs Import) reads FAT 32?

I do not suggest that Apple is not at fault, just curious.

Gunleik
 
basically the main problem is that apple are making us convert the files into quicktime movies in order to put them in the timeline.
If you really want to solve all these issues then you have to ask apple to forget the quicktime proprietry lockdown with QT and let us bring in the P2 data without conversion. This would also mean all meta-data etc. would be in there too.

So - yes - complain to apple - but if we decide exactly what we want and ask for that repeatedly - maybe we will get it. Personally I have already sent them the above complaint. IF you feel the same: click > Final Cut Pro > Provide Feedback - at the top of the menu.
 
Just for clarification, FCP has always been a QT based NLE. Re-wrapping (it's not really a "converstion") for QT shouldn't be a big deal, shouldn't cause any problems. If it is causing problems, Apple has it in their power to fix it.

When you say, "...all meta-data etc." you are aware that the QT re-wrap does keep all the metadata at this time, nothing is lost.

I don't care that it needs QT files, that acutally lends to stability. Native MXF would be fine. Let me clarify, natively reading Panasonic's version of MXF would be fine. But the QT re-wrap doesn't bother me.

The first post has the URL for the feedback page already so you don't have to launch FCP to get there.
 
I had this problem, and it was solved by deselecting the REMOVE DUPLICATE FRAMES option. But since this happened with P2 log as well, that can't be you issue.

But hopefully Apple resolves this in 6.0...
 
i ran into this problem today for the first time ever. 1 clip gave me the 'error unknown' red stop sign exclamation point. any solutions? im running fcp 6.0.4
 
I have had that problem before when I had assigned a really long name to the clip... took me forever to figure out that was the problem. Maybe that is your trouble too?
 
I've been having this problem (red exclamation mark, unable to ingest footage into FCP), and I've tried everything I've seen suggested (short file names, trashing prefs, etc.) Anyone have any new info on this problem? I'm on osx 10.6.2 (didn't upgrade, came on my macbook pro), and FCP 6.0.1.
 
You are using log and transfer? And you've unchecked remove duplicate frames?

Are you ingesting from the p2 card itself or from a drive?

Have you tried importing a portion of the clip rather than the entire clip? That is, mark an In and an Out point and then import...about a minute or so of the clip?

I've had the exclamation mark when I've ingested from a drive formatted as FAT32 and the clips are bigger than the 4 gig limit. My solution was to ingest the clip in multiple parts.

Bob
 
I use to use Raylight for Mac and now Calibrated. Drag my MXF files right into the timeline. Never had any problems and never had to wait on Log and Transfer or whatever they're calling it now.

But it seems that before I got these I never have had a problem working with P2 on my G4 Mac or my current Intel Mac.
 
everybodyclap said:
I've been having this problem (red exclamation mark, unable to ingest footage into FCP), and I've tried everything I've seen suggested (short file names, trashing prefs, etc.) Anyone have any new info on this problem? I'm on osx 10.6.2 (didn't upgrade, came on my macbook pro), and FCP 6.0.1.
Click to expand...
Any reason why you've haven't upgrade to 6.0.6?

Do you have FX Factory installed? What version?

How are you mounting the cards? Did it ever work?
 
You must log in or register to reply here.
Back
Top