fbpx
3 Post Moderation Rule for New Boarders (25 Jan 2021)

New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.

Failed Import / Relink Question

More
03 Jan 2013 14:32 #19604 by wilbah
Longtime FCP editor, getting serious with FCPX- and have run into a problem.

It appears I have been editing a multiclip sequence (oops- "project") with footage that was not properly imported. Which is to say, the files will NOT properly import. These are 4 files from a Canon 5DmkII, all above 3GB, one is above 4GB. When importing, a dialogue box opens and says there was an error importing, and the footage needs to be re-imported from the camera.

That being said- the footage still appeared in the viewer, and was mutli-cammed with other footage, and edited successfully. All of this is fine, until you go to export the project, and FCPX wont let you export a project that references camera master footage (all the footage needs to be properly imported).

In trying to re-import directly from the camera archive, I'm getting the same error issues.

So I now have a project with many hours of time in on edit, that I cant do anything with. I've tried the basic FCPX re-link unsuccessfully. I'm suppposing that FCPX is looking for an exact duplicate in order to relink- by exact i mean file name, and meta-data.. is this true?

Do I have any other options to explore before I have to re-edit all of tis footage? For instance, I've successfully made ProRes files of the "corrputed" clips, and they work fine..... is there any way to re-link the new Pro Res files to my original edit so I dont have to redo all of this work?

I've trashed the prefs- re-installed a clean version of FCPX. Never really run into this before. In looking earlier posts, I see similar issues cropping up lately- was there ever a solution?

OSX 10.8.2
FCPX 10.0.7

Chalking this one up to the "live and learn" file!!!

Thanks in advance for you advice and time!!

Best,

W

Please Log in to join the conversation.

More
07 Jan 2013 16:39 #19711 by RickUrb
Are you sure your referencing actual files, and not just the alias? You can confirm by right clicking on clip in event, and going to show in finder. An alias file will have a small arrow in the icon.

Please Log in to join the conversation.

More
10 Jan 2013 19:54 #19841 by jefforig
Wilbah,

Did you ever solve this? We are having the same exact problem on one of our events/projects as well. I tried re-importing into a new event to create a brand new event, but it won't let me do that. FCPX 10.0.7 on both OS 10.7.5 and 10.8. Also using external thunderbolt drives. Never had this issue before.

Thanks.

Please Log in to join the conversation.

More
15 Jan 2013 01:15 #19929 by wilbah
I wish I can say I did! I ended up transcoding everything in Compressor, and then reimporting and having to re-edit the footage.. I also asked around on many other forums, and more or less there wasn't a definitive answer.

For some reason, FCPX had difficulties with larger files (above 3gb) after several failed import attempts, and relink tries nothing worked. I never got to the point that these files would have become alias's as they were never properly imported. I thought that it might be an issue with my CF cards (read /write errors causing issues with meta data) because the video and audio played back fine off the card, as well as inside FCPx, I edited the footage, but when it came time to export I got an error because the footage wasn't properly imported! I trashed prefs, reinstalled FCPX, etc- no help. The footage actually imported fine and without event into FCP7.

Gotta say I was a little bummed- but I'm chalking it up to a "learning curve" with this software. I simply can't find a reason why FCPX would allow you to edit footage, but it won't allow you to export the edited footage if it wont import correctly. Tragic to look at and playback a sequence in perfect shape, but not be able to export it!!!

In large part I jumped on FCPX because it edits H.264 natively without transcoding-and creates proxy in the background- I'll never trust that feature again- it cost me a lot of time and work.

Please Log in to join the conversation.

More
15 Jan 2013 14:52 #19949 by jefforig
I did the same thing by transcoding. This is a bug in the 10.0.7 release.
I have not fully tested the following theory, but the two projects that we had problems on had mixed footage from a Canon 5dM2 and a Canon 7D. A similar project with a 7D and T2i seemed to work fine.

We will be editing a project that was shot with the 5dM3 and 7D. I will let you know what happens.

This is a bummer, because one of the main reasons we use FCPX is to edit footage quickly without having to transcode. Granted I know there are potential performance gains with transcoded footage, but sometimes edit deadlines are more important.

In Final Cut Pro, under the Final Cut Pro menu, there is a feedback form link. Can you send them information about your experience with the bug? I know they actually read that thing. I once sent them feedback on a sound issue I was having using multicam and they responded to help them replicate the issue.

Please Log in to join the conversation.

More
15 Jan 2013 15:02 #19950 by wilbah
Sorry to hear that this is a potential bug in 10.0.7

I'm really disappointed- my biggest reason for switching to FCPX was the native handling of h.264; and back ground transcoding.

I have, and will continue to use the feedback to FCP function- Lets be hopeful they can get at this quickly! Meanwhile- its back to the safe shores of FCP7 for me!

Please Log in to join the conversation.

More
15 Jan 2013 15:15 #19951 by jefforig
Agreed, but please note that native H.264 editing worked perfectly in previous versions. And I am one of the few that converted and really love FCPX now. I used to hate it, but I think it was the change that I hated more. I wrote a thorough blog post here: origmedia.com/2012/09/22/fcpx-is-the-fut...g-and-love-the-bomb/

Please Log in to join the conversation.