Apple Event: May 7th at 7 am PT

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

10.0.3 DISASTEROUS

System -

Fastest MCP one can buy (with extra 2.5gz processor model 8gb ram 1.7core) Lacie THUNDERBOLT drives. 10.7.3 OS.


10.0.2 ran "relatively" fine. NOTHING changed except upgrading to 10.0.3


Re-renders everything everytime I restart the program - Even though it rendered to 100% on last shutdown.

And when it is rendering - it does it SLOWER than the last version 10.0.2!


Playback stutters. Beach ball is more present than 10.0.2 !


Titling of previous projects is messed up - baslines and tracking are changed!


To test - I reinstalled the previous version 10.0.2 and reloaded in those previous projects. All runs smoothly.


Reinstalled the 10.0.3 again - EVERYTHING THE SAME - and same issues!


WHO CARES ABOUT ALL THE NEW "FEATURES" WHEN IT DESTROYS MONTHS OF PREVIOUS WORK, AND EVERYTHING IS EVEN SLOWER THAN BEFORE??? Its so frustrating to read reviews by magazines etc who do not lay down feature length, complex movies and only talk about all the "great new features" and how performance is "improved" simply because they read that it SHOULD be improved!


Well it isnt - its WORSE! Doesnt Apple actually test things before releasing it ? Where has the trust gone???


And I have the most pimped out (portable) system one can get. Pity on those with less endowed systems!


EXTREMELY DISAPPOINTED AND ANGRY!

Final Cut Pro X

Posted on Feb 2, 2012 4:53 AM

Reply
272 replies

Feb 2, 2012 1:16 PM in response to Dirk_Williams

Dirk_Williams wrote:


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!

Didn't work for me. FCPX 10.0.3 re-renders every time I start. Puts a real damper on things.


My FCPX system is entirely stock. I don't have any third party plug-ins installed.


I installed and updated from the Mac App Store so I don't have the original 10.0.2 version to re-install a 'working' version.

Feb 2, 2012 1:33 PM in response to Tom Wolsky

Tom Wolsky wrote:


What drives are the projects on? What are the read/write permissions set to?

They are on a Firewire 800 connected 2TB drive in an OWC enclosure. The drive has 1.43TB available.


I'm using a late 2010 iMac 2.93 GHz i7 with 16GB DRAM. My system drive has 479GB free.


The permissions are set to Read & Write for the drive and individual folder and file permissions are set to read&write for <username>(Me) and for read only for everyone else.

Feb 2, 2012 2:06 PM in response to Tom Wolsky

Tom Wolsky wrote:


That should work but try setting to read/write for everyone.

That didn't help. However, one thing I failed to mention is a further strangeness.


Not all of the clips need to be re-rendered each time I restart and it is not the same clips each time. Here is what I did:


1. Start FCPX and wait for project to open and render.

2. When rendering is complete exit FCPX.

3. Restart FCPX.


Rendering always needs to be performed but each restart seems to 'choose' it's own set of which clips need to be rendered.


To me this does not indicate a permissions problem, it indicates a problem either within FCPX or in how FCPX operates in my environment. Since 10.0.2 worked without problems I suspect it is the former.

Feb 2, 2012 2:17 PM in response to crh24

Doing the same garbage on my system. I have clients waiting for projects. I need to get work done, ALOT of work and yet I've spent the better part of the past week dealing with Apple failures like this! I've given up on trying to get Compressor to upload a video to YouTube and I'm seriously considering dropping the Mac and going back to Premiere Pro.

Feb 2, 2012 2:25 PM in response to Tom Wolsky

I'm starting to get a little nervous reading about these problems with 10.0.3. I am currently using the free trial (10.0.2). I have about 17 days left. I was planning on purchasing it after that. Now it looks like the only version I can purchase is 10.0.3. I sure hope I'm not disappointed. I very much like the version I've been testing with.


Once I get the new version, there is no way to go back to 10.0.2 if I have problems...

Feb 2, 2012 2:36 PM in response to Tom Wolsky

Tom Wolsky wrote:


Again, how long is the project?

Sorry, Tom. I missed that question in your first post.


I can tell you pretty accurately how long it is.


The project I'm using for the testing is the one created when I went through the Ripple Training FCPX course with the subject of Weekend Warriors. I stayed as close to the lesson as I could. It is about 1 minute long. Rerendering doesn't take all that long on this project--maybe a minute or so, but for any 'real' project that is much longer than 1 minute the rerendering would be excessive.

Feb 2, 2012 2:50 PM in response to Andy Drefs

Andy Drefs wrote:


Doing the same garbage on my system. I have clients waiting for projects. I need to get work done, ALOT of work and yet I've spent the better part of the past week dealing with Apple failures like this! I've given up on trying to get Compressor to upload a video to YouTube and I'm seriously considering dropping the Mac and going back to Premiere Pro.

Although I am decidedly not a pro nor do I have any aspirations to be one I can sympathize with your frustrations.


I originally used Vegas Video on PCs starting with VV 4.0 and stopping with VV 7 when I moved on to the Mac Platform. I couldn't justify the cost of a system similar to VV that ran on the Mac platform so I looked around. I first tried iMovie...inadequate...then Adobe Premiere Elements 9...inadequate...and then the FCPX system including Compressor 4 and Motion 5 which has worked very well for my limited hobbiest needs.


As I mature in the use of FCPX I may run into some of the more frustrating eserotic problems reported with FCPX but I can honestly say that 10.0.3 is the very first release that has been frustrating for me.


If I relied on FCPX for even a portion of my income it is likely I wouldn't care for the 10.0.3 release, either. It does seem to me that these problems should have been caught prior to release.

Feb 2, 2012 8:15 PM in response to crh24

I downloaded the Ripple media. Built a short project a bit over a minute. Added four titles, Asembler, Split drift I think it's called, a lower third, and the hideous Far, Far Away, which ran for over 20 seconds. It took forever to render FFW, probably a couple of hours. Couldn't do anything in the app while it was working. Basically the app was seized after the render process started. It wasn't worth working with. Quit the app part way through the render. Opened it up again and the render state was as before. Partially rendered. Oddly closing the app and opening it speeded by the render, probably part of the memory problem, though the available memory never went below 1.5G. After the render finished, I closed and opened the app and none of the render files were lost.

Feb 3, 2012 12:34 AM in response to Tom Wolsky

For me the definitive point is that none of those problems happened to me with 10.0.2. They all came about with the update to 10.0.3.


As I say, I'm not one who needs the functionality for my livelihood so I'll just wait for Apple to fix it as I'm sure they eventually will. In the meantime I'll go back to processing a lot of my old stills using the Nik plug-ins for Lightroom and Photoshop. I'll return to FCPX when the problem is fixed.

Feb 3, 2012 2:56 AM in response to Emilia

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!

10.0.3 DISASTEROUS

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