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

Final Cut Studio 2 and OSX Lion issues

I tried to upgrade to Lion on my Mid-2009 MacBook Pro, but afterward I tried to startup Final Cut Pro 6 (which is part of FCS 2), only to be told that FCP6 is a PowerPC application and it wouldn't run. I don't understand this, since I have Shake 4.1 installed on the same computer, and both applications are Universal Binary; after the lion install Shake still continued to work (Shake is older than FCS2, and Motion replaced Shake) while FCP didn't! I had to wipe my haddrive and downgrade back to Snow Leopard, just to use FCP6! What gives?

PM G5 (Late 2005) 2x 2.3GHz, 6.5GB RAM | MBP 17, Mac OS X (10.7), iPhone 4 32GB- v4.2.1

Posted on Aug 8, 2011 9:23 AM

Reply
Question marked as Best reply

Posted on Aug 8, 2011 10:33 AM

FCS 2 is a four year old application...and Lion is brand spankin' new. Sometimes old software has issues on new operating systems.


Why did you install Lion? Do you NEED it? Does it do something that Snow Leopard does not? Why not just stick with what works? Especially if you earn a living with that machine. There is no need to install the latest and greatest JUST BECAUSE it is the latest and greatest.

18 replies
Question marked as Best reply

Aug 8, 2011 10:33 AM in response to Terry Smelker

FCS 2 is a four year old application...and Lion is brand spankin' new. Sometimes old software has issues on new operating systems.


Why did you install Lion? Do you NEED it? Does it do something that Snow Leopard does not? Why not just stick with what works? Especially if you earn a living with that machine. There is no need to install the latest and greatest JUST BECAUSE it is the latest and greatest.

Aug 8, 2011 10:51 AM in response to Shane Ross

Well, Shane, since OS's from 10.2 to 10.6 were such easy upgrades, I was expecting the same of 10.7. After all, isn't that the point of using a Mac? I guess I should have included in my original question that I was looking for a solution for this problem, not just snarky comebacks.


But to answer your question, I want to make sure that I can make use of iCloud when it is finally rolled out. There seems to be debate on whether it will work with other operating systems like Leopard (which is what I have on my Power Mac)., and it would be nice to have one Mac in the house running Leopard.


Overall, one would be tempted to think that Apple jumped the gun with Lion, since it doesn't seem to play well with many applications (especially Apple's own) that it is supposed to play nice with. These are the kinds of problems one would expect with a Windows upgrade, NOT with a Mac OS.

Aug 8, 2011 11:18 AM in response to Terry Smelker

Pardon the snarky reply, but from a professional editing point of view, one NEVER updates a working machine, unless something is offered in the new OS that one needs right then and there. And when one does update, one needs to do a boatload of research first, to make sure that every application they rely on is compatible with the new OS. Because if it isn't, it means the edit station cannot function properly, and that means that one cannot work and make money with that station. So ALWAYS look, and look well, before you leap.


You want to make use of iCloud, when it is "finally rolled out." OK, why not wait to update the OS until it is rolled out? You don't need it now, you need it when a feature comes available. SO use what you have until it comes, and then research to make sure things work. And if you really need iCloud, can you not just get another computer with Lion to access all of that? So that your current system can run under the OS that it works well? And yes, Studio 2 might have worked under all those previous OSes, but support for the old software will stop at some point, because Apple looks back only so far. So this might be the point where it doesn't work.


But really, FCP 6 and LION might be an issue. I do know that the INSTALLER for FCS2 is PowerPC based, and requires Rosetta, and Rosetta isn't included in Lion. Lion not working with Apple's own software? Well, yes, it does, the NEWER ones. The older software? As I said, they extend support only so far...they can't keep looking back if they want to look forward. If you want things to always work with the latest OS, then you need newer software. You cannot expect the older software do always just work...it won't.


Especially since FCP X is out...Apple doesn't give a hoot about supporting the older versions.

Aug 8, 2011 1:20 PM in response to mishmumken

Installing something that wasn't tested on the OS you are installing it on...and not sanctioned by Apple. Sure, but go at your own risk...and don't moan and complain and blame Apple when it doesn't work. It wasn't designed to work...they removed Rosetta from Lion.


Just warning you. DO what you want. Personally, since I use my machine to make money, I run it under conditions that have been tested and green lit. Failure costs me time and money.

Aug 8, 2011 2:34 PM in response to Terry Smelker

