Any way to just share a project without original media (FCP X10.2.2)?

[Tangier Clarke]

Actually, that’s what we tend to do. Once we finish a project and complete the archive we will delete unused render files, proxy files, etc.

If need be we go into the library package, delete all media that we originally shot so all that’s left is the library with music, stills, graphics, perhaps. The point is not to duplicate files and increase space because we already have the camera originals backed up to cloned drives before any editor gets their hands on it.

I won’t say this is ideal but it does mean we don’t have to buy archive drives as much because we’re not doubling our space by keeping the card copies and the copies of the card FCP X brings over. One could wonder why we don’t just keep the library original media in the library and call it a day; delete the camera card backups since FCP X copied it in. I considered that at one point, but the problem is that assumes that all of the media was imported. Not a risk I am willing to take.

After we’ve made all of our deliverables such as masters, stems, audio archives, etc. All that’s left is a streamlined and lean FCP X library that we can connect back to the camera originals and FCP X will transcode as needed. And we export XMLs of the final project and the entire library.

Next stop in this process is trying out KeyFlow Pro by years end. We’ve really wanted access to all of the keywords and metadata from FCP X from several projects; akin to what Final Cut Server did. Once we archive a project all of that searchable valuable information is locked with it; something NeoFinder can’t help us with.

Tangier

[Bret Williams]

Just did a quick test and color board info comes across just fine. I’ve never seen anything that doesn’t come across FCPXML going between FCP X and FCP X. The aforementioned concept certainly works, but just export the project as an xml and bring it back in on the client’s end.

[Tangier Clarke]

Perhaps I need to do a reinstall. The reason this all got started was because I was sending XMLs to someone else who had a duplicate of the library and none of the color using the built in color board was being maintained.

Sorry for spreading misinformation everyone. On this search I did read that the XML did not support color. Now reading your post I went to the FCP X XML format description doc and it says that in XML version 1.3 it does support color.

We’re on FCP X 10.2.2. One computer using El Capitan, the other Yosemite.
Back to the drawing board. Interesting though that nobody caught that throughout this thread or perhaps I just read over that too.

Tangier

[Bret Williams]

Transfer libraries are probably your safest bet. But if the XML works for what you’re doing I’d try that. Can always send a low res QT with it to make sure things match up.

[Tangier Clarke]

Yeah, you’re probably right. Though if the color was maintained in the XML i sent I probably would have never started this thread.

Tangier

[Bret Williams]

I wonder what setting you used? For example for my test earlier, I used XML 1.5 and chose Basic. I know that certain things don’t come across to Resolve if you use the wrong setting. Perhaps you don’t get the color settings if you use extended or something. Opposite to common sense, I’ve heard the best to use is the basic or general settings.

[Tangier Clarke]

I do know that I tend to leave it on extended instead of basic. I’ll have to visit specifically what those settings are for and how to better use them.

Tangier