10.0.3 DISASTEROUS

10.0.3 is not a "total re-write" of 10.0.2. That's absurd and anyone at Apple who told you that should be fired. FCP X is the complete rewrite, not a .DOT, .DOT update of FCP X.

Yes, these forums are for users to help each other out with specific issues. Some like to use them to rant or promote Premiere Pro or discuss politics. If those posts get reported, Apple will review them and delete them if they are not tech support discussions.

Ths long thread started off with montster saying that FCP X 10.0.3 was a disaster and not working and then on page 1 of this thread said

I turned off all plug ins that were from 10.0.2.

MOST of the speed issues went away (except for issues with missing attributes in titling).

To me, this indicates that there are a slew of plug-ins (filters, effects etc) that are "incompatible" with the new update, and should either be disabled OR wait for an update from that particular company making the plug in.

I have no clue why the thread didn't end there.

Montster - Got the new, matched, Apple specific 16G RAM from Crucial today and my fan is running like mad (temps were at or below 100* and fan was at 4000+ RPM - go figure). It does appear that I get smooth playback though even while rendering, so that's an improvement.

Ran the inital AHT today and it came up with nothing, will run full test tonight.

With regards to Time Machine: Is what you're saying that if I revert to 10.0.2 then any projects that I've opened and rendered in .03 will no longer work in .02? I didn't make any copies of them and I always have a number of projects in various stages of completion. So those folks who say never update in the middle of a project obviously only have one going at a time.

@monster...awesome! (inside info) hehe....

thanks for the great read. I am no where near your production house, but I do make complex multi-multi layered projects, things connected everywhere with relativley heavy media and long clips with massive amounts of event info. Lots of effects, a lot of correction, auditions, so on and so forth. I like to work with my media raw....etc...So working out of the box with me is the only way to go, right now....

I cant wait yet again....thanks for your understanding and info!

Sounds like I'm stuck then as I never know when a client might want an update/change, whatever...

Still just stymied (and a bit steamed) on the fan thing as mine NEVER ran before, it's soooooo annoying to listen to that thing when I've had perfect silence for years!

Guess I'll just hope and pray that Apple gets this figured out quickly...yeah right!

Thanks again for all of your incredible input on all of this, really appreciate it.

A

@montster

Exactly my man!😎 ...your 100% correct. 😀If you look at the numbers this isn't a significant update...Your right - its not even a tenth? lol Its a hundreth of a step forward....lol😁

its just the patience and the testing and the wait and the run around and being a beta tester....😢 thats the issue

ahhh...i've got to get back to it....⚠

talk to you guys tomorrow!

Bill and Monster: Looks like the problems lie in the fact that some major code got re-written and certainly affected the way plug-ins and filters work and are rendered. I downloaded a 'preferences manager' to see how much that helps. Any suggetions or tips??

The more I think about it, if various Plug-In companies did not have a chance to test all of thier products in 10.3 (Which is the number it should be. They don't wont to get to 11 too fast) this could surely be the crux of what's wrong with any pre-set text effects and filters. Any suggestions on how to deal with the Plug-Ins? Should I disable them altogether and wait for the companies to do something, or just re-activet them? Or just wait (oh god!) for Apple to address the problem. Maybe someone needs to suggest in FCPX feedback that their Techs read some of these posts to see the things you guys are doing to remedy the situation.

Lets just hope Apple isn't sitting back saying something like: "See, we knew you guys would figure it out!!"

GET IT FIXHED Y'ALL !!

personally i think the answer is for montster and others who are indicating their issues with fcp x 10.0.3 update should do as i did with my iphone 4s when it would not update . . call support. their fcp x has to be fairly new and montster with a 2.5ghz processor is obviously a new computer . . and therein . . call support and let them know what the problem is.

here's why . . if you call, they know and log the problem, it gets attention, and the fix update comes sooner. to blunder around in the dark is like not getting your money's worth. the current update on the iphone 4s is a result of my own scenario so apple tech's told me. they said that i was the only person with a mac that the phone simply would not update. they called me . . not me calling them after that first call . . but they called me at all hours of the day and even left messages and only one tech worked my problem until they came up with a temporary solution for my phone only. the tech said that no one else in the world has the prob i am having but through my submitting them little files per their requests they found the prob and that there would be an udate out in 24 hours that would fix it so that no one else would have the prob either. sure enough, i got the call asking me to update my phone then try it. i did and the prob was solved. when i called the tech said, "how about that, you personally were responsible for this update and fix and we at apple wish to both apologize and thank you for your this malfunction, your patience, and your perserverence, for helping us fix what might otherwise have been a minor glitch"

so, all those with issues, get on the phone and tell them, let them work with you to get to the source of the prob so that ... 1) your problem will get solved, 2) fcp x gets a better name and not a lot of bad publicity, and finally 3) so that others can benefit from your struggles and the whole community moves forward. i know i for one would love to use fcp x BUT with all this uncertainty floating in the air of sluggishness about it, i am NOT going to lay down 300 bux to experiment and see if i get a winner or a bummer.

Keep in mind that the problem is not completely related to third party Plugins. The requirement to re-render every title created in prior versions is for text created with built in fcpx titles which are apple motion templates. Now if apple rewrote the code to be incompatible with their own software, well then I am at a loss.

Photog01 wrote:

Which explained how one of my Projects audio was now distorted during playback. It added new code and or other stuff beyond my knowlege base to everyone of my existing projects.

You don't have "Preserve Pitch" selected in the re-time editor do you?

Apple changed a couple of defaults.. select Reset Speed and see if that changes anything.

I may have missed it because I haven't read every post on this thread, but has everybody who is experiencing problems actually given Apple their feedback.

It's not much use using these forums as "Apple" does not read them.

Everyone who finds there is a problem with the software should send feedback directly.

The more people who do it, the greater will be the chance of getting the problem rectified.

For anyone who doesn't know how, go to the menu and select:-

Final Cut Pro>Provide Final Cut Pro Feedback . . .

Then fill in the web form that appears.

Keep your fingers crossed and maybe FCP X will become an even greater app in every respect than FCP 7 .

Monster you are Right!! Its not a Plug-In Problem (which I never suggested), but indeed a CODE problem. CODE that was not fully tested on real-life projects. I like you have watched a bunch of demos and tutorials and the projects are as basic as they can be. And most never do some of the things I do, especially with still images.

And anyone on this site who says that a minimum of 4GB of Ram will work with FCPx is misleading anyone who wants to tuse this editor with any kind of ease. I reccomend a minimum or 16GB and no less.

The potential of this editor is coearly seen by everyone for sure. But its the recklessness and disrespect to those who make a living by Apple that has most people so upset. And to IAN, I think that most on this THREAD have used the FCPx feedback site more than onece!!! I know I have and will continue...a lot!!!