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

Re: Resolve XII...

COW Forums : Apple Final Cut Pro X Debates

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

Walter Soyka
Re: Resolve XII...
on Jul 31, 2015 at 12:15:01 pm

[Andrew Kimery] "To keep the example simple, let's just say an editor and a mixer are both working concurrently on the same edit. Having a truly shared timeline that updates in real time sounds horrible to me because the media in the timeline will be constantly changing. We will be constantly stepping on each other's toes.

If the editor and the mixer have two versions of the same timeline then we won't be stepping on each other's toes, but at the end of the day someone will have to take the changes made in each timeline and conform them into a single timeline. A computer can track the changes but it won't know which changes to apply when both the editor and the mixer have

Waiting until the end of an edit to start the finishing process isn't just done because we have incompatible tools, it's done so that time and money isn't wasted polishing media that won't make it into the final cut."

There are tools and methodologies outside of our industry for dealing with exactly these issues. For example, software development happens across a team in parallel, with source control, check-in and check-out, and tests to find and resolve conflicts.

You do get diminishing marginal gain as the team size grows, because as you point out, coordination does take time.

If you think about the way we work now, it's a challenge. If you think about the way we would work if we had different disciplines working together at the same time, then you'd probably build a different workflow. Some tasks are clip-based; these can be done in parallel. Some tasks are sequence-based; it may be prudent to wait on these until the end of the process. For tight schedules, it may be worth the risk of having to do something twice to try to get it done earlier.

[Andrew Kimery] "At some point though I think you have to curb how much non-NLE functionality you put in the NLE and say to the user, "Look, if you want to do some really advanced stuff you are just going to have to cowboy up and learn a dedicated mixing/grading/compositing, etc., app". If you try and too much other stuff in an NLE I think it can become bloated and too difficult to use by the majority of it's target audience."

Let's talk about "bloat." What does that mean to you?

Apple has done a really good job of not showing you functionality you don't need. FCPX does a lot, but the UX is so smooth that a lot of people still underestimate its capabilities as iMovie Pro. Is FCPX bloated?

Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive [twitter]   |   RenderBreak [blog]   |   Profile [LinkedIn]

Posts IndexRead Thread 

Current Message Thread:

© 2020 All Rights Reserved