APPLE FINAL CUT PRO: Apple Final Cut Pro X FCPX Debates FCP Legacy FCP Tutorials

Re: Why FCPX?

COW Forums : Apple Final Cut Pro X Debates

Respond to this post   •   Return to posts index   •   Read entire thread

Oliver Peters
Re: Why FCPX?
on Oct 9, 2017 at 9:04:55 pm
Last Edited By Oliver Peters on Oct 9, 2017 at 9:06:07 pm

[Walter Soyka] "For a team with multiple interdependencies, it's much harder. Every decision on a team has ripple effects, so changing a single piece of the workflow or slowing down a specific step for retraining may have broad ramifications (positive or negative)."

What gets overlooked is that NLEs are no longer operating in a standalone mode at many places. It's part of a larger workflow pipeline and in more cases than not, the driver is After Effects and not the NLE. I have worked in the past and currently work with a number of younger editors where the heavy lifting is all in AE. The NLE is just the place to start and end with.

To place FCPX into this workflow actually lowers efficiency, not improve it. And no, Motion is not an option. To make that move involves a lot of training in multiple disciplines, plus rethinking the whole pipeline. And it locks you into Apple hardware.

- Oliver

Oliver Peters -

Posts IndexRead Thread 

Current Message Thread:

© 2020 All Rights Reserved