Beach ball for 2min 6 times an hr.

[Juan Peña]

No 3rd party filters. Background rendering “Idle”. I’m thinking is more of a ram issue.

[T. Payton]

Slowdowns because of compounding timeline complexity (not length) is unfortunately still an issue not resolved with FCP X. See here:

https://forums.creativecow.net/thread/335/21342

I haven’t seen any amount of RAM, CPU or GPU, or even HD speed helping. Resolution of the project also doesn’t effect this.

To find out if it is, check the size your “CurrentVersion” file for both your event and your project. AND ALSO ANY EVENT you have in your Final Cut Events folder — even if you are not accessing media from it. I have found that if any of these approaches 80MB things slow down. Can you report back on the size?

——
T. Payton
OneCreative, Albuquerque

[Juan Peña]

21.5MB for Event and 9.4 for project

[Juan Peña]

It has to be an I/O or RAM issue. I switched to proxy and it has gotten allot better. I doubt is the drives because i never had this issue with FCP 7 using these drives.

I have 6GB 3X2GB. Can I buy an 8GB or do I have to buy another 2GB module?

[Michiel De leeuw van weenen]

I think T. Payton is absolutely right about the Events and Projects.
With ‘Event Manager X’ I disabled all events and projects and worked only with the project and event I needed.
All my problems we’re gone.

I can work with original media and no wheel of death any more.

I’m working with 6GB RAM and an 2008 Mac Pro on Snow Leopard.

So the solution for me: Only use the events and projects you need at the moment and disable the others with ‘Event Manager X’

[T. Payton]

This is an unfortunate bug. The FCP team does know about it, but it wouldn’t hurt to give some feedback or even call them about your specific situation. I would request that they make a better solution for “loading” events and projects. It shows not only a problem with the database handling but also that need a built in solution for “ejecting” events and projects.

——
T. Payton
OneCreative, Albuquerque

[Tapio Haaja]

There are still some memory and CPU bugs in FCPX. Last week one day I wasn’t doing anything and my MacPro almost halted completely. I looked activity monitor and all 8 cores were used 100% and FCPX wasn’t processing anything. I could barely move my mouse pointer. Restarted FCPX and everything was running okay once again.

But yeah you should give feedback to Apple so they know they must spend some serious time with these issues.

Best
Tapio Haaja

On-Air Promotion Producer
https://avseikkailuja.blogspot.com/

[Alban Egger]

16GB RAM seems for me to be a must.

And I also played with media on an SSD and suddenly FW800-Raid0-RAIDs seem so slow…

[Loren Risker]

What does your system log say when your beach balling (console.app in the utilities folder).

If it’s a problem with your hard drive you’ll know there because you’ll be getting a lot of Disk I/O errors.

My money is physical damage on the Hard Drive. You have plenty ram.

[Juan Peña]

I’ll monitor the console to see, but I doubt is the HD.