Q: 10.0.3 DISASTEROUS

I use the, ATI Radeon HD 5770 1024 MB installed on my, 2 x 2.66 GHz Dual-Core Intel Xeon with 16GB of Ram.

FCP X works fine for me except for a few crashes once in awhile. I will say I just bought the production suite of Premiere Pro. I am yet to have a crash. Funny! You would think an Apple program would run better on an Apple computer. Something is wrong with this picture :=\

Premiere Pro CS3, the first version on the Mac, was created in 2007 based on the first Windows version created in 2003. FCPX was created last year. I would expect Adobe to have a bit of a head start here.

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.

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

Also, how long is the project? Relinking to render files can take a bit of time.

Message was edited by: 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.

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

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.

Again, how long is the project?

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.

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...

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.

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.

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.

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.

For me all those issue look like a combination of FCPX render file management and a memory problem.

Do all users with this problem run OSX Lion, does this happen to Snow Leopard users?

Me I am still on (good old) 10.6 with FCPX 10.0.2