Help with Premiere Pro GPUs

DeathPrincess

Fully [H]
Joined
May 15, 2010
Messages
18,205
I was bored and while waiting for some things to be done. I threw this together...

A few months ago, Adobe released an update to Premiere pro (cs5) which meant that the rendering of effects wasn't done entirely by the CPU, but was passed to the GPU (which makes sense) and called this thing the Mercury Playback Engine. This engine allows you with your GPUs the ability to edit video in realtime without bothering your CPU so much. Even if you try this on a hexa core 980EE i7 your going to be into problems rather quickly and it will slow down to a crawl. This engine allows you to render effects in real time. Which is a huge bonus. Especially done on 20 layers of content!
This guide came about because first of all, i've been asked several times how to do it, and secondly because nvidia + adobe are glacial in adding new GPUs to the "frequently updated list" (it's never been updated). This way I can just copy and paste a link instead of typing it out again.
Secondly, i've always been intrested which GPU work and which don't, to give better advice. Not having a huge selection to work from (9500, 260, 470, 480 old ATIs) it's hard for me to test every GPU. So I am looking for some assistance in that front. Now if people want to be helpful, they could test this out with non tested cards and see if it works. You don't even need to buy Premiere to test it, as there is a trial availible from adobe. I'd recommended it if you do any type of video editing, especially over lots of older CPU driven editors, especially as it doesn't really have much industry exposure. Being able to edit video using consumer video cards is a great help to independant video editors who don't have the budget to stretch to "professional cards" or giant suercomputer machines or something. If you do want to buy, get the education discount if you can (find a relative friend with an education email account). Its something like 66% off.
One day Nvidia and Adobe are going to add more GPUs to the list. But for now, this shall have to work.

First of all !Disclaimer! !type! !thing!
This shall only work for those with 64bit operating systems.Premiere Pro CS5 is 64 bit ONLY.
MPE runs on a single GPU ONLY. No SLI/Duals. 295 and dual GPU cards will work, but with ONE GPU only. Other cards can be left in, but just won't be used.
This guide is for the mercury playback engine, so this won't work for CS4.
This shall not work with ANY ATI cards. No CUDA = no hope. Unless ATI have started having CUDA support and this is 2200. Then please send me your old cards, as i'm probably tired of thinking 1000fps in quake 2 is funny. Though i'm probably dead or senile now.
This shall probably only work if you have the minimum spec for running Premiere. which is. CPU: Intel Core2 DUO or AMD Phemnom II, OS: Vista or 7(64bit so no XP proabably), Memory: 2GB RAM, HDD: 10gb (7200rpm or more drive), Display: 1280x900.
This isn't a crack or anything like that, nor anything illegal.
This guide is provided as is (whatever that means).There is no way this will mess up anything in your system. But just incase anything you do is your fault not mine. I'm crAppling you're ass.
All the images are hosted on tinypic, because a) i'm too lazy to host it on my host (can't remember login) and b) I can't remember that imgus or whatever it was image hosting place. If you have a better place please tell me and i'll edit.


Now if you've come this far through the annoying way I type things and my stupid layout of information then you've probably already closed the tab. But anyway

If you have one of the "officially" supported cards, you will not need to go through these steps. These are;

GeForce GTX 285
Quadro CX
Quadro FX 3800
Quadro FX 4800
Quadro FX 5800

Quadro 4000*
Quadro 5000*
GeForce GTX 470*

Quadro 5000M**

* these cards require the 5.0.2 patch to work without the steps below.
** these cards require the 5.0.3 patch to work without the steps below

I would reccommend that you fully update your copy of premiere pro to the lastest patch. This can either be done via adobe update or via the website. This is because the list has changed from the original txt file that came with the release copy, which are used for examples below. I am not sure about the patch version of the demo, but the proceeedure is still the same with any version of CS5, you will just see different initial cards listed.
One thing to note, that if adobe releases a patch that adds supported cards, on install this will replaces the cuda_supported_cards.txt file that this is based on. This will mean after such patches (such as the recent 5.0.3) the TXT file will have to be reedited. When Adobe releases more patches in the future, I shall update this guide further.




These are the steps for the workaround. (if anyone doesn't understand things then comment and i'll dumb it down more. with fraps!?)

1) Close premiere. Go to the folder where you installed premiere pro.
usually "DRIVE\Program files\Adobe\Adobe Premiere Pro CS5"


2) Open up command prompt. (easiest way is to go to the start menu and type "command prompt" and click the thing that turns up)


