FCP X 10.2 - Slow down with H.264 clips

I know, 10.2 is supposed to feel a lot snappier, but I just noticed the opposite. I was working with a 2 GB G-RAID full of H.264 clips in the previous version, and skimming in the browser was not bad. JKL worked fine. - On a new big iMac.

Now that I updated to 10.2, drawing thumbnails takes longer and when I try to fast forward with JKL, FCP X gets stuck and after a few seconds of doing nothing, starts to play.

I know what you guys are going to say - transcode, but that's not the point. I am just comparting the previous version of FCP X to the just released one and at least as far as H.264 clips are concerned, it feels sluggish now.

Is anyone else seeing this?

Trash prefs, see if that helps.

Same issue here with sluggishness.
As well I see the timeline playbar take up to a second or more before it will start to move.
This seems intermittent for me, about 50% of the time, and it happens after editing for a while.
I havent tried different timeline views yet to see if that matters or not.

Thanks for the tips. I did two things - I repaired disk permissions (I had just upgraded to Yosemite for 10.2) and trashed the FCP X preference file.

There was some improvement (the frequent beach ball is gone now), but - at least as far as working with H.264 compressed clips is concerned (I have a ton of them on that drive and I know I should transcode in an ideal world) - 10.2 is NOT a speed improvement. It still feels a tad more sluggish than 10.1.4 (with the exact some drive full of H.246 clips)

Just my observation.

The same here, very disappointing, maybe it's just a childhood problem and simple patch could fix it...
The Manifesto plugin generator works strange as well - when used inside storyline clip it just... does nothing, disappears.
Connected to primary storyine - works as usual

Hey Markus, What kind of clips are they? h264 .mov files I've made via compressor work fine here. Is there a specific clip type? Are they camera files or ??

They are H.264/AVC ecoded quicktime movies in 720p. Files we got from a client. We just needed to look for and grab a few shots, so there was no way I would go ahead and optimize over 1 GB of these files. FCP X worked fine, I just noticed a slight slow down compared to the previous version. I am aware that this way of working is not what you'd normally do.

MarkusW wrote: They are H.264/AVC ecoded quicktime movies in 720p. Files we got from a client. We just needed to look for and grab a few shots, so there was no way I would go ahead and optimize over 1 GB of these files. FCP X worked fine, I just noticed a slight slow down compared to the previous version. I am aware that this way of working is not what you'd normally do.

Gotcha.. was just asking because there's apparently some issues with AVCHD video. Dunno if if it's a plugin thing or something else. I've been getting really good performance, but I have heard of others with similar issues to yours. I'm a lot of help huh?

Have you tried to make your H.264 clips to prores first, then reload them into FCP? Because even if you don't do such job, fcp will help you do it at the backstage, that's may why it may take some time to importing those clips.

Thanks for the suggestion - but under normal circumstances I would not work with over 1GB worth of H.264 files. If this was the footage for a bigger project, I would transcode. But all I had to do was search for some shots and export them. Transcoding would have been overkill (and not worth the huge extra storage requirements).

It was just a speed observation.

The same situation here...
I've noticed several bugs in the software:

1. Spinning ball after almost each operation on timeline. It happens not immediately after start of FCPX, growing slowly until the work is impossible.

2. Placeholder text bug - can't see any text on placeholders

3. Manifesto bug. When placed inside secondary storyline, the Manifesto generator becomes invisible... Outside as a separate clip - everything is OK

my specs: Macbook Pro 8,2 2ghz I7 quad core, 16 GB RAM, 1 TB SSD.
reverted back to 10.1.4, eberything went fluent again...