Off and on I’ve tried tackling the metadata approach for a large-documentary project I’m assigned at work, as of today the raw footage consist of 2,864 movie files spread across the last 201 days. All of these files are stored on a network drive via gigabit ethernet.
This is a follow up post, mainly for Eric, about the iMovie + server workflow that I’ve been trouble shooting for months now at work. Long story short, iMovie doesn’t like working with alias files after all, so that set up ended up breaking on me fairly quickly once I got into tagging / key-wording media.
But!, on account of the recent updates to FCP X, I started testing out how it handled working with media organized on a server over gigabit. It turns out, if you go into the preferences of FCP X, that you can by default have it import footage without moving the original files or recomposing proxy files, meaning it simply creates aliases for you!, and it doesn’t mind at all if your original files are stored on a server. It can analyze for rolling shutter / face detection / stabilization, also while syncing audio and video files, fixing audio issues, keywording and sorting footage into folders / smart folders, etc!
In other words, FCP X solves every single issue I’ve run into over months and months of testing different file organizing and management apps that don’t hold up over a server. Amazing. Not to mention FCP X can do all of these things in the background, whereas other apps, like iMovie, are unusable until after they finish analyzing imported media (which, in this project’s case, can take upwards of 3 days). I do admit, FCP X is a different kind of editing approach than I’m used to, but for any features it lacks in comparison to FCP 7, it has so far made up with ease of media management and background processing.