[Matt Kemp]

I don’t think expecting something as fundamental as keyframing to actually work is too much to ask, do you?

FCPX doesn’t need to be different, it just needs to be better.

[Matt Kemp]

Feel a bit bad hijacking this thread with these thoughts, after all I only came here after frustratedly googling ‘why is key framing in FCPX so bad’ ☺

I wouldn’t say that FCPX is only suitable for modest projects at all. With a pro using it, high end products can be made. I myself have used FCPX almost exclusively on projects which have gone on to win some awards. I also don’t think it’s representative to write an A-B list of what X can’t do which Pro can (although for VR, which I work a lot with, that list certainly exists).

It’s like with the keyframe question. It’s not that you can’t keyframe in X, it’s that the function is badly designed, making it difficult to work with and adding default ease functions which Apple has decided we all need but which more often than not need to be manually removed.

Anyway I think the point really is that different pieces of software suit different kinds of projects, and people feel more or less comfortable and happy with different suites for different reasons. In that sense I think it’s healthy to be system agnostic. If you have access to both Mac and Windows machines, FCPX, Adobe CC and Resolve, then the bases are covered for whatever the clients throw at you 🙂

[Matt Kemp]

I think you make a really good point Bill, and it’s an easily forgotten element of all this – how the software makes you feel while using it.

X makes me feel like an amateur, forced to adopt techniques and stylistic choices which Apple think is the way it should be done, and I find it frustrating and occasionally borderline insulting (I really should get out more) 🙂

[Matt Kemp]

Maybe the word ‘crappy’ was a bit harsh. Certainly the inclusion of colour wheels is a huge improvement over the colour board.

And again, this is all purely subjective – I’m not trying to insult anyone who finds X a great tool. For many, many functions I also thinks it’s really useful. But for colour correction (seeing as though you ask), I’m used to tools like Lumetri, curves adjustments, gamma controls and other features which are pretty basic in Premiere, After Effects and Photoshop, all of which I use extensively.

I know for example that Resolve was born as a dedicated grading software, but can you really imagine a series DaVinci user going to the colour wheels in X and thinking ‘wow, this is great’.

Nope.

Again, it goes back to what Apple intended with X. If it wanted to produce a piece of software which developed organically on from 7 with groundbreaking new features such as the magnetic timeline, but with all the pro functionality found in the other high end NLEs, it could have. But that was never the intention. So I think it’s disingenuous and fanboy-ish to defend the ‘pro’ credentials of X when it clearly was never designed to meet those kinds of high end demands. I like X, I use it. But I’m not about to defend it to the death just to be dogmatic.

For certain projects I wouldn’t dream of using Premiere. For others, I wouldn’t go near FCPX. I just don’t really see why the debate can’t be a bit more honest. My two (or maybe now 20) cents: For quick turnaround ingest, cut and output projects, FCPX rules. For graphics, grading and motion effects (and anything which requires key framing), it sucks. No NLE is perfect, that’s why we have the luxury of choosing the one which is right the project we’re working on.

[Matt Kemp]

Yeah I guess I should’ve known that last post was going to generate that kind of response.

Sorry, but as far as I’m concerned, the FCPX apologists can kid themselves as much as they like, but this is not a serious product, and won’t be for some years. Like I said, I am a committed FCPX user since the first version. I edit everything from promos to feature length docs, to VR video, and there are things I love about it, primarily it’s speed of ingest, edit and output.

But the multitude sub-standard features such crappy keyfaming, colour correction and the ridiculous iMovie effects and title functions keep this at the prosumer level, which as far as I can tell is exactly what Apple intended. Sure, I’ve loaded up on all the third party extensions which help a lot (Color Finale for example), but as far as I’m concerned any app which relies on third party plugins to bring it up to par with Premiere or other NLEs doesn’t deserve that much credit.

Sure, pros can use it, because they’re pros. But the death of 7 and inception of X lowered the bar for high end video editing on a Mac. It was called iMovie Pro since day one, and despite the new features, it’s still just an (admittedly greatly) improved iMovie Pro.

This isn’t a statement of fact, this is my opinion as someone who edits video every day. You can agree or disagree, it really makes no difference to me. I’m no Premiere evangelist or FCPX-basher. One last time to reiterate, I use it every day. But I’m not suckering myself into believing it’s the best thing since sliced bread. It isn’t.

[Matt Kemp]

I do agree, and for the most part it hasn’t stopped me using FCPX for 90% of my work.

I guess it’s just frustrating. Having mastered the magnetic timeline and all the other functions which make FCPX unique, I see it’s power and potential. But then these ridiculous amateur oversights (like keyframing, and to a lesser degree, colour correction, amongst others) just stop it being a really amazing piece of software truly worthy of pro use.

It’s so close, but so far away..

Imagine if we had all the best bit of X and all the best bits of 7 in one package. It would be an incredible piece of software.

As it is, using FCPX always leaves a bad taste in my mouth one way or another, whereas Premierem even though it’s slower and in a lot of ways feels more old fashioned than X, gives me the warm and fuzzies because it makes me feel I’m working with pro kit.

[Matt Kemp]

5 years later, a whole range of amazing new features and functionality introduced to FCPX.

And keyframing is still complete shite.

What a joke.

[Matt Kemp]

So by the fact that there are no replies or comments, I have to assume that nobody else has experienced any of these problems? At all?

Seems very strange. Patience here is running out very quickly with the continuing problems with using Blackmagic Multibridge/Media Express. If we can’t find a solution in the coming weeks we’re switching to an AJA card, so please if anyone has even an inkling about what could be wrong, any ideas are very welcome.