-
Export Several clips from FCP X Event Library?
Bear with me folks, as I think I’m missing an easy way to do this:
I have a client who would like the Full Res Quicktime versions of several clips on a hard drive. All of the clips are tagged in my event library with the same keyword. Unfortunately, you can’t just right click on that keyword and select export. I briefly went fishing in the “Original Media” folder, but with the naming conventions, and the number of other clips, it is proving near-impossible to fish them out.
Anyone have an idea how to export a group of videos from an event?
-
9 Replies
-
Create a new temporary event. Drag all the clips from your keyword collection to the new event. Then just open up the folder of the new event in Finder and only the clips in the new event (the clips your client wants) will be the only ones showing up in that new event folder. Hope that makes sense…
-
Perfect! Thank you!
-
The Event Library doesn’t directly “export.”
But its reasonably trivial to do what you want.
Just open a new Project in the project library.
Open it and you can drag and drop as few or as many of your selected clips as you like into the project. Since the Magnetic Timeline assembles them automatically, no editing is required unless you were sloppy with your Trimming in the EB. Then the Share Menu lets you export them as standalone files.
You specify that you want Quicktime files, but X isn’t really built on Quicktime any more. It’s built around AV Foundation and Core Video – and ProRes and H-264 are it’s “default” video formats – both of which are more modern and more efficient codecs, IMO.
Most client requesting “quicktime” files often just want something to play on their laptop – and the H264 or ProRes options will work fine. If someone actually does need a formal quicktime wrapper – then you’ll have to export from the Share Menu to Compressor and use the QT encoder there – but do a test first. In my experience nearly anyone who thinks they need a QT file will nearly always be able to use an H264 encode without a traditional QT wrapper just as easily.
Also, when you’re in the Share Menu, take a look at the direct email and direct posting options. I’m rapidly migrating my client review workflow to these rather than sending cut off files via FTP and/or Server services like YouSendIt – YMMV.
Hope that helps.
“Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor
-
Bill in your post you mention
When you’re in the Share Menu, take a look at the direct email and direct posting options. I’m rapidly migrating my client review workflow to these rather than sending cut off files via FTP and/or Server services like YouSendIt – YMMV.
Ok you really got my attention with this. How does this all work? I’m forever exporting and uploading to my YouTube account for clients to review, but of this is a easier option, please do tell :-)))
-
I also use these options often. Youtube or vimeo and the best is e-mail (for short projects).
It basically saves a step which you can use for other tasks.If you want to edit on, you´ll have to “Send to Compressor” though, because these export options need FCPX to work.
-
[Tony Sarafoski] “When you’re in the Share Menu, take a look at the direct email and direct posting options. I’m rapidly migrating my client review workflow to these rather than sending cut off files via FTP and/or Server services like YouSendIt – YMMV.
Ok you really got my attention with this. How does this all work? I’m forever exporting and uploading to my YouTube account for clients to review, but of this is a easier option, please do tell :-)))
“Under the Share Menu, you’ll find that YouTube and Vimeo are direct options. It just takes a few minute to store your account access codes here. The “built inside X” functions even let you append search keywords right in X. Then a click literally posts your X work directly to your main account at either service.
You still have to go directly to the service to manage portfolios, etc – but the basic upload happens directly from within X. Which means you can work on, revise, publish, and re-publish projects and revisions in a live and dynamic way – rather than getting everything “perfect” before exiting your NLE to upload your work.
Also understand that instead of baking and cutting off separate files in X to the desktop to manage your masters, just use X’s Share “Media Browser” function to store copies of your current edit in the Shariing folder that lives in the root folder where you have X keep your Project and Event files. This travels with your project and keeps a “live” copy of your current master no matter whether your root clips are on-line or offline.
This is the new orientation of X. Change thinking from “cutting off” a master file to “”publishing” a current master version, that can be easily amended by simply firing up you project inside X and tweaking it.
It’s a seemingly small difference, that has profound implications in a connected workflow.
For the past 20 years. a finished piece was something that was cut off and put on a shelf. Not so much anymore. Now, your “connected master” can live inside X, ready to be changed at will and re-published.
Finally, as alban noted, the Email option in the sharing menu is amazing for short projects you want someone to take a quick look at. It’s subject to email system limits on the size of attachments – so it’s only good for short work – but if it’s appropriate, it generates a complete email message directly from within X and attaches it to a highly compressed thumbnail size video (with some customization possible by the sender) all in a single “send” step.
Essentially, X shares like a sweet, friendly 3rd grader. Very naturally and without a lot of guile required.
“Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor
-
Bill there a few things you’ve mention I’m still a little hazy about.
Bill: YouTube and Vimeo are direct options
I’ve played around with this a few times now, however the thing I don’t like, is there’s no upload monitor when it begins uploading to YouTube or Vimeo.
The other was that it completely ties up FCPX not allowing me to do anything else.
Bill: Which means you can work on, revise, publish, and re-publish projects and revisions in a live and dynamic way – rather than getting everything “perfect” before exiting your NLE to upload your work.
Bill I’m a little confused with this part. When you upload to YouTube or Vimeo via FCPX, it’s unusable till this finishes?
Bill: Share “Media Browser” function to store copies of your current edit in the Shariing folder that lives in the root folder where you have X keep your Project and Event files. This travels with your project and keeps a “live” copy of your current master no matter whether your root clips are on-line or offline.
Interesting… I’ll have to play around with this
Bill: the Email option in the sharing menu is amazing for short projects you want someone to take a quick look at. It’s subject to email system limits on the size of attachments
Ah yes… thought so. I’m working on testimonials for a website and was thinking this would have come in really handy.
-
[Tony Sarafoski] “I’ve played around with this a few times now, however the thing I don’t like, is there’s no upload monitor when it begins uploading to YouTube or Vimeo.
The other was that it completely ties up FCPX not allowing me to do anything else.”
Agreed in both cases. The first, particularly can be a problem. But if it bothers you – you can always work the original way by Sharing out to the desktop and uploading the traditional way via the Vimeo or YouTube direct upload – so it’s an optional convenience, not a requirement. I also usually upload from my laptop – and go back to work on my desktop – so it’s not such a big deal for me to wait for the upload to complete.
[Tony Sarafoski] “Bill I’m a little confused with this part. When you upload to YouTube or Vimeo via FCPX, it’s unusable till this finishes?
“No, in X, when you publish, you’re concurrently refreshing the available version in your Project Library – so you have a persistent “display” of all your current projects easily accessible. Sharing them (to YouTube or elsewhere – exports that version directly, without leaving the timeline. If you want to export and get back to work, you can do the same thing you did in Legacy and make a standalone file to work with outside X, but it generally takes essentially the SAME amount of encoding time to just post out of X that it doest to export to the desktop, so X is simply saving you an unnecessary step.
[Tony Sarafoski] “Ah yes… thought so. I’m working on testimonials for a website and was thinking this would have come in really handy.”
Just create an empty project. Copy and paste any part of any other project to it – then share that via email. Then delete and replace that clip (not the project, no need for that – it’s just a temporary container in this use) with a new one, and do the same again. Repete as needed. Your original clips never actually leave their original project.
It’s the way you share “parts” of projects out of X rather than the “range export” that we had in legacy.
Working across and understanding Projects is a bit different than always working inside the “one at a time” timelines of Legacy – but it’s no less efficient in my experience.
Hope that helps.
“Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor
-
Interesting Bill, I’ll have a play around with that…
Reply to this Discussion! Login or Sign Up