Q: 10.0.3 DISASTEROUS

I dont think the issue here is what happens when making a basic, simple project within FCPX 10.0.3 from scratch. The issue is what happens when one has a COMPLEX project of considerable length, made in 10.0.3 then CONVERTS that project (10.0.3 must recreate/update the 10.0.2 PROJECT files - which then become incompatible with previous versions -so something is def. being "altered" by definition - not only the updated app).

I did a test. Starting from scratch and making some basic projects in 10.0.3 was ok.

Then I imported in SIMPLE projects (my definition of SIMPLE might even be complex for some others - I make short, but complex made sports films ) from 10.0.2 and those were also OK. BUT I believe this is because ---those ----particular projects were not what I would call COMPLEX nor of any real length.

Because when I brought in my perfectly working 10.0.2 COMPLEX film projects into 10.0.3 - this is where all the havoc begins. Everything slows to a crawl compared to 10.0.2. Attributes on text completely ga ga. Rendering required EVERY TIME. Hello beachball with every click. And all on the fastest MBP system and HD one can purchase.

They, and the computer environment -  work PERFECTLY on 10.0.2.

So it is CLEAR that this is an UPDATE issue and to experience the same issue means one would have to be testing the same(similar) issue.

I doubt that MY app update or others with issues are getting "monday job" updates. So why do some say "we dont have any problem". Clearly different peoples idea of what a "similar" project are will be different. I say, if ONE person with problems occurring ONLY after making an update to $$$$ projects that are rendered useless, is not a reasonable issue for accepting this "slip out the door" from Apple. It should not BACKTRACK for the worse on things like speed and altering previous projects (these are not even 10.0.1 files - they are 10.0.2 files. Its almost the definition of "ruining" your work. Not acceptable.

And fanbozy without this >>same<< problem should not run around making knee-jerk reactions to defend something like this. This is NOT an issue about "its only a new version" etc. because that is NOT what this is about! NO ONE is complaining about 10.0.2! Get it straight. Its what happens after one incremental update promising "performance improvements"and overall stability etc! If there is any #1 fanboy its me! And I know Apple products and FCPX like the back of my hand - and love it! All our Apple products are the top models and thunderbolt drives/monitors etc. So for me to criticize, is an exception to the rule.

But THIS time I cannot stand idely by and accept this. Apple already has a lot of pros laughing about the treatment they have made to those customers and this must surely make them say "there ya go - told ya!" Well, I'm a professional PHOTOGRAPHER and "only" semi-pro videographer but both are my INCOME. Apple - how you let this one out the door is beyond me. I dont ask for any miracle feauture and have forgiven you for ALL of the features lacking - AND the performance issues of past. But THIS time - to release an update pretty much screwing up all my previous work which has cost me a ton of unnecessary time and $$$ is unacceptable. If its not ready to release and update - AFTER TESTING IT. Please do not release it.

Let the knee-jerkers begin their call to arms of defence.

And for those who have suffered this issue wherever you are - at least there is one FANBOY (me) who actually understands your grief this time!

Hi Wild G and thanks buddy

The good news is that the projects are already finished. But as clients will come back to re adjust things etc. etc. in my world - a project is "always in the middle of a project" if ya follow me ;-)

There really isnt any issue in one way. Just use 10.0.2 and re load backup projects that havent been altered by the 10.0.3 update. But a lot of headaches, time and money to fidget around with all this "testing this and that" only to find things simply dont work in an acceptable manner with films made in 10.0.02 and as complex or structured as mine - which are made for pro sports organizations. Remember this update requires an altering of the files - so hopefully everyone has backups and can return to the old version ;-)

My beef is just that the way this was released and the result of it using real world complex professional films, was clearly a flaw with the beta-testing dept.

Appreciate your reply. I will give that a go and see what happens but keep in mind my point is if one has to figure all those workarounds for an update that is supposed to solve all these performance issues only to make them worse (FOR SOME) then *** - you know?

Thanks again. Your gingerbread man's making me hungry so gonna have a snack now ;-)))

Finally got to try this... didnt change a thing.

But thanks for sharing your own experience.

After a lot of fiddling, it seems something has actually worked to eliminate the constant re-rendering after trying all the other (much appreciated) suggestions that unfortunately did not do the trick 100% (for my situation).

1. As opposed to manually deleting render files, I chose this option from the menu of the project(s) created in 10.0.2 that refused to stop re-rendering on reloads.

2. Then quit.

3. Then relaunched the app. Stopped all rendering. Made a duplicate of the projetc(s) affected.

4. Then quit.

5. Used Event Manager (although this can be done manually) to switch over the new dupe and switch off the old one.

6. Relaunched FCPX 10.0.3

7. Let the rendering rip away . This time first as PROXY files. Then as high res files (original or optimized option). Had a coffee. Looked to see if any more were posting angry posts about me

8. Quit FCPX 10.0.3

9. Relaunched. Voila. For the first time - everything was rendered as before.

Of course this might not work for others as we all have our own situations in our projects, but after everything else this seemed to fix at least this particular productivity-breaking "bug". It has no affect on any of the other issues of course, as far as I can tell.

One thing I might add, it might take (depending on the complexity of the file - mine are VERY complex) a while when quitting. The tendency might be to ForceQUIT because we think its "frozen". Just wait and wait until it finally finishes before restarting again. Otherwise it might not "fix things" completely while collecting the shutdown data.

Crossing fingers for anyone affected that this will help their particular situation.