FCPX 10.0.3 disaster!! rendered text file nightmare...

FWIW, I don't see the render issue here in 10.0.3.

Edit: I also upgraded Motion at the same time if that makes any differrence. I assume text layers are motion templates and perhaps there is a relationship to what you are seeing?

James

OSX 10.6.8

After reading this thread I thought I would check and see if I had this problem. I opened a project I had just started in 10.0.3 added some text, rendered, closed, reopened...... and no problem. Then I saw someone had mentioned that it only seemed to be older projects that this happened with. So I dug up a project I had completed in 10.0.1/2, greenscreen, motion graphics, text, composites, compound clips, etc...... and everything needed to be rendered.

I then rerendered everything, closed the App, reopened, and my text and other things needed to be rendered AGAIN.

I closed FCP went to the FCP events folder, and project folder and deleted all render files folder for the project. Opened FCP, rerendered and quit FCP. When I reopened FCP ALL renders stuck.

Deleteing old render files worked.

I am on and older 2*2.33 4g of ram running 10.6.8

Hope this will help someone.

sz

I upgraded to FCP 10.0.3 and I could see that older project was much slower in rendering. Older projects did not need total render again as you describe. I made a totally new project to day and the render was ad it should be, fast. So my FCPX is working fine now. And this is on my old Mac Pro 1,1 2006 with 10 GB. I am running on Snow.

Hi Steve, and thanks for sharing.

I just went through this task completely.

Didnt change a thing. Appreciate the possibility though.

Apple needs to slap someone fairly firm on the wrist for pushing the "send" button on this absurd update billed as "performance and stability improvements" lol...

I see you're running 10.6.8.

I've got the latest one. Maybe that's a difference? You'd think the latest OS update released the same day as this FCPX update would be compatible. Maybe the new OS update is meant to improve performance for Premier and Avid users only. They should have mentioned that in the notes... 😉

I've been having the same problem having to re-render all of my Projects every time I reopen Final Cut Pro X, and it has been driving me insane. I updated to FCP 10.0.3 and Lion 10.7.3 within a 24-hour period, so unfortunately I do not know which update has caused the problem.

I downloaded "Preference Manager" (which is great, by the way) but it did not fix this particular problem. I tried using Proxy media, but this didn't work either. I removed clips from the Timeline and replaced them with new ones from the Event Browser to no avail. It didn't matter what I did to those old Projects, I had to re-render every time I quit and reopened FCPX.

A few posts back someone suggested trashing pre-update Projects, so I did. I then created a brand new Project and created the exact same edit (with same effects, transitions, titles), quit the program, then reopened it. I did NOT have to re-render the Project! So TRASHING PRE FINAL CUT PRO 10.0.3 PROJECTS seems to do the trick. In fact, rendering itself seems to be happening a bit quicker as well.

Luckily all I had were practice Projects at the time. I feel badly for anyone who has substantial work in the Timeline, who now has to trash it and start over (or be really patient).

ACE001 wrote:

A few posts back someone suggested trashing pre-update Projects, so I did.

I thought I read something about trashing the old "rendered" files, not the "projects". Did I miss that?

Add me to the same problem. Have a project about 1 hour in length. A simple project, no plugins, just vanilla FCPX. Yesterday, updated both Lion and FCPX. My project which ran just fine in 10.0.2, now re-renders every time. I also had title effects (sports lower third) which lost their Logo Drop Zone. I fixed that by reattaching the correct drop zone and that at least sticks.

I don't make money using FCPX, but if I were a pro i'd be pretty PO at Apple right now.

You could definitely try trashing the pre-update Project render files first. That makes sense to me. I bit the bullet and trashed the whole Project. If you have something you cannot risk losing, I'd try the render files before the whole Project. I should have been more specific.

Having to find this fix was annoying, but to tell you the truth one has to expect some bugs with a new update, especially a new update on a new program. With FCP 10.0.3 there is this problem with having to re-render, but it seems like many of us now have a fix. Despite this, I still think the new update is phenomenal. I'm reading all over the internet that high-end users and calling the new multicam feature 'the best of any nonlinear editing software'. It may be a bit too early to say that so boldly, but still, it does say something. The advanced keyer is nice, as well as the automatic Project backup, the ability to relink media, some changes to the Color Board and the Scopes, and a few changes in Preferences. I think FCP X has come far in the last seven months, and we certainly haven't seen the last update.

As far as pros being 'PO'd' at Apple for this, to tell you the truth any pro who would completely abandon his or her old software and workflow for the brand new and relatively untested FCP X is just asking for trouble, and should really just be 'PO' at themselves. I do get paid to edit with FCP X --and overall I love the program-- but I don't have clients knocking down my door (yet), so I do still have some time to troubleshoot a few hiccups. If I had more business last June I would not have completely dumped FCP 7 for FCP X right off the bat.

Thank you for your understanding and realism here. This isnt about making friends with apple fanboyz - the kind that god forbid one criticizes the "thinking" going on with their "pro" app. THIS fanboy (me) is pizzzzed to say the least- so again thanks for some straight talking!

What really irks me - other than them releasing it without a proper test - which should now be OBVIOUS, is the fact that they FOR SURE KNOW ABOUT ALL THIS NOW and still dont acknowledge the problem!

With money (that means both payment and general time wasted) this whole update is a true unforgivable fiasco.

Someone seriously needs their wrist slapped.

While we all slave away to try and find some kind of band-aid "fix" Apple sits smug and silent. Not cool.

ACE001 wrote:

Having to find this fix was annoying, but to tell you the truth one has to expect some bugs with a new update, especially a new update on a new program. With FCP 10.0.3 there is this problem with having to re-render, but it seems like many of us now have a fix. Despite this, I still think the new update is phenomenal. I'm reading all over the internet that high-end users and calling the new multicam feature 'the best of any nonlinear editing software'. It may be a bit too early to say that so boldly, but still, it does say something. The advanced keyer is nice, as well as the automatic Project backup, the ability to relink media, some changes to the Color Board and the Scopes, and a few changes in Preferences. I think FCP X has come far in the last seven months, and we certainly haven't seen the last update.

As far as pros being 'PO'd' at Apple for this, to tell you the truth any pro who would completely abandon his or her old software and workflow for the brand new and relatively untested FCP X is just asking for trouble, and should really just be 'PO' at themselves. I do get paid to edit with FCP X --and overall I love the program-- but I don't have clients knocking down my door (yet), so I do still have some time to troubleshoot a few hiccups. If I had more business last June I would not have completely dumped FCP 7 for FCP X right off the bat.

I am a high end user. This update is a huge step BACK because of other major issues that cloud the new "features." A lot of the so called great reviews are articles just read off the contents of the notes.

I for one dont need a lecture what "any pro should or should not do" . THIS particular update reconverts the files so they become incompatible with previous versions. So for sure I will go through all the trouble to reinstall the previous version and use backups of all my previous stuff. But what an outrageous process when seeing the advertising of "performance improvement and stability" LOL!

THIS IS NOT A COMMENT ABOUT FCPX - ITS ONE ABOUT A JUMP FROM ONE VERSION TO A NEW ONE AND TWO STEPS BACK IN A WHOLE LOT OF PERFORMANCE AREAS. PRO OR NOT (I AM) WHY DONT SOME GET THAT.

Geeeeez!

I'm going to try this. I'd like to know if this is correct. Open FCPX, my project loads, go to file, delete render files, choose all, close FCPX, reopen - let it render everything, close FCPX, reopen FCPX and see if everything is fine.

Ok, tried this. Didn't work.