FCPX 10.05 released

Don't get too excited, Only retina support and stability improvements

WOW a full update just for Retina... :ohmy:

Next week, the anniversary, crossing my fingers. Seems if folks are going to buy this new retina MBP (which looks very impressive on paper), apps need to work on it right away. Aperture, iPhoto, FCP X, Motion. But, um, "Compressor" updated for retina display? Really? Why? So the UI doesn't look as crappy and outdated as it is?

But they do state "improves stability". I wonder if it really does?

Ok downloading now. About to start work so I'll keep you posted if there's anything nasty in there.

I'm working in intensely in Motion today, not seeing any changes or bugginess so far. I'll also post if I find anything. You just kicked in my fear of something breaking now, Seanus. Thanks.

There's often other unmentioned changes.

This Apple support note for Final Cut Pro X and Motion says that the updates require MacOS 10.6.8 or 10.7.4 - no earlier versions of Snow Leopard or Lion will work.

As Motion 5.0.4 is built into Final Cut Pro 10.0.5 (so effects can play, it doesn't have the Motion UI), then this sentence from the Motion 5.0.4 release note is relevant:

This update also resolves issues in FxPlug 2 where some images were returned at half height or upside down.

This will make it easier for effects developers to fix effects where there are display problems, but few developers were informed about this in advance of today.

On the new MacBook Pro with Retina display (MacBook PremiAir?) machines, some plugins that use images for on-screen controls might not display properly.

Developers were only told about 10.0.5 and the small extension to the way plugins are coded to support the new hardware and software 4 hours ago.

Well batch renumbering is still as borked as ever. Had one project not show up that I worked on last night. A simple restart of FCP X seemed to 'remind' it that it did in fact exist. Whew!

No changes one way or the other in Motion as far as I've found. Except the "retina display" version of the extra content won't download properly. But then, why have it take up room on my non-retina Mac?

I just notices that I also downloaded a "Motion 5" content update.... no word on this? Appears to be something different than the update...

Unless I'm just really lucky it looks like the disappearing project when rippling out a gap clip has been corrected.

Also the skimmer is more saturated red. Maybe that has something to do with retina display.

JBBronstein wrote: I just notices that I also downloaded a "Motion 5" content update.... no word on this? Appears to be something different than the update...

Yes...many content templates have been updated to take advantage of the Retina display in the new MBPs.

I wonder if it replaces the content, or appends to the content?

Just trying to use the keyer in Motion, and it won't let me manually select a color with the sample tool after the 5.0.4 update.

Well been using 10.0.5 all day. Gave it a real work out too. :evil:

All is still well with the world and another piece of movie making history has just left the building. So update with confidence I say.

With the Sample Color [square selection] tool from the Refine Key? :dry:
Works fine here.

did they fix the audio waveform display, in realtime when you increase-decrease volume ?

toxotis70 wrote: did they fix the audio waveform display, in realtime when you increase-decrease volume ?

Yes!

But it still doesn't update when you scroll while it's playing back. In fact, I'm finding it often stops outputting audio when you do that. So that went from bad to worse.

In Motion 5, if I use the graphic tool, top of the Keyer filter's controls, and try to drag across a section to sample a color, it only moves the image around, it will not in any way let me actually draw the square. Works in FCP, not in Motion, on my system.

If anyone is having issues with an update to FCPX or Motion it seems the best practice is to uninstall the app with an app like AppZapper or AppCleaner, then redownload from the App Store. Installing fresh (not over writing) has fixed problems in the past after updating for me.