3) In the premiere folder find GPUsniffer(.exe) and drag it into command prompt.
And press enter. It shall come up with the following text. (if you just click it you'll just get a flash and it shall close itself)

This is with my with GTX 470 (this was done pre 5.0.2 patch so now doesn't need this now, but is shown for illustration purposes)
2ezi4ip.png


Now we can see the important GOOD information here. (i'm sure "Extensionator" isn't a word)
OpenGL Version needs to be 2.0 or greater.
Supports Shaders! = Good
all the next things need to be good obviously.
Testing for cuda support needs to find a CUDA supporting device.
Total Video Memory needs to be 765mb or more. (Total is misleading, this is total UNUSED vram)
Completed shader test! = good the ! means extra good!
Internal return value always seems to be 7.

If any of the above comes back saying bad things, then the chances are this shall not work. Also note that if it comes up good there may be a line saying "CUDA Device # 0 not chosen because it did not match the named list of cards" instead of the CUDA device # 0 Supported line. This doesn't show up in these screencaps because during the testing I added all the cards to the list before testing because i'm lazy. But don't worry about this line for now.

I'll now do this with a "bad" card and you can see what this test shouln't look like.
With 9500GS.
2v16zit.png

Ok everything is good apart from not enough memory. You can also see why the 460 has 768mb perhaps...but back to 2008, the 9500GS = bad.
Because all the shaders come back fine for this lower end 9000 series i'm guessing that the 9000 series shall all be fine if the 765mb unused RAM is there. The 8000 series i'm less certain because their older. But the 8000 PCB was used for some of the older qaudros that work, so who knows.


4) In the premiere pro folder find the file named "cuda_supported_cards" (it's a text file) and open it. Note that on computers with strict group policys you may have to disable UAC etc. to edit this file, because it resides in program files.
You'll be greeted with the following short list.

GeForce GTX 285
GeForce GTX 470
Quadro CX
Quadro FX 3800
Quadro FX 4800
Quadro FX 5800
Quadro 4000
Quadro 5000
Quadro 5000m

This is adobes rather short allowed CUDA card list. So to this list, we need to add the card that the GPUsniffer found. You need to make sure you use the exact name that GPUsniffer gave it. If it calls it a POS 201 then you name it POS 201. Heres what I added when I added a Geforce GTX 480

GeForce GTX 285
GeForce GTX 470
GeForce GTX 480 <- Here I added the 480.
Quadro CX
Quadro FX 3800
Quadro FX 4800
Quadro FX 5800
Quadro 4000
Quadro 5000
Quadro 5000m

I haven't played around with this so much, but it would make sense if you added it in order. So 480 after 470 etc. e.g.

GeForce GTX 260 <- My 260.
GeForce GTX 285
GeForce GTX 470
GeForce GTX 480 <- The 480
Quadro CX
Quadro FX 3800
Quadro FX 4800
Quadro FX 5800
Quadro 4000
Quadro 5000
Quadro 5000m

Save the file. If you want to play it safe, you can create a backup file first. Or you can just go back and delete the one line you added.


5)Rerun GPUsniffer.
Just incase it actually does something.


6) Open up premiere.
Now we're going to enable the magic GPU accelaration. Open up a project (yes you'll have to do this with every project) and go to "Project > Project Settings > General" which opens this menu.
2urq8ee.jpg


Now at the bottom is the option we want. Switch from software (CPU) to GPU accelaration.


7) Start using GPU accelarated effects!
(you can still use all the effects just the non GPU effects will be rendered by the CPU.)
The effects menu has a filter above it. (red arrow)
dmz6fs.png


Click the top left button and it filters out all non GPU effects. Any effects without this symbol aren't GPU accelarated and you'll see no difference whatsoever (i've added some childish annotation to which are and aren't. Green = GPU. Red = CPU)

OK, ANY card with 768MB VRAM and CUDA should mean the following. If you're too lazy to find out if you're card has the required specs, i've listed them all below. This was done based on my best knowledge, but theres probably lots of errors in here and I don't know every OEM version ever made, so there is likely to be a few cards missing off this list. Also, as has been pointed out the 765mb ram is UNUSED ram. So using aero/flash and other GPU using programs takes away from your total availible ram score, as does resolution, so if you are going to try this with one of the three 768mb cards you may need to diable aero/run at a lower resolution/color depth in order to get this past GPUsniffer. If the card isn't listed as tested and has less than 765mb of ram, you're welcome to try. The 1gb, 896mb cards are more certain, however. Please also note that this list is laregly based on the official cards memory values. Some like the g 210 have non standard versions made by manafacturers with a greater amount of memory than the nvidia spec, and there will work, but the standard layout wouldn't. Basically 1GB versions are what you are looking for.

The colors represent what I have found out so far.

GREEN = Already tested and works.
RED = Tested and doesn't work. Also ATI (because they don't work)
DARK GREEN = I think it should work, but not tested, so no promises.
DARK RED = Not tested, but probably wont work. But you're welcome to try.

OK big list time.

7000 Series or under. There is no CUDA support.
ALL NO

