|
crowd sourcing the experts |
|||||||
| |
|||||||
 |
|||||||
(Page 2 of 2 pages for this article < 1 2) Filed under: Editing •Post Production •Software •Tips • Final Cut Pro’s achilles heel or how I hate the reconnection danceFrom the Editblog archives: October 08
One way to lend a hand to FCP’s media management is with a new application from Digital Heaven called Loader that specifically address part of the problem. Loader allows the editor to drag media into the Loader interface and then Loader will copy (and in certain instances convert) the media to a designated media folder for that particular project, be it graphics, audio, etc. At first you might think that this workflow defeats the purpose of FCP being Quicktime based since you don’t want to have to make a copy of every piece of media you bring into FCP, that’s what Avid has to do after all, but this step that Loader takes is a crucial step to making FCP be much more organized in its media management. It puts part of the responsibility of good media management on the software and not the editor. While this may be a bad thing in some people’s minds, an app like Loader can help take even the experienced editor’s mind off the media management task if only for a minute. It’s a must have application if you use FCP, IMHO. But while it gets that media to a more centralized location and can make the reconnection dance a bit less time consuming Final Cut Pro still needs some type of database-based solution to always track its media. Project to project. Version to version. Editor to editor. Ben at Buttonpusher.tv has posted his own tips and techniques for avoiding the reconnection dance. They are great ideas if you can plan to name the media drives with the same names and paths as those you are sharing the drives with. It may not be possible with permanent, networked drives at a facility but with a little pre-planning his advice is well worth the effort in the time it could save. At its most simple implementation, a type of FCP project-based database could make the reconnection dance a thing of the past. But at its most advanced maybe it could be smart enough to make the attribute mismatches that often occur when you move clips from one drive to another a thing of the past as well. It could allow for more accurate media manager tasks and remove the stigma of the “media mangler.” And how about if it was smart enough to track all aspects of the timeline, specifically renders in the timeline so you could disable and enable clips and tracks without losing renders. This type of advanced media management would open the eyes of a whole generation of FCP editors who don’t know the joys of rock-solid media management. It’s sad that 6 versions into Final Cut Pro we don’t have something so useful. This new version of FCP, whatever it may be and whenever it may come needs to be a real doozy! UPDATE: Things aren’t much better today with FCP version 7Here we are today with version 7 of Final Cut Pro. There was some touted “Improved render management” in FCP 7 but nothing in the way of improved media management in general. If you’ve ever had to move media via the Finder you might have been faced with a File Attribute Mismatch error: This has plagued FCP for years. Sometimes it might be the Media Start and End that is an issue, sometimes it might be a Reel name. But it makes no sense when you are working with cloned media that, as an editor, you know for a fact is the exact same media that is on a different drive and you still get this error. It becomes even more disconcerting when you click Continue, connect the media and then get this message:
That pretty much says that something in your edit might have changed. It’s usually fine and nothing will have adjusted unless you have used Merged clips, then all hell can break loose. They can cause problems. But it’s just incomprehensible that 7 versions and a decade into this product that we call Final Cut Pro that these error messages would even still exist. It’s possible to avoid these errors if you do your moving of a project from within FCP using the Media Manager as that process will reconnect the media internally in a new FCP project. But that’s not always possible, especially if you don’t have control over how the media is moved; say if you are sent a drive to complete and edit. If you are using an exact duplicate of the media then these errors should not happen ... but they often do. This is the world that we live in.
(Page 2 of 2 pages for this article < 1 2) 
You must be registered to comment. This is an effort to reduce spam. Please REGISTER HERE.
|
|
||||||
|
|
||||||
The Editing of “Courageous” Part OneThe off-line edit of a RED feature film
Last October, I had the rare opportunity to edit a feature film called “Courageous,” which is in theaters now. “Courageous” was the number one new movie the weekend it opened (September… |
Final Cut Pro X Multicam Editing webinar now available on-demandPlus a little screencast in this blog post on a topic we didn’t get to cover.
I had great fun last week presenting the Final Cut Pro X multicam editing webinar… |
Editing and Effects Together in One Editor Part 2The NLE revolution isn’t over… Enter Autodesk Smoke for Mac
Editing & Effects All-In-One |
Editing and Effects Together in One Editor Part 1The NLE revolution isn’t over… Enter Autodesk Smoke for Mac.
Post NAB 2012 Adobe has released the CS6 suite, Avid is pushing Symphony, and you may think that the editing revolution is over… but you would be wrong. Autodesk announced Smoke 2013 for… |
To be considered for listing, contact pr (at) provideocoalition (dot) com
Copyright © 2012, HD Expo, LLC a division of Diversified Business Communications. DBA Createasphere
All rights reserved. HD EXPO, High Def EXPO, Createasphere, E-Tech, Entertainment Technology Exposition, 3D Production Workshop, VariCamp, P2 Camp, ColorCamp 101, and Lighting, Filters & Gels for HD are all trademarks of HD Expo, LLC.