Multi-editor multi-location FCPX workflow — Felipe Baez

How many times have you faced a problem? I guess most people have some sort of issue they need to fix on a daily basis. What do we do? Some of us prefer to ask other people, others prefer to google it first to see if that question has been asked before and if someone has already answered. No matter which way you do, one thing is a fact, if no one has figured out something yet, someone will.I work in a multi-editor multi-location environment, across 5 different cities in 4 countries. With multiple editors in each locations, our team produces something between 5 to 12 hours of live broadcast content every day, all corporate, mostly internal but some external as well. We have to edit some of those broadcasts into shorter segments to be shared inside the internal “youtube”, be used by the numerous marketing teams or to be used in a later broadcast as a roll-in.Every day my team of video editors receives at least several new project requests. These can vary from simple edits as the ones mentioned on the previous paragraph to much more complex, full production type of projects, where we’ll script, storyboard, shoot and edit. We are basically a production house. It’s common for an editor to be working on 5 to 8 projects at any given time, with customers all around the world and almost never sitting in the same room.It’s common that we would have a request coming in for an European customer by the middle of the day in Europe and to be delivered the next day. That’s when we’ll leverage the collaborative workflow, to have an editor starting the work in Europe, handing over to the Editors in the US and then handing over again to the European based Editors for final delivery, or any permutation of this example.In order to accomplish this without glitches you need: * Editors that understand and commit to the workflow * Shared Storage in all locations * A very good connection in between each colocation (to sync media)If you don’t have editors scattered across the world like I do, then you can have just a local workflow setup. On the next paragraphs I’ll share how I name my folders and how they work. Each project that we work on has a numeric ID assigned by the request system we use. This ID is has 5 digits and you will see it being repeated over and over.Disclaimer: Originally I developed a workflow based on an episode of MacBreak Studio where Sam Mestman and Mike Matzdorff share a very interesting way editors can get things from other editors without anyone having to stop their work or being asked. I then applied that workflow to what made sense according to my daily needs and made it compatible within multiple locations. In the past few days I decided to create a new workflow on my own, without having my specific team in mind, something simpler and faster that could be easily implemented. This is the one you’ll read about below, not the original one I wrote. I hope this can help you in some way or another.All editors in all locations have access to a network RAID (It’s connected through a Mac serving the storage over NFS on the network, but the best thing would be to have a Lumashare network storage) and this share has the same name in all locations, Video Editing. I’ll call our Editor John, Jane, Rick and Felipe. All macs have their internal 1Tb SSD drive partitioned into 1 250Gb main partition for the system and applications and a 750Gb secondary partition (all with the same name) with a folder called FCP Cache in the secondary partition (for caching).Inside the Video Editing share the editors will find the following folders:Location 11_Ingest    – 00001    – 000022_Projects    – 00001 – Project Name 1    – 00001 – Project Name 23_Archive    – 00001 – Project Name 1    – 00002 – Project Name 2    – 00003 – Project Name 3    – 00004 – Project Name 4Location 21_Ingest    – 00003    – 000042_Projects    – 00001 – Project Name 3    – 00001 – Project Name 43_Archive    – 00001 – Project Name 1    – 00002 – Project Name 2    – 00003 – Project Name 3    – 00004 – Project Name 4The Ingest folderInside the Ingest folder the editor will create a folder with the numeric ID of the project he/she has been assigned to. All the media assets necessary for this project will be “dumped” into this folder. Depending on how the editor likes to work, they can organise the assets inside it as they will, and then import everything as keywords on FCPX.The Archive FolderContains everything from a project, Libraries, Media, exports. Folders are created automatically (to be explained later). The sync profile that copies from the Project’s folder to here is a “A+>B” (Backup mode, doesn’t track deletions)There’s a second sync tasks (AB) that copies everything inside the folder from one location to another, but doesn’t track deletions.Projects folderThe editor will create a folder for the project that has the numeric ID and the name of the project. Inside the folder they will name the Library the same way, appended by their name (Examp

Source: Multi-editor multi-location FCPX workflow — Felipe Baez

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s