Skip to main content
Curt Wrigley
Inspiring
April 1, 2010
Answered

Pr CS5 - List of supported CUDA Cards

  • April 1, 2010
  • 24 replies
  • 65419 views

Adobe is working on a playback and rendering engine for Adobe Premiere Pro called the Mercury Playback Engine. This new engine is NVIDIA® GPU-accelerated, 64-bit native, and architected for the future. Native 64-bit support enables you to work more fluidly on HD and higher resolution projects, and GPU acceleration speeds effects processing and rendering.

The Mercury Playback Engine offers these benefits:

  • Open projects faster, refine effects-rich HD and higher resolution sequences in real time, enjoy smooth scrubbing, and play back complex projects without rendering.
  • See results instantly when applying multiple color corrections and effects across many video layers.
  • Work in real time on complex timelines and long-form projects with thousands of clips — whether your project is SD, HD, 2K, 4K, or beyond.

Ensure your system is ready to take advantage of the Mercury Playback Engine in a future version of Adobe Premiere Pro. The Mercury Playback Engine works hand-in-hand with NVIDIA® CUDA™ technology to give you amazingly fluid, real-time performance. See it in action

* PR CS5 supports the following list of CUDA cards:

GeForce GTX 285Windows and MAC
Quadro FX 3800Windows
Quadro FX 4800Windows and MAC
Quadro FX 5800Windows
Quadro CXWindows

More hardware details:

