-
Moving projects between libraries loses years of clip renaming
Hello Hive Mind,
Any ideas on how to move projects between libraries without losing all the source clip renaming for the shots contained within the project? When we move a project between libraries FCPX converts the associated source clips back to their original camera card name. This is a nightmare when matching, interacting with others in our pipeline, integrating edited sections from one project to another, on and on. All of our source clips are renamed for a variety of reasons so this process is undoing years of hard work.
Methods used to move projects between libraries all with the same result:
– Select project within an event choose “copy to library”
– Move project to it’s own event then select event “copy to library”
– Drag and drop project from one library to another
(often doesn’t move project it bounces back visually doesn’t transfer)Many thanks in advance!
MA
Harvest the compromises…
-
6 Replies
-
-
This app looks perfect for all the duplicate Multicams we have due to collaboration, very nice! It may be a bit spicy for our current challenge but I think I can visualize a workflow:
– copy project to desired library names get goofy
– use XML to bring project in again now that desired media is in library use merge app to fixing names
– delete first copy of project and associated goofy named source clipsSeems worth a shot, thinking we’ll give it a try especially if this software can clean up our duplicate multicam issue after the fact. It’s mind boggling why it doesn’t just work but there’s lots of cool things that FCPX does so there’s that ????
Thank you for your thoughtful share Jeremy!
Harvest the compromises…
-
[Michael Angelo] “It may be a bit spicy for our current challenge but I think I can visualize a workflow:”
You would have to test this workflow, but I think the best thing would be to export an XML from your current Library Event with the “good” names.
Then export an Event from the “bad” library (no reason to import any footage first).
Merge those two Events with the emphasis on the “good” metadata. Import that XML in to the “bad” Library and Replace when it asks you to. At that point, if the metadata is secure, you can relink the media to another data set (if that’s the goal).
I have just started getting to MergeX. It is very cool and powerful. The newest version also handles Project and Roles and can “pass down” updated information from the Event to Projects, which is awesome.
Jeremy
-
[Jeremy Garchow] “I have just started getting to MergeX. It is very cool and powerful. The newest version also handles Project and Roles and can “pass down” updated information from the Event to Projects, which is awesome.
“How well does this work? If I have everything in my events set as a dialogue role, do my edit, then go back to the event and properly set Music, SFX, Broll Audio, Dialogue, VO, Graphics, Logos, Titles, etc…., I can “update” my project and it will push all the new roles down? Because I’ve been making that feature request to Apple for years now!
Does it push subroles too?
—————-
Michael Hancock
Editor -
[Michael Hancock] “How well does this work? If I have everything in my events set as a dialogue role, do my edit, then go back to the event and properly set Music, SFX, Broll Audio, Dialogue, VO, Graphics, Logos, Titles, etc…., I can “update” my project and it will push all the new roles down? Because I’ve been making that feature request to Apple for years now!”
I haven’t done extensive testing with Projects, but what I have tested has worked.
I use it mostly for getting Events from other editors, and updating their Events with my Events or vice versa.
Here’s an article from Ronny C: https://www.fcp.co/final-cut-pro/news/2098-free-update-for-merge-x-make-changes-to-clips-in-the-browser-and-see-these-changes-reflect-on-the-timeline
-
Wow this does seem pretty amazing for a variety of reasons.
Thanks for the tip and the workflow suggestions Jeremy!
MA
Harvest the compromises…
Reply to this Discussion! Login or Sign Up