Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

FCPX 10.1 Very slow on iMac and lots of spinning beach balls

I have noticed since I have started to use FCPX 10.1 on my Late 2012 iMac (32GB RAM, 680MX Graphics, i7 quad core, thunderbold Arecca Raid) I am getting lots of spinning beach balls and things are generally slower.


I am really hoping Apple thought about people who cannot affored a Mac Pro, and ensure the performance is also good on iMacs, but unfortunately I am seeing a drop in performance compared to 10.0.9.


Has anyone else with an iMac noticed this?

Posted on Dec 22, 2013 5:37 AM

Reply
200 replies

Feb 27, 2014 5:53 AM in response to remoran

When I upgraded (more like down graded) to 10.1, all my 300 or so video projects/events became amalgamated into two very large 1.2 and 1.6 TB files. This was the start of all problems.


Then I had to disconnect my two USB 2 drives that worked fine up until this point, and copy the files to the internal hard disk for faster access. This after Apple suggested I buy an $800 Thunderbolt drive.

After two calls to Apple Care, we determined that the software and/or hardware simply could not handle the large file sizes the conversion created. Notwithstanding the fact that FCP X also lost some connections to my files, so that created a lot of work for me as well.


The solution (or work around) is to create a brand new library file for each project, and keep the file sizes as small as possible.


It would have been nice if the conversion process was a little more helpful, and did not bring my system to a complete stop for weeks now.


On the call with Apple, they sort of implied that I might want to look at the Mac Pro. I will not be doing this if they continue to treat the FCP community like they do now, and did in the FCP 7 mess. What I will be doing is switching to Adobe Premier Pro on a PC, and leave the Apple platform completely.

You can say what you want about PC's, but at least that PC community doesn't charge me $900 for a $60 motherboard if I need one, and Adobe seems to have a little more common sense and respect for their customers. And now that you can get everything that Adobe makes for only $50 a month, I am on board.

Feb 27, 2014 6:13 AM in response to Michael.Poczynek

Michael.Poczynek wrote:


When I upgraded (more like down graded) to 10.1, all my 300 or so video projects/events became amalgamated into two very large 1.2 and 1.6 TB files. This was the start of all problems.


The *same day* 10.1 came out there was detailed information on how to handle such large content. Granted, most was not from Apple, but from knowledgeable people like Philip Hoggetts (author of Event Manager X, which he turned to a free application that day), and Ripple Training (who published free videos with great advice on how to handle the upgrade).



Then I had to disconnect my two USB 2 drives that worked fine up until this point, and copy the files to the internal hard disk for faster access. This after Apple suggested I buy an $800 Thunderbolt drive.

After two calls to Apple Care, we determined that the software and/or hardware simply could not handle the large file sizes the conversion created. Notwithstanding the fact that FCP X also lost some connections to my files, so that created a lot of work for me as well.



It is bad that some connections were lost, but frankly: did you expect smooth sailing when you have a 1.6TB library?!




The solution (or work around) is to create a brand new library file for each project, and keep the file sizes as small as possible.


It would have been nice if the conversion process was a little more helpful, and did not bring my system to a complete stop for weeks now.



There is no need to create a library for each project. It may even be possible to work with a single library for all your stuff - but here comes the concept of "external media"...


There is also no reason why the update might have you stop for weeks - unless you opted to immediately delete the original events and projects. It would be just a matter of going back and redoing the update the right way...

Feb 27, 2014 11:50 AM in response to alexgrainger

Hi,


I haven't touch FCPX the last 4 month, and what a bad surprise.

I have a mac mini mid 2011 (16 Gb Ram and 2 512 MB SSD) and I was using FCP X since the release and it was working fine. I have my FCP Project on an external 4 TB FireWire 800 G-RAID Hard drive.

I ran FCP X 10.1.1 for the first time this week. FCP updated for hours my project and reorganized it. it took it 12 hours to dot it. The result is incredibly bad.

If I want to back up manually my different project on my back up hard drive, the way it is, make things, more complex.

But this is not the worst. The software is completely broken. It's impossible to edit anything. now.

I'm having green screen even with proxy and transcoded media. I can't believe it. The software freeze all the time. FCPX as soon as I touch a reel is using the the full load of the CPU even if I'm not doing anything.

I'm really disappointed.


What is going on with the software Apple?


I want to go back on to the previous version of the software via TIme Machine. Do you think, this will work? I'm a bit worried the library might have data for the 10.1.1.

Feb 27, 2014 11:31 PM in response to alexgrainger

After slow performance, cursor not responding on time line, spinning wheels, delayed playback on timeline and even crashes now and then I decided to do what's possible and hope for the best.

Even if you have ,as I, an old 2009 mac pro its not the end of the world.


First the results:


No problem with spinning wheels almost direct playback on timeline..

Very good response when moving cursor over timeline.

Fast loading of projects loading tumbnails and waveforms fast.

Render much faster, a clip with some filters old system 29 sek now 5 sek !

Analyse for stabilization now very fast.

Analyse a clip for optical flow earlier minutes now 18 sek.

And a much faster backup/archive system.

No chrashes.


For you to compare: 10 sec clip with filters 50sTV/AgedFilm/BokehRandom/Combat/GlassBlock

renders now in 18sec. But also unrendered clips seems to play much smoother now.


This is what I have done:


Before: Mac pro early 2009 2x2x66 Ghz QuadCore Intel Xelon.

12GbRam.

Radeon 4870.

Cal Digit VR external disk in Raid 1. Speed about 100 too 120 MB/sec.

OSX 10.7.5 and FCPX 10.8


After:

Mac pro early 2009 2x2,66Ghz Quadcore Intel Xelon . OS 10.9.1 FCPX 10.1.1 installed on an empty disc.

32Gb Ram from OWC US.

Amd Radeon 7950

Caldigit Esata/USB 3.0 card FASTA 6GU3 Pro. (gives you two Esata and 2 USB 3.0)

Buffalo Drive station DDR HD-GDU3 2TB (Single disc give you read about 220Mb/sec)

I use my old CalDigit (impossible to change Raid 0) as it is in Raid 1 as backup disc with Software “Back Ups for Final Cut Pro”.


Now working with a quite large project where the spinning wheel was my daily friend just to notice it seems to be buried in piece.

Finally some experiences: Always check your available memory with “activitycontrol” (translation from Swedish). Every time I import from camera (a Panasonic GH3) it eats it all, all 32 Gb. And at some other occasions. It's not enough to restart FCPX to free memory you have to restart the computer. Out of memory slows everything down and this problem is still there even if I can handle it quite easy.


Here in Tranås in southern Sweden the snow is gone, life is on its way back, daughter in London said water is going back there and its friday which gives me a reason to buy a steak and a bottle of wine. Isn't life beautiful.

Mar 1, 2014 12:18 AM in response to alexgrainger

Today I made a new library & moved all 1tb of media into it after doing so, it wanted to re render the whole project so I let it render surprisingly it rendered under an hour but after rendering I tried to use it limiter filter on a 1 minute clip I came across a new problem the first 15 seconds I could not hear any audio with the filter when it was on but as soon as I turned off the filter audio was back on. Ok continuing Edit I tried copying that clip after pressing command & C on the keyboard I was hearing the audio double this was also where the Beachball was coming and going. Just got frustrated I called Apple FCP department and AFTER TALKING TO THEM FOR 40 MINUTES THEY suggest me to talk to the head management but unfortunately they were gone for the day so I am supposed to call them back and talk to them in the morning will let yous know guys what happens, but please if someone has any suggestion I would be happy to try FYI I have the 2014 Mac Pro 12 core 1 TB 32 gig ram 12 gig VRAM. With promise Pegasus R 6 12 tb.

Mar 1, 2014 10:46 AM in response to alexgrainger

I've been a Mac user since the old SE & IIci days. I've given much of my time & $ to Apple and have always been a strong supporter.


My latest purchase was a fully loaded quad core which I use exclusively for editing. I LOVED FCP but today, Maverick is clearly the issue as everyone's previously said (same issues myself).


This is a forum & not a debate, as that will only delay Apple's going into fix mode. The iPhones & iPads are nice but this could quite possibly be the end of the Apple pro user if not properly addressed now.


Does anyone have any "usable" feedback from Apple, as previous comments in this thread have come up dry?

Mar 15, 2014 4:46 PM in response to alexgrainger

Hi Guys...

Im in the same boat, but with a MAc Pro....3,1....24 gig ram, 8 core 3.2


Getting the slow movements around time line, and zooming,etc.....


Working with long projects ( 50 mins).....


I thought it was my Graphics card GTX 680 ( 4 gig) being a CUDA card......

BUt after reading this post, Im not so sure.....


Ive been battling with getting a new MAC PRO, but £4000 and it may still be teh same......


Im now really thinking of dumping FCX and moving over to Premiere..... which will be a sad day.....

FCPX 10.1 Very slow on iMac and lots of spinning beach balls

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.