07 March 2010

offline/proxy workflow for p2 materials


After trolling the internet for a solution similar to Avid’s offline workflow for Final Cut Pro, I found myself stumped, and at best left with the message “Dude, why?  Just cut natively.”
From keeping your master safely away from the cutting room, to needing cramming those extra shots on a portable drive for a mobile edit, there are a number of reasons one might want to cut at “offline quality” whilst cutting P2 in Final Cut Pro.
One of my largest gripes with FCP is the bullish slow down encountered when cutting with large amounts of footage in your browser (read: unscripted documentary).  The larger the files, the more system resources FCP eats up attempting to manage it all.  This means when you access bins or load clips in the source viewer you’re going to be waiting.  By creating proxy footage you can alleviate some of the stress on your NLE system and speed up your editing.
Due to the possibly confusing nature of the term ‘offline’ (as it refers to low-resolution media and media that has gone missing from it’s pointer), I will refer to the new media that we’re creating as “proxy” footage.
PLEASE NOTE: I will be using my own person version of media management when it comes to this demo.  Here’s a brief explanation of my personal system:
To manage Media I create a master folder for each project, this becomes the ‘project folder.’  This folder acts as an all-encompassing living space for all the elements that are related to your cutting project.
I tend to create six folders inside the project folder.  My project directory looks something like this:
PROJECT.NAME { 1.Cuts, 2.Materials, 3.Sound, 4.Working 5.Exports 6.Docs }
The cuts folder contains all the projects related to the edit.  The materials folder contains all the media that you add to your browser (I capture footage in a general capture bin and move the media using the finder).  Sound is where I keep audio files and mixes.  Exports contain exported QT’s and OMFs.  Docs is where I keep scripts, notes etc.  The working folder is a catch-all for incomplete files that are under construction (any files that are proxy I keep the materials folders, and just switch out media without changing names so that FCP automatically updates).
Assuming you have all your media in your “Materials” folders.  To begin, I create a new folder within the Materials folder called “Proxy.”  This will be the home of your new proxy media.
If you have already created a project to log your footage, you’ll want to keep all the logging meta-data  you have generated.  In order to maintain this information, you will need to use FCP’s Media Management tool to create an offline (read: proxy) project with the proper settings.
With nothing selected in your browser, select FILE > MEDIA MANAGER to bring up the Media Manager window.  Under the “MEDIA:” drop-down option and select “Create offline.”  This will grey out most options.  Now under “Set sequences to:” option scroll through the list and select “Apple ProRes 422 (Proxy) 960×720” with the frame rate that matches your project.  Make sure that “Base media file names on:” to “existing file names.”  And click ok.  It will ask you where you want to save your project (1.Cuts folder).  I normally append the word “proxy.”
Next, we’re going to load compressor.
First, create a new custom DESTINATION.  Set the PATH to your MATERIALS/PROXY folder and make sure that under “output filename template: simply says “Source Media Name.”  THIS IS VERY IMPORTANT.  If you change this, and append anything to the proxy file name you will be unable to relink back to your online media.
Next, under settings, create a new QUICKTIME MOVIE setting.  Under encoder settings / video and select “Apple ProRes 422 (Proxy) and set the Frame rate to “current.”  Under the geometry settings, change the frame size to “50% of source.”
Now apply the setting and the destination to all the files in the compressor window and select “submit.”
Go grab some food, coffee, etc.  Depending on how much footage you have this could be a while.  (Note, this process is best if done at the beginning of a project, think of how you’d import footage into avid at an offline resolution.  You can also, selectively convert footage if you’re in a situation where you only need to worry sections of your timeline.)
Now to reconnect / relink the clips to the proxy media.  In FCP select the bins and select FILE > RECONNECT and navigate to the PROXY folder inside MATERIALS and select the first clip.  Final Cut will now automatically reconnect the media files and you’re ready to edit!
When it comes time to prepare an online (full resolution version) of your final edit.  Use the Media Manager only now under the “Set sequences to:” select the full resolution and create a new project entitled PROJECTNAME (online).  Using the RECONNECT tool, select the full resolution clip.
Happy cutting.