http://www.adobe.com/products/premiere/systemreqs/

    This topic has been closed for replies.
    Correct answer Wil Renczes

    I think I just have to wait and see how bad my GTX260 will perform before I buy a new card. I would like to know wich card to buy, though...that´s why I am interseted in knowing the difference in performance between the supported cards. But I´ll try to patient.

    About the Mercury Engine supporting CUDA - i just found this post: http://forums.adobe.com/message/2583980#2583980

    It seems that the Mercury Engine was not initially build for CUDA, but just for 64-bit...that might be the answer to why all CUDA cards are not supported. But tell us the story Adobe and Nvidia!!!!

    Could one of your evangelists or some one else from Adobe and/or Nvidia (no offense to all you great guys who have heard something from someone who might know etc) not enlighten us here, in this forum, before we start some kind of conspiracy theory about Adobe and Nvidia? Put the (video)cards on the table (so to speak ;-) ) and tell us:

    1. What is the main reason why all NVIDIA CUDA cards are not supported? Is it techincal? A time issue? Or what? Why?

    2. When will we know if older less expensive Nvidia cards like GTX 260 will also be supported? We need to know so we can see if we need to buy new cards or just stick to the old ones long eneough to get support....is this not a valid wish?

    3. When will we get an overview of how the supported cards perform compared to each other in preview, rendering etc.? We need to know so we can get excact the card that meets our needs. Roight now I don´t know if I just need a GTX285 or the Quadro CX. I need to know how much more performance I will gain from buying a much more expensive card. If I get fx. a 50% performance boost buying the CX I will buy it at once. Is it only 2% I think I will buy the GTX 285...otherwise i would be a fool with my money.

    These are all questions that would be nice to get answers to before the shipping of CS5 - so we can make our choices whether to buy new videocards and if - which to buy - or we would like to wait untill our existing older Nvidia cards is working with the Mercury Engine. If we continue to not get any information about these questions this could develop into be a karma-killer for both companies....And you both have good karmas with me untill now!

    I very much like Adobes products - been using allmost every one of them them for years. I have also had several Nvidia Cards over the years and have only tried the ATI cards a few times with bad experiences. So i stick to Adobe and Nvidia - no matter what - have no choice either;-) But I will be a very unhappy and dissapointet customer and user, if this story ends up looking like some kind of dirty deal between two companines. But I guess there is an explanation and it has to come from your comapines directly - not from a second source.

    You could avoid all this by being more open about this issue and tell us more - and no more sales-talk - we allready want your products - they are all great - but we need help to find out which and when to buy what....please!


    Now that the launch is done and this information is all public, I'm going to summarize all the bits of information that have been floating around into one distilled post:

    The Mercury playback engine comprises of 3 areas (our chief weapons are surprise, surprise and fear...  nevermind...):

    - 64 bit support, and better memory management / frame cache management / sharing between the Adobe apps (ie Premiere and After Effects & the Media Encoder have a notion of shared memory now, and are aware of how much is being consumed by their peers);

    - optimizations to multithreaded rendering, to the playback's pipeline, speed improvements with various media types, and all around general fine tuning

    - CUDA acceleration of effects / transforms / pixel conversion routines.

    Don't have a supported CUDA board?  You still get two out of three.  Might not seem as sexy on the cover, but CS5 is still a massive improvement over CS4 even without the hardware acceleration.

    (Conversely:  let me dispel the myth that you can drop in a CUDA supported board into any box and you magically get umpteen layers of RED 4K in realtime.  All that CUDA does is free the CPU from the tasks of doing image processing - video footage however still needs to be decoded by the CPU.  If you're looking to do high end 4K, do yourself a favor and don't shortchange yourself on a cruddy box.  Get an i7, for cryin' out loud...  but I digress)

    Now, why the limited card selection?

    One of the biggest themes was to improve stability and making Premiere truly earn the Pro moniker.  To quote another engineer, "This was a decision about being Pro."  By limiting the selection of cards, you have a guarantee that the product will do what it's supposed to, that your rendering accuracy will be as good as in software, and that these cards will play nice with 3rd party I/O vendors.

    What's the difference between the level of functionality I get with the GTX 285 vs the Quadro boards?

    The GTX is limited to 3 streams of realtime.  Also, the Quadros come with more memory, so this helps if you're looking to do hi-res (eg RED) editing. Lastly, as a gaming card set, the GTX cards will downclock themselves if they're overheating, so your performance might drop if your cooling isn't the best.  The Quadros OTOH have a fixed clock rate, assumingly they have better heat tolerance levels.

    When will that selection expand?

    TBD.  All I will say is that we are looking at some of the next-gen Fermi cards, but they're still undergoing evaluation.  Let's put it this way - the beta users group is still running so that they can help test the new card support going forward.   Keep your ear to the ground, I'm sure there will be plenty of noise made when they're announced.

    Can you add me to the beta list?

    Nope.  Not my domain, I'm afraid.

    What's the scoop with ATI cards, and openCL?  Why nVidia / CUDA only?

    When the acceleration work began over a year & a half ago, openCL wasn't even a finalized specification.  CUDA was a more mature technology, so that's what we went with.  For the future? It'll be evaluated for CS 6.

    24 replies

    Inspiring
    July 19, 2010

    Too bad this thread has gotten so snotty, as it started out to be a helpful review.

    Anyhow, I'm locking it for the time being.

    Participant
    June 15, 2010
    Want Premiere pro CS5 / Mercury Playback for your non-compatible graphics card? Here's the solution:

    How to make Premiere CS5 work with GTX 295 CUDA and possibly all 200 GPUs
    ________________________________________
    Here are the steps:

    Step 1. Go to the Premiere CS5 installation folder.
    Step 2. Find the file "GPUSniffer.exe" and run it in a command prompt (cmd.exe). You should see something like that:
    -----------------------------------------------------------------------------------------------------------------------------------
    Device: 00000000001D4208 has video RAM(MB): 896
    Device: 00000000001D4208 has video RAM(MB): 896
    Vendor string: NVIDIA Corporation
    Renderer string: GeForce GTX 295/PCI/SSE2
    Version string: 3.0.0

    OpenGL version as determined by Extensionator...
    OpenGL Version 2.0
    Supports shaders!
    Supports BGRA -> BGRA Shader
    Supports VUYA Shader -> BGRA
    Supports UYVY/YUYV ->BGRA Shader
    Supports YUV 4:2:0 -> BGRA Shader
    Testing for CUDA support...
    Found 2 devices supporting CUDA.
    CUDA Device # 0 properties -
    CUDA device details:
    Name: GeForce GTX 295 Compute capability: 1.3
    Total Video Memory: 877MB
    CUDA Device # 1 properties -
    CUDA device details:
    Name: GeForce GTX 295 Compute capability: 1.3
    Total Video Memory: 877MB
    CUDA Device # 0 not choosen because it did not match the named list of cards
    Completed shader test!
    Internal return value: 7
    ---------------------------------------------------------------------------------------------------------------------------------------

    If you look at the last line it says the CUDA device is not chosen because it's not in the named list of card. That's fine. Let's add it.

    Step 3. Find the file: "cuda_supported_cards.txt" and edit it and add your card (take the name from the line: CUDA device details: Name: GeForce GTX 295 Compute capability: 1.3

    So in my case the name to add is: GeForce GTX 295

    Step 4. Save that file and we're almost ready.

    Step 5. Go to your Nvidia Driver control panel (im using the latest 197.45) under "Manage 3D Settings", Click "Add" and browse to your Premiere CS5 install directory and select the executable file: "Adobe Premiere Pro.exe"

    Step 6. In the field "multi-display/mixed-GPU acceleration" switch from "multiple display performance mode" to "compatibility performance mode"

    Step 7. That's it. Boot Premiere and go to your project setting / general and activate CUDA

    Tried it and tested, unbelievable speed comes from this little trick. Will try a GT9800 as well. Thought the people in here using CS5 could use this high performance tip.

    Best,
    Kaliya
    kaliya is online now Add to kaliya's ReputationReport Post  Edit/Delete Message
    Participant
    June 16, 2010

    Fantastic, kdd108.

    I'm very interested in your 9800 experiment.

    I have several friends on mac desktops that have the 8800 equivalent card, and if the 9800 works, there's a good chance they'll be able to tweak their settings and get accelerated effects.  They're still sitting on the upgrade fence, but I'm sure that would get them off it.

    Known Participant
    June 16, 2010

    canuscanus wrote:

    Fantastic, kdd108.

    I'm very interested in your 9800 experiment.

    I have several friends on mac desktops that have the 8800 equivalent card, and if the 9800 works, there's a good chance they'll be able to tweak their settings and get accelerated effects.  They're still sitting on the upgrade fence, but I'm sure that would get them off it.

    many 8800 only have 512 or 640MB though

    Moxtelling
    Inspiring
    May 5, 2010

    Hi

    I can now confirm that FX3800 (wich I have just installed) and a GTX 260 (with the modificated txt-file as described elsewhere in this forum) - are performing equal in playback. I can not see any difference in speed or performance playing back. Have not tested encoding speed - and will not either - don´t wanna install the old GTX once agian. The AVCHD clips i had problems playing with the GTX 260 does have the same issues with the FX3800. But I have found out that the main reassons are: 1) using non-accelerated effetcs like Shadow/Highlight 2) The AVCHD issue with CS4/CS5 - that one can not use the same clip twice adjacent to each other. Fx if you take a movieclip and make two clips out of it and put them togehter at the timeline and use a Croos-dissolve between the two clips - you will experience stuttering and pausing in playback if you use AVCHD. THis issue has been reported to Adobe!

    So waste of money? Maybee - but at least I now have a card that has been tested and is officially suppoorted by Adobe/Nvidia. My FX3800 is from PNY and there are as I recall only this manufacterer - when my GTX is from Inno3D - and there are lots of dirfferent manufacturers. Meaning the FX3800 is more Pro in the way it is allways made by the same company - and not as the GTX made by several.that might user different parts in the production that may vary and give different results - and might even cause issues? BEsides the FX3800 has been heavely tested by Adobe to meet the requirements - so they say...

    So - all in all - I hope I made a good choice here.Hoping for Adobe to give even more advantages in near future to us that has invested in supported Nvidia cards.

    /Morten

    Known Participant
    May 5, 2010

    Morten, I think you made a great choice. I'm thinking of buying the FX3800 to "get me by" until the next round of video cards gets validated. I strongly feel that the Quadro series is heading toward Legacy Land in the near future. As far as getting non-certified cards to work, I'm okay with it but would choose not to go down that rural road being that CS5 is in it's infancy. I think there will be enough variables (or shall I say bugs) to deal with early on without introducing more by faking out MPE by putting a non-certified video card in the picture! Come to think of it, I may not bother with MPE at all, being that I only have two 2Tb drives in a RAID 0 for media (but they are the new SATA III kind). I just hope I'll at least get faster rendering out of CS5. And even if I don't, the stability of a 64-bit app alone is worth the upgrade to me.

    metalsaber
    Participant
    May 5, 2010

    The "hack" works with my GTX 260 card.  My 480 should arrive today.  Will install it and put the new card in the list.  Will check it out.

    Participant
    May 3, 2010

    Are the GTX 285 1gb and 2gb cards compatible with Premiere CS5 ? I am putting together a computer  right now and just wanted to make sure everything would work fine.

    Participating Frequently
    May 3, 2010

    The requirements say nothing about the amount of memory on the card.  I would guess that it is GPU specific.

    http://www.adobe.com/products/premiere/systemreqs/

    Line
    Inspiring
    May 2, 2010

    I am so annoyed at myself.

    Bought a GTX295 thinking, i'll be ahead of the game and have an even more CUDA powered card for the next CS suite. First thing that happens is it overscans my computer monitor. Bought a new monitor. Now CS5 is released, and GTX295 is not even supported but the previous version is!

    Doh doh doh doh!!!!!!

    //Signature// I'm a creator. I love illustration, designing, animating , writing, voice overs, acting, making games .. Woo woo!
    Participating Frequently
    May 2, 2010

    See this:

    http://forums.adobe.com/thread/629557?tstart=30

    Be warned it is a hack so don't expect much if anything at all.

    You paid $500+ for that card?

    Participant
    May 1, 2010

    To All

    This is the price you pay for progress. Just figure on not using the Mercury engine if your not on a supported platform.

    You can operate without it. This is for the big boys that really want the most power for the dollar and have the budget to

    upgrade or purchase new systems to support Adobe's tech. If you don't have it well that is something you will have to deside for

    yourselves. Do your productions benefit you enough to upgrade your hardware.

    Participating Frequently
    May 1, 2010

    How about a Poll and then a Petition for which cards get support?

    Maybe an organized message including statistics from one of the board veterans would be helpful.   I vote for zenviolence   (ha......ha)

    To appease the masses, Adobe should support some high-end consumer card....i.e. GTX 470 & 480. My 2 cents.

    What say you?

    trilobyte550m
    Participating Frequently
    May 1, 2010

    It's been said (by an Adobe employee) that the GTX480 will be added to the list sometime after release, hopefully this summer (it's a newer card, they got a late start).  No word yet on if that support would extend to the GTX470, the upcoming GTX460, or any other upcoming cards in the 4xx line.

    Participating Frequently
    May 1, 2010

    ...but it has also been said (Wil/Adobe) that the GTX 480 does NOT fit into the current MAC cases.  Wil - "from what I hear the GTX 480, while being the better card, won't fit  into the mac pro chassis"

    The point of my post was to get some kind of organized communication to Adobe versus just ranting on this board.

    April 30, 2010

    http://i42.tinypic.com/oh00lv.jpg

    Harm_Millaard
    Inspiring
    April 30, 2010

    So what?

    trilobyte550m
    Participating Frequently
    April 24, 2010

    It's worth pointing out that, according to a post from Adobe staffer Simon Hayhurst on the Red user forums (click here and look at post #133) confirms that the GTX 480 will get CUDA support, though it's not likely to happen until sometime this summer.  From day one it will be a ludicrously fast GPU that runs Creative Suite, and then in an update to follow it'll gain support for CUDA acceleration of the Mercury Playback Engine.

    I didn't see any mention of the GTX 470, but from a technical standpoint it should be a no-brainer (both cards use the same chip, the 470 just has a portion disabled).

    April 24, 2010

    I want to say what I find wrong with all of this issue cause I think there are things that need to be said. The problem that I see here is that when Nvidia promoted the CUDA standard it promoted it precisely as such and as far as I know a standard is supposed to be exactly that but now some people are finding the hard way (an expensive way) that the "standard" may be really a "quasi standard" or "pseudo standard".

    The problem I see is I that I think people expect something that is CUDA compatible or Open CL compatible to be exactly that and now they are realizing that that is not the case. This is like buying a Direct 3D or Open GL compatible card and then when you buy a Direct 3D or Open GL compatible software or game you find out that despite the "standard" it still doesn't work. This is exactly the same thing happening but with another standard.

    Now think of the history of the PC 3D standards and precisely of some that are very closely related to this issue like 3D acceleration cause they are right there in these same graphic cards. One thing that comes to mind is the fact that in the early stages or days of both Direct X and Open GL there were growing pains and it took time to work the bugs out but there are still some issues.

    Nowadays you are less likely to find problems with Direct X or Open GL but you still find them. How many times you brought a PC game home only to find out that it doesn't run on your graphic card even with the latest drivers. It has happened to me a couple of times and I'm not talking about performance issues, I'm talking here about your hardware far exceeding the minimum system requirements only to find out that your 3D program or game looks all crazy on the screen and is unusable.

    Now, like I said nowadays is harder to find such an issue and I wonder if the same thing is not happening here again. The problem is that Adobe may said whatever they want to say or Nvidia may say whatever they want to say but the bottom line for those that bough expensive hardware is that it didn't work the way it was touted. When people bought those CUDA capable or CUDA enabled cards they bought them with the idea that any CUDA capable or enabled software was going to be able to take advantage of their investment and now they found that that is not the case. How can we not expect them to be very angry? And whose fault is it for this? Adobe or is it Nvidia or both? Who is taking responsibility for the problem?

    These are all valid questions because it entails other questions such as if this is a problem that people that posses CUDA capable hardware can expect in the future with other software programs. Are people that have such CUDA capable cards going to have a spotty coverage or spotty compatibility from many CUDA enabled software programs out there? Is this a similar growing pain such as what happened in the early days of the Direct X and Open GL standards? Will it go away as the "standard" matures?

    Has Nvidia had enough time already to mature the CUDA standard enough to the point that this is not supposed to happen? Is it a standard that is robust enough to prevent this kind of thing from happening and if it is, is it Adobes fault for not working properly with it? If there are kinks in it that need to be worked out and will Nvidia work them out soon? Will we see a CUDA version 2.0 that has less of these type of problems? Good, good questions but at the moment the bottom line is that many people that bough CUDA capable hardware are going to feel disappointed that their expensive graphic cards didn't work as touted.

    I have in particular two Evga 260 GTX Graphic cards in SLI mode but at the moment I have no use for Premiere. I only have Creative Suite CS4 Web Premium so I didn't buy Premiere and I don't plan to buy CS5 anytime soon cause I'm very happy with my CS4 suite at the moment but if I had bought Premiere CS5 thinking that my CUDA capable graphic cards could give me that extra performance that Adobe was promising and then when I got home I found that it didn't work like that I would probably be as upset as those people.

    What if I bough the Hypershot renderer (a very expensive thousands of dollars CUDA capable renderer) thinking "Oh with my two 260 GTX cards it is going to run much faster" and then I found something like "We are sorry but Hypershot doesn't accelerate at all with your graphic cards you will have to use it with CPU acceleration only" and worst what if instead of those two 260 GTX cards I bough two very expensive Quadro cards and found out that they were not compatible with my also very expensive Hypershot? Uffffffffff!!!!! Boy would I be angry!

    So best practice for people now is of course that from now on when they are in the market for those CUDA "capable" cards and CUDA "capable" programs they have to be certain first and ask the software manufacturer to make sure that their hardware is compatible with it and for those that already made the investment sorry for them and let's hope that either Adobe or Nvidia fix their problem and soon.

    Eric Addison
    Participating Frequently
    April 24, 2010

    This thread has been pretty interesting and in some ways entertaining to read and follow. I'm really starting to believe that many people just can't be satisfied. I've been a part of these forums for years now, and with every release people have complaints. And this release seems to be no different - even though it has yet to hit the shelves.

    Users have complained for a long time that PPro is unstable, bug-ridden, not "Pro" enough...I don't agree with that, but that's what seems to come up time and time again. Some of this stems from (by my observation) users who don't always follow the recommended hardware requirements, sometimes it comes from using odd consumer formats, and other times it's just a bug - every piece of software has them...even FCP and Avid.

    But getting back to the bit about hardware - the other two big A editors have hardware requirements. FCP has the most restrictive - you have to buy a Mac. Avid works on both, but has it's own set of requirements for it to work properly. Adobe hasn't really ever set any strict hardware requirements (compared to the other big A companies) other then processor speed, memory, and hard drive space - and for cutting DV, those are pretty low. And I've always felt that many people who try to use home built machines that were built after a weekend at Fry's Electronics and done without really consulting anyone who knows anything about video editing often seem to complain the most. Now some on these forums REALLY know their stuff and can build themselves one hell of a computer. Others (and I admit - I'm not really a hardware guy) should leave it to the pros.

    So this time around, Adobe comes up with a great, powerful new feature - the catch is that you have to have one of a handful of video cards to use it. Why? So that it they could focus on those cards during development to create the most stable, most reliable, and best performing feature they could. They finally got some strict guidelines. And you know what - I'm glad. Why? Because I've seen MPE work, and it's amazing. I would much rather have a limited number of video card choices and have software that performs brilliantly, then have a large number of cards that half work, or work some of the time.

    I believe that Adobe listed what cards would be supported some time ago - it's not like this is any big surprise. Will cards be added...I'm sure they will, but I'm also guessing that it will be a short list to keep the level of performance high. Adobe has limited resources, and can't be expected to test and certify every card out there. By limiting it, they have done us all a favor - given us something that works great with the right equipment.

    I'm glad Adobe has finally laid down some ground rules for working with PPro. I'd welcome more of them if it meant a more stable NLE with more great features like MPE.