Re: After a year has perception of FCPX changed?

[Bill Davis] "My concern is that the higher up the food chain you go in the realm of design and editing, the less you want to make the entire process accessible to the whole team. One way to do that is to build complex workflows with specialists in-house - and wall off people via access restrictions. The other method is to let the designers "reach in" and apply their expertise directly into the project creation stream.

I'd disagree and say that the higher up the food chain you go the more you need software to be able to talk to each other. Be it all the collaborating editors using the same NLE or using software that understands industry standards like EDLs, OMFs, etc., so that two different pieces of software can at least talk in a common tongue.


And if you opt for the latter, then each contributor using their own tools and methods is perfectly reasonably - rather than making them come into a fixed "seat" and work on only the tools the company provides.

A homogenous workflow is inherently redundant which is a must in a collaborative edit because Murphy's Law dictates at least one person (or one machine) will become unavailable at the worst possible time. If you started editing a long from project and figured you'd need some help for a couple weeks to meet your deadline would you seriously not put any constraints on what the other editor used for his NLE?



I guess I just see more work available in the distributed creation model these days rather than the "under one roof facility" - but I know many others work inside that more traditional model."

Like in my example I gave before you don't have to be under one roof in order to collaborate and gain advantages by using the same software. For example, take two editors working on different scenes of the same TV show but in different States. They are both have all the media and they both have the same NLE so when they want to compare edit,s and stitch it all together at the end, all they have to do is send a project file. Boom, easy as pie.