How do we feel about replacing (overwriting) media files stored inside an FCPX library?

If i create an animation in Motion and render it out for import into FCPX and then I have to make a change to it I will tend to re-render and re-import.

However I have been toying with the idea of instead overwriting the already imported file which works well in that everything is automatically updated in X provided the file name is the same. Is this considered to be a safe practise or would people warn against it?

I can imagine that it may cause trouble if there are differences in the specs of the replaced file versus the original (for example if i rendered with an audio track originally and then without, or perhaps rendered ProRes 4444 when the original files was ProRes 422)

Thoughts?

Don't do it inside the Library. Make a folder to go with the Library that has your Motion project files and export from each project. Import into FCPX from that location, but Leave In Place. Then just overwrite it, after backing up the original.

Thanks Ben, that's what my instinct tells me and it's the advice I would give to others... However I do prefer to keep my media within the Library package so if there was wondering if my instincts have any actual basis or not. Is there anything known that can go wrong with replacing media files stored within the library as opposed to outside it?

Same danger for both, FCPX isn't always good at relinking or recognizing media even if the slightest little detail is changed.

But then, it takes so many steps to get into a Library bundle, etc, I'd just set that Library to store the media in an external folder. Make life more simple, easier. One folder, rather than digging into a Package and then two or three more folders deep...

I do the type of Motion dance you're describing often, and I put Library into a folder with the name of my production. Then I have a folder for Motion project and output files. When I import any of those, I "Leave In Place". I do a lot of composing, and have a folder with my Logic project and output files, also. Plus a folder for any Pixelmator or other external graphic work I do. All specifically so I can simply replace one with a new export, and I'm done.

But then, it takes so many steps to get into a Library bundle, etc, I'd just set that Library to store the media in an external folder. Make life more simple, easier. One folder, rather than digging into a Package and then two or three more folders deep...

You can avoid all that trouble by using the "reveal in finder" shortcut: Shift-Command-R

When I have created a new version of the Motion graphic I hit export in Motion and it takes me to export dialog box. I then return to FCPX, select the clip I am trying to replace and then use Shift-Command-R to reveal the location of the clip in it's folder within the package. I can drag that folder from the Finder into the Motion dialog box, click on the clip I am replacing and over-write. Even if i kept media outside the Library package I would use the same technique to easily locate the external folder as it's so convenient.

I have to admit that realising I can drop folders into save dialogs throughout OS X is something I figured out WAAAAY too late and which is something i now use daily.

Same danger for both, FCPX isn't always good at relinking or recognizing media even if the slightest little detail is changed.

If it's the same danger for both i guess I would prefer to keep things in a package (personal preference). But FCPX's inability to relink similar (as opposed to identical) files is something I'd love to see improved with at least the option of a "Force Relink" made available.

Thanks again, Ben.

First export in Motion, I set the folder location. To update the file, Motion goes to the last location automatically. But yes, that OS X trick is super handy.