03 March 2010

OS X Server and Final Cut Server

Yes!  The old G5 is no longer sitting idle; the good ol' 'EditDroid' has now been renamed "Mother" and is slowly becoming the center for my 'Final Share System.'  After doing much research online, I've been interested in setting up an "Edit in Place" media sharing system with in my sublet workspace.  This would allow me to remotely  access projects and media as well as keep all my media on one central system.

Wish me luck... I'll do my best to blog through the process, unless that is, I accidentally destroy the internet in the process.  Which is likely.

16 October 2009

Editing On Set!

I'm blogging live from the set of a short film produced by Samsung / Fort Productions to promote their new line of wireless streaming BluRay players.  What am I doing here?  I'm camping out in the video village, laptop, P2 reader and stack of hard-drives to boot (no pun intended).

The film is a cohesive action-short that is being embedded into the latest line of promotional materials.  They're shooting "tapeless" Panasonic P2, VariCam 24p.  The P2 footage is coming in as the AVC-Intra codec and we're importing them into Final Cut Pro (Fort is strictly a FCP house) as Apple ProRez 4:2:2 (HQ). The footage recording to the cards is far smaller than the unwrapped MXF files, but thanks to the FW800 P2 card reader we're not being held up too much.

Camera assistant is swinging by, more footage.  Will continue to blog about the experience of dealing with this crazy Intra format!


14 October 2009

Updates Coming Soon

Hi everyone!

Keep on the look out, as a new Demo Reel and over-all website changes will be happening soon!  Very exciting stuff coming down the line!

04 October 2009

The Editor Updates :: After Effects

As you all know, we currently had very bad luck with installing Photoshop CS and CS2.  I'm currently waiting on my current employer to extend their licenses for their production suite so I can get some extra work for them (read: so I can open Photoshop without crashing my computer).

I have installed After Effects CS3 and had o.k. luck with it.  It operates in the same way that 6.0 did :: it works, just really unstable when preforming particular featuers (such as frame paint).  I'm going to see if I need to upgrade the current version of CS3, or if Adobe is just telling everyone to go to CS4.

I'll try to nail down some of these issues in more detail as AFX works comes rolling in. It is a little difficult to isolate the issues whilst just playing around.

That being said, I have yet to experience the system-wide crash caused by Photoshop.

01 October 2009

The Editor Upgrades :: Weekend on hold

Today is the big moving day. Will get to testing part three (After
Effects) tonight once I'm in the new space.

Wish me luck, I'm gonna need it!

---
Peter Haas
+ 01 646 468 6743
www.peterjhaas.com

29 September 2009

The Editor Updates :: Photoshop

Last night I struggled with my first major glitch in the upgrade.  My ancient copy of Adobe Photoshop CS refuses to run on Snow Leopard.  I take that back, it almost runs.  It will fool you well, launching as normal, even letting you create a new file and edit for a bit.  After enough usage of the font face tool you will find that your screen(s) will turn bright blue and all your current applications will close.  I assume this is the experience of Rossetta crashing.  Hurm... a Mac version of the Blue Screen of death?! No, your Finder will return shortly, and the system recovers itself nicely.  The down side is, more money will need to be invested into this upgrade.
Since photoshop is $700 application (the $299 upgrade I believe only applies to CS2 and above but this will require some more investigation), it might be worth the extra $400 to grab the production bundle (which includes the latest After Effects, Illustrator and Flash software... oh yeah and those other editors I'll never use... what was it call.. oh yeah Premiere).  I should eat my words though.  I've heard some fantastic things about Premiere CS4, including the script/transcript sync.
Back to Photoshop.  I also took a stab at using my friend's copy of CS2, which resulted in the same failure as CS.  Does anyone have any experience with CS3?  I've heard many conflicting reports and would be interested in people's first hand experience.
There are some freeware alternatives to Photoshop which I used last night to accomplish some basic titling tasks.  I found that several of the programs were fantastic, but my 11 years of photoshop use has rendered my ability to migrate difficult and a bit frustrating.