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

montster Author

Level 1

15 points

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

272 replies

Feb 3, 2012 6:15 AM in response to montster

Wow you are really upset. Have you tried copying all the clips and pasting them in a new project? I found that this weeds out a lot of little bugs in a very complicated timeline.

Feb 3, 2012 6:31 AM in response to Wild Giles

From my own personal experiences, I have to be very cautious of doing an update to any video app in the middle of a project. I did do a prefence manager clean a day after the update and that seemed to speed up everything.

I am really happy with the new convert FCP7 to X app. I had to do a lot of testing on that and found out that I had to unlink all the clips in a sequence for FCPX to import all the sound clips. A days worth of trial.

montster Author

Level 1

15 points

Feb 3, 2012 6:46 AM in response to Wild Giles

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 ;-)))

Feb 3, 2012 7:29 AM in response to montster

Computer at home (MacPro 2008, 5770, SSD, 16GB RAM, Lion) is also having constant crashing when opening a legacy project. Have not tried a NEW project. I dont see any memory leaks, just the beach ball. Also my Event Manger X is acting strange, not moving projects when asked too, needs an update. I have 1 crumple pop 3rd party plugin that might be a suspect as well. More to come.

Feb 3, 2012 8:14 AM in response to montster

I've not had many issues on this end with a Mac Pro 2.8 dual processor, 3 internal 1 TB drives with 16GB of memory

I always trash preferences before starting/opening FCPX and use the program memory "purge" during FCPX.

It's important to trash the "prefs" before starting/opening FCPX, not during it's operation

I make sure all other applications that I am not using have been "quit" not just closed

I also trashed my applications of both iMovie and Final Cut Pro which were on my system. I don't know if that helped anything but I did that

My work is mostly 5 - 10 minute pieces (when finished) and most of my import footage is coming from a Canon T3i - H.264. That is running very smooth in as far as working with H.264. I believe these short projects may fair better in FCPX, although I am loading a lot of footage

It seems different people have different issues and obviously the program still has some issues but some of the problems, in my own opinion, seem to stem from third party plug-ins effecting FCPX operation. I did find that going from 8GB to 16GB paired memory helped with the overall performance of FCPX.

It has crashed twice within the past month and approximately 6 spinning beach balls, but those corrected themselves so to speak without freezes or crashes. It did hang the system up for a minute but everything kicked back to normal

http://www.skyjamvideos.com

Feb 3, 2012 8:33 AM in response to montster

Is there any chance that this could stem from incompatible graphics cards that don't play nice with Lion? There seems to be quite a bit of info out there on compatability issues with the Lion update. I have been told by NVIDIA that my card is not compatable but they neglected to tell me what is. I replied back and am still waiting for support center (no doubt in Bangladesh) to respond.

Feb 3, 2012 11:03 AM in response to montster

Okay I added some text to some footage and after it was done rendering, I closed the FCP X. Reopened it and had to re-render the text again. Someone suggested before colosing the app, to just move or do something to something in the timeline, and undo it. Then close the app. I tryed that and when I re-opened FCP X, everything plus the text didn't need to be re-rendered. I forgot who came up with that work around and in what thread, but good fix!

steve z

Level 3

824 points

Feb 3, 2012 12:25 PM in response to montster

Wrong thread!

montster Author

Level 1

15 points

Feb 3, 2012 2:48 PM in response to Dirk_Williams

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

But thanks for sharing your own experience.

Feb 4, 2012 6:29 AM in response to steve z

Steve Z, who are you referring to?

montster Author

Level 1

15 points

Feb 4, 2012 9:40 AM in response to Andy Drefs

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.

montster Author

Level 1

15 points

Feb 4, 2012 9:51 AM in response to montster

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.

Feb 4, 2012 9:57 AM in response to montster

Montster - You lost me a bit on your first line: "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."

You say that you chose "this" option..etc., etc.. and then quit. Which option are you referring to?

Thanks for all of your hard work on this one!

Did you see my other question with regard to possible graphics card issues? It seems that the Lion update has jumped ahead of the graphics drivers and I was told by NVIDIA that my card is in fact not compatible. If this is in fact the case I could see that causing all sorts of issues...

Feb 4, 2012 10:03 AM in response to BROOKLYNTREEZ

Update: Never thought I would say it, but trashing my preferences restored X for me!

Preference Manager

http://www.digitalrebellion.com/prefman/download.html

montster Author

Level 1

15 points

Feb 4, 2012 10:27 AM in response to Andy Drefs

Brother Drefs,

Sorry for the unclarity 😉

I just mean one can manually go through and delete the folders by hand or choose this from within the app. I am wondering if this might in fact do something other than what one does when deleting manually? Anyway, first you must be in the projects library. That area where only the "projects" without all the clips are stored. From there, just "select" the problem project. Then go to the FILE menue and select "delete project render files." If it tells you that it cant work, then cancel any rendering that might be running or paused. Not pause it - cancel it. Then it should go ahead and process the request for deletions.

My apologies but I havent noticed that about the graphic card issue (too much fending off angry fanboyz - although I'm a fanboy myself lol)

But holy moly if your card is not compatible as per Nvidia this is no doubt going to cause a great deal of issues for sure. Prior to my current setup I was using a 2009 MBP and although it was pretty slow, it did allow me to make some amazing videos and earn life-blood coin. I always used FCP legacy for years, but the great things implimented in FCPX have really hooked me into using it as much as possible for jobs that merit it. What people dont get is that my beef is the fudge-up Apple made with this incremental update - not the app itself.

Does that info help at all buddy, just let me know if you need more info....I'm an old man of 50 so perhaps I'm losing my mind and memory in the process of all this jimmy-rigging of the new update LOL 😉

10.0.3 DISASTEROUS