Activity › Forums › Creative Community Conversations › Status of FCPX in 2019
-
Douglas K. dempsey
January 16, 2019 at 10:39 pmI have a 26-year old son in the biz … not an pro editor per se, but he grew up cutting his own films in FCP7, and when he got a few jobs out of college, was forced into PPro CC (which he set up with the old FCP7 shortcut commands ☺
He works with some young commercial shooters, a lot of indie filmmakers, and it’s all PP. I can’t recall a name, but there was some post-house guru in NYC who trashed X a few years back, and the indie crowd listened. And then, when the Coen Brothers who previously did their own editing on FCP7 (as the pseudonymous “Roderick Jaynes”), switched to PPro when FCP7 was EOL’d. From that moment on, PPro was cool, X was uncool.
Of interest, though … virtually EVERY one of these young filmmakers and editors is working on a MacBook Pro … the only Windows machines I see are in the hands of people working in gaming (Unity or Unreal), effects (After Effects and others) or coding work.
Doug D
-
Douglas K. dempsey
January 16, 2019 at 10:50 pmTo acknowledge Ronny’s comments, though … the New York scene I am referencing is largely a peripheral and/or wanna-be Hollywood / TV crowd … a group that used to be told, including by NYU film school et al, “The pros cut on Avid” – but as Ronny notes, Avid is largely being “aged out” in that group.
Doug D
-
David Mathis
January 16, 2019 at 11:59 pmI see the current version as paving the way to a huge and potentially useful update when it comes out later this year. There is some speculation it could be during the NAB show. The extensions are a nice addition and possibly more extensions are on the way depending on the path Apple takes. It might be possible we could export individual clips from the timeline without the need for third party apps though that opens up opportunities and options for the end user. I predict Frame.io will have a larger presence in the ecosystem with a richer feature set. Apple does need to improve keyframing and add mask tracking to the toolbox. Outside of that it will be interesting to see what awaits us with the next update.
-
Oliver Peters
January 17, 2019 at 12:18 am[Ronny Courtens] ” I can see FCP X and Resolve evolving into a great combination for the future”
Agreed. A great combo.
– Oliver
Oliver Peters – oliverpeters.com
-
Neil Goodman
January 17, 2019 at 3:26 amIts def come a long long way but since I cant earn money using it – I gave up on keeping up with it last summer.
Im really surprised it hasn’t gained any traction in marketing and shortform. I think thats a space where it could really shine but I dont see people giving up on Avid and PP anytime soon.
-
Jay Soriano
January 20, 2019 at 2:03 pmRonny & Oliver,
Interested why Resolve and FCPX is a great combo? Starting to use Resolve but looking into FCPX as well. Curious on your thoughts. Thank you.
-
Oliver Peters
January 20, 2019 at 5:22 pm[Jay Soriano] “Interested why Resolve and FCPX is a great combo?”
Let’s assume you want to do your creative editing in FCPX. But then if you want to do advanced color correction and mixing, so you want more tools. That’s where Resolve comes in. Plus it plays well with FCPXML exchange. You also have more in-depth Fusion compositing. Both apps can be purchased/installed/updated through the App Store mechanism, too.
– Oliver
Oliver Peters – oliverpeters.com
-
Jay Soriano
January 21, 2019 at 4:27 pmThank you for this Oliver. The move from FCP 7 to Davinci Resolve was a smooth transition. What I loved about FCP legacy was the vast amount 3rd party plugin support. Is there reason why there is a limited amount of 3rd party plugin support for Davinci Resolve OFX vs FCPX FXPlug? There seems to be a huge amount of FCPX effects availability out there.
-
Steve Connor
January 21, 2019 at 4:44 pm[Jay Soriano] “There seems to be a huge amount of FCPX effects availability out there.”
I would imagine it’s because a lot more people use FCPX to Edit than Resolve and it’s quite easy to develop effects because of the Motion “engine” that underlies it.
-
Oliver Peters
January 21, 2019 at 5:00 pm[Jay Soriano] “The move from FCP 7 to Davinci Resolve was a smooth transition.”
I would add though, that I find the XML from Premiere to translate better into Resolve than the FCPXML from FCPX. Some things simply don’t translate well. Also the FCPX workflow is really dependent on using compound clips. You don’t have to, but the tendency is for users to fall back on them more so than in other NLEs. Those also don’t always translate well.
– Oliver
Oliver Peters – oliverpeters.com
Reply to this Discussion! Login or Sign Up