Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations Resolve 16 vs FCPX

  • Michael Gissing

    April 17, 2019 at 10:50 am

    James Resolve 15 is so last year.

  • Eric Santiago

    April 17, 2019 at 1:49 pm

    [James Culbertson] “That said, it is really easy to get FCP 10 timeline’s into Resolve, “

    Do it all the time for a few years now.

  • Craig Alan

    April 25, 2019 at 6:13 pm

    “FCP X has evolved and has become the most widely used NLE in our market”

    Is that professional market or over all usage. Is it active use or number of sales?
    I’m not debating just curious.

    Imacs (i7), Canon C300, Canon 5D Mark IV, Panasonic ENG HPX250P, , FCP X, teach video production in L.A., Cool Light Productions, Producing series of multimedia Portraits of creative women in the production arts.

  • Mark Suszko

    April 26, 2019 at 6:49 pm

    I know he didn’t mean anything insulting by it, but the comment suggesting that features of FCPX are “dumbed down” for the “simpler user” is I think, a tad unfair.

    I’ve been having to work in FCPX and Premiere side-by-side now for a while, and I have to say, a lot of the FCPX functionality is seemingly done in a much less “clunky” way than my experience of Premiere. FCPX is very intuitive and there is an economy of steps to do what you want, whether that’s using shortcut keys or the mouse.

    My Premiere experience so far includes way more tabbing around to get to what I need, functions that seem similar but aren’t, and the paths to get to those items or tools I need don’t always seem “logical” to me.

    Part of that, i’m sure, is just that I have more familiarity and practice in FCPX; I’m way faster in it, I know where everything is, and how the tools work.

    But part of it is also just a better user experience, not “dumbed down”, but clearer, logical, “more intuitive”, and maybe more “accessible”. One little example of this, for me, is the implementation of crop tools. In Premiere, it’s buried two steps away in it’s own little bubble. In FCPX, it’s with all the other transform controls, and I like that.

    I am impressed with how much faster Premiere renders out a file over FCPX. I’ve even done whole jobs where I’ve done the cutting in FCPX but handed off the final render to Premiere… But much of the rest of it seems like it’s pretty old-fashioned in how you have to work in it. I hate the interface, just hate it. They are putting me on a ledge, in terms of mastering Premiere before they take away my Final Cut Pro X at some random, unknown future date, so I’m under the gun to get better at Premiere… But cutting in Premiere to me just feels like work, when FCP has always felt like play. Simple isn’t “dumb”; it’s powerful.

  • Oliver Peters

    April 26, 2019 at 7:07 pm

    [Mark Suszko] “I am impressed with how much faster Premiere renders out a file over FCPX. I’ve even done whole jobs where I’ve done the cutting in FCPX but handed off the final render to Premiere..”

    Weird. I’m generally found FCPX and Compressor to be much faster renderers. I suppose it depends on your machine and the codecs involved. OTOH, I find Resolve to render faster than either for complex, multi-codec timelines.

    – Oliver

    Oliver Peters – oliverpeters.com

  • James Culbertson

    April 26, 2019 at 7:42 pm

    [Mark Suszko] “but the comment suggesting that features of FCPX are “dumbed down” for the “simpler user” is I think, a tad unfair.”

    More wrong than unfair. I think by now most of us know that this kind of talk is code for “I don’t really know how to use FCP 10.” A fair statement would be something like, “I prefer to use Premiere over FCP10.” (or vice-versa).

  • Oliver Peters

    April 26, 2019 at 8:07 pm

    [James Culbertson] “I think by now most of us know that this kind of talk is code”

    At this point it’s all water under the bridge.

    I think the best way to look at it is there’s the base of the tree where the concepts of tape cutting and film cutting were combined to envision modern NLEs. Avid/Adobe/Media100/EMC/etc all went in a very similar direction – one branch of the tree.

    In creating FCPX, the development team went back to the bottom of that trunk to start up into a different direction/branch. As a result you now have two large branches that diverge a bit from that common base, but still with a ton of similarities. Blackmagic has attempted to embrace both with the Cut Page + Edit Page in Resolve 16.

    We’ll see how well that works in practice.

    – Oliver

    Oliver Peters – oliverpeters.com

  • James Culbertson

    April 26, 2019 at 9:41 pm

    [Oliver Peters] “there’s the base of the tree”

    That’s true Oliver.

    I spent my first couple of years editing on both flatbed and tape to tape. Editing on FCP 10 and Premiere makes me realize that more traditional timeline-based NLEs like Premiere are like tape to tape, and FCP 10 feels like it has gone back to a more film-feel type edit style. FCP 10 just feels more tactile while at the same time getting out of the way to embrace a more intuitive way of editing. I still have a hard time explaining the feel to my editing friends who do not use FCP 10. Also, they don’t believe me… 🙂

  • Lee Doucet

    April 28, 2019 at 5:15 pm

    Downloads aren’t indicative of much, since you had to register to download updates as well. They only just added an in-product update system in Resolve 16b1…

    Resolve is exceedingly popular by virtue of Windows’ market share vs. macOS; and the fact that it is also available on both macOS and Linux.

    It probably already has more users than FCPX, at this point.

  • Lee Doucet

    April 28, 2019 at 5:16 pm

    Cut is not meant to be a replacement for Edit. I think complaining about some of these things is missing the point, a bit.

Page 3 of 4

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy