What's new, fixed or different in FCP 10.3?

I upgraded a large library and lots of the proxy files are marked "missing". It appears if I re-transcode them they appear and work OK.

Is it normal that everytime I start the app it asks me what library I want to open without providing a list?

This is a cracking update but there are clearly issues that need some attention. I (carefully) completed a project this afternoon by duplicating a library and (only) opening the duplicate in 10.3. The audio mixing worked as advertised but it was virtually impossible to use the Channel EQ filter as playback stutters, skips, stops as you adjust the parameters. Also switching the filter in and out causes a playback hesitation. We carried on and mastered the final cut for the client and then swapped back to 10.2.3 to test this out with the original library and it was silky smooth. Have reported to Apple.

Also, the Frame.io plugin needs an upgrade as it triggered the transcode but waited forever for FCPX to hand it over for uploading.

All, I'm sure, will be fixed (and maybe the stuttering would vanish if I upgraded the OS from El Capitan) in the fullness of time. For the moment I have retreated to 10.2.3 on the Mac Pro (late 2013! - where's the new one?) and will run 10.3 on my 4 year old MacBook Pro 15" Retina when I'm training.

The filmstrip clip length is not persistently retained after restarting FCPX. I can set it to a thumbnail per clip but then it reverts back to the middle of the slider.

In other testing, the I/O rate seems slower when generating thumbnails in a large library and Hawaiki AutoSplit plugin intermittently malfunctions: hawaiki.co/autosplit.html

I've noticed that when adding keywords via a keyboard short cut I no longer get the little animation reassuring me that the keyword has been set. Only way to confirm it now is to open up the key word editor.

DFPete.

"Is it normal that everytime I start the app it asks me what library I want to open without providing a list?"

Try going into System Prefs>General and try setting the Recents to something like 10, instead of none. I was having this issue a while back and that seemed to work after opening a few Librarys. It then "remembered" the list.

JL

Don't forget to send feedback to Apple for every oddity you find

ianstubbs wrote: Also, the Frame.io plugin needs an upgrade as it triggered the transcode but waited forever for FCPX to hand it over for uploading.

All, I'm sure, will be fixed (and maybe the stuttering would vanish if I upgraded the OS from El Capitan) in the fullness of time. For the moment I have retreated to 10.2.3 on the Mac Pro (late 2013! - where's the new one?) and will run 10.3 on my 4 year old MacBook Pro 15" Retina when I'm training.

I had the same issue with frame.io with Final Cut Pro X 10.2.3 so I wouldn't shot from the hip and point at the 10.3 update. Frame.io did suggested a clean install with permission fix on the boot drive with success fixing the issue. They are looking into.
I will defiantly contact them after Halloween.

On my side 10.3 is running much snappier and responsive on both my personal Mac Pro (late 2013) with the 300 cards and on studio Mac Pro with the 700 cards.

aepictures wrote: I can see that now we can select color space when creating a new project. On my MBA it's grayed out and fixed at REC.709.
It depends on machine's screen or I do something wrong?

Set Rec 2020 in the "Library" settings, and you can chose color space in any Project's settings created in that Library.
Set Rec 709 in the "Library" settings, and you are limited to Rec 709 in all of the Projects in that Library. Thus, that option for Projects in that Library is grayed out.

Rec 2020 (wide gamut) is coming, cause outside of the new iPhone, not much records in it yet. But will be nice when it is more widely accepted.

A helpful feature for people like me: define any title for default Text and Lower thirds.

- Andreas

Apple Pro Video Format 2.0.5.0
support.apple.com/kb/DL1898?viewlocale=en_US&locale=en_US

I updated my edit station at work and spent about 8 hours working on 10.3 yesterday. I like the flat look, at first it felt a little confusing but it's just a matter of getting used to. At the end of the day I was already more adapted to it. I love some of the little things like the ability to double click inspector to expand it to the full height of your screen or how in the inspector it's easier to jump to previous/next keyframe.

To my surprise I found it really annoying how the timeline scaling slider was moved. Didn't realize how much I used it until it was removed. The default keyboard shortcut Cmd & +/- feels slower because I have to use both hands or at least move my hand from the mouse, so for now I just made a custom shortcut that I can use with just one hand.

Jonathan Levin wrote: One thing I noticed is that un-rendered clips in project are represented as a series of white dots where it used to be a red line.

I preferred the old red line, it was easier to see than the new style. I also preferred to see the background tasks dashboard (or whatever they call that) right above the timeline. It was easier to glance while working, now it feels I have to look for it instead of kind of just seeing it there all the time. You know, little things, but they start to matter when you work on FCPX all day every day.

Overall I like the update and once I learn to utilize all the new features I think it'll allow me to work faster.

I agree, I do not like the Timeline controls tucked away in another menu.

Another step to access a command. I finally got used to it... Usually use hot keys to zoom in and out.
But adjusting the timeline settings was sexier before .

Has anyone tried Neat video with 10.3? Does it work? Any other well known plug in not yet updated for 10.3?

In FCPX 10.3, the lines denoting connections between the timeline and connected clips are gone, replaced by small dots on the timeline. I find the dots hard to work with; they are difficult to see and, depending on the number of connected clips, it can be difficult to determine which dot is associated with which clip. In earlier versions, these connection lines could be either enabled or disabled by the user. However, I can not find where to enable them in 10.3, if, indeed, it is possible to do so. I have searched all the menus, and can not locate a keyboard shortcut to do so. Has anyone found such a command?

If not, and you prefer the option to show connection lines, please submit feedback to Apple. Or, if you'd like to do a guy a favor, submit feedback in any event!

Edit - thanks to the ever knowledgeable Tom W. for this: it turns out that when the clip in the timeline is selected, the connection line appears. Hopefully I'll get used to this.

I think I have found a new audio trim behavior/ bug/ oversight I am not psyched about.

In previous versions I could select a range on a connected audio clip and trim it by pressing Delete.

Selecting range before delete (trim):




Pressing delete in previous versions would yield this:





Now pressing delete yields this:




(this was normal edit behavior when I would edit within audio components in previous versions, but now seems to have become standard).

It seems the only way to trim connected audio clips is by using an extend edit, replace with gap (which makes no sense because it trims like an "extract" edit and leaves no gap), or a trim start/ end command?!?! Trimming with Delete works as expected in connected video clips.

The ramifications for me are huge, especially with music editing within a storyline.

Am I missing something?

PS same behavior holds true for audio clips that have been put in their own storyline.

Yes, delete a range for an audio clip mutes that segment of the clip. To delete, Shift-Delete the range. New behavior.

screendor wrote: Has anyone tried Neat video with 10.3? Does it work? Any other well known plug in not yet updated for 10.3?

Coremelt has a new video noise removal plugin coming out. It is in development now. Will be a fraction the cost of Neat.

Thanks for the reply EditorGuy,

I understand that it's a new behavior, but consider trying to do a delete edit in a storyline with a music clip in it.

For example: You want to trim out 3 bars of a song.




Pressing Shift-Delete yields this:



This adds 2 steps to trimming audio storylines (or for audio only clips in the primary story line for that matter) from the above example because now I have to highlight the gap clip and the press delete.

I can do Delete trims to video all day long. Seems like an oversight to me.

Wrong, it's still only one step, Option-Command-Delete.