Re: New blog post from Philip Hodgetts. Worth the read.

Jeremy - "PPro, at least with CS5.5, makes some sort of cache files that you have zero control over, and sometimes don't really help (they seem to be audio related). And if you want to make proxy files, how do you do it? You'd have to do it through third party apps. FCPXs workflow in this regard has a leg up, it also wholly depends on your source footage as well. Not all workflows need proxy creation."

I wouldn't exactly call proxy creation a "leg up". While it's true, CS5.5 DOES create cache files, they are very small pointers that don't have to be archived with the project. The problem most folks over look in this with the FCPX implementation is the fact that is DOUBLES YOUR VIDEO DATA. Yes, it is just a re-wrap of the footage and it is quick, but now you have twice the physical data on your system. At this point you have a few choices; 1. Keep all of that data, both raw footage and re-wraps and archive it. That's going to become cumbersome really quickly if you have more than one person in your shop. 2. Get rid of your raw data and store ONLY the re-wraps. Several problems here such as meta-data from the RAW files not completely being transferred, sharing re-wraps across platforms (anyone know if sending these to PC's is feasible? Historically hasn't been) and what if you need to send the data back to the camera for some reason? (lining up shots for direct matching is one example).

The point is, native does NOT mean re-wrapping raw data. FCPX loses to CS5.5 hugely on this one. Don't see how you can really say otherwise.

Marvin Holdman
Production Manager
Tourist Network
8317 Front Beach Rd, Suite 23
Panama City Beach, Fl
phone 850-234-2773 ext. 128
cell 850-585-9667
skype username - vidmarv