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

EditorGuy,

You are a genius!

Has that command always been there or have I been ignorant of it for the last 4 years?!

***sorry for the feedback report Apple*** :blink:

I just purchased version 4.2.2, upgraded from NeatVideo V3. I emailed them and they told me that their latest version works well in FCPX 10.3. I Just worked on a project and applied NeatVideo and it took a long time to render, but after that the playback is fine. I'm on El Capitan.

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?

Running Neat Video 3.6.1 with no issues under Final Cut Pro X 10.3 and latest OS.

Update on my issue with live adjustment of Channel EQ in 'final mix' CC - this appears to be a library/project issue. This project was started in 10.2.3 and there is clearly something in it that makes it sub-optimal in 10.3. There is a workaround - play the role that you are adjusting in the Inspector. The adjustment is now possible in real time and the pictures from the Timeline play in the Viewer. Even with this restriction it was worth converting the project to 10.3 to gain access to the mixing features for the final stage. Outstanding work FCPX team!

I am having issues with FCPX not loading the current project on re-start when using a user defined workspace which does not include the Browser. The Library is still open but nothing is selected and the interface is empty. I'm having to open the Browser window and re-open the project manually. Anyone else having that?

The audio meter gets stuck on occasion too. Turning it off and on again wakes it up. Although, on one occasion, the small version under the Viewer disappeared. I could still click on it even though it was invisible.

This is observation, not carping. The use of screen real estate and the extra functionality, particularly in the sound department, is a huge step forward. And who could argue with the upgrade fee?

Thanks to those sharing the love from the development team in Cupertino. The silence is sometimes difficult to live with so the insight into what's happening and the level of commitment is very welcome. Particularly Ben Balser - great blog - thank you.

bcassin wrote: EditorGuy,

You are a genius!

Has that command always been there or have I been ignorant of it for the last 4 years?!

***sorry for the feedback report Apple*** :blink:

No, that's brand new shiny 10.3 goodness, buddy.

ianstubbs, what are your hardware specs?

Try this, export an XML from the Library you had in 10.3.
Create a brand new Library.
Import that XML into the new Library.
See if that helps to fix things up.

Speaking of XML, remember when you used to import an XML it crated a whole new Event? Now you can import a Project XML into and existing Event, you get a new Project, not a whole new Event.

Plus, there are now "XML Objects". This allows third party systems supporting it, to have drag and drop functionality for specifically designated XML Objects. This was made primarily for DAM/MAM systems. So once they adopt it, moving metadata between FCPX and those management systems becomes more tightly integrated, faster, easier user interfaces to be designed. I'm sure some other developers will figure out ways to implement this into new third party apps we've not yet imagined. But just so you know, yeah, the "Apple Pro Video Team" (as Apple officially calls them) is seriously working hard to create solid professional stuff.

They are also pushing hard to get the FCPX 3rd party developer tools to allow third party plug-ins inside of FCPX to take over the Touch Bar. THAT could be really cool, but ONLY if someone gave me a brand new late 2013 15" MBP. Apple said my good looks and boyish charm wasn't enough to get a freebie... (sigh)

Has anyone noticed or figured out the different in/out setting when playing through the timeline?

When playing on the main storyline with no clips selected I used to be able push "i" to set an in on the primary storyline or, "o" for out. Now it seems that I and o don't do anything unless I clip a clip on the storyline first and then push I or o while playing trough that clip. Has anyone figured this out? I have major muscle memory tied to that functionality, left over from avid days. Hoping I'm just missing a new possibility

That's odd, it didn't change, works for me. Nothing selected, hit space bar to start paling, i makes an In point on the Primary Storyline clip, o makes an outpoint. Should work.

Try trashing prefs. Also, is this an updated project, or a new one? I've seen a couple of really minor issues with one or two updated projects.

EditorGuy wrote: That's odd, it didn't change, works for me. Nothing selected, hit space bar to start paling, i makes an In point on the Primary Storyline clip, o makes an outpoint. Should work.

Try trashing prefs. Also, is this an updated project, or a new one? I've seen a couple of really minor issues with one or two updated projects.

It is an updated project. Will try that tomorrow at office. I just tested on my home computer and it works here like you said. Thanks!

I like the new 10.3! But in 10.2 and the versions before there was that little button underneath the viewer that showed that background tasks where running and the percentage of it. I understand that this "button" went in the upper left corner, but I can not see any percentage unless I click on it. Is this just me.. am I missing something?

Jonathan Levin wrote: 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

It just happens on El Capitan. In Sierra everything is ok.

