Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Anyone successful getting a GTX 670 CUDA enabled inside of Premiere CS6 in ML?

1ricca said:
Shut down, put video card into slot 2, booted, Replaced dylib with original, rebooted, run CUDA-z = still not detected.

Re-installed CUDA 5.0.24 drivers, rebooted, CUDA-z= DETECTED!

I definitely had 5.0.24 already. Totally f'd up weirdness. Next up... OpenCL. Would really be fantastic to see it work.
Click to expand...

For make OpenCL I used an app called Multibeast, its for hackintosh only, but it have the GTX 670 kext in the installation.
http://www.tonymacx86.com/downloads.php?do=file&id=139

You can download it and select ONLY the GTX 670 kext.

That made my GTX 670 to run OpenCL


Still if you are afraid of any damage multi beast can do to your computer you can try the manual step-by-step I gave you before.

I just remember that doing so it disabled CUDA in my system but enabled OpenCL, it's not the same for everyone.

I suggest that whatever path you choose, you backup your original "GeForceGLDriver.bundle"
 
Davirus said:
OK.

First you have the originals system files, no patched, not modified (at least not anyone related to the video card)

Next, you need to download the latest CUDA driver (5.0.24)
http://www.nvidia.com/object/cuda-mac-driver.html

Check if it the same CUDA version you do have, and be sure you don't have any modified .kext or .bundle related to your card.

If CUDA Z fails to detect your video card as CUDA capable, there is no chance Adobe will do it.

First lets get CUDA-Z working and then Adobe should be working.

[url=http://s11.postimage.org/6w53dhcan/Screen_Shot_2012_08_26_at_19_50_15.jpg]Image[/url]
Click to expand...


So I backed up the original bundle (actually backed that up before this thread even or ever touching it), ran multibeast, selected ONLY the 670 driver, rebooted, , and still have CUDA but no OpenCL.

Next I did the manual dylib replacement, rebooted, still have CUDA, no OpenCL. Strange huh? I think OpenCL might actaully have better performance for my workflow. I'm not sure though which is why I want to test both.

Thanks for all your help so far.
 
1ricca said:
So I backed up the original bundle (actually backed that up before this thread even or ever touching it), ran multibeast, selected ONLY the 670 driver, rebooted, , and still have CUDA but no OpenCL.

Next I did the manual dylib replacement, rebooted, still have CUDA, no OpenCL. Strange huh? I think OpenCL might actaully have better performance for my workflow. I'm not sure though which is why I want to test both.

Thanks for all your help so far.
Click to expand...

mmmm... weird.

Did you repaired permissions after installation? It might help.
 
1ricca said:
No not this time. And guess what... Broken install again. Have reformat for 4th time now. Amazing huh?
Click to expand...

Doesn't amaze me. I've been ripping apart computers since the first IBM PC and done a few hacks as well. I followed the instructions (once I deciphered them) and had the exact same issue. CUDA was no problem, but OpenCL is a different story. After doing the >2 GB fix, I then replaced the library ext file, and my Mac Pro promptly turned into a 40 pound brick. Fortunately I had a cloned disk ready to get back up and running. I've read a few other posts where people had the same problem.
 
xav8tor said:
Doesn't amaze me. I've been ripping apart computers since the first IBM PC and done a few hacks as well. I followed the instructions (once I deciphered them) and had the exact same issue. CUDA was no problem, but OpenCL is a different story. After doing the >2 GB fix, I then replaced the library ext file, and my Mac Pro promptly turned into a 40 pound brick. Fortunately I had a cloned disk ready to get back up and running. I've read a few other posts where people had the same problem.
Click to expand...

Yeah same :). Sounds like I'll just stick with CUDA or take the dive and do a full reformat from scratch and stay on 10.8 GM rather than the full release or 10.8.1.

----------
xav8tor said:
Doesn't amaze me. I've been ripping apart computers since the first IBM PC and done a few hacks as well. I followed the instructions (once I deciphered them) and had the exact same issue. CUDA was no problem, but OpenCL is a different story. After doing the >2 GB fix, I then replaced the library ext file, and my Mac Pro promptly turned into a 40 pound brick. Fortunately I had a cloned disk ready to get back up and running. I've read a few other posts where people had the same problem.
Click to expand...

Did your system profiler say GTX 670 4GB before trying anything? Do you have the Zotac 670 4GB?
 
1ricca said:
Yeah same :). Sounds like I'll just stick with CUDA or take the dive and do a full reformat from scratch and stay on 10.8 GM rather than the full release or 10.8.1.

----------



Did your system profiler say GTX 670 4GB before trying anything? Do you have the Zotac 670 4GB?
Click to expand...

The GM and "full release" are the same. 10.8.1 isn't a big change at all and shouldn't affect this issue either. My fiasco was with the GM and I haven't tried since. I have the EVGA 670 SC 4 GB and yes, it shows up properly and CUDA works. The OpenCL fix(es), as I said, trashed my system.
 
Holy cow I got it working. I know what I did wrong. When applying the
>2GB fix with a hex editor I did not do the "32 bit part". I only did
the "64 bit part... For ML".

This time I did both, did the dylib replacement with the ML GM
replacement file and ran fix disk permissions. Rebooted and bam! And
CUDA still works!

Luxmark 2.0 result 1089!

Thanks for all the support. Just hearing from others who have gone
down this road and comparing minute differences I figured it out.

