Constantly beach balling/hesitating in 10.1.1

Hi all,

Doing an edit for a client who's just updated to Mavs and 10.1.1 on a 2011 iMac i7/20g RAM/RadeonHD6970. Footage is native from C300, with a little GoPro and 5D thrown in for good measure. Not optimised.

What I can't fathom is why the disks (in this case a G-Raid Thunderbolt 8TB, only one library on disk) are constantly writing - with the concurrent beach ball - whenever I do anything. Sometimes I'll get a flow where 3 or maybe 5 operations in the timeline are all fine - then the ball appears again. Can take maybe 5 or 10 seconds to clear. App Nap is off BTW.

Any suggestions?

Ta

J

How is that RAID connected to the iMac? If it is Firewire, that's your bottleneck. You may have to go the Proxy route.

Also, not the greatest GPU, so optimizing would be the way to go.

You're using all Long-GOP footage that takes a lot of GPU/CPU to process. Optimized or Proxy media would take care of that.

It's Thunderbolt so no bottlenecks there. I've cut C300 footage in this system before with no issues - that was on ML/X10.09 though. It's since the upgrade to Mavs that this seems to have happened... I'll try optimising and see what gives.

You should see performance gains with 10.9 and FCPX 10.1. That is odd. Personally, I'd run Disk Warrior to repair all the drives, see if that helps.

Make sure background rendering is unselected in your FCPX preferences. Try removing the unoptimized GoPro clips from your project. A bad plugin or effect as well as a bad render file can often cause the beach ball to appear. Try deleting render files for both project and events and restart Mavs. Trashing FCPX prefs and rebooting (or better yet powering down for 2 min) and starting your Mac back up. might also help. Repairing your system drive permissions should also be tried. Good luck.

dgwvideo wrote: ... Try removing the unoptimized GoPro clips from your project...

This is good advice. GoPro material is computationally intensive to render. As a test, remove those or copy a sample of the non-GoPro stuff to another library, delete render files, then try it. If it's fast there, add a few GoPro files (unoptimized) and see if it slows down. If yes, optimize them.

Alternatively if you don't have much GoPro stuff, in the original library, event browser, right click on each GoPro clip and select Transcode...Optimize Media.

Just a quick question, was the project updated from 10.0.9 by any chance? I'm agreeing it could be the go pro footage, but I have had several clients have your symptoms with updated projects.

No, new project from scratch. Will try the GoPro trick when I get the chance. It seems to definitely be writing lots to the drive; not rendering as I always make sure that is off.

I'm seeing this too.