-
Any way to just share a project without original media (FCP X10.2.2)?
I have a drive with all of the media and so does the producer. I did y editing, but just want to send the project only. I could send an XML I realize, however I did color correction and adjustments using the built-in color board. The FCP X XML doesn’t support that so the producer won’t see that work so XML is out of the question.
Unfortunately when you try to copy the project to a new library it copies the original media too; even with optimized or proxy files unchecked as an option to copy those types of media.
It’s amazing it’s this difficult to simply send a project. There is one solution I found at this link (https://larryjordan.com/articles/fcp-x-10-1-collaboration/) which essentially suggests sending the backup file which is pretty good idea.
I had just wondered if there was a native way I hadn’t come across, read about, or heard about yet.
Essentially all that would be needed is an extra option for the copy to new library feature that says “do not include original media”.
Tangier
-
27 Replies
-
From the Larry Jordan article you linked, doesn’t this do what you what to do? The description is going in the other direction, but it’s the same process.
“Import all media so that it is copied into a single library, then duplicate that library onto a second hard disk and give it to the producer. Because the media is stored inside the library, you don’t need to worry about cloning drives or matching file path names, the library handles all of that.
The producer opens the library inside their copy of Final Cut Pro X, creates a new project and edits a rough cut. When she is done with the rough cut, the producer selects the project and chooses File > Copy Project to new Library to create a new Transfer Library.
This creates a new library containing the project, with links to all the existing media. The producer sends that library back to the editor, who opens it, then drags the project into the existing library. At which point, the Transfer Library can be deleted.”
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
I and the producer do have copies of the same library. The problem Oliver is that there is no way that I can currently see that FCP X can just send only the project, even inside a library as is required, without at least copying the original media. When you create that transfer library File > Copy Project to new Library to create a new Transfer Library, even with the two options of bringing over proxy and/or optimized media, FCP X will still copy the original media into the new transfer library and it says it’s going to do that. I don’t want the media. The producer already has it. It’s making a large transfer library with files I don’t want and makes it even more difficult/time consuming to send to someone.
Sure I could let it copy all of the original media into the transfer library, then delete all of the media (either using FCP X or at the finder level inside the library package.
This is why someone on that link (I’ll paste it below) had to explain a workaround using the backup file. It seems this is the best solution so far. It’s sad to have to go through all of this just to send the project. A previous version of FCP X before the library model had the option of just duplicating the project only without media. I could not use unmanaged libraries as well, but I’d have to delete render files and such to keep the library small before sending it to someone else a transfer library.
One cool thing I use to make sure libraries are ion sync is I use Decimus Synk. It goes inside the library package and compares everything and makes sure they’re in sync. However I only do that when I have both drives near me or I and the other person are on the same network. It’s a fantastic part of my workflow.
Here’s where I could be drastically wrong, but I don’t think so just yet. If I copy the project to a new transfer library, having every option unchecked and FCP X still saying it’ll copy the original media into the library, then perhaps the size of the library that’s showing up in the Finder is not real. Rather it’s counting symlink as media and calculating the size of the original media though it’s not actually there – hypothetically. However when I go into transfer library package, that’s not the case. The media is in fact there.
Here’s the method I found on Larry Jordan’s site from Chris:
“I seem to have found a workable solution to allow for transferring of events and projects between editors with managed libraries – exchange the backup file!A hack, but it works. For example, both my assistant and I have the same managed library of a shoot. At this stage no editing has been done so no projects. She edits, making a few projects, events, whatever. When she is finished she lets me know and gives me the latest backup file. I open up that file – double click in the finder. Although this opens, usually it says that the original media data can’t be found so it opens as a new library with all the files highlighted in red as unconnected clips/media. All I have do then is drag the projects that my assistant made to the library I have with the media in. Everything is automatically connected. Perfect!
And to make things even easier, we are storing ours backups on dropbox so all my assistant has to do is make sure that it has backed up recently by checking the time code on the backup file name and then I just drag that backup file to, for e.g., the movie folder of my mac and then double click from there.
Seems to be a solution for sharing projects between editors both using a managed library in 10.1 anyway.”
Tangier
-
[Tangier Clarke] “When you create that transfer library File > Copy Project to new Library to create a new Transfer Library, even with the two options of bringing over proxy and/or optimized media, FCP X will still copy the original media into the new transfer library and it says it’s going to do that”
I just tried it and it doesn’t copy any media if the two options are left unchecked. The only thing in the Original Media folder within the new package of the copy is a sim-link to the media. In my example all media is external to the original Library file to start with. I normally never put actual original media into the Library file.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
I missed putting in my above reply that I meant if you have both options unchecked. I left the word “unchecked” out.
Your scenario is exactly what is discussed on the Larry Jordan link I posted. My libraries are managed. Yours are not. I mentioned that as well near the bottom of my last reply – which I realize also should have been edited (typing too fast to get my thoughts down).
I said, “I could not use unmanaged libraries as well, but I’d have to delete render files and such to keep the library small before sending it to someone else a transfer library”
It should have been : I could use unmanaged libraries as well, but I’d have to delete render files and such to keep the library small before sending it to someone else a transfer library.
Tangier
-
I will run another test again, but I’ve done it several times already. Folks (on that linked thread) pointed out that there is a difference in the way the copy project behaves depending on whether the library is managed or unmanaged.
Tangier
-
[Tangier Clarke] “the way the copy project behaves depending on whether the library is managed or unmanaged”
When you have a managed Library and make a copy on the same drive, the internal Original Media files appear to be actual full-res media in both. But that’s not the case, because the OS keeps the media from being doubled, even though it looks like it is. The test for this is to check the capacity of your hard drive. It doesn’t change by the amount of extra media if you copy the managed Library.
But, when you then copy that Library off to an external drive, it copies the full media into that copy. This way you don’t have media go offline. It’s a “feature” between FCPX and OS X. When it comes to shared operations, I just think managed Libraries are a really dangerous way to work.
Some links:
https://www.provideocoalition.com/the-magic-of-hard-links
https://www.fcpworks.com/fcpx-hard-links-can-save-hard-drives/– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Thanks Oliver. I’ll look at those and give it another try. I’ve been used to working with managed libraries, but am open to not doing so. Pre FCP X my media was always separate from my project file. That’s not to say that there aren’t benefits to a managed library, but definitely worth exploring.
In the meantime, using the backup file has worked like a charm.
If I didn’t have to worry about sending a project with color correction done, I could just use XML. Problem solved.
Tangier
-
[Tangier Clarke] ” I’ve been used to working with managed libraries, but am open to not doing so. Pre FCP X my media was always separate from my project file”
Ever since you could place the Library anywhere and set up preferences to have media folders outside of the Library, you can operate like you used to in FCP “legacy”. I usually create a production folder for that job and place everything pertaining to the production in organized subfolders, outside of the FCPX Library file.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
I understand your comment about the dangers of using managed media in libraries in a shared project. I wonder whether that applies to a one person project, typical of what I do. It is very convenient (lazy?) to let FCPX manage the media by storing it in the libraries. I do keep original media elsewhere as a backup. To keep the media outside of the library would require some discipline and a rigorous file structure, which I haven’t developed.
Thoughts?
-
[Claude Lyneis] “It is very convenient (lazy?) to let FCPX manage the media by storing it in the libraries”
It’s not necessarily wrong and it’s an idea that Apple adopted from Avid. The reason that it’s good is solid media relinking. I just prefer to have better and direct control of the media I work with.
For example, given the choice, I don’t work directly with DSLR H264 files. I try to process them before I bring the files into an NLE. Just an example. But ultimately it depends on how organized you are. FCPX is trying to protect the unorganized editor from his or herself.
I wrote a bit about that here:
https://digitalfilms.wordpress.com/2015/08/07/final-cut-pro-x-organizing-tips/– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com
Reply to this Discussion! Login or Sign Up