FCPX 10.2.1

10.2.1 released today...

WHAAAAA?

And "Disproportionate Pictures" had no time to create a "10.2.1 PRE-RELEASE DISCUSSION"?

Pull it back, Apple! Show some respect for the fans! He deserves to open his classic threads before an update!

LOL...would be great to get a 10.2.2 feature update at WWDC.
Come on Apple. ROLES....

Feature update? NO that's exactly what we don't need. We need Apple to fix the bugs that already exist, not add more features making the app even more buggy than before.

More bug fix releases please. FCPX doesn't really need any new features at this time. I'd rather have a good working and dependable app than one with lots of glitz and glamor that works like a horse's ass.

Redifer wrote: Feature update? NO that's exactly what we don't need. We need Apple to fix the bugs that already exist, not add more features making the app even more buggy than before.

More bug fix releases please. FCPX doesn't really need any new features at this time. I'd rather have a good working and dependable app than one with lots of glitz and glamor that works like a horse's ass.

True, but why not both bug fixes and features???

daviddelreal wrote: 10.2.1 released today......

oopd, haven't even updated to 10.2.0 yet (never update in the midst of a project etc etc ...) :ohmy:

daviddelreal wrote:
True, but why not both bug fixes and features???

Mainly because there are only so many people who work on FCPX and only so many hours in the day to code and test. Apple seems to care less about fixing bugs and more about adding new features which often have brand new bugs.

I guess that's why this bug fix update came out so fast...

And it doesn't even address the lagging timeline or keyframe bugs. I imagine those are things that they will NEVER fix.

Redifer wrote: And it doesn't even address the lagging timeline or keyframe bugs. I imagine those are things that they will NEVER fix.

Sorry, what are the keyframe bugs?

Timeline performance with 10.2 is much better for me. When I get a bunch of title clips loaded I still see a little lag but nowhere near as bad as 10.1 was.

Keyframing is a little weird sometimes but the things I use keyframing for in FCP aren't all that complicated. That S-curve nonsense has to go. Proper easing is really the main thing I ever used in 3D or in AE and I don't think it's implemented well in FCP X. I wish it was more like Motion with a true keyframe editor and interpolation controls.

From an aesthetic point of view I can't imagine what kind of keyframing people are doing in FCP that causes so much trouble. Do we need a bunch of stuff flying around the screen like the old days of hardware DVE?

canelson wrote: Sorry, what are the keyframe bugs?

Park your playhead somewhere on the timline. Now in the inspector mark a keyframe. Sometimes (seemingly at random) the keyframe will not be placed where the playhead is but many frames before or after it. This is especially obnoxious on audio tracks when adjusting levels. Also sometimes between keyframes when moving an image, FCPX will make up its own position inbetween them even with the two keyframes are at the same exact value. So instead of your image staying still between the keyframes, the image will move around for no reason whatsoever.

Also you can't control "smooth" or "ease" for all keyframes. But that's not a bug, it's just piss-poor design.

Gonna take a look at that when I get back home. Thanks.

@Redifer

The jumping around you're referring to is not random at all so I wouldn't see it as a bug.

If you drag the playhead to position and then create a keyframe in the inspector and the playhead is on a subframe then it jumps either to the beginning of frame A or to the halfway point between the beginning of frame A and the beginning of frame B. That is where the keyframe is created. It always jumps to closest of those two points to the left. It does not jump to the right.

If you use the arrow keys to navigate from frame to frame you are always at the beginning of a frame and the playhead will not jump.

The image moving around between two keyframes when it's supposed to be static is usually due to one of the keyframes or the other being smooth rather than linear.

For the keyframe issue, I have seen this many times as well.
The keyframe gets created many frames and seconds off.

I have seen it as well create a keyframe beyond the point of a trimmed clip!
So the keyframe is created in an area that is trimmed off the timeline.

anickt wrote: The jumping around you're referring to is not random at all so I wouldn't see it as a bug.

oh, it's definitely a bug.

anickt wrote: If you drag the playhead to position and then create a keyframe in the inspector and the playhead is on a subframe then it jumps either to the beginning of frame A or to the halfway point between the beginning of frame A and the beginning of frame B. That is where the keyframe is created. It always jumps to closest of those two points to the left. It does not jump to the right.

This isn't what I'm talking about. I've seen it jump to the right on the order of over a second away from where the playhead is. I have also seen it jump to the left on the order of around a second away. Maybe even more than that. I hope Apple doesn't see the issue as you do because the problem is real. I'm guessing people who don't see it don't really do much keyframing. They may think that they do but I don't think they do. Otherwise they'd surely run into the same problem.

anickt wrote: If you use the arrow keys to navigate from frame to frame you are always at the beginning of a frame and the playhead will not jump.

This is the only workaround that I have found. Park your playhead, bump one frame ahead and then back one frame and then place the keyframe. It's annoying and I should not have to do this. The keyframe should be placed on whatever frame I have displayed in the viewer.

anickt wrote: The image moving around between two keyframes when it's supposed to be static is usually due to one of the keyframes or the other being smooth rather than linear.

Again, no. It moves way beyond whatever curves could be there. Like it moves waaaaay up and then back down for no reason. Motion doesn't do this, but FCPX will. Also even if it did have a curve, it's curving to the same exact value so it shouldn't move at all. And EVEN THEN what if I want a curve on one and but not the other? I should be able to do this if I so chose without FCPX going insane. You can't explain a bug away no matter how much you love FCPX. All the bugs I report are legit.

Redifer,

Can you put together a video showing the bug? I think it would make things a lot clearer.

I'm not really sure what's unclear about it but here you go. The timeline here isn't even zoomed in very far and the keyframe ends up quite the distance from the playhead. It doesn't happen all the time, it seems to be at random.

Super annoying. On my machine the keyframes never appear on the right, though, they appear left from the playhead. Which sucks even more if when on the beginning of a clip because it means you have to extend it left, reposition the keyframe and then shorten the clip again. This bug has been around for a long time and yes, it sucks badly.

…This bug has been around for a long time .…

Never noted it, tried a minute ago, with 48kHz.aiff, with 44.1/VBR.mp3 ... no, the dot appears right on spot ....

That is the worse case of a bug:
repeatable but obviously just under some circumstances ... define 'some' :lol: