-
10.0.3 Considerably Slower, Re rendering & importing/transcoding
Is anyone else experiencing this? I read a similar thread on the Apple forums which attributed it to old projects being reconfigured for 10.0.03 of which all of mine have been so far but my computer is becoming slow almost to the point of being un workable! I’ve had to play wait on the cursor to catch up twice whilst writing this with an added beachball and freeze of music in Itunes! which along with firefox are the only things running right now it wasn’t a struggle 4days ago and trying to do anything in FCPX is even slower than it was before!
Currently seeing many clips having to re render and transcode, one 15second timelapse took about 20min to render in. If I click back into FCPX and on a clip I beachball and have to wait about 5-10 seconds each time to be able to do anything with it.
Running on a OSX Lion, Macbook Pro purchased in Aug 2011 with 8gb ram, projects running off of Seagate go flex via firewire.
I’d say on the whole it actually seems less stable than before!! I haven’t tried creating a project from fresh yet but seems like Apple really dropped the ball on QC if this isn’t limited too new projects I’ll have to jump ship as this is almost completely unworkable
-
11 Replies
-
Chris,
Don’t lose heart! I think something else is happening that is causing the slowdown. First do the basics:
1-Trash Preferences. Use this if you don’t have it: https://www.digitalrebellion.com/prefman/
2-Repair Permissions on your startup drive. Repair external drive.If you are on Lion 10.7.3 a number of folks were having trouble with the Software Update updater. Specifically app crashes and slowdowns. Download the combo updater here instead https://support.apple.com/downloads/
If none of the above do anything try one of the following:
– Move unused projects/events to unused events/project folders
– Copy a few of your clips to a new event. Disable other events/projects, see if you still get the slowdown.
– If you suspect it is an updated project issue, as a test, Export your project as an XML, reimport. See if slowdown persists.One more thing: How large is the “current version” of your event and project?
——
T. Payton
OneCreative, Albuquerque -
Chris, I am experiencing the same after the update. My render time have increased by 10x. I have to constantly re-render sections of projects after restarting FCPX every time. I have 32 gigs of ram, esata external storage, latest Mac Pro, etc… very frustrating and hoping to find a solution soon. This is adding hours of extra time to my workload. C’mon apple.
-
About to trash preferences but HDD’s are ok. It is also all events, and projects I started a new project referencing an old event and it is the same as well.
How do i downgrade to a previous version?
-
Also experiencing some alarming problems. Was trying to Render a Timelapse today shot with a 7D. Computer completely froze up twice and I was asked to “Restart the Machine.” All this is happening after I recently updated FCP X to 10.0.3 and the latest OS X update. Lost about two hours of work today and eventually had to cut and paste the timeplapse in a new project which seemed to free up the system temporarily.
I would view the activity monitor and watch the system methodically eat away at the available ram. This whole FCP X is completely mad.
Brandon Leigh
-
What OS are you on?
——
T. Payton
OneCreative, Albuquerque -
OS X 10.7.3.
I did find a trick to type “purge” into the terminal to free up all the inactive ram which is great considering I won’t have any more crashes. BUT rendering is still taking a substantial amount of time especially when adding a Lower Third !
Brandon Leigh
-
Did you install the combo updater for 10.7.3? There were some problems with the delta updater (what was in Software Update) and Apple pulled it today. If you haven’t installed the combo updater, you should do that here:
https://support.apple.com/kb/DL1484
Regarding free memory, this is a neat free little app to save you a trip to the terminal:
https://itunes.apple.com/us/app/freememory/id460931672?mt=12
Also repair permissions and trash your prefs.
No one thing in mind. I never render in FCP X. Seriously, unless you have multiple stacked effects there is much more reason to NOT render than there is to render. Rendering on the timeline is about 10X slower than rendering during export. See here:
I don’t have my broadcast monitoring up yet, so that might change my opinion regarding rendering, but frankly not rendering is one of the best things about FCP X.
——
T. Payton
OneCreative, Albuquerque -
D/L the combo and the App now. Thanks for the advice, always helps when you have clients breathing down your neck. I also found a trick for the rendering issue, if you disable (V) and enable a clip that has already been rendered it will no longer need a render. Thank you for the help.
Brandon Leigh
-
Saw on another thread someone saying about typing “purge” into terminal to free up more memory… out of pure frustration I gave this a go and… it seems to have worked! Currently running Firefox, mail, itunes, rendering at a normal speed in FCPX and no hint of slow down/beachballing/text waiting to play catch up.
My only concern would be does purging the memory cause any knock on effects too anything else in the system? As this seems to good to be true and I’ve always been wary of messing around with command lines.
-
My export of a final project has now grown substantially. The computer doesn’t seem to want to use any of the CPU when exporting from FCPX or bringing it into compressor. At best I can get it to run 80% idle. Any suggestions !?
Brandon Leigh
Reply to this Discussion! Login or Sign Up