final cut X disappeared in my computer

[Oliver Peters]

[Umberto Aguiar] “What went wrong?”

You installed FCP “legacy” on top of FCP X without first moving FCP X to a safe folder. Apple has a white paper on their support site for best practices in how to do this. My suggestion: Delete both versions from your computer using the free Digital Rebellion tools. Then, first, do a clean install of FCP/FCS “legacy”. Then re-install FCP X from the App Store. It will take care of properly moving the apps into safe folders.

– Oliver

Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com

[Oliver Peters]

https://support.apple.com/kb/HT4722

– Oliver

Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com

[Bret Williams]

No need to reinstall 6. It simply asks for the original serial number when you install an upgrade. Imagine how long it would take for me to install all 7 versions!

[Umberto Aguiar]

Thanks a lot for the information.

I deleted the incomplete final cut studio I had in the new mac. I couldn’t find final cut X to delete it so I just installed fc X again. I have a third and “ancient” macbook pro with final cut studio that I will keep but I won’t install fc 7 in the new mac anymore. I installed, instead, adobe CS6…

This final cut X/final cut 7 “situation” caused me a lot of stress and unexpected expenses. I made a few decisions after this last problem I had with final cut X/final cut 7:

1. I will keep final cut X, just in case I am wrong about it or if I have to work with it because of the market.
2. I will try to edit only on Adobe from now on.
3. So long, final cut 7. Rest in peace.

I believe that Apple’s decision to change from fc 7 to fc X was mainly a money matter. Moreover, they showed an extreme arrogance and inconsideration towards its pro customers when they launched a “new” final cut that doesn’t have backwards compatibility. I, for one, had enough. Forgive me the expression but Apple can go to hell and take their greed with them.

Be good to your camera and your camera will be good to you

[John Godwin]

You’re right, FCPX is not directly compatible with FCP7, although there are third party solutions that fix that.

Remarkable that you didn’t read the simple instructions Apple provided as to how you can easily keep FCPX and FCP7 on the same machine. You’d have avoided all that hassle.

Best,
John

[Umberto Aguiar]

Well, months ago I installed fc X in a mac that had fc Studio. I did read, that time, Apple’s white paper on fc X installation but I just installed fc X, without any specific steps. I had no problems.

Considering my previous experience, I didn’t expect that installing final cut studio in a mac that already had final cut X would be a problem. This thing of “hiding” one final cut from another sounds to me like Cain and Abel…I really had enough.

I know, in this case, that I should have read ( is that correct?) the white paper again but to read Apple’s information about a product does not necessarily avoid troubles.

I did read, for example, Apple’s requirement for final cut X and my mid 2009 mac book did meet them.

Despite of that, I had to change the battery mode in order use a more powerful graphics card that would run final cut X . It ran okay but just okay. Motion wouldn’t run at all. Images were jerky and I just couldn’t work with Motion. So I had to buy a new macbook pro and had to install again final cut X and final cut Studio.

I was going to migrate them but then I read, on Apple’s site, that migrating final cut studio to a mac with lion could be problematic so I decided to install fc and installed fc X first because it would be quicker and I would have an editing system in my new mac book pro in a matter of an hour or so. Then I tried to install fc studio and the problems began…

But all those installations and “hidings” and white papers wouldn’t be necessary if only final cut X had backwards compatibility. As I said, I had enough of this Cain and Abel story. I am moving to “Adobeland”.

Be good to your camera and your camera will be good to you

[Umberto Aguiar]

Well, months ago I installed fc X in a mac that had fc Studio. I did read, that time, Apple’s white paper on fc X installation but I just installed fc X, without any specific steps. I had no problems.

Considering my previous experience, I didn’t expect that installing final cut studio in a mac that already had final cut X would be a problem. This thing of “hiding” one final cut from another sounds to me like Cain and Abel…I really had enough.

I know, in this case, that I should have read ( is that correct?) the white paper again but to read Apple’s information about a product does not necessarily avoid troubles.

