[Bill Davis]If your output target is movie screens and network TV, you’ll want to stay with something like the model FCP-7 represents. Full features for long form work, and support for huge corporate or production house integrated workflows.
My output is, by and large, the web, and yet I find myself needing to do what the other Gary was talking about, and even in more simplified productions, I have to make cuts that, so far, seem very complicated from the FCPX workflow point of view.
Nor does your database driven CMS really excite me. With very few exceptions, all of my projects are self-contained and I have no reason to access media from each other (nor does that really work for me considering the space that would be needed in one large clump to make that actually work). The only way this is at all interesting, would be to have a significant B-roll library, but again, you run into problems with space to keep all of that in one location that is accessible by FCPX for all time.
Tomorrows production WILL NOT be the same as yesterdays. Sorry, but as with all massive industrial change – we adapt or die.
I don’t agree. Only the tools have changed, the fundamental aspects of production have remained the same since their inception, with a few tweaks here and there. I really don’t see FCPX being as “revolutionary” as people claim it is. It’s a Vegas timeline with a lot of automation. That’s it.