Check out what EOSHD.COM had to say about the speed of FCPX

Andrew Reid ( Who I think is a FCPX hater) at EOSHD.COM did some testing of the playback speed of 4K ProRes on different NLE systems. Guess which NLE won?


www.eoshd.com/2015/01/now-you-can-transc...3x-faster-with-fcpx/

I don't think Andrew hates FCP X. He is just one of the former FCP7 users who still believes that a pimped up version of legacy FCP could have survived in the new digital era, which is wrong.

Now he starts to see the benefits of an application that has been re-written and re-organized from the ground up. The best line in this article is: "No matter how good the performance is, I won’t go back to it as an editor yet." The "yet" being pretty significant for everything that is happening around FCP X at this moment.

- Ronny

I think NLE's (besides FCPX) and spreadsheet apps are the only ones that have remained the same for the past two decades. Just sad to be so outdated and insist on not changing for the better...

There's Microsoft Office

Exactly my point...

I totally agree with you, Ronny. Actually, the whole paragraph you took that line from states the point-of-view of many editors refusing to see the new paradigm in X as something positive:

Apple’s decision to start afresh with FCPX on the technical / architecture side is really paying off. The best performance by far. The problem with FCPX is they also threw out the design handbook and years of editor terminology and usability (“library” for project, “project” for “timeline” and “share” for “export” – why!?) as well as fundamental basics. Stuff like batch export and many preferences / tuning options removed for the sake of dumb simplicity. Final Cut Pro 7 was not broken, it just needed a performance hike, not remoulding into iMovie. No matter how good the performance is, I won’t go back to it as an editor yet.

1. They don't get that tradicional NLEs were designed with the analog systems in mind, in order to ease the transition to computers for the working editors of the time. The metaphors that worked back then, don't work anymore for the current generation. As a trainer, that's something I noticed quickly as I found myself teaching history lessons more often in Avid and FCP7 courses...


2. They also don't get that those early systems couldn't fully embrace digital technology (see #1), because for many years they had to interact with the analog world (tapes, decks, etc.) for both ingest and print to tape. Only the editing was done "digitally" but in a limited manner. Both, Avid's AMA and FCP's Log & Transfer were a workaround to accommodate tapeless workflows in two systems that weren't initially designed for that. And it wasn't a very elegant solution: duplicity, confusion, incompatibilities... I could go on and on.

FCPX is the first system that confronts these issues in a fresh, innovative and well though-out way. And now it is in an ideal position to mature and grow (and take digital editing to another level), like it's been doing since it was introduced.

Other systems keep on improvising, adding "new features" on top of the old ones with every update (many of them directly ripped from FCPX by the way) without any serious consideration on their part. The end result is a complete mess. Just look at how Avid's contextual menus have grown in the past years... How is that useful to anyone?

So yeah, in this context, everything that Andrew Reid described as a flaw in X in the paragraph that I quoted, I think is actually the real value here:

• Simplicity in an NLE is not only a good thing, but a very needed and welcome feature after so many years of NLE history.
• Throwing out the old design was more than necessary for the reasons I outlined. And it's also more than welcome!
• Changing the terminology is only coherent (new design = new terminology = new functions). And it's a great way to remind people that they have to let go of the old habits and embrace the new paradigm.

Anyway, just my two cents.

I think somebody should tell the author that PrimariesExporter (released last week) is a solution to the lack of Batch Convert.

Anybody knows him? Or has an account to post on the forum ?

I used the contact form to tell him about PrimariesExporter. Let´s see if he responds.
-Thomas

ronny courtens wrote: He is just one of the former FCP7 users who still believes that a pimped up version of legacy FCP could have survived in the new digital era, which is wrong.
- Ronny

Agree, there a still quite a lot of those folks, many of whom think Premiere is the answer to all their problems. I work with people of this mindset, which is maddening. Especially considering the fact that I'm using X quite successfully. I really wish they'd wake up, as cutting in other NLE's, which i need to do when we're all on the same gigs, drives me crazy. Need more FCP X centric options around here honestly... Oh well...

At this point, if someone uses another NLE, SO WHAT? If it fits them, fine. We are not the FCPX Nazies. If someone bashes FCPX, it is none of our business. Their opinion is theirs to own, not ours. Free speech means letting the other guy say stuff without being vengeful. Something American (and other) politicians have lost track of. He wil decide, you will decide, neither of you will change the other's mind magically.

Save time to promoting what will improve our own thoughts about our own NLEA of "choice", rather than spend the time promoting what you believe iOS wrong with someone else's ligitimate, and factually solid opionion.

Truth is, FCPX is NOT the end all and be all of all NLE systems on the market. It has serious short comings that other NLEs do much better. And it does some things better than they do. Has, is, always will be the case.

Admitidly my humble personal opinion on these comparative, overly judgmental threads.

FCPX is great, but in no way superior to other NLEs universally. It has a LONG way to go, honestly.

The "love it or leave it" mentality should not exist any longer...

FWIW, I'm not judging anyone, and I cut on other NLE's as much I do in X. My opinion is based on the fact that people I work with do not want to learn X, based on no reason other than the ridiculous "nobody uses it" meme. This affects my ability to use what I choose to use, and honestly kinda makes my job more difficult and less enjoyable. In the grand scheme of things I could not care less what anyone likes to cut on. But in my immediate surroundings I do care.

And for the record, I don't believe X is perfect. At all. But I like it more than Pr. A lot.

JPM Editor wrote: ...They don't get that tradicional NLEs were designed with the analog systems in mind, in order to ease the transition to computers for the working editors of the time. The metaphors that worked back then, don't work anymore for the current generation....

Also they don't understand FCP X was not some hack job by an uninformed novice. It was headed by Randy Ubillos who was *also* the initial designer, architect, and lead developer of the first three versions of Adobe Premier, Final Cut Pro, and iMovie. He created Premiere for Adobe, then went to Macromedia and created a new editor which was purchased by Apple and became Final Cut, which he managed through FCP 7, then he created iMovie, then he created FCP X. He also created and managed the Aperture photo management app for Apple.

Supposedly Ubillos himself initially thought FCP 7 was just fine with only refinements needed, but then had trouble finding and organizing his own vacation footage, which led to the metadata-focused approach of FCP X.

nofilmschool.com/2011/12/avid-apple-excerpt-timeline-history