Showing posts with label hack. Show all posts
Showing posts with label hack. Show all posts

Friday, June 24, 2011

How To Run Final Cut Pro X on Non Open CL Capable Cards

Hardmac has an article up describing how someone discovered that, while slow, FCPX and Motion 5 can run on a Mac without a video card that supports Open CL.

"Yesterday I was unable to install Final Cut Pro X on my Dual-Core Mac Pro Intel Xeon rev. 1.1 (from September 2006) because the graphics card is not compatible with OpenCL. I created a session with my name on a friend's recent MacBook Pro and bought it with my iTunes account to test it on his computer and buy it on mine after would have changed the graphics card.
Today I put the MacBook Pro in target mode to transfer some video files.
Then, from my Mac Pro, opened the Application folder of the MacBook Pro and I was able to launch the Application!
I then copied it in the application folder of my Mac Pro and tried to launch it again, it worked!
I went to the software update menu and the other softwares were installed!

For Motion, a 10 seconds animation is read in 23 seconds in Motion 5 on the Mac Pro.
Graphics cards are important, but since I am not a professional, it is plenty enough for me. I understand that Apple didn't want that lower performances with older hardware would be officially possible.
On the MacBook pro 5.2 (Intel Core 2 Duo 2.66 GHz), the animation is read in real time, 10 seconds."



I'm unure of the complete legality of this but it's pretty interesting. It would likely be too slow to be of any real use though in real-world editing.

Apple has a support document here which lists cards that do support Open CL.

Monday, July 27, 2009

Installing Final Cut Pro 7 on unqualified machines



I haven't (and cannot) test this so if you try this you try it at your own risk.

If you want to install Final Cut Studio 3 on a machine that doesn't meet the minimum requirements you can try this hack which involves navigating to:

Final Cut Studio Installer > FinalCutStudio.mpkg > Contents > Resources > Requirements Checker.app

and deleting "Requirements Checker.app".

Again, I have no idea if this works but it could be helpful.



You could probably also edit the minsys.plist file in there but I don't know what that would do. The important part of the file is probably this:

<key>AELMinimumVRAM</key>
<dict>
<key>block</key>
<string>128</string>
</dict>


(If you don't get the reference in the image then you're young.)