Cheers to better, clearer instructions in the future rather than speed
typing and never linking to his other posts that are related.
 
Actual Instructions for GTX 6xx 2GB AND 4GB cards

1) Download dylib from http://rghost.net/39181502 (ML 10.8+)

2) Navigate to /System/Library/Extensions and find the file "GeForceGLDriver.bundle"

3) Right-click and "Get Info" on newly downloaded dylib file and unlock it and change to read/write for "everyone" and any other groups in there.

4) Right click on this file and select "Show Package Contents"

5) Select "Contents" then "Mac OS" and you will find the original "libclh.dylib" file. Rename this "libclhBAK.dylib"

5) Copy the new "libclh.dylib" file you just downloaded, enter your password


=<2GB Cards skip to step 10
>2GB Cards ONLY do steps 6-9


6) Navigate to /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL and make a copy of OpenCL file and rename to OpenCL.bak. DO NOT DELETE OpenCL file.

7) Make another copy of OpenCL onto your desktop and open it with a Hex Editor like Hexedit - http://hexedit.en.softonic.com/mac

8) Make these changes using cmd+f to find and replace these strings

find 3d 01 00 00 80 73 e7
replace with 3d 01 00 00 80 90 90

find ff 50 68 4c 39 e0 73 e7
replace with ff 50 68 4c 39 e0 90 90

9) Save the file and copy it into the real /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL and replace file. Enter your password.

10) Open disk utility and select your OS X hard drive partition and click repair permissions.

11) Restart

12)go to after effects and premiere apps->show package contents->contents-> add your card name (must be exact) into supported cards text files (multiple files in each app).


isn't that better? these instructions were spread out across

http://netkas.org/?p=1174

http://netkas.org/?p=1161 **

http://forum.netkas.org/index.php/topic,2774.msg13516.html#msg13516

**along with a red herring where he says "P.S. doesnt applies to gtx670/gtx680, they have a different problem" when it DID apply...

That's 2 incomplete blog posts without links to each other and a page 3 of a random thread... And netkas himself came on this forum to insult a guy on here before me, for asking questions, saying "people need to learn how to read"

Well read THIS everybody!
 
Last edited:
jhero said:
I'm on a Mac Pro 3,1 ML 10.8 and got the ASUS 670 (awesomely quiet). Installed in Slot 2 rather than Slot 1. Also, make sure you are booting into 64 bit kernel.

After having installed CUDA 5 (stock installation, did not change any additional files in framework folder) and doing the OpenCL enabler from netkas, everything works as expected. Premiere Pro (had to add gfx card name to .txt), AE (added gfx name to .txt), and Photoshop CS6 (just worked) are all accelerated. Even filters in fcp7 recognized OpenGL acceleration

Unigine Heaven gave me a result of about 10fps less than in Bootcamp but I'm sure that'll improve later down the road
Click to expand...


One final question for any of you out there. Where are the files to add supported card names to in Adobe Photoshop, AfterEffects and Media Encoder (not sure if the latter has one or not)? I only found the Premiere ones.

PS tested and confirmed both CUDA and OpenCL are both selectable in Adobe Premiere CS6 with my Zotac GTX670 4GB
 
1ricca said:
One final question for any of you out there. Where are the files to add supported card names to in Adobe Photoshop, AfterEffects and Media Encoder (not sure if the latter has one or not)? I only found the Premiere ones.

PS tested and confirmed both CUDA and OpenCL are both selectable in Adobe Premiere CS6 with my Zotac GTX670 4GB
Click to expand...

Photoshop OpenCL is natively supported by MacOS, it doesn't require any editing.

If you video card support it, Photoshop too.

For After Effects, the .txt files are located into the After Effects .app
 
jhero said:
Hey, sorry I couldn't respond earlier, hopefully things are now settled?
Click to expand...

Thanks, I got everything technically working... but seems like some plugins might still be having issues. Magic Bullet Looks is having trouble opening the editor now but I was still able to get it to open a few times. Needs looking into. These drivers are obviously not 100% solid yet.

Has anyone done any comparisons on Premiere Pro as far as performance between software MRE, OpenCL and CUDA on these workarounded cards?

EDIT: Tested out MBL on my iMac 2011 with Radeon 6570M running 10.8 and getting same issue. Probably just a ML hiccup until they update. So everything seems kosher then :)
 
Last edited:
I know this is getting off topic but it might be useful to some people out there trying this. If your workflow uses a lot of Red Giant or other non-CUDA/non-OpenCL effects, you might as well just wait until Red Giant updates their plugins and by then CUDA and OpenCL might be supported out of the box.

I did some brief tests on render times and results are as follows.
Test clip was 1080/24p H.264 dslr video clip. One with sharpening and warp stabilizer and one with sharpening, warp stabilizer, RG denoiser, and MB Looks.

OpenCL and CUDA rendered my test clip with some built-in effects in half the time of CPU rendering. CUDA and OpenCL times were exactly the same by the millisecond.

With Red Giant effects on the clip, there was no difference between any of the 3. CPU render time was identical to the others. Red Giant effects are OpenGL and seems to cause "time sharing" with the other frameworks. Even with other CUDA and OpenCL enabled plugins mixed on the same clip with Red Giant ones the results were the same.

I tried changing MB Looks to use CPU and not OpenGL and times only got worse.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back