-
Prognostications on FCPX compared to OSX and iOS from Alex4D
Final Cut Pro X features: catching up and superseding
https://alex4d.wordpress.com/2012/06/25/fcpx-past-and-future/Interesting read on some interesting thinking from an interesting plugin creator (amongst other things).
-
69 Replies
-
[Craig Seeman] “Final Cut Pro X features: catching up and superseding
https://alex4d.wordpress.com/2012/06/25/fcpx-past-and-future/Interesting read on some interesting thinking from an interesting plugin creator (amongst other things).
“Interesting! (Seriously.)
-
hmm… interesting reading!
“You never want to get to get a call from the editing room”
Art Adams -
Alex4d has some great pontifications. I always enjoy reading them, especially when they get kinda “far fetched” as that’s when it gets interesting.
His idea of multiple skimmers (with a keyboard modifier) is pretty awesome.
At some point, these dreams need to become a bit of a reality, at least somewhat.
I am beginning to trick myself that I am not an editing professional because I actually like a lot of FCPX. For shame.
I also want flying cars, or at least the more plausible intermediary of me not driving a car, but rather being driven in it while Holographic Alfred Hitchcock navigates the route and narrates “The World Without Us”. I will then get to enjoy the irony. Or perhaps I’ll ride on top of it Teenwolf style. I don’t know. Either way, Alfred’s driving while I’m just along for the ride.
-
I really hope Alex is right about the shared Events/Projects databases. That has been the endgame I’ve been pulling for all along. I was a big fan of Final Cut Server, though I was sometimes disappointed in its limitations in actual use. While as admin I could do really cool things with it, the users felt it was more of a burden than a tool.
My pie-in-the-sky dream was for Apple to better integrate FCP and FCSvr, where FCSvr essentially replaced the Browser window (or rather become a tab). FCP would become a direct client of FCSvr’s database, eliminating the troublesome Java GUI and making it a work-saver instead of a work-maker for the editors.
FCPX already has a database-driven local asset manager, the Event Browser. Now all they need to do is put a database server behind it (like it’s that easy, right?). The database underpinning FCSvr was PostgreSQL, which Apple recently adopted as the bundled database for OS X in Lion. In OS X through 10.6 they shipped MySQL. Probably just a coincidence.
Best,
Andy -
Andrew,
From what I’ve seen of the software and read here in the forums, it just strikes me that “workflow” was entirely an afterthought to FCPX design: renders kept with the project file which is designed to be kept on the boot drive. Really? At what point in the design process was that idea analyzed and arrived at as the ideal solution? Using the finder to organize projects?
A better database and workflow model is certainly needed (as per your post) but right now that prize is up for grabs and it doesn’t seem to me that Apple has any particular advantage built into its software, nor any particular drive in that direction.
Also this is pretty funny (from the linked post):
“Secondary storylines could be modified by assistant editors while they are repositioned in the primary storyline.”
Solutions looking for problems …
Franz.
-
I’m not sure where you got the impression that the Project/Render files are designed to be kept on the boot drive. That’s only true insofar as FCP7 defaulted the scratch disk to the Documents folder on the MacHD.
-
[Franz Bieberkopf] “A better database and workflow model is certainly needed (as per your post) but right now that prize is up for grabs and it doesn’t seem to me that Apple has any particular advantage built into its software, nor any particular drive in that direction.”
While I agree that it’d be nice to be able to separate render files from database location, I think the rest of your analysis is misinformed.
It certainly does not look or operate in a familiar way, and it is true there needs to be more functionality built in to the software, there are many advantages to the FCPX media management process, especially of you have a central storage system and multiple users.
It takes much more than a cursory glance to realize this, and yes, as it stands right now, it takes a bit of imagination, but there’s also quite a bit of power built in already.
I think the separate event and project method is actually going to be quite nice, but it does take getting used to.
Perhaps having another person work on a separate part of your timeline is of zero use to you. That’s fine. For some of us, it will be of use, and if it’s presented in a logical and “better” way it will be a step forward. It might not “solve” a problem, but it will certainly enhance the workflow and allow easier collaboration and creativity.
-
[Jeremy Garchow] “… yes, as it stands right now, it takes a bit of imagination, …”
Jeremy,
This does seem to be the forum that discusses imaginary software the most.
Franz.
-
Marcus,
There was a discussion on issues with network media – I think it may have even been Jeremy? Search is failing me. Solution was to keep things on the boot drive, including renders.
Someone else may remember more detail.
Franz.
-
[Franz Bieberkopf] “This does seem to be the forum that discusses imaginary software the most.
“Sometimes, it appears using one’s imagination is certainly frowned upon in this forum.
Have you tried to share a Project with multiple users on a SAN with FCPX? How’d it go? What about an Event?
How about media? Have you shared that yet?
How about archiving a Project or Event, and then restoring it?
Tried it? Have you emailed a Project to someone who has duplicate media? How’d it work out? How was the reconnection process?
Have you tried any of these with other software beyond fcs3? How’d it go?
Reply to this Discussion! Login or Sign Up