[Jeff Kirkland]

You’re right of course, didn’t think of that…

Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland

[Jeff Kirkland]

Just a thought if I get what you’re trying to achieve, but have you tried adding one of the angles to a timeline and creating a compound clip with no gaps, then using that compound clip as the master angle and letting the other cam’s clips sync to that?

Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland

[Jeff Kirkland]

Does the project open if you move it back to your startup disk?

FCPX is database driven and moving a project to another drive is something that should be done within the application.

I recently had a hard drive crash and was forced to move a project using the Finder and I can say it took a very long time for FCPX to open the project. From memory it was three or four hours of waiting while (I guess) it searched the hard drive and rebuilt its database.

If you’ve had it open for any length of time, it might be too late but you could try using the Finder and restoring the project backup file that FCPX keeps in the project folder.

Other than that, I’d take the event offline, and try getting the project to open properly. Lots of missing media warnings is better than an empty timeline. Then I’d bring the event back, and try relinking the event in the project info panel.

My only concern would be that you said you re-imported the media… Hopefully that was from within FCPX? Again, being very metadata and database driven if you make changes to anything outside of the application, you run the risk of it never reconnecting.

I’m no sure if any of that is especially helpful but let me know how you go and maybe I can think of something else.

Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland

[Jeff Kirkland]

Relinking in FCPX isn’t the best and interrupting an import can be a step on the path to weirdness so my #1 general tip would be don’t mess with it while you’re importing or moving files. Bring up the task monitor, step away from the computer, grab a coffee and let it do its thing.

On to trying to fix things…

When you need to reimport, what is the status of the file? Is it missing, or just not recognised by FCPX any more? Is there some other app touching the clips? Is the hard drive actually working properly?

If relinking isn’t working for you then once you have gotten all the clips back online manually, I would try duplicating the project and event to another drive (remembering the step away from the machine rule), then check it there. Having FCPX create a duplicate should resolve any database oddities that might be causing the issue.

That’s about all I can think of without knowing more about how the import was done and what FCPX is saying about the missing files, etc.

Cheers
Jeff K

Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland

[Jeff Kirkland]

You can add a post export action that runs the Automator script once the export is complete. I used to use this to run a script that sent a push alert to my iPhone when a long render was done.

Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland

[Jeff Kirkland]

Premiere used to have a bug that meant it ignored the alpha channel in ProRes 4444 footage. It was supposedly fixed but maybe not?

Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland

[Jeff Kirkland]

I didn’t know you could use an EX3 clip without rewrapping it so I’ve learnt something new – although it sounds like I might never actually want to do that. As to the analysis, I’ve not thought about it but for most things FCPX has a tendency to analyse the entire underlying clip in the event rather than just the part you’re using on the timeline so, yes it is quite possible that its analysing the entire three hours if that’s how long the clip actually is.

You may be able to work around it by making the section you want to slow down a compound clip and seeing how that goes.

Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland

[Jeff Kirkland]

Command-shift-7 opens the angle viewer, not the angle editor. Go back to the actual angle editor where you set up your multicam and colour correct there. (right-click the multicam clip and choose ‘open in angle editor’).

Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland

[Jeff Kirkland]

Hmmm… Can’t think of any alternatives. I guess sooner or later everyone hits that point where it’s update or do it the hard way.

Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland

[Jeff Kirkland]

I didn’t think of just exporting a range but I’d assumed they might not have wanted to export each clip one at a time.

Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland