[Ben Balser]

Where’s that statistic posted? I and using FCPX and documenting lots of bugs in 10.6.6. I see lots of issues on the various FCPX forums.

[Ben Balser]

I use Simon Says as an extension directly inside of FCPX. Very affordable, very fast, and allows for text based editing.

[Ben Balser]

Yep, seems to be a bug. Fill out the feedback form.

https://www.apple.com/feedback/finalcutpro/

[Ben Balser]

You’re really misunderstanding things here. What you are doing is not adding an “audio cross fade” but a video Cross Fade video transition, which does an automatic crossfade on the audio, also, which can not be manipulated independently of the video except in the Inspector. Thus, there’s no fade handles the command you are accessing via the menu can affect, as stated, you’re applying the default VIDEO Cross Fade, which fades audio automatically, it does not use fade handles. The menu option you’re trying to access via the menu only affects fade handles. You have to manipulate the fade handles first, to use that option.

If you’re trying to do an audio only transition, you’re going about it totally wrong. There is no bug here, you’re simply using the wrong tools.

1. Double click the audio portion of a clip to expand the video and audio of that clip so you can trim the video and audio independently of each other.

2. Extend the audio portion if desired, adjust fade handle as desired.

And yes, this has been a huge weakness in FCPX for 12 years now that Apple thinks is unimportant.

[Ben Balser]

This is not about one person’s individual experience, this is about an industry’s experience.

And, there are LOTS of users with lots of instability with FCP, and it’s full of bugs. I’m actually in process of learning to Resolve better. But Apple has stagnated it, and focused it on the YouTubers, and tossed off high end editors. I guess we just wish they’d openly admit it, rather than make promises to listen to high end editors in network broadcast and feature film. Let’s not mention it’s lack of real audio tools, etc.

[Ben Balser]

I still don’t understand. The shape of what represents a keyframe doesn’t matter, it’s still a keyframe. FCP does it the way most all other NLEs do it, with keyframes. Yes, Apple probably could make keyframing more dynamic in FCP, but they’re not horrible or difficult. Can you explain exactly what you’re trying to do?

https://support.apple.com/guide/final-cut-pro/add-video-effect-keyframes-ver8e3f20ea/10.6.6/mac/12.6

https://support.apple.com/guide/final-cut-pro/modify-groups-of-keyframes-veraca9b445e/10.6.6/mac/12.6

[Ben Balser]

Easy, two ways to do this.

First, place your playhead in the Timeline on the frame you want to hold, Edit > Add Freeze Frame (Opt-F). That gives you the freeze frame as a separate clip.

Second method is to select the clip, Cmd-R to bring up the retiming header, the Shift-H to make a hold frame. Grab the end of it’s red header and drag to adjust the duration.

[Ben Balser]

Every piece of media in the Browser has its own timeline. Select it, Clip > Open Clip. With this method you’re working on the Master Clip, so every Timeline you drop it in to will have the changes you made. <font face=”inherit”>Compound and Layered clips you can simply double-click (as with Sync and Multicam clips) to do the same thing. And even in a Project Timeline, you can double-click it to open it into </font>its<font face=”inherit”> own </font>timeline. If you do this from a Project, you’re working only on the copy that is in that timeline, not effecting the Master Clip.

So it sounds like you’re making things way more complicated than they are.

[Ben Balser]

I have found numerous bugs in the latest update of FCPX.

[Ben Balser]

What “monthly maintenance” are you referring to?