Apple released a 10.0.2 update to Final Cut Pro X late Wednesday.
The update is free and available as an update through the App Store. Primarily a bug fix, this new version:
* Fixes an issue in which a title may revert to the default font after restarting Final Cut Pro X
* Resolves an issue that could cause files recorded with certain third-party mobile devices to play back incorrectly
* Addresses a stability issue caused by changing the start time on a Compound Clip
According to Apple, the update is recommended for all users of Final Cut Pro X.
For more information, visit www.apple.com/finalcutpro.
10 Responses to Apple Updates Final Cut Pro X
Great to see them keeping these rolling. I’m not surprised to see an exclusive bug fix update. As Apple said at launch, the app store model for delivery seems to be making updates easier [and therefore] more frequent.
People had been theorizing that the Multicam/Monitoring update that Apple has already slated for “early 2012”, but at this pace, I don’t think it’s out of the question they could mean EARLY 2012.
I guess my forward thinking question would be, is Apple looking at a yearly major update cycle for FCPX? 10.0 was announced in March and launched June 21st. That gives them just over 6 months to reinstate or replace [ala roles] features, and improve stability. If there is a Summer launch planned for 10.1, I’d wager Apple will want to have all the legacy concerns addressed by then- so that V2 can be look forward to new features and ideas, and not back…
Yup. They seem to be delivering on their promise to update the program frequently.
As to their future plans, well, we will just have to see. However, I agree with you that the release supporting multicam will be out sooner, rather than later in 2012.
Larry
I’m very anxious to see them get these issues sorted out.
I think the whole conversation around FCPX has been tainted by the confusion between missing features and fundamental [and conscious] changes to the UI.
I think only after Apple engineers put the missing features list to bed, can there be an honest evaluation of what real benefits [or deficiencies] FCPX has to offer.
It’s too bad that they couldn’t have waited and just released it with all those features a year later. Ultimately though, I think the benefit of getting it into people’s hands, and letting those for whom FPCX meets their needs “as is” work with it and react to it, was ultimately the lesser of two evils.
@ Marcus:
I won’t spend too much time on it as I think everything that can be said has been said, but I really disagree. they should have waited a year to get it right. Instead, they’ve given idea to their competitors by playing their game too early. MC6 was announced and it too now does 64 bit (althought every body knew that it would even before FCPX was released), and more importantly metadata. And everything that’s been missing in FCPX. And they did re-invent the wheel.
From a marketing AND strategic stand point it’s been a debacle.
And I will point out that Apple has always been pretty good at releasing pro apps updates that solely fixed bugs, usually around 6 months from release.
10.0.1 was good (despite the role/omf that is still not a solution audio mixers want to deal with). 10.0.2 is worth reporting, and it’s good that it’s fixing some bugs, but I wouldn’t praise Apple for it. Their only doing what they should do.
Anyway, I don’t want to start a religion war here. I’m just pointing at that this is good, but hardly amazing. FCPX is promising but has a long way to go. I think Apple can do a lot better than that.
Now that I’ve gone through most of Larry’s training video and edited on FCP X, I’m starting to like it more. I’ll reserve full judgement until I edit a few more projects that are more elaborate.
I also hope they don’t screw up and/or dumb-down multi-cam. I bought a Promise external drive with Thunderbolt specifically so I can edit multi-cam HD without the computer having a heart attack.
I do have some gripes. I’ll mention only one here: If you manage to get your video and audio out of sync, there’s no visual indication/warning. This is inexplicable. I de-link my audio and video all the time for various reasons. Why would Apple fail to include this important feature? I hope that V2 will correct this omission.
OK, here are two more FCP X features I hope they bring back:
–Please save I/O points in the Event Browser. There’s no reason not to have this function. It makes the workflow harder. (I don’t want to have to save them as Favorites.)
–Also, as far as I know, in the Event Browser I can’t arrow and up and down between I/O points. If I do, the playhead goes to another clip. I hope this feature is also put back in V2. It’s a big time saver.
Caesar:
I COMPLETELY agree about preserving In and Out points. I’ve discussed this with Apple and they told me they are “thinking” about it. That was a few weeks ago, so I’m hoping they’ve moved past thinking into doing.
As for jumping between In and Out try Shift+I and Shift+O.
Larry
Larry,
I think the reason why In and Out points are not stored with the events is because in a shared environment, different editors would like to save different I/O points in the same clip. Perhaps one good point is to allow in preferences to save or not I/O selection. Who knows.
I suspect Leo might be on to something. I can’t help but think, when I look at FCPX, that it’s really designed for a shared environment. I’d suspect they’re thinking about what a stored I/O be regarding meta data. I’m happy with using the F key to save favorites. For me, it’s effectively multiple I/Os for a clip. I suspect some are bothered by hitting that extra key and the accumulation of Favorites over time if they don’t clear them.
BTW Evan Schechtman of OutPost Digital recently spoke in NYC about FCPX and apparently he’s a beta tester. Obviously he couldn’t say much but he did say he was going to move his facility (roughly 50 seats I understand) to FCPX as their main NLE on the next release (Multicam, Broadcast Monitoring). I infer from his comments that night there’s going to be a lot more than that in the next release it some of it seems to relate to shared environments.
Larry, thank you for the info about jumping between I/O.
Regarding saving I/O points: I’m sure Apple can make it an option. That way they meet everybody’s workflow needs.