final cut X disappeared in my computer

I've just received a new macbook pro. I had final cut studio in my old mac but made the mistake of not migrating it. I thought that installing final cut studio would be better. Well, I couldn't install fc 7 because I needed to first install fc 6 and fc6 won't install in lion. I read here in creative cow that all I needed to do was to install rosetta from a snow leopard disk. I installed rosetta and then install the first disc of final cut studio2. The installation happened too fast and I knew that something was wrong.

I had final cut X in the new mac and now, after rosetta and an attempt to install final cut studio, i can't open or even see final cut X anymore. It says that I can't open it because the application is incomplete or damaged. I can't even find it in applications so I could delete it and go through the hassle of contacting Apple to ask for a new download of final cut X ( It was my second download).

Apple is closed and now I need to work but don't have final cut studio and final cut X won't do for what I need to do ( print out to tape ). What went wrong?

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

- Oliver

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

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

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

[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] "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".
"

Umberto.

I understand how you're looking at this, but we just have different philosophies.

And as to your X verses iMovie distinction, I coudn't disagree more.

Yes, some interface elements are similar. But that's not anywhere the same as saying that X is particularly similar to iMovie in any meaningful way.

My understanding is that while Randy U worked out some conceptual ideas in iMovie that found expressions in X (like the concepts of events and keyword tagging) the way they are coded and function is significantly different in X.

Consider it this way. You can build a modest 100 square foot playhouse for your kids out of two by four lumber and for fun, give it both a "lockable front door" and a "mailbox." Which are nice features.

The family home in front of it, likely also sports a lockable front door and a mailbox.

So if your 'test" is reduced to "does it have a door and a mailbox" - then I guess you can argue that those two buildings are kinda the same.

But nobody who takes the time to understand things beyond the surface would actually argue that for very long.

It's essentially as foolish as arguing that a Yugo and a Rolls Royce are the same thing because they both have four wheels and an ashtray.

Look, we've known for a while that X is working in sports, episodic TV and other high end spaces - but folks probably worried that it was only safe if you had a team of engineering pros to make sure you met specs.

This thinking is disappearing fast.

Just today, one of my quick DSLR-to X packages ran on our local former ABC O&O (now a major independent) in broadcast HD directly compressed from my timeline into H-264 - and uploaded to the station via YouSendIt. They didn't ask a single question about the file, they just ran it as regular programming along with everything else.

I simply don't know anyone doing this kind of thing out of iMovie.

Do you?

So if you want to paint X as "iMovie light" or "not AVID" or "not as Legacy-like as Premier" be my guest.

I'm just going to keep delivering my work a whole lot more easily, rapidly and successfully than I did last year - by using FCP-X. It's a great tool for today's deadline driven, how and what will I need to communicate today - era.

Simple as 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] "I am not upset with FC X. I am upset with Apple. "

Fine. Now I understand. Your feelings were hurt.

Sorry about that. Hope you get over it someday.


[Umberto Aguiar] "My move to Adobeland, where the "sun shines everyday on the birds and the bees", is partially a personal protest against Apple because what Apple did with fc 7 is disgraceful. It caused and it is still causing a lot of trouble and expenses to many good people. The lack of backwards compatibility is especially revolting. Please don't tell me that 7toX fixed the problem because it didn't. "

Wow. Good luck then. Both "disgraceful" and "revolting" - good thing this isn't any kind of an emotional thing for you. Again, sorry you were so deeply hurt. Again, Hope you get over it someday.


[Umberto Aguiar] "It looks like you are one of those Apple believers who think that Apple can do no wrong, in which case there is no point in go on with this discussion because it is not a technical argument anymore but a religious one.
"

Well, as someone who once spent $17,000 on a MacIIfx system - which in a couple of years was worth maybe 20% of what I'd spent for it - and I had to slog through another three years of lease payments to cover the cost, I'm perhaps a bit more sanguine that you might suspect about Apple's "perfection".

But I kinda do have to call you on your language here.

It's clearly not "technical" at all for you. It's emotional. As your own words clearly indicate. And I suspect that since religion clearly lives closer to emotion than to fact, it's you who actually has the religious issue since you've cast yourself as the heretic having been so evilly and wrongly consigned to wander the desert by the all powerful Apple priests.

Again, sorry for your loss. Hope you can find salvation at Adobe. They make fine products. I wish you nothing but the best over there.

"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