warning: do not open your media files in another program

[John Pale]

Thanks for that too. I think the share method more than the freeze method works for me, as I needed to take it into Photoshop.

I think I missed it in the help file because my brain was thinking “export” when I should have been thinking “share”.

[Robbert-jan Van der does]

yes, you’d definitely want to use share then.
One thing I wondered that might be of help.
Do you have Time Machine activated on your Mac? There might be the possibility to restore the file from there??

robbert-jan

[Ts O’grady]

Thanks Robbert!

[John Pale]

I did think of Time Machine, and did try it for kicks, but the problem is the media file, not the project file. I don’t backup my media with Time Machine. I did try using a “fresh” copy of the media file from the camera backup, but that doesn’t work either. FCPX is looking for whatever metadata it added to the media file when I first imported.

Bottom line… There is no re linking. If anything happens to your media file’s metadata, you have re edit from scratch. Be careful.

[David Burch]

One thing you might try for relinking is the “Modify Event References” button on the inspector when in the project library. I’m not sure if it will relink files with modified meta data, but I know it worked for me when I moved a project from one computer to another. I have a company logo that I use on nearly all my projects that generally resides on the internal drive in whatever computer I’m using, and as such have multiple copies on a couple of different computers (all the same filename). When I transferred my project which had its event on an external drive to a different computer, it naturally didn’t have a link to my logo files on the other computer. An exclamation mark showed up on the project, which when clicked took me to the inspector. I clicked on “Modify Event References”, and it showed me that it had found the missing files on my second computer drive. I clicked OK and it relinked them just fine.

[Robbert-jan Van der does]

This is useful information. At the moment I only have aliases in my events folder because I chose to uncheck copying of mediafiles to my events. Tomorrow I will check what will happen if I open the original file (the one where the alias is pointing to). If this raises no problems it might be the safest way to leave this always unchecked.

robbert-jan

[Tony Silanskas]

[Robbert-Jan van der Does] “Tomorrow I will check what will happen if I open the original file (the one where the alias is pointing to). If this raises no problems it might be the safest way to leave this always unchecked.”

I have all my media referenced like you Robbert but have the same media offline problems mentioned in the thread. Seems to happen every time with After Effects and only some of the time when I open up a clip in FCP 7. I did notice that when the clip goes offline, in the Project Properties (or even Clip Properties) when you “Show File Status” it says “1 Modified File” now. Doesn’t seem like a useful message in this version but maybe eventually it will give you a dialog about how a certain clip was modified, what changed and do you want to keep it.

tony

http://www.HungryCliff.com

[Chris Conlee]

[Craig Seeman] “Programmers deal with hard realities we editors don’t. Your expectations doesn’t mean they can meet their deadlines . . . no matter how badly you “expect” something. Programmers face all sorts of logistics when it comes to prioritization.”

Wow, while this is undoubtedly true, editors deal with hard realities that programmers don’t. It goes both ways. And if Apple wants to call this a professional application, a hard reality they need to face is that they need to have their programmers talk to some real editors. I get that you want to defend this application, and I don’t really care one way or the other because i’m largely an Avid editor, but don’t be blind to legitimate criticisms. If they’re honest and constructive, it will eventually improve your preferred tool. If everybody continues to make excuses for Apple, some of these deficiencies will never get fixed.

Chris

[Craig Seeman]

You brought up “expectations.” It’s a 1.0 app. Of course they will add features. For whatever reason they had to get this out the door in its current state. That’s usually not the programer’s decision. Management tells them what to do. Management didn’t want to wait regardless of what “expectation” the end user has. Granted that’s not a good thing but the point is it’s a managerial decision, not a programmer decision. If the clock was winding down, they had to lock the feature set, test, get it out the door.

[Alban Egger]

uhm…there is a command “SHARE -> Save Current frame…”
that saves your still out of the timeline….