What hasn't changed is that Apple hasn't given us curves for scaling keyframes. This is incredibly weak and puts FCPX behind all other NLEs in transform abilities, including Final Cut Pro 4. Who at Apple is responsible for this weakness? I am unimpressed.

At least they seem to have fixed the audio keyframing bug. That blows me away. Something concerning keyframing was fixed?

Thanks Jonathan. This fixed it for me on my Mid 2012 MBP.

After installing Sierra, FCPX doesn't remember my window layout... Unfortunately this hasn't changed in 10.3. Have to spend time rearranging things everytime I open the app
Saving a workspace doesn't help either... I have two monitors and want the viewer on the MBP's monitor and everything else on my second monitor. But FCPX now defaults to having the viewer on the second display...

Yes, looking forward to that but in the meantime have projects that use Neat Video and nee to be able to use it to upgrade to 10.3.

A number of changes to the UI were not welcome. I suppose the ability to customize the layout is a plus, but I find myself having to look around for familiar items in unfamiliar spots. I am annoyed that the line marking the break from one clip to the next is not more distinctive. Audio fade ins and outs are also not as easy to see with the new "dark" interface. And why did they have to bury the horizontal time line "zoom" feature in a menu. When adjusting exposure levels in the Color Table, the text for the Color and Saturation tabs disappears. And what's with the barely-visible "dots" that replaced the red lines indicating rendering is taking place?

Overall, in the latest release of macOS Sierra, FCPX 10.3 seems to more or less work as it should. In fact, it seems to be speedier right now than 10.2.3 in El Capitan. (I am using a base-model 15-inch Retina MacBook Pro.) Core Melt Lock & Load is working for me. I managed to stabilize several short clips using Stabilize and Smooth Shutter with no issues.

What is "scaling keyframes"?

cyuill2015 wrote: A number of changes to the UI were not welcome. I suppose the ability to customize the layout is a plus, but I find myself having to look around for familiar items in unfamiliar spots. I am annoyed that the line marking the break from one clip to the next is not more distinctive. Audio fade ins and outs are also not as easy to see with the new "dark" interface. And why did they have to bury the horizontal time line "zoom" feature in a menu. When adjusting exposure levels in the Color Table, the text for the Color and Saturation tabs disappears. And what's with the barely-visible "dots" that replaced the red lines indicating rendering is taking place?

Overall, in the latest release of macOS Sierra, FCPX 10.3 seems to more or less work as it should. In fact, it seems to be speedier right now than 10.2.3 in El Capitan. (I am using a base-model 15-inch Retina MacBook Pro.) Core Melt Lock & Load is working for me. I managed to stabilize several short clips using Stabilize and Smooth Shutter with no issues.

Allot of things where moved which have easy access with shortcut keys.
The only two tings that really bug me are the Color and Speed changes. But looking at Interface it actually should have been right by the Crop and scale tool. So I see it as a fix.
the other option like Sharing (similar to Premiere Elements) and import plus key working could have stayed where they are.

Regarding to the Timeline function I welcome it for more timeline space and no need thanks for short cuts.
I beat when asked experience editors what would like more more real estate or the zoom tool. I think more timeline wins.

EditorGuy wrote: What is "scaling keyframes"?

Keyframes set on the scaling parameter. Ease-in/out is not allowed. Likewise on the rotation keyframes ease-in/out is always enabled and cannot be disabled. Apple can't figure out how to do it, I presume. Either that or people who use FCPX do not normally do complex projects which would make such features desirable like they are in other NLEs.

Here's an example. This is Adobe Premiere:



By right clicking on a keyframe in the "inspector" the editor is given glorious control over how the movement of keyframes is handled. FCPX cannot do this. FCPX is less able than Premiere. If you want more features, gotta use Premiere. I keep hoping Apple will step up their game, show some semblance of actual competition. This is something that should have been in FCPX 10.0.0. Apple clearly does not desire giving editors who choose Final Cut Pro such control. Apple clearly feels it's customers do not desire such control in their NLE. And like I was saying, maybe they don't. Maybe FCPX is not the NLE for complex projects which would benefit from such control. Round-tripping to Motion is not a solution or an excuse.

Although on a multicam project I can drop a classic dissolve from the Transitions panel, the same cross dissolve is not available as shortcut CMD-T and that command in the edit menu is greyed out. Was this like that in 10.2.3 ?

On my previous multicam edits, I only had cuts to take care of, so without the ability to look for that on another not updated machine right now, I thought that perhaps anyone here with some multicam experience could clear this up.
Don't see any justification for that shortcut being greyed out.

thanks for possibly enlightening me.