Performance issues with 10.0.7

I've been experiencing a slowdown in performance since I updated to v10.0.7. Just wondering if anyone else is experiencing anything similar. Same projects/events are loaded; basically nothing has changed except I went from v10.0.6 to 10.0.7 and now things appear to have slowed. Playback seems to be "jerky", rendered transitions are slow, just a general degradation in performance. I'd be interested to learn if anyone is experiencing similar issues.

I've noticed an increase in performance.

What are your hardware specs and OS version?

Really?! Hmmm...latest version of MT Lion, Mac pro with 32Gb RAM, SATA RAID Hard Drive, Nvidia Quadro 4000...really doubt it's my system. Never had the problem before and Adobe Premiere flies.

You're running a CUDA GPU, not an OpenCL GPU. Apple wants OpenGL, Adobe wants CUDA. You're comparing apples to onions, in a way. You're not getting the GPU support out of FCP X and Motion.

I guess I understand that but the board hasn't been changed and I got better performance with fcp 10.0.6, using the CUDA board. So, while I accept that Premiere benefits from CUDA and the Mercury Engine, I'm not sure that it explains the degraded performance between 10.0.6 and 10,0,7.

No answer why you seem to experience these things. My point was that with a CUDA card, you're not getting the best performance out of FCP X anyway. It doesn't work with CUDA cards, so the GPU you have has never boosted FCP X at all.

I use an OpenCL card and have seen no performance change between 006 and 007. Only thing done were some bug fixes, nothing that would effect performance. Performance from 005 to 006 was somewhat better, but from 006 to 007 there is no performance increase at all.

If 007 in fact degrades performance, the only thing to look at is hardware compatibility. Unless someone has another idea of what to look at. I'm not seeing anyone complain of slower performance between 006 to 007. So, I'm just guessing...

Drive space? Do all drives have enough free space? Events and Projects? Any increase in how many are loading up?

If there are no other issues, all I could think is some bug fix in 007 needs GPU processing more (such as with exports and renders) than it did before, and not having an OpenCL GPU simply makes it stand out more. Again, without more data, I'm just guessing.

I appreciate you're input very much and I'm the first to admit that I'm not an expert when it comes to hardware. That said, 006 ran without a problem on my system using the CUDA card and 007 is ridiculous. Renders are incredibly slower and if I look at Activity Monitor during a render FCPX is using at times 500+% of the CPU. That said, if you look at the "approved" video cards for FCPX from Apple's own information, there are CUDA cards on the list: Nvidia Quadro FX 4800 and 5600 for example. My understanding has been (and from the board specs)that CUDA cards also support OpenGL.

Not all CUDA cards support both CUDA and OpenGL 100% both at the same time. SOME very few CUDA cards support OpenGL, and to varying degrees. The Quadro FX 4000 is not on Apple's list.

So what about disk space, third party plugins, etc?

I see that my card is not on their list, although a comparison of specs between the nvidia cards that are and mine make it hard to see what the difference is. But, again, I had absolutely no problem with version 006 and this card. Disk space is definitely not a problem, and yes I have a number of third party plugins installed but nothing added since I went from 006 to 007. I have made only two changes to my system: (1) I replaced an old cinema 30" display that I was using as a second monitor driven off the 4000 display port (I couldn't get very much resolution from it but FCPX worked just fine with my MultiSync PA271W as the main monitor and the cinema display as the second monitor; in fact I ran the viewer on the second monitor). I replaced the cinema display with a 24" Viewsonic display also running off the 4000 display port but at a much higher resolution), and (2) I went from v006 to 006 for FCPX.

I meant I went from v006 to v007

I knew I wasn't going crazy!! I decided to trash FCPX along with all supporting files, etc. and did a clean install of the program. Problem solved! Not a board issue. Thanks for all your help and suggestions; I just knew that everything was running just fine with the hardware I have before I went to 007.

FWIW..I never had to reinstall FCPX, but I do notice that the FCPX preferences need to be trashed a bit more in 10.0.7 than they ever did in 10.0.6 (at least for me).

I have to say that the last upgrade on my 3 mac (mac pro 2008, imac 27 2010, mbookpro 2011) is less responsive and stable than the previous.

The spinning beach ball is coming out again often. There is a topic on apple user forum and many are experiencing these problems.

After months I feel like I have a beta code on my hands and is not a good feeling.

Trashing pref helps but just for a while.

Add that some plug in behaves not well (like some split screen).

I still have the compound clip timecode bug. The duration on the event browser is different (much shorter) than the real duration in the timeline.

Hope the give us a much robust code in the near future.

I'm having the same problem with certain plugins. Particularly split screen. And I had no problem at all before the upgrade to 10.0.7...WITH THE IDENTICAL HARDWARE CONFIGURATION. I am convinced that something got broken between 10.0.6 and 10.0.7. I have a documentary project I'm working on that incorporated a split screen effect using Crumple Pop Splitscreen. It worked perfectly fine under 10.0.6 and now won't playback correctly under 10.0.7. I've even reinstalled the plugin and started over...no change.

I'm not sure if this will help you, but under 10.0.6, I experienced a lot of problems with background rendering; from the outside, it looked to have very bad cache management bugs so cuts in the timeline that needed rendering could get mixed up. I often had to restart 10.0.6 to get it to show me the correct rendering of a clip part. Eventually, I deleted the project's render products and turned off background rendering. Things were better.

In your case, if the render products got somewhat mixed up under .6 for you, I could see .7 stumbling over it. Try File/Delete Project Render Files on it.

If the plug-in isn't working at all, it could be affected by the plug-in API change they made; hey who needs backward compatibility anyway...