Strange FCP Import Scenario

[nsoltz]

It is well documented and discussed here and elsewhere that there are some real problems with P2 import and OS X, and specific problems that many of us experience with FCP 5.1.2

Today I imported some footage shot 24p to FS-100 (with the 3.0 firmware-- shot as 24p in camera with the FS-100 doing the pulldown so that these become 23.98 to disk).

FCP imported all of the files but the import window displayed the red exclamation point, which means a problem with the import or usually a failure to import.

All of the files imported to the designated bin in my project. The one spanned clip was recognized and imported. Yet FCP reported an error.

Anyone seen this one?

By the way, the FS-100 3.0 upgrade is terrific. Close to 4 hours of 24p footage. I was a beta tester and couldn't say anything about it until now, but I hope all FS-100 users agree it was worth the wait to get a stable revision.

Ned Soltz

[Shane Ross]

How can I become a beta tester? I have access the camera...I am a forum leader in many forums. I was one of the FIRST people to deal with this footage.

ANYWAY...enough tooting my horn. I really am impressed that they got the native formats to work. Do you have access to FCP 5.1.1 to try to import? If not, would you like me to test import one partition of footage? I can send a drive...

[nsoltz]

Yes... I have saved FCP 5.1.1. on an external drive and use it for problematic imports.

Meanwhile, as I said, the footage imports and is all there without so much as a dropped frame. It is just in the case FCP reported that it did not import.

Can't give away trade secrets in a public forum, but I'll tell you at NAB how to get all the good gigs.

Ned

[BenB]

My current theory, based on all the stories I've collected about this issue, is that FCP is reporting corrupt P2 clips that are no, in fact, corrupt. I also see that P2 Log 1.0.3 will do the same thing. Going between the two, I get 99% of my clips in. Taking the camera to a PC, and copying to a Windows unit, 100% of everything has no problems.

EVERY single time you have a problem with a Mac and P2, go here and let Apple know!
http://www.apple.com/feedback/finalcutpro.html

There is a thread about this in the FCP section, I recommend checking it out. From what I see, it's an OS X issue, not an FCP issue. Ned, I know you swear by 5.1.1, but I've personally had the same problems on 5.0-5.1.2, all versions. Count your blessings you're 5.1.1 isn't doing it, as mine did.

[gaston]

So basically, there are no problems with any of the footage. The only problems are with the mac and FCP. Though it might be a hassle, as long as you have the files copied to a hard drive you'll eventually be able to use them. Am I understanding correctly?

[nsoltz]

As long as you have saved your MXF files, you are fine. Eventually we will sort out this OS X/FCP thing and you will be able to use your files. What is so strange, as I have said, is the inability to read the clips or as in the last case, the clips come in fine but FCP says they are corrupt.

Ned