Activity › Forums › Creative Community Conversations › “Or Not” was born of the FCP X Launch. So…
-
“Or Not” was born of the FCP X Launch. So…
Bill Davis replied 10 years, 1 month ago 13 Members · 48 Replies
-
Bill Davis
June 3, 2016 at 5:57 pmTHIS seems entirely fair and on point to me.
Creator of XinTwo – http://www.xintwo.com
The shortest path to FCP X mastery. -
Claude Lyneis
June 3, 2016 at 6:38 pmTo me Apple’s launch presented existing users of FCP7 with a fork in the road. Switch to X , which was incomplete and required a steep learning curve due to its very different concepts. or switch to something easier to grasp, which was Premiere Pro. In that launch they lost most of a generation of editors and it carries on. At the local college film school, trying to talk to almost any teacher or student about FCPX today is an exercise in futility. The response I get are the same we heard in 2011. I am a one man band and took the less traveled path and enjoy FCPX, but within our local community it makes collaboration difficult.
Could Apple have made a smoother, more helpful transition? Sure, but to sell a radically different approach to existing editors would require overwhelming benefits and I think FCPX can’t make that case. Hopefully, it is doing better in the next generation, unless they go to film schools.
-
Philip Hodgetts
June 3, 2016 at 7:26 pmJust to be clear: No-one at Apple ever said the translation from FCP 7 to FCP X was “impossible”. The original was “It is not possible to translate from FCP 7 to FCP X with perfect fidelity”. Two prominent community leaders decided to drop the last bit and continually misquote what Richard said.
Philip Hodgetts
President, Intelligent Assistance
Personal Blog https://philiphodgetts.com -
Oliver Peters
June 3, 2016 at 8:00 pm[Philip Hodgetts] “The original was “It is not possible to translate from FCP 7 to FCP X with perfect fidelity”.”
Thanks for the clarification. Although that’s certainly a nuanced difference, it really gets down to semantics. From this AppleInsider story at the time (assuming they quoted accurately) the FAQ uses the language of “impossible to translate old projects without changing or losing data”. That seems a bit more troubling than “perfect fidelity”. Of course, it’s all water under the bridge these days.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Walter Soyka
June 3, 2016 at 9:04 pm[Michael Gissing] “And while all this revisionist history is being argued and FCPX users have only had Automatic Duck to bring any excitement in May, the third public beta of Resolve 12.5 has been in the wild for a week with another dazzling array of new features and performance improvements. “
IMHO, Blackmagic Design delivered THE big desktop-post NAB performance this year with Resolve 12.5. Sure, they drop massive releases every year, but Resolve 12.5 is the first release of just about anything from BMD that strikes me as a bit “boring” — that is, it is completely focused on daily user issues. It’s not a pile of cool, marketing-driven, wowie-zowie-demo features meant to gloss over an obvious deficiency. It’s the work BMD needs to do to eliminate those deficiencies.
If you’ve been studiously ignoring Resolve (like I have), I think it’s time to stop.
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn] -
Oliver Peters
June 3, 2016 at 9:30 pmThis article seems vaguely appropriate to this thread:
https://www.theguardian.com/technology/2016/jun/02/ken-segall-apple-steve-jobs-simplicity
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Oliver Peters
June 3, 2016 at 9:35 pm[Walter Soyka] “If you’ve been studiously ignoring Resolve (like I have), I think it’s time to stop.”
What I find interesting is this. If FCPX users were completely happy with what Apple is doing with X, none of them would have any interested in Resolve as an NLE. Clearly that doesn’t appear to be the case. I would think it’s more than just a step back to a traditional source-record-track model. Something definitely is missing in X, even for those who like it a lot.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Walter Soyka
June 3, 2016 at 9:42 pm[Oliver Peters] “Something definitely is missing in X, even for those who like it a lot.”
What do you think that might be?
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn] -
Oliver Peters
June 3, 2016 at 9:50 pm[Walter Soyka] “What do you think that might be?”
I’m not sure. Maybe that Resolve takes a wider range of native media. Maybe that the speed of development in Resolve is putting Apple to shame. Could be a lot of things. Free could also be part of it.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Claude Lyneis
June 3, 2016 at 10:32 pmI guess not much is changed. I was poking around on the FCP7 forum and ran into this advice from
—————-
David Roth Weiss on May 25, 2016 at 12:54:41 pmX does indeed support 4K both natively and by transcoding to a mezzanine codec such as ProRes, which it does in the background. That being said, X does require that experienced users learn entirely new and unfamiliar nomenclature and editing techniques that are unfamiliar to most and require a learning curve that many are not willing to take the time to learn. In my opinion Premirre and Resolve offer most FCP user the easiest and most inuitve path for migration to a new NLE.
David Roth Weiss
Director/Editor/Colorist & Workflow Consultant
David Weiss Productions
Los Angeles
———————
I had to go back to 7 to try something and X and 7 are certainly different. It would now require a learning curve for me to use it after switching in 2011.
Claude Lyneis
Reply to this Discussion! Login or Sign Up