-
My thoughts after a few hours…
I’ve been toying around with FCP X for a few hours and at the same time reading comments on the COW. I’m more positive than most, in that I’m actually starting to like the way it behaves.
THE BAD
– Missing features: OMF, EDL, XML, Multicam, export options, RED RAW, third-party hardware support, etc. I expect some of those to become available through upgrades. I am afraid that we will have to pay extra for individual features (or buy them in packages), especially proprietary codecs that involve license costs. This is a common strategy with Store apps, and wouldn’t be beyond Apple. Can you imagine? 100$ for RED RAW support, 75$ for OMF export, etc… by the time you’re set up, FCP X cost you 900$ or so. That would explain why Apple is selling FCP X for 300$. Or maybe I’m just paranoid. But then again, it might be a good thing for those that don’t need everything.
– You can’t import legacy FCP 7 projects. Sure you can retain your FCP 7 install, but I would have liked to transition one of my current projects to FCP X, in order to learn it in my free time.
– I don’t like the inability to save a project where you want. I usually save my project in a Dropbox folder, so I can work from the office or home; media files remain in local copies. I’ll have to go back to carrying around an external hard disk every day (which will have to contain both project an event folders).
– You can’t customize the interface, other than sending either the Event Library or Viewer to the second monitor. But I have to admit that the UI is growing on me and I forgot my initial reaction.THE GOOD
– The “one project, one timeline” paradigm; it requires an adaptation, but it’s actually more effective than the old way of doing things. In fact, the way I can organise my projects in custom folders from the Project Library renders the point moot. You can still have multiple versions. You just have to re-learn what the words “timeline” and “project” mean. It’s a smarter way of implementing project management.
– The Event Library: I wasn’t so pleased when I saw it at first, but I’m loving it now. In fact, I LOVE that it’s global rather than project-based. Project-based media management is so 2010. It’s going to be a time saver.NOT SO SURE
– The magnetic timeline: Overall I am very impressed so far, but I’m not used to its intricacies yet. Problem is, you have to use it the way it’s been designed to be used, not the way FCP use to work, and that’s not an easy thing to do…THE STUFF I COULDN’T CARE LESS ABOUT
– Consumer features in my Pro app. I have to admit I did cringe when I saw the SHARE entry in the upper menu, and I double-cringed when I saw it contained Export to Youtube, Vimeo and Facebook features. But that has absolutely no impact on how I will use the product, so why should I care.
– Deleting something from an event moves the source file to the trash: Well considering that the sub-menu option is called “MOVE TO TRASH”, is that surprising? The shortcut is Cmd-Delete, not Delete, so it’s not going to happen by accident. If you want an element to disapear from the Event Library without actually deleting the file, just set its rating to “Rejected” and Hide Rejected clips from the Event Library (Ctrl-H)I feel that a lot of criticism of FCP X so far comes from people that:
– haven’t actually used it, or
– want it to work like FCP 7, and don’t want to take the time to learn the “new ways” that Apple is proposing.Many people say it’s dumbed down… That’s not my experience so far. Sure, at first, it’s strange, but it’s actually pretty deep once you spend some time with it.
For now, I’ll keep editing professional projects on FCP 7 and play around with FCP X in my free time. Once I’m up to speed, I’ll probably make the jump for good.