Mishmumken, that's VERY helpful news. I'll be sure to give it a try.


Shane, thanks- but I never said my MBP was the ONLY mahine I use- it's just the only one that suports Lion. I'm perfectly willing to try whatever I need to. Personally, although I agree with your statement about better timing with upgrades, I find it interesting that you've acheived Level 8 status with the kind of attitude you displayed in your last post.Good luck to you.

Aug 8, 2011 3:50 PM in response to Terry Smelker

Ehh...those guys are paid...I'm not.


So...seriously. Tone of voice is tough to express on forums. I don't mean to be rude...I do mean to ask "why did you install Lion? Does it have something you need?" I don't mean that sarcastically...I mean it truthfully? Why did you do it, and did you really need to? It is best not to. That's all.


And I am explaining how ALL OS makers work when they make the new OS...they rarely look back to see what will work. They might do a short distance, but not more than a few years. I don't have sympathy for them either, just stating facts. Apple might look to see if FCP 7 works, but they won't look at FCP 6.


I didn't mean to be condescending...just factual.

Aug 8, 2011 11:38 PM in response to mishmumken

Completely agree with Mish, the advice of Shane not to update if everything is working well is golden. I too want to get rid of MobileMe and change to iCloud (especially for the calendar) but I decided to wait until next summer to decide wether or not to update my station (I only updated to 10.6 last May). And I also have a recent and bootable copy of my workstation just in case...And I'll stay on FCP6 as well for the coming year. Shane thanks for all your advices in the past years, it was (and still is) a great help!


WA

Aug 27, 2011 8:34 AM in response to Terry Smelker

Well, thanks to no one here, I wiped my drive, reinstalled SL and all my apps, then reinstaled Lion 10.7.1 over all that, and all my apps- including FCS2- worked fine now. In addition, I reinstalled Rosetta as recommended by another thread here, which should help in the future. Since I grabbed Lion basically right out of the gate, I inadvertently proved what most people say about Mac OS upgrades- wait for the update!

Aug 28, 2011 6:49 AM in response to Terry Smelker

Terry,


You have found out, what others, who have installed LION, on the their Mac.

You will have to re-install all of your software over top. LION does not see those

software items. You did the right thing. To bad you had to wipe your drive and re-install all your

software.


I will not install Lion on any of my Mac's till either Apple address this issue or other 3rd party

FCSP software makers stop suppoerting older OS's.


Terry get use to this-This is the new APPLE. They did this with FCPX and now with LION.

If they are not carefull, Apple could lose their base supports, who date back before LISA,

and the 1st Mac.

Aug 28, 2011 7:33 AM in response to russ Andris1

Well, I only had to wipe the drive becuase I didn't have a Time Machine drive for this laptop. Once I completely restored SL, however, I bought a portable drive to use for Time Machine backups- which will serve me well as a backup video storage drive once Lion has settled in.


Russ, I don't particularly like the 'new' Apple- especially their incessant push to make their computers 'obsolete' just to drive new Mac sales. It seemd their decision making for new products has doen a crazy Ivan recently. And I am one of those people who have been supportign their products for a VERY long time.

Nov 3, 2011 2:25 AM in response to Terry Smelker

Hi there,


My edit partner has a Mac Pro running Leopard and FCS2 and Adobe CS5 and is living in Mozambique.

I´m presently living in Europe.


We used to work together by having a copy of the media files on external disks that were identically named on either side of the globe. We would send over the FCP project files and comment on the work in progress.


I´ve an older Macbook running Leopard and with FCS2 and Adobe CS5 installed. That did the job.


I bought a new MBP running Lion and want to have it installed identically with FCS2 and Adobe CS5.

I now understand I cannot install FCS2 (FCP6). Installing FCPX is not an option since project files seem not to be compatible.


Upgrading the MAC Pro to Lion is not an option, since it would go against the golden rule never change a running system. We also keep all the project files archived, in case we need to make changes in the films at some stage. (Like subtitling in yet another language). Changing to FCPX without the ability to read the old project files is a stupid omission by Apple.


So what are my options? Can i use migration asssitant to transfer FCS2 and Adobe CS5?

Should i rather use set-up assistant. Should I use time machine? Can I get rosetta from my old MB and copy it somewhere on to the MBP?


Any help appreciated.


Regards,


Bert

Final Cut Studio 2 and OSX Lion issues

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.