Stop shouting, calm down, and you'll sort the problem out - ranting is not exactly helping is it?
Go to Preferences in FCP X and turn off background rendering.
Have you tried trashing your preferences?
Unexplained faults like this can often be fixed by clearing out FCP X's preferences (for some reason, they get knotted up from time to time).
Download Digital Rebellion's Preference Manager (free, simple to use, and perfectly safe, both to download and use).
With Preference Manager, you can backup the Prefs when FCP X (or any of the Apple Professional Applications) are working normally. Then when either of the applications are acting strangely, Trash the Preferences, then Restore from your backups (just a mouse-click).
If you trash the prefs and don't restore them, you will need to manually restore all your FCP X settings again, so it's a great idea to backup Preferences from time to time when FCP X is working well, then your backups are up to date.
Doesn't fix every problem, but it fixes a lot.
FCP X runs very well (not perfectly, by any means) on my 2009 MacPro 2 x 2.26 GHz Quad-Core Intel Xeon with 16 GB RAM and ATI Radeon HD 5870 1024 MB
First, check the spec of your iMac against the system requirements:
Particularly your graphics card. If it's listed here, it's not suitable:
If you are getting crashes, there is some conflict on the OS. Create a new (admin) user account on your system and use FCP X from there - if it runs a lot better, there's a conflict and a clean install would be recommended.
Other ways to improve performance:
Create optimised media.
Hide Waveforms at all times when you don't need them (both in Browser and Storyline / Timeline). They take up a lot of processor power.
Create folders in the Project library and put any projects you are not working on currently, in there. (Twirl it closed to hide them).
Move your Projects and Events to an external HD (make sure it's formatted OS Extended - with journaled on or off) and run from there.
The biggest single improvement I saw in performance was when I upgraded the RAM from 8 GB to 16.
It depends what the problem is. If the application crashes it's a good idea to do, because the preferences, which are created/resaved on quit, are almost always corrupted. If you read the forum extensively you'll see many instances in which it has overcome problems, especially when the application does not appear to be working normally.
As for the OPs problem, I can't say I'm seeing anything that's reported, nor have I heard that kind of report elsewhere. The render problem sounds like a permissions problem. The poor playback may be related to the render problem, if playback is of an unrendered timeline. Don't know anything about the format or media so not much to go on.
What Emilia is referring to, and the reason my reaction is valid is simply because there are those who are quite fed up with some people who think they can solve all issues by suggesting things like "trash your prefs" and "optimize your hard drive" etc.
And you know what? In SOME cases this might be a so-called "solution". But if you actually READ what I said is the issue here, it has nothing to do with ---graphic cards --- preferences ---- hard drives ----etc. It has to do with the UPDATE.
I'm not here to try and make buddies. I posted to WARN people who might have similar work created in previous versions and save them a lot of grief and potential disaster.
UPDATE TO ORIGINAL POST :
There is even MORE issues with this update than I originally posted. I found that many of the attribute of text/titling throughout my projects are completely gone with the new update. Vanished! But , if I switch back to 10.0.2 they are there as intended. And this is only the things I've discovered so far.
Preferences, hard disk , graphics card (how can I have a problem with graphics card when I said in the beginning I had the latest MBP , ram and thunderbolt drives for that matter as well).
So MAYBE this might be something for someone to be cautious about. Or, of course we can take the plunge and just use the advice like "trash your preferences" to save the day! Get real.
Why do you call it a myth Emilia ? This little "trick" has helped me many times both with FCP and FCPX but of course it has not solved all problems.
And that is
How is this for simplicity.
Everything is perfect.
Upgrade to 10.0.3
All kinds of issues arise with exactly the same EVERYTHING as was working perfect on 10.0.2.
And it is clear that a major change takes place to projects because prior to the final processing of loading up the app, there is a "conversion" that is NOT backwards compatible with 10.0.2 that must take place to all your projects.
After this conversion of the 10.0.2 projects to 10.0.3 ones - this is where all the issues arise and they are not all just SPEED issues, they are also other issues such as missing attributes etc.
Only way to fix that is to REDO things. And if that is a chance one wishes to take - fine. Just be warned. And warning is something SOME people consider helpful.
Well that was a polite, and helpful reply....
Did you read this post? It has to re-render EVERY time upon re loading of the app.
And a host of other issues that never get solved by taking a lunch break.
And because your project seems to work for you, it must be A-OK for everyone elses.
This is the kind of answer that is about as useful as "trash your preferences."
It helps to read all of the information instead of cherry picking things so one can appear to have the solution for bad coding of an update.
I'm beginning to be suspect of a few things that could be causing this issue with 10.0.3.
For anyone with third party plug-ins, there could be some of those used in your 10.0.2 timelines that are struggling with something in 10.0.3. This is causing it to re-render everytime the app is launched, plus bringing that rendering down to a crawl.
I notice that everything that used to render within seconds, is actually taking minutes now for the smallest things.
I put everything back on an even slower comp system running 10.0.2. General operation was relatively smooth and quick.
Then I did the same things on the fastest MBP machine one can by plus thunderbolt, and everything was a crawl.
So I did a test.
I turned off all plug ins that were from 10.0.2.
MOST of the speed issues went away (except for issues with missing attributes in titling).
To me, this indicates that there are a slew of plug-ins (filters, effects etc) that are "incompatible" with the new update, and should either be disabled OR wait for an update from that particular company making the plug in.
Sorry, didn't mean to be short with you.
What I found that fixed the problem with having to re-render everytime you lanching the app, is to have a short dummy project that you select before you close the app. Sounds crazy, but it worked for me and a few people. So don't leave projects that have a lot of rendering open when you close. Give it a shot!
Appreciate the karma here. It's tough to explain issues with people who, because they dont have such a problem themselves, act like things are "no big deal" and only offer advice such as "trash your preferences" etc. Or worse, dont read what one writes, so tell you to "check your graphics card" (when you wrote you had the latest MBP avail) and/or "move your projects to an external HD" (when you wrote you had 2 external Thunderbolt drives).
So let me tell you - YOUR response is like a breath of fresh air! Thank you!
I havent tried this workaround but def. gonna try it!
What I did find was that there appears to be a lot of plugins from previous version that are "incompatible" with the new update. This is causing havoc. Turning them off/deleting them eliminates the problem but obviously leaves one with a new problem ;-)
Again - THIS is the kind of feedback that is actually useful and worth reading!
Glad I could help. I had this problem when FCP X first came out.
Here I found my original thread from Aug 2011 on this subject. I start talking about the work around on the 2nd page.
I have done almost all of the aforementioned fixes to no avail;
created folders for projects & toggled closed...
projects are on a 2T (internal) drive
added 24G of RAM (didn't do a thing, sent it back, saved $320)
using optimized media
etc., etc., etc........
One other question I have is what is a good video card for editing purposes? You list an ATI Radeon 1024 MB. There are many with as much as 2G GDDR5 memory in the $200 range. Would this help with rendering speeds? I currently have a NVIDIA GeForce GT 120 card with 512Mb VRAM in my 2009 MacPro 2 x 2.26 GHz Quad-Core Intel Xeon with 7 G RAM