Thanks, Ronny (and others), for your comments.
One of the things I was highlighting was that increasingly a typical workflow extends beyond the NLE – quite a long way beyond the NLE.
I think, for a lot of us, simply being an editor sitting in front of a closed-system NLE is less and less of an option as the audio-visual world we have to service gets more and more complex and diverse.
And that’s why, for many, it’s the overall ecosystem (and its associated interchange issues/solutions) that becomes the most important part of the equation.
But again, different ecosystems will suit different projects at different times.
For me, Resolve/Fusion represents an ecosystem that works really well, if that’s what you need. BM have managed to mesh together two entirely separate products in a way that delivers great flexibility and lots of power. And they’ve done so with a minimum of fuss and in a remarkably short space of time. It also helps that Resolve talks very nicely to just about every other platform going, in a way that few other products can match. It’s greatly to FCP X’s advantage that Resolve can serve as an interchange “translator”, for instance.
But of course, there are other ecosystems that favour different types of projects …
Simon Ubsdell
tokyo productions
hawaiki