8000 Series. (you're not so safe with these because of small memory, old shaders, proabably using XP)
8100 mGPU no (memory)
8200 mGPU no (memory)
8300 mGPU no (memory)
8300 GS no (memory)
8400 GS no (memory, rev.2 as well)

8500 GT yes (1024mb model only)
8600 GS no (memory)
8600 GTS no (memory)

8800 GS yes (768mb model maybe see 768mb note)
8800 GTS no (both)
8800 GT yes (1024mb model only)
8800 GTX yes
8800 Ultra yes


9000 series (bigger memory models are safer, still i'm not so sure...)
9300 mGPU no (memory)
9400 mGPU no (memory)
9300 GE no (memory)

9400 GT yes (1024mb model only)
9500 GT yes (1024mb model only)

9500 GS no (memory) TESTED
9600 GSO Yes (768mb model maybe see 768mb note)
9600 GSO 512 Yes TESTED not 512mb model because memory)
9600 Green edition yes (1024mb model only)
9600 GT yes (1024mb model only)
9800 GT Yes (1024mb model only)

9800 GTX no
9800 GTX+ yes (1024mb model only)
9800 GX2 no

100 series (I think so, not sure if they had CUDA this is just assumed i've never owed one)
GT 100 no (low memory)
GT 120 no (low memory)

GT 130 Yes
GT 140 Yes
GTS 150 Yes


200 Series (Yes, unless its a shitty one then no)
205 no (memory)
G 210 yes (1024mb version only)

GT 220 yes (1024 model only)
GT 230 v1 yes (1024mb model only)
GT 230 v2 yes
GT 240 yes (1024mb model only)

GTS 240 yes TESTED
GTS 250 yes (1024mb model only)
GTX 260 yes (both original and core 216) TESTED
GTX 275 yes TESTED
GTX 280 yes TESTED
GTX 285 yes (already listed) TESTED
GTX 295 yes (half of it) TESTED####


300 series (see 100 series rant)
310 no (memory)
315 no (memory)

GT 320 yes
GT 330 yes (all models)
GT 340 yes (1024mb model only)


400 series (all should work as all have the magical 768mb RAM)
GT 420 yes
GT 430 yes (gddr5 model will have better performance)
GT 440 yes
GTS 450 yes (has 1gb)
GTX 460 yes (768mb model maybe see 768mb note)
GTX 460 SE yes (unreleased, if it has 1 gb VRAM etc then yes.)
GTX 465 yes

GTX 470 yes TESTED, now officially listed!)
GTX 480 yes TESTED


500 Series All work so far (all 3 cards)
GTX 550 yes (and has GDDR5)
GTX 560 yes (unless there is a 768mb version like with the 460 then that wont work)
GTX 570 yes

GTX 580 yes TESTED
GTX 590 yes (though only half)####

Quadro (these should almost all work, I haven't listed all of them)
FX 1800 yes
FX 3800 yes (already listed) TESTED
FX 4700X2 yes
FX 4800 yes (already listed) TESTED
FX 5500 yus
FX 5600 yes

FX 5800 sure (already listed) TESTED
FX 5900 go for it
CX yes (already listed) TESTED
600 yes
2000 yes

4000 Yes (already listed)
5000 Yes (already listed)

6000 yes TESTED###
Quadro Plex 7000 Yes

Quadro Mobile Specifically listed because it works without the fix
5000m yes (already listed) TESTED


The mobile versions of the nvidia GPUs should in thoery work (as the 5000m does), but I haven't listed them due to the huge variance in ram. As a rule, anything with over 800mb vram and cuda (GTX 7000 series and later) should work, even with the mobile chips.

#The 768mb note. The MPE needs 765mb ram is UNUSED ram, now if you have a 768mb card it is possible to have less than this when running the GPUsniffer program but as mentioned above you may need to lower your color depth and resolution and also stop things like AERO, transpanrency on windows and background tasks and other windows to lower your video ram usage to within 3mb. It would be difficult but i'm sure it's possible, so thats why the 768mb have been left in the "Yes" card places. MPE doesn't use all of that memory, premiere only uses about 200mb of vram running a single layer of 1080p footage and no effects. Effects ontop of this are only 1mb for simple effects and at most 70mb for more complex effects, so it's is still quite usable with this level of ram.

##Gddr2/3/5 note. Some video cards come with different types of memory. Because GPGPU activities are so reliant on vRam the bandwidth of these will affect performnce. So if given the choice between gddr3 or gddr5 for example, for this (and pretty much anything) you should go for the gddr5. The 3 will work, just with reduced performance.

###Over 4gb memory note. It would appear that for some cards over 4GBs in memory that Premiere will only use 4gbs. This isn't a limitation of CUDA, but one premiere would appear to currently have (as of the recent patch). 4GB will get you...more than I can think 1080p layers, so this will not be a problem for all but a few extreme users with the newer Quadro 6000's :D

####Dual GPU note. All Dual GPUs are set up as 2 cards in SLI with each other. This means that the vRAM, like in SLI cannot be used by the second GPU and cannot be added to the total. Exceptions, changes to this shall be noted.

Thank you!
 
Last edited:
Great write up ! thanks!

Thanks for the help with the 295! Need to find someone with something really old with 768mb memory. Oh, and I asked about the FireGL cards...their not so good. Apparently ATI hasn't put any care into them for a long time, their just the game cards with different drivers.
 
yea i figured that FireGL Card wouldnt help in premiere pro cs5. im lucky that newegg sent me a email saying they were on backorder and so i canceled the order. thanks agian
 
yea i figured that FireGL Card wouldnt help in premiere pro cs5. im lucky that newegg sent me a email saying they were on backorder and so i canceled the order. thanks agian

Its the GPU apparently, even though they both are marketed as professional graphics solutions, the FireGL is aimed squarely at programs like MAYA, CAD and such. The Quadro are more general purpose so can do more GPGPU tasks and such. Also the quatro have software specific drivers for certain programs (the professional cards use different drivers so that they use higher bit precision and such things) which the ATI cards lack, because it's kind of an afterthought project. Needs to be more competitive then these shall really go down in price!
 
Thanks for posting this, that's a great guide.

I'm still using CS4, but now that I know how to do this in CS5, here we go!!! :D
 
DeathPrincess,

I would like to make one small correction to your list:

Premiere Pro CS5 requires at least 765MB of unused (not total) graphics RAM in order to use the MPE GPU acceleration feature. It also requires a display resolution of at least 1280x900. This means that the only way for a 768MB graphics card to use MPE would be to drop the color depth to medium (16bpp); otherwise, at the minimum required resolution, there would be less than 764MB of available graphics RAM on a 768MB card. As a result, if your work in CS5 requires 32bpp, then a graphics card with at least 896MB of RAM would be required (this is because there has never been an NVIDIA CUDA-powered card with anything between 768MB and 896MB of RAM).
 
Last edited:
DeathPrincess,

I would like to make one small correction to your list:

Premiere Pro CS5 requires at least 765MB of unused (not total) graphics RAM in order to use the MPE GPU acceleration feature. It also requires a display resolution of at least 1280x900. This means that the only way for a 768MB graphics card to use MPE would be to drop the color depth to medium (16bpp); otherwise, at the minimum required resolution, there would be less than 764MB of available graphics RAM on a 768MB card. As a result, if your work in CS5 requires 32bpp, then a graphics card with at least 896MB of RAM would be required (this is because there has never been an NVIDIA CUDA-powered card with anything between 768MB and 896MB of RAM).

You are right to an extent, though a 768MB card wouldn't be enough since only 3MB would be free. Right now, I'm using 85MB of video memory in a 2D 1920x1080 resolution on the machine in my sig. 3MB might only be used in Win XP, but in Vista/7, more memory is used due to Aero and other programs such as Flash 10.1, etc.

So having a card with 1GB or more is almost essential, though cards like the GTX260 with 896MB would work just fine.

The most memory I've seen eaten up in a 2D environment with 1080p is 122MB, but I was also running Adobe Premiere Pro CS4 as well.
 
DeathPrincess,

I would like to make one small correction to your list:

Premiere Pro CS5 requires at least 765MB of unused (not total) graphics RAM in order to use the MPE GPU acceleration feature. It also requires a display resolution of at least 1280x900. This means that the only way for a 768MB graphics card to use MPE would be to drop the color depth to medium (16bpp); otherwise, at the minimum required resolution, there would be less than 764MB of available graphics RAM on a 768MB card. As a result, if your work in CS5 requires 32bpp, then a graphics card with at least 896MB of RAM would be required (this is because there has never been an NVIDIA CUDA-powered card with anything between 768MB and 896MB of RAM).

You are right to an extent, though a 768MB card wouldn't be enough since only 3MB would be free. Right now, I'm using 85MB of video memory in a 2D 1920x1080 resolution on the machine in my sig. 3MB might only be used in Win XP, but in Vista/7, more memory is used due to Aero and other programs such as Flash 10.1, etc.

So having a card with 1GB or more is almost essential, though cards like the GTX260 with 896MB would work just fine.

The most memory I've seen eaten up in a 2D environment with 1080p is 122MB, but I was also running Adobe Premiere Pro CS4 as well.

The first part of this master plan was mostly about fooling the GPUsniffer to register cards that would otherwise be turned away, which is where the 765 number came from. The lowest ram I have got it to work with so far is 896 (the 260), so I need to find someone with a 8800 GS or a 9600 GSO (the older models with 768mb) or even a smaller 460 (maybe why there is two models?). I haven't actually done any tests to see how much of the VRAM gets used during various applications, and need to come up with a set of benchmarks, testing a 1.2gb ram 470 against a 896mb 260. But as I said the 260 does work fine, but you are correct that the OS will take away a chunk of this memory, especially at higher color depth. Especially if the 400 series of cards can do deep color, I know sub 200 definately cannot even though the quadros can (using the same GPU).

Thankyou, ill make some adjustments!

What I didn't notice before is that there is a "Device: 00000000002D46C8 has video RAM(MB): 896" Then later "Total Video Memory: 877MB" which is 18mb less. So it must discount used video memory. This was done with several irems running just now (source SDK load of internet windows/normal things) with aero and win 7 with 1 monitor at 1680/1050. The 9000 series "fail" test was done with nothing running on a different computer with the same OS and shows 17mb using the same monitor.
Because of the line "cuda device not chosen because 658mb are required, and 495mb are present" it must mean it is coming form the availible, not total memory. So people running the three cards mentioned before would have to set the resoultion/color depth in order to run the GPUsniffer. But what i'm not sure is if premiere would run after returning to a higher color depth/resolution, and how stable/quick it would be. Do either of you have a 460 per chance?

@Red Falcon, also have you tried using CS5 yet?
 
Last edited:
The first part of this master plan was mostly about fooling the GPUsniffer to register cards that would otherwise be turned away, which is where the 765 number came from. The lowest ram I have got it to work with so far is 896 (the 260), so I need to find someone with a 8800 GS or a 9600 GSO (the older models with 768mb) or even a smaller 460 (maybe why there is two models?). I haven't actually done any tests to see how much of the VRAM gets used during various applications, and need to come up with a set of benchmarks, testing a 1.2gb ram 470 against a 896mb 260. But as I said the 260 does work fine, but you are correct that the OS will take away a chunk of this memory, especially at higher color depth. Especially if the 400 series of cards can do deep color, I know sub 200 definately cannot even though the quadros can (using the same GPU).

Thankyou, ill make some adjustments!

What I didn't notice before is that there is a "Device: 00000000002D46C8 has video RAM(MB): 896" Then later "Total Video Memory: 877MB" which is 18mb less. So it must discount used video memory. This was done with several irems running just now (source SDK load of internet windows/normal things) with aero and win 7 with 1 monitor at 1680/1050. The 9000 series "fail" test was done with nothing running on a different computer with the same OS and shows 17mb using the same monitor.
Because of the line "cuda device not chosen because 658mb are required, and 495mb are present" it must mean it is coming form the availible, not total memory. So people running the three cards mentioned before would have to set the resoultion/color depth in order to run the GPUsniffer. But what i'm not sure is if premiere would run after returning to a higher color depth/resolution, and how stable/quick it would be. Do either of you have a 460 per chance?

@Red Falcon, also have you tried using CS5 yet?

http://blog.orbmu2k.de/

Use the top two tools to measure your GPU memory usage ;)

As for CS5, no, and I probably won't until I make a new build with a dedicated video card with 1GB+ memory.

Right now I use my netbook (in sig) to do all of my video editing with Premiere Pro CS4.
 
ok here we go! First test with the NVIDIA inspector 1.91

For this i'm using the secondary rig as i'm too lazy to swap things about.

For scientific purposes everything is at stock
Q8200 (quad core) @ 2.33
4gb RAM (800mh/z DDR2)
Stocked 896mb GTX 260 (XFX 216 core model)
OS is win 7 ultimate 64bit
Screen is 1680x1050 60h/z


From desktop (aero, with only a single 1680x1050 monitor, and [H] in ie8) Intrestingly [H] uses 3mb of vram (i'm guessing the java). Steam uses 18mb. I closed all of that. With a few tasks floating around it's 88mb.
Now to test how much vram this uses at desktop.
Going down to 1280/960 gives me 85mb. usage.
Back at 1680 dropping to 16bit color gives me 22mb usage!
Stragely when I drop to 1280 it goes UP to 76mb...Until I find that changing resolution in win7 resets the display to 32bit. We now have an ugly display and 21mb.
Disabling aero still leaves it at 21mb, which might be due to background items, or program error. (GPU is constantly at 0% at every stage).

Ok back to being pretty, closed all the background junk. Now reading 60mb, i'll take that as the base reading. (this program does seem to have lag on the reading of a few seconds). So take away about 60mb (or more damned java updates) from all these measurements. Also I'm not doing this fullscreen, plus aero, 32bit color, so all these measurements could be about 38mb lower ontop of this.

Premiere pro doing nothing registers as 112mb.
Loading in some AVCHD footage at 1080p/25fps is 192mb
Playing vanilla footage shows 199mb and 3% GPU

I noticed this program has a small lag on it. But playing the 1080p footage uses about 70mb ontop of base premiere vram.

Applying RGB curves (4 curves layers) 200mb.GPU 8%
Added noise generation layer (100% noise) 200mb. GPU 9%
Added a gausian blur layer 234mb 15%
Added a second layer of 1080p footage at 50% opacity (which looks cool!) ontop.234mb(might be an error but tried it 3 times) 16%.
Third layer 50% opacity. 256mb 18%.
4th video layer with basic 3d offset added (rotated on Z) at 33% opacity. 321mb 23%
5th layer 33% opacity 3d rotated, drop shadow 433mb 27%
8 point matte applied to 4th layer. 433 28%
Levels on 3rd layer. 434mb 28%
Fade in put on all 5 levels 535mb 34% for duration of fade then 434mb 28%

CPU never went above 40% (avchd decoding i'm guessing), and never went below full speed playback.

So 5 1080p 25fps layers with fade, 1 or more effects and a matte and 2 different 3d rotations uses about 475mb of memory. Some effects (3d rotations, fades) use about 20-30mb more and basic effects (noise, blur, histograms) use only 1mb more memory roughly. The additional layers seems to have a culmative effect, of adding a few more vram mb's but probably have more effect on RAM and HDD. The usage % of the VRAM was usually above the GPU % but that does put into question some of the lower end 8000/9000 that might be GPU limited before the 758mb question comes up.
 
Last edited:
DP thanks so much for doing this. I built a PP/CS5 workstation for work, and I went through all sorts of personal hell justifying a gaming video card (GTX 470) to my boss. (and it beats spending 4X as much for a Quadro "workstation" card)

9000 series (bigger memory models are safer, still i'm not so sure...)
9300 mGPU no (memory)
9400 mGPU no (memory)
9300 GE no (memory)
9400 GT yes (1024mb model only)
9500 GT yes (1024mb model only)
9500 GS no (memory) TESTED
9600 GSO Yes (768mb, 1024mb models only)
9600 Green edition yes (1024mb model only)
9600 GT yes (1024mb model only)
9800 GT Yes (1024mb model only)
9800 GTX no
9800 GTX+ yes (1024mb model only)
9800 GX2 no

BTW, Newegg's shellshocker today (8/5/2010) is a EVGA 9600GSO w/ 1.5GB for $25 after rebate card. I snagged one just to see if it would work w/CS5's Mercury/CUDA engine.
 
BTW, I had to turn UAC off to edit the "cuda_supported_cards" file.
 
BTW, I had to turn UAC off to edit the "cuda_supported_cards" file.

The fermis do work great for premiere (it's what I use) and they are supposed to be the next cards to get "official" acceptance! If the GSO works/doesn't please report back! he quadro cards have always kind of...irked me being so expensive for what they are (gaming cards with different drivers) you do get better support however, so some of the extra cost is justified and some more ram. The MPE is great because it can run on "gaming" cards and the quadros can't run games, so its win/win and I was able to get a gaming rig under the guise of video editing machine!
I've never come across the UAC to edit the cuda support file, which OS is that using? As all I have had to test it has been win7 ultimate.
 
Last edited:
TThe MPE is great because it can run on "gaming" cards and the quadros can't run games, so its win/win and I was able to get a gaming rig under the guise of video editing machine!

I've resisted every temptation to install Steam on this sucker- just to see what this 470 can do. (I have a GTX 260 216 at home)

I've never come across the UAC to edit the cuda support file, which OS is that using? As all I have had to test it has been win7 ultimate.

Win 7 Enterprise x64. (supposedly identical to Ultimate)

It may be some obscure group policy.
 
I've resisted every temptation to install Steam on this sucker- just to see what this 470 can do. (I have a GTX 260 216 at home)

Win 7 Enterprise x64. (supposedly identical to Ultimate)

It may be some obscure group policy.

But you do know that games are one of the "best ways to test out airflow and heat in a case"! Epecially in "workstations". You don't want that thing overheating during a rendering run, which would cost you "time and money!" So just get steam and run...metro 2033 for a few hours to make sure everything is fine! You can't put a price on "safety"!

The file being in program files probably does flag up UAC in more "company" setups, which would make sense in more controlled enviroments to stop people editing it (I just mispelled enviroments about 10 times). But it is worthy of adding to the guide as many people will be doing this in a more professional enviroment!
 
Gah... I wish Sony would implement something like this for Vegas Professional... I can't stand Premiere. :(
 
But you do know that games are one of the "best ways to test out airflow and heat in a case"! Epecially in "workstations". You don't want that thing overheating during a rendering run, which would cost you "time and money!" So just get steam and run...metro 2033 for a few hours to make sure everything is fine! You can't put a price on "safety"!

Airflow is not a problem. There are five case fans on the case, and three are LED-lit. Yeah, my boss gave me hell about that too. He who thought a pre-configured Craptiflex would be more than enough for CS5. And he vetoed other components for the build like SSDs, Raid-0 HDDs, quieter more efficient CPU coolers and an extra 6GB of RAM.

But the rig as is would run Just Cause 2 like buttah.... if I were so inclined.
 
Airflow is not a problem. There are five case fans on the case, and three are LED-lit. Yeah, my boss gave me hell about that too. He who thought a pre-configured Craptiflex would be more than enough for CS5. And he vetoed other components for the build like SSDs, Raid-0 HDDs, quieter more efficient CPU coolers and an extra 6GB of RAM.

But the rig as is would run Just Cause 2 like buttah.... if I were so inclined.

What is it using as an HDD? Raptors? To be honest though, during this test above I was using a single hitachi deskstar 7100k whatever its called 7200rpm drive and it was fine. I think it depends on what type of footage you want to run!
You should point out that while it will run with those specs, the ram etc will allow faster rendering and workflow, so it will make the unit more productive, remember that the extra 6gb would limit the overclock, if you're using one. But from your boss it sounds unlikely! Plus for most things it's not needed! LED fans are a bit hit and miss, if they go with your colors, then fine! I'm still stuck with my blue fans in my green and purple WC setup. so its not...
But the "airflow testing" is a great ruse for gaming on things. You need to make things "very hot" so play a game for a few hours, the most intensive you can find! For at least 3 hours for "burn in"!
 
The fermis do work great for premiere (it's what I use) and they are supposed to be the next cards to get "official" acceptance! If the GSO works/doesn't please report back!

:cool:

Geforce-9600-GSO-512.jpg


The biggest difference is the "Compute Capability" score of 1.1. (vs 2.0 for the GTX 470) But the GPU enhanced effects showed up in the PP menu, and I was able to color correct a clip w/o rendering the timeline.
 
The biggest difference is the "Compute Capability" score of 1.1. (vs 2.0 for the GTX 470) But the GPU enhanced effects showed up in the PP menu, and I was able to color correct a clip w/o rendering the timeline.

Thankyou for that!
Damnit another internal return of 7! I want to know what that means! it's always been 7, but you are using windows 7?...
The 9500GS got a 1.1 too, so it makes sense that the 9600 +O has the same value! I't might be something to do with OpgnGL... Yours worked because the memory was higher, so that is a good sign for the 9000 and possibly 8000 series that they are vram limited only! Why did they leave the name with a 512 on the end? It should be called a GSO 1536! I also noted something I have missed! With both the cards I ran it with their names already on the list, so I missed the line about "non listed card"! I'll add that and the TESTED card. It's now the earliest confirmed working card!
CS5 with no rendering is so much better than CS4! I just wish theyd add more effects already. But then again it's has most things covered already!
 
Last edited:
Thankyou for that!
Damnit another internal return of 7! I want to know what that means! it's always been 7, but you are using windows 7?...

Yup, just replaced the GTX 470 w/ the 9600 GSO on the machine at work. And despite slight temptation, I put the 470 back. :)

The 9500GS got a 1.1 too, so it makes sense that the 9600 +O has the same value! I't might be something to do with OpgnGL... Yours worked because the memory was higher, so that is a good sign for the 9000 and possibly 8000 series that they are vram limited only! Why did they leave the name with a 512 on the end? It should be called a GSO 1536!

This particular 9600GSO has half of the stream processors as the other GSOs. (48 as opposed to 96) I'm assuming the "512" is simply to denote that change since there are other cards with 1GB and 1.5GB configurations

I'm guessing the Compute Capability score is directly tied to the number of stream processors on the GPU.
 
Yup, just replaced the GTX 470 w/ the 9600 GSO on the machine at work. And despite slight temptation, I put the 470 back. :)



This particular 9600GSO has half of the stream processors as the other GSOs. (48 as opposed to 96) I'm assuming the "512" is simply to denote that change since there are other cards with 1GB and 1.5GB configurations

I'm guessing the Compute Capability score is directly tied to the number of stream processors on the GPU.

You got me intrested and I looked it up, and there was two models of the 9600 GSO. A normal 9600 GSO and a GSO 512.
The chips and clocks were different. Core/Shader/Memory
The GSO - 550 1375 1600
The 512 - 650 1625 1800
The cores were a g92 chip for the normal and a g94 for the 512. And a 65nm core was replaced by a 55nm for the 512. And the chips were 96 shaders (cuda cores) 48 (textures)12 ROPs for the normal and 48/24/16 for the second chip. But the 512 used more power... oh nvidia. It's faster at pixelfill, but slightly slower at textures (having half the texture cores). The 512 was because it was the only GSO with 512mb. You are correct! But it does mean new entries! There was also a 768mb 512...and a 1gb.
The 9500 GS has 32 of the CUDA cores of your card again and various factors means it has half the terraflops. So it's a mystery again...But it's good to see that it was only the memory that failed the card...

Well at least you can game and high quality at work. You just need to work an SLi angle in there...it's more difficult as hardly any professional applications use SLi which is damned stupid...
 
More cards added.

The Plex 7000 with Dual Fermi GPUs and 6gb of RAM looks promising. This will definately have support with 3gb of RAM per GPU. The SLi is promising as well. Having Sli on a "officially" supported card would hopefully mean that SLi would work for other setups as well (though to be honest this isn't really needed for most premiere/after effects work...)
 
More cards added.

In addition, Premiere Pro CSE 5.02 update is now available for download. The new version now adds "official" (Adobe-certified) support for three of the new Fermi GPUs: the GTX 470, the Quadro 4000 and the Quadro 5000. Users who have the GTX 470 and have already applied the "hack" may now undo that hack before applying the 5.02 update.

Thus, you should now see the following GPUs in the default cuda_supported_cards.txt file after updating to 5.02:

GeForce GTX 285
GeForce GTX 470
Quadro CX
Quadro FX 3800
Quadro FX 4800
Quadro FX 5800
Quadro 4000
Quadro 5000

Sorry, GTX 480 users. You'll still need to reapply the hack after updating to 5.02 since the update will replace the hacked cuda_supported_cards.txt file with a new default cuda_supported_cards.txt file.
 
Last edited:
In addition, Premiere Pro CSE 5.02 update is now available for download. The new version now adds "official" (Adobe-certified) support for three of the new Fermi GPUs: the GTX 470, the Quadro 4000 and the Quadro 5000. Users who have the GTX 470 and have already applied the "hack" may now undo that hack before applying the 5.02 update.

Thus, you should now see the following GPUs in the default cuda_supported_cards.txt file after updating to 5.02:

GeForce GTX 285
GeForce GTX 470
Quadro CX
Quadro FX 3800
Quadro FX 4800
Quadro FX 5800
Quadro 4000
Quadro 5000

Sorry, GTX 480 users. You'll still need to reapply the hack after updating to 5.02 since the update will replace the hacked cuda_supported_cards.txt file with a new default cuda_supported_cards.txt file.


Thanks for this! I just got the update because i'm all fresh install AGAIN...SSDs are wonderful, but i've been unlikely twice in 1 week.

It's weird they didn't include the 480...as the only difference from the 470 is more memory and 1 more unlocked cluster on an otherwise identical (same exact chip) GPU...At least thats in my mind official confirmation for the 480 and 465, and so they must have fixed the "rendering errors with fermi" whatever they were (that I never noticed!).
I just thought I should add a list for the "official" cards to the top, to stop those with those cards from going through the process needlessly. Also the guide sections will need to be updated!
I read through the Reade me and they have fixed quite a lot of junk. Especially the p2 footage drag and drop weird delay. I'm not sure if you need to undo the hack or the update will simply overwrite it. It is probably safer to just reset the text file. Updating...
 
I'm not sure if you need to undo the hack or the update will simply overwrite it. It is probably safer to just reset the text file. Updating...

The hacked text file is simply overwritten by the new default text file when updating from 5.0.0 or 5.0.1 to 5.0.2.
 
Last edited:
The hacked text file is simply overwritten by the new default text file when updating from 5.00 or 5.01 to 5.02.

Thats good! Well also bad too, as the file will have to be redone after every card adding update! Still i't good they added 3 more. I just wish they hadn't randomly picked the one card I used for all the code screenshots! Added another line about that.
 
This guide worked for me with my GTX 260 but whenever I am rendering a large sequence it crashes with C++ error or Nvidia driver error. I'm using the latest drivers. 258.96

Any ideas?
 
This guide worked for me with my GTX 260 but whenever I am rendering a large sequence it crashes with C++ error or Nvidia driver error. I'm using the latest drivers. 258.96

Any ideas?

I'm using a 260 on the second rendering machine and haven't had any problems like that. So this will need some troubleshooting.

When you say rendering, do you mean in the timeline or on the output? (via media encoder) also does it always happen at the same point, with the same effect etc?

Did you patch Premiere to the latest version 5.0.2? And if you have did you reapply the fix after doing so? The patch does solve a few problems with the program that causes C++ errors in certain situations. Especially with cineform files.

I'd try a repair install of CS5. C++ files sound like they've been broken at some point. I know of a few people that have had the same errors without the fix as well, and that helped for them. Make sure you reinstall the patches if needed.

Another thing that might help is going to the Nvidia control panel, then finding "Manage 3d settings".
On this find Premiere Pro CS4 (for some reason CS5 is listed as CS4...). If it's not listed click add and find the Adobe Premiere Pro.exe file (in Program files\Adobe Premiere Pro CS5).
Now change "Multi-display/mixed-GPU acceleration" to compatability mode. And apply and exit. (youll have to restart premiere for it to have effect).

I asked someone and they said something about some computers bios having a "nVidia GPU Ex" setting (for controlling memory) and to make sure this is disabled. This does sound like it's related to video card memory. Have you got anything that monitors Vram usage during renders?

If none of those help i'lll come up with some more!
 
I'm using a 260 on the second rendering machine and haven't had any problems like that. So this will need some troubleshooting.

When you say rendering, do you mean in the timeline or on the output? (via media encoder) also does it always happen at the same point, with the same effect etc?

PPBM5 benchmark program is what it was doing when I first had it happen. Yes timeline though.

Did you patch Premiere to the latest version 5.0.2? And if you have did you reapply the fix after doing so? The patch does solve a few problems with the program that causes C++ errors in certain situations. Especially with cineform files.

Yes.

I'd try a repair install of CS5. C++ files sound like they've been broken at some point. I know of a few people that have had the same errors without the fix as well, and that helped for them. Make sure you reinstall the patches if needed.

Okay.

Another thing that might help is going to the Nvidia control panel, then finding "Manage 3d settings".
On this find Premiere Pro CS4 (for some reason CS5 is listed as CS4...). If it's not listed click add and find the Adobe Premiere Pro.exe file (in Program files\Adobe Premiere Pro CS5).
Now change "Multi-display/mixed-GPU acceleration" to compatability mode. And apply and exit. (youll have to restart premiere for it to have effect).

Did this. Nothing changed.

I asked someone and they said something about some computers bios having a "nVidia GPU Ex" setting (for controlling memory) and to make sure this is disabled. This does sound like it's related to video card memory. Have you got anything that monitors Vram usage during renders?

First I've heard of this I will try it tonight

If none of those help i'lll come up with some more!

Thank you so much.
 
No under normal circumstances it works fine. Guess I should just live with it. I'm a sucker for a good benchmark though.:D
 
No under normal circumstances it works fine. Guess I should just live with it. I'm a sucker for a good benchmark though.:D

It would appear its something the benchmark is doing. I looked at the site and it says it's just a project file...but how does it gather the results then? Does it also include a program file of any kind?

I had something similar when I saw the heatsink benches on HardOCP... all of their results said a i7 idle at 25c...or something. I spent ages redoing my cooling until I got down to 28c (I was still annoyed why my CPU was so hot..)...problem was that they had taken away the ambient tempreture from the results. So it was actually 50c (or something) in the benchmarks. I sat going through TIM, redoing things like airflow, more fans, different directions to get down to 25c... Later I found out the original 38c for an i7 was lower than normal. Benchmarks seem to exsist to make people feel something is lacking/wrong with their systems. :D

If any other problems happen with normal rendering theres probably more things that can be done. Adobe software does tend to have its...moments.

Oh and...

Theres a new Nvidia beta driver out now, that might be worth a try...
 
Last edited:
Yes the new driver. Excellent. As far as the benchmark.....it runs a script at the end that you answer 22 questions to and then you send in your results. It is supposed to show areas where your system is "lacking". I guess I shouldn't be too disappointed, even without the help of CUDA I still scored somewhere in the middle.


Thanks for you help again. ;)
 
So upon further inspection and use I have realized that I am running out of V-ram. It shows in EVGA Precision I am using 890mb. Then it crashes. I think I found my answer. Guess its time for a 1GB card.
 
So upon further inspection and use I have realized that I am running out of V-ram. It shows in EVGA Precision I am using 890mb. Then it crashes. I think I found my answer. Guess its time for a 1GB card.

How many layers and what kind of footage is that video benchmark using!?

If you look above (here) theres a vRam usuage test 5x 1080p AVCHD with a load of effects that uses 475mb total vRam. Which was also done on a XFX 896mb GTX260 (the 216 core one)

It really depends on what you are going to do with it. Even on some of my "wilder" videos I usually never get about 3-5 layers. Most effects like color correction, levels and histogram type adjustments don't take much vRam. The 3d manipulations and fading in/out of clips (alpha changes like opacity didnt take much, just fades for some reason) took the most.

Remember theres stuff you can do to increase your vRam. Like closing background things, turning off aero, transparency. Shutting anything that uses vram would help obviously. Also if your using multiple monitors shut them off if their not needed.

But whether you need to get a 1gb card is down to how much your going to use. Remember most benchmarks are designed to stress the system to breaking point, and from the sounds of it will use more vram than is likely to be used in a normal situation. If you are looking to edit footage off a red ONE camera or do lots of 4k/6k footage then it would be a good idea to go buy a quadro with 4gb. Also if you are planning to do something with heavy heavy layering (above 10 footage layers) or some heavy scheme of post production it might be a good idea. But really, only upgrade if you need to. If it comes to being a annoyance often and your running into difficulties on a weekly basis based on vRam then i'd go for the new card. But the benchmark probably doesn't represent a normal workflow. Unless you really wan't to make a benching machine or can get/exchange for one for cheap!
 
More cards added.

GTS 450 (specs list 1gb) so should work.
Also
GTS 430 which isn't released yet but lists 1gb Vram, looks like a 460 variant. It's only $86.70 so might be one of the cheaper options that should work (obviously I haven't tested it yet). It is almost a single slot (the heatsink/fan goes abot the line, but the backplate is single slot, so might be a decent physx GPU...
 
Back
Top