Upgrading from 10.1.4 to 10.2 install taking too long

Make sure you have a complete backup just in case anything goes wrong. I use SuperDuper! to create bootable backups; Carbon Copy Cloner is another solid choice.

Yosemite runs perfectly fine on my wife's 17" 2010 MacBook Pro. I have not tried FCP X on this machine under Yosemite (it worked fine under Mavericks).

As always there are people with problems, but the silent majority just keeps happily working.

Luis Sequeira1 wrote:

As always there are people with problems, but the silent majority just keeps happily working.

Seriously, Luis, how could you state things like these when half of the posts since 10.2 update on this very forum are pointing to crashes and important bugs?

But you are right about one thing: make serious install backup before upgrading to 10.2 or, preferably, wait until Apple fixes major bugs.

THere are a lot of sick people in the hospital. There must be an epidemic. A lot of people are updating the OS, the apps, the pro video formats, plugins, drive formats, sounds like a recipe for a ******** of problems.

Updated to 10.10.3 and 10.2 on the same pass, upgraded 4 Event Libraries, and encountered no bugs. All events (including those with 4K media clips) playing and functioning the same as with 10.10.2 and 10.1.4 (and earlier). There is a majority for whom it is going as expected.

Ernie

I thought I was having the same problem as you while updating software. Waited overnight, while grey screen with Apple logo showed progress bar at only half-way point after 8+ hours. I thought I was doomed. Powered off computer, waited a few minutes and fortunately update had taken affect. Have not yet worked much within FCP X, but everything appears to be okay. In addition, I also repaired permissions and deleted preferences, not sure if those 2 things necessary, but it can't hurt.

Good luck.

Midge

You have to be running Yosemite (10.10.2 or later) to be able to run FCP 10.2. (https://itunes.apple.com/us/app/final-cut-pro/id424389933?mt%3D12)

Geoff.

Ernie Stamper wrote:

There is a majority for whom it is going as expected.

Hopefully there is a majority of good scenari (which have to be defined and understood, thus the long coming post). But, dears, I cannot follow the Apple apologists brotherhood this time, given the simple fact you cannot work on, or render, anymore a project on which you've used Neat Video Plugin, that your have been using smoothly since FCP7 and all previous version of FCPX — and which counts among the most used plugins on Earth. In comparison: Logic Pro, even during the 32bit to 64bit migration, had maintained its API compliance with third party plugins, which has guaranteed the ability to continue working on running pro-projects. This is what you expect from a "pro" application: not to totally mess with your current and previous projects. Means, keep your plugins safe for starters. So why Apple is not able to provide the same standard as Logic with Final Cut "pro" (and I have to stress this:) for what is not even an upgrade but an update? ... I don't know. Why not proposing to update a _copy_ of your libraries, maybe too? ... I don't know, either. In my case, I've updated FCPX by error because of this nasty little "update all" App Store button I've mechanically pushed under the wrong user account in the middle of a long night. YES! Who would be stupid enough to update its Software, on purpose, stuck in the middle of a huge project with approaching deadlines? Nobody I've ever heard of. As a consequence, and for this very specific reason, I cannot think that the happy cases you're all talking about regarding this so-duper-fresh 10.2 release are coming from intensive or professional workflow (Since, lately, by the way, these tend to not fit at all with Apple would-be "pro" apps anymore, it seems). The good case scenari you are talking about are from those who don't do, thus teach, or don't teach thus write articles ... well, you know the drill. The big projects have not gone through 10.2 yet (and they'd better not!).

You're state a number of things here as fact, which really aren't so. Neat is not that widely used. It's expensive and very slow. It has broken on a number of FCP updates before in both legacy FCP and FCPX. Some people love Neat, many don't. The comparison to audio plugins really doesn't have relevance to video applications. There have always been a great array of audio plugins based on agreed standards around a small number of formats. Video applications have always been very different, probably because they have always had to deal with a huge, constantly changing array of formats they have been aoproached very differently.

An API defines THE (processing) standard within an app, whatever the input formats are (exactly like with the numerous audio formats), otherwise the core principle of plugins would not be achievable. Did I need to state the obvious? I will not dive into the my opinion vs your opinion, my point has been made against the usual apologists.

To close my previous quote and go to the bottom of it: "Finally, those who can't (even) write articles shall be kings over the forum realms." - Do they have a life out of this place, we might wonder...

So, as a poor craftsman I'm leaving this quite sad place, but not without saying for those who might be on the same path that the solution for me has been to switch back to 10.1.4, unfortunately. Not without pain and a deep cleaning of 10.2 install.

My Neat plug-in works.

You need to work with clips with a different fps than the one on your timeline (always my case: 50fps/25fps which gives you on demand nice slowmo - I use them intensivily on my work), and even the bug might appears on peculiar config/videocard only. This important info for those experiencing this issue has not been provided by the community (except me here and there) which apparently and mainly prefers to make useless comments than be helpful. Indeed. This bug is listed on Neat video known issues as follow for two days:

"FCPX 10.2: A new problem (possibly a bug in FCP X) related to use of Neat Video along side with transitions between clips has been introduced by Apple in FCP X 10.2. This problem shows up when the frame rate of the project is different than the frame rate of the clips involved.

For example, if a cross-dissolve connects two clips while instances of Neat Video are applied to each of those clips and their frame rate is different than the frame rate of the project, then the transition area may render incorrectly. Also, a part of the second clip may even go black, apparently because FCP X serves incorrect frames to that instance of the filter in such circumstances.

A possible workaround is to make sure the frame rate of the project is exactly the same as that of the clips involved."

Cf. http://www.neatvideo.com/bugs.html

In my case no transition is needed to have black clip instead of rendered ones each time Neat Video is involved, on a clean, brand new and up to date Apple config/install. I've never experienced any issue with this plugin before.

So, how comes your not meeting a bug (which is quite frequent with bugs) is of any interest for those who do?