Kyle Gordon wrote:A few points.
The reason fcpx is so powerful is that it speaks ProRes natively. When working with ProRes clips, fcpx can handle many more streams, color corrections, bandwidth than any other NLE running on the same computer with any codec of similar resolution and quality.
For this reason, fcpx will never use braw natively. Like any other codec, you transcode on input (or with another app) and then work in ProRes.
Huh? Redcode Raw has worked inside FCPX for ages. In fact, they have just released an important update, worked out in conjunction with Apple, and Redcode uses Metal in FCPX, making it incredibly efficient and fast. So, yes, while working in ProRes inside FCPX is a breeze, it's also a very stable program when working with mixed codecs (unlike Premiere), so this argument is unsound.
Furthermore, it's already possible to work with Braw by transcoding into (ProRes) proxies-- it's how I work every day and the only way I get to work with Braw. It's nearly bullet-proof, but it does require the extra steps of creating proxies and roundtripping. I always finish in Resolve so it's not an issue, but as FCPX (and Blackmagic Raw) gain even more market, it makes no sense for this gaping hole to exist.
I love Resolve for all it does, but there is no way I'll be going back to track-based editing after 10 years working in FCPX. Even Adobe, with Premiere Rush, is slowly catching up to the future (present).