Another Side Benefit to Using Transfer Libraries for Project Sharing

We use Transfer Libraries as an primary means for projects and media sharing for remote editor situations, aka via web. I had started a thread previously on release day about using these in addition to other means, ( www.fcp.co/forum/4-final-cut-pro-x-fcpx/...t-know-where-to-look ) but I wanted to illustrate another possible side benefit for some users, to using Xfer libraries here.

While largely, I believe you should keep your media out of the library, you don't always have to. Sometimes you might want to put some clips in, as I will get to in a sec. In 10.1, we can now easily move our media, in-app, in and out of the library, events or even projects, at any time- by selecting custom external locations in the consolidation menu. This makes for some cool workflow adaptability if it meets your needs. (Recommend that your new ext location be on the same drive as your existing library.)

Anyhoot, here is a basic example of the workflow that we have confirmed through testing:

Let's say I am passing a project back to my assistant editor (who has the same core media for the project/event that I have) and I have added some files that he (or she, of course) doesn't have, i.e. new Voice Over files, Animations, etc. I can "package" those files (selectively consolidate) into my outgoing Xfer Library and then he or she can re-consolidate them out/externally to their respective Project's/Event's custom location upon receipt.

Another handy benefit of utilizing the idea of Xfer libraries- keeping the number of files being passed back and forth between editors as small (and simple) in number as possible.


Cheers,
Dusty

And allow me to add, since I was on the receiving end of this library, that it works beautifully and is extremely easy to do. I simply opened the XFER library, right click > Consolidate Media, select my respective area for my footage storage for this episode and then moved the project into my episode Event - all done in-app. I'm loving the new features of 10.1, especially now that audio presets can be copied over across Apple ID's

Great information, guys. And thank you for sharing your experiences!

- Ronny

How big are these transfer libraries that you're moving? Even very small libraries for me with no original media are half a GB or more. Even If I strip out render files from each event internal using the app function the library are still a few hundred MBs. Are those the kind of numbers that you're moving using Dropbox? Thanks very much.

Thx Ronny!

Tom Wolsky wrote: How big are these transfer libraries that you're moving? Even very small libraries for me with no original media are half a GB or more. Even If I strip out render files from each event internal using the app function the library are still a few hundred MBs. Are those the kind of numbers that you're moving using Dropbox? Thanks very much.

Hi Tom,

Xfer libraries that are truly metadata only should be very low in MB- or med to high in KB, as (see below for actual size examples) it's all about building them to be a transfer library, as a temporary shuttle, as the more in number and complicated the total events/projects inside, the larger the end file size, same as with any collection of events, projects would have been etc. previously in FCPX.

In a metatdata only Xfer library, the largest file you'd have should often be the actual project file (the second event file found inside the library package).

The Xfer library that I sent to Nate, via FTP, was 115MB (73MB zipped), but it had the actual raw VO media (.aiff file) consolidated inside. (roughly 20 minutes of recording via clip in the event and project with edited vo + audio effects w custom presets)

However, if I consolidate that media externally- to mimic sharing a metadata only Xfer library, then, the file size becomes 3.2 MB (695 KB zipped)- small enough for email.

Playing devil's advocate/scientist on myself, the real question is, why does an edit this small have a core project file that is 2.5 MB inside the library... ^^ Poor engineers, we always want more!

Merry Christmas,
Dusty

Thanks very much Dustin. Just to clarify, in the Xfer Library you're sending an event that only has project files (except in the instance where you included VO). My libraries with events that have symlinks to media are quite large because of render files.

Thanks Tom! I appreciate your interest. I see you post on here a lot and it's cool to speak with you.

Yes, we are sharing Xfer Libraries right now in two ways- with Selectively Consolidated Internal Media (VO Example) and also with "Sym Links Only". (Episodic Television Event + Projects/edits per that Event) We keep the "Sym Links Only" Xfer Libraries as close to "Database-only info", as possible. So, basically, no Render Files, Analysis Files, Optimized Media, Proxy, etc. are included for that work flow process.

We choose not to share Render Files and these other temporary app files most of the time (although users could certainly could choose too) for our work flow/the given scenarios, as those files are simply too large for fast web transfers and can often when planned correctly, be easily regenerated. (But our originals are preserved) Render Files can also be conveniently deleted inside of FCPX.1 for your Xfer Library, if the files are present in the Xfer Library for any reason- whether on purpose or perhaps because Background Rendering was left on, etc.. Other in-app files like Optimized Media/Proxy can just be chosen to be left out when prompted, as the Xfer Library is being custom built.

Again, all of this, we felt, is a benefit of using Xfer libraries, *because our original/master library's Render Files, Optimized Media, Optical Flow Analysis Files, etc. (which are very important as we should always be looking to avoid instances of doing things twice) are kept safe and intact, in this case.

Cheers,
Dustin

What is a Xfer library a Application?

A transfer library is an FCP library used to pass data like projects and metadata between collaborating users.

Tom Wolsky wrote: A transfer library is an FCP library used to pass data like projects and metadata between collaborating users.

I am guessing you giving the definition of Xfer library??? Where does this term come from why not just call it Transfer or Shared Library?

Most people call it a transfer library. Xfer is just a contraction. You can call it a shared library if you like, though I wouldn't. For me a shared library is a common library used by multiple editors. A transfer library is usually only used one time to move information between editors and then discarded. At least that's the way I use the term.

I guess all depends how you see the definition, sharing or transferring over a pipeline.
The Xfer caught of guard didn't see where Transfer fits into Xfer.