I did read, for example, Apple’s requirement for final cut X and my mid 2009 mac book did meet them.

Despite of that, I had to change the battery mode in order use a more powerful graphics card that would run final cut X . It ran okay but just okay. Motion wouldn’t run at all. Images were jerky and I just couldn’t work with Motion. So I had to buy a new macbook pro and had to install again final cut X and final cut Studio.

I was going to migrate them but then I read, on Apple’s site, that migrating final cut studio to a mac with lion could be problematic so I decided to install fc and installed fc X first because it would be quicker and I would have an editing system in my new mac book pro in a matter of an hour or so. Then I tried to install fc studio and the problems began…

But all those installations and “hiding” and white papers wouldn’t be necessary if only final cut X had backwards compatibility. I have 7to X but it doesn’t work that well so you can’t say it fix the problem.
7toX will improve, I guess, but I don’t see why I should wait. As I said, I had enough. I am moving to “Adobeland”.

Be good to your camera and your camera will be good to you

[John Godwin]

Before any major upgrade of anything on the computers that I make my living off of, I use Carbon Copy Cloner to make 2, count ’em, 2 backups of the system drive. That way if there is a problem I can get back to where I was before the upgrade and figure out the solution to the problem. I recommend this method highly, as it’s saved me a couple of times.

Best,
John

[Bill Davis]

[Umberto Aguiar] “But all those installations and “hiding” and white papers wouldn’t be necessary if only final cut X had backwards compatibility. I have 7to X but it doesn’t work that well so you can’t say it fix the problem.
7toX will improve, I guess, but I don’t see why I should wait. As I said, I had enough. I am moving to “Adobeland”.”

Well, have you considered that all those “installations and “hiding” and white papers ARE necessary because they didn’t just slap some new makeup on the old code, they started with a clean sheet of paper?

There’s very little in X that works the way it did in legacy – not the least is that one was build on a rudimentary “flat file” database and the other is build on a pretty robust relational database – and as such, the entire code handling process in X is vastly different from Legacy.

Add to that that all the old underlying tech like Quicktime was stripped out in favor of AV Foundation and Core Services and what you’re asking for is a bit like demanding that I tell some kid a satisfying lullaby – but neglecting to take into consideration that I speak only English while the kid only understands Dutch.

Good luck with that.

“Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor

[Umberto Aguiar]

{Bill Davis} “Well, have you considered that all those “installations and “hiding” and white papers ARE necessary because they didn’t just slap some new makeup on the old code, they started with a clean sheet of paper?”

Thanks for your post. Well, this is off the topic but you really can’t say that Apple started with a clean sheet because Final Cut X is an upgrade of iMovie. I learned Final Cut X very well, thanks to three excellent books, and also got Apple’s pro certification on fc X. I worked with final cut studio 2 and 3 before. I never worked with iMovie. I did try once but just couldn’t understand the weird logic of it. Guess what? After learning to edit on final cut X I found out that now I can also edit on iMovie and I didn’t spend one single minute reading or watching tutorials about iMovie.

Final Cut X wasn’t “Rebuilt from the ground up” as Apple misleadingly advertises. Final Cut X’s interface is very similar to iMovie’s , so are many of the buttons, features and concepts such as “events”. All those features shared by fc X and iMovie don’t exist in fc 7. As a matter of fact, FC X even has an option to import projects from iMovie…

I don’t actually dislike Final Cut X. It is certainly faster to edit news than fc 7 was, although fc 7 has far better options to compress and output edited videos, what is so important in news. What I really don’t like about fc X is the lie behind it. This lie that fc X is “revolutionary” and “rebuilt from the ground up”.

I might end up working a lot with final cut X because of the market. I don’t know yet. Meanwhile, I will be moving to Adobeland and I know that I will meet lots of former fc 7 editors over there.

Be good to your camera and your camera will be good to you