GPU acceleration in AE

guys i have an AMD 6850, is there a way to accelerate something in AE?
rendering or preview or something?

Here's a quote from the AE System Requirements page:
The following NVIDIA GPUs are supported in After Effects CS6.
Mac:
GeForce GTX 285
Quadro FX 4800
Quadro 4000
Windows:
GeForce GTX 285
GeForce GTX 470
GeForce GTX 570
GeForce GTX 580
Quadro CX
Quadro FX 3700M
Quadro FX 3800
Quadro FX 3800M
Quadro FX 4800
Quadro FX 5800
Quadro 2000
Quadro 2000D
Quadro 2000M
Quadro 3000M
Quadro 4000
Quadro 4000M
Quadro 5000
Quadro 5000M
Quadro 5010M
Quadro 6000
Tesla C2075 (Windows)/Maximus configuration
Check your card against the list.
Oh, wait. You have an AMD card. I guess you don't have to check.

Similar Messages

AME takes a long time to start encoding when using GPU Acceleration (OpenCL)

Have had this issue for a while not (current update as well as at least the previous one).
I switched to using GPU Hardware Acceleration over Software Only rendering. The speed for the actual encoding on my Mac is much faster that software only rendering. However, more often than not, the encoding process seems to stick at 0% waiting to start for a long time, say anywhere from 1 minute to several minutes. Then it will eventually start.
Can't seem to find what is causing this. Doesn't seem related to any particular project, codec, output format or anything else I can see. I'd like to keep using GPU Acceleration but it's pointless if it takes 5 times as long to even start as rendering by software-only would. It doesn't even pass any elapsed time while it's hanging or waiting. Says at 0 until it starts. Like I said, once it starts, it's a much faster render than what the software would take. Any suggestions? Thanks.
using an iMac, 3.4Ghz, 24GB RAM, AMD Radeon HD 6970M 2048 MB

Actually, I just discovered it doesn't seem to have anything to do with OpenCL. I just put the rendering back to software only and it is doing the same thing. hangs for a long time before it starts to run. Activity monitor shows it running 85-95% CPU, 17 threads and about 615 MB of memory. Activity Monitor doesn't say its not responding, it just seems kind of idle. It took almost 7 minutes for it to start rendering.
1- Running version 7.2.2.29 of Media Encoder,
version 7.2.2 (33) of Premiere.
2- Yes, a premiere project of HD 1080 source shot with Canon 60D, output to H.264 YouTube 720, fps 23.976
not sure what you are referring to by native rendering. The rendering setting i tried now is Mercury Playback Engine Software Only if that is what you are referring to. But OpenCL gives me the same issue now.
3- H.264 YouTube 720, 23,976 - seems to happen on multiple output types
4- In Premiere, I have my project timeline window selected. Command-M, selected the output location I wanted and what output codec, selected submit to Queue. Media Encoder comes up, the project loads and I select the run icon. It preps and shows the encoding process setup in the "Encoding" window, then just sits there with no "Elapsed" time occurring until almost 5-6 minutes later, then it kicks in.

How can I open a project that has been created with Mercury Playback Engine GPU Acceleration software, on my trial version of Premier Pro CC?

Hi,
I'm working with a colleague who is using Mercury Playback Engine GPU Acceleration software on his PC version of Premier Pro CC. I am using a mac and have a trial version of Premier Pro CC. When I try to open a project file that he has sent me I get an error message-
"Missing renderer: This project was last used with Mercury Playback Engine GPU Acceleration (CUDA), which is either not available or not certified on this system. Mercury Playback Engine Software Only will be used."
When I click OK and locate the files I get a message saying "File format not supported".
Can anyone tell me what to do so that we can share project files?
Many thanks,
Jessie

Shouldn't really be the MPE at fault here ... what is the codec of the footage/sequence/project?
Second, can you create a new project in PrPro, then in the media browser, import that sequence from the other project?

Playback and Rendering issues when GPU acceleration is enabled

I'm using the new MacPro with dual AMD FirePro D300. When I enable GPU Acceleration (Open CL) I can no longer play through an entire sequence. It specifically has issues playing through any layered graphics or titles, but seems to play with those disabled. I have tried having "Composite In Linear Color" enabled and disabled, and neither seemed to make a difference. It's the same deal when rendering. If I have titles, and use GPU Acceleration it jumbles clips, cuts to black or static, all manner of weirdness. Is there something I'm missing?
An example of what playback looks like if I have titles and GPU Acceleration enabled.

This computer thing seems complicated enough that if your system works better with GPU accel off, that's you best performance. I understand they've been trying to sort out these sorts of issues but there's so many dang variables, and trying to build software that interlinks with other complicated software is something no other NLE or Grading program does. That throws even more kinks into the list.

IMAC's Top graphics card frustration - Cheap and no support for Adobe Mercury Playpack Engine GPU Acceleration?

If anyone has a solution for getting the Mecury Playpack Engine GPU acceleration to work with Premiere Pro CS6 on an iMAC 2011, please let me know. Like I wonder if you could Thunderbolt an External graphics card somehow? Or is an upgrade possible? Ahh...not worth the risk.
Please, if you have a solution for me, let me know. Otherwise I find it pretty frustrating that I purchased a top-end iMAC, fully maxed-out in every way possible, and that the iMac doesn't support Adobe Premiere's Mercury Playback Engine GPU acceleration. Also, an old USB 2.0 Hub and thus the built-in SD card reader is slow. If you have SD cards with 95MB/s Transfer, Read and Write speeds, the iMAC will only transfer at around 30MB/s if you're lucky. Technically 480Mbs which is around 50MB/s but I haven't seen those speeds.
I figured this could at least be circumvented with a Thunderbolt SD card reader or a Thunderbolt to USB 3.0 adapter but of course no such thing exists.
Well, nothing with a reasonable price tag. This all might seem trivial to some but when you're uploading 24 hours of HD video footage from a 128GB SDXC card, the speed makes a big difference.
And come on, no BluRay support? Ridiculous. I get the politics of why but still, just ridiculous. It would be nice to be able to burn a BluRay to watch in my home theater system. There are other methods but BluRay is convenient and great for backing up large Video Files. Unfortunately BluRay looks like it's not going to make it. Maybe cable distribution companies will increase their Internet upload speeds one day and I can just store everything in the cloud and watch full length movies(that I've created) on Vimeo.
Anyways, I went and took a look at the hardware Apple stuffed inside my fancy (3.4 Ghz i7, 16GB 1333 DDR3, 2GB AMD 6970M, 256 GB SSD Internal and 2TB 7200 Internal) machine and it appears to be pretty middle of the range stuff. It's an iMAC, not a Mac Pro so why am I griping? Because my 2009 PC(which I tricked out over the last two years) is faster and does support the Mercury Playback Engine. I spent $2100 total on this PC which includes all my upgrades. I spent around $3300 on the iMAC. I feel ripped off.
Yes, I do love my iMAC on multiple levels but had I known my dated 2009 PC would render video projects faster, I would have gone with a MAC Pro or just a new PC. It seems that Mac is moving completely away from making high-end computers for niche markets(video editing) and focusing on their tiny laptops, IPADS and IPhones for the masses. Obviously smart from a capitalistic perspective(at present at least) but very frustrating for some.
I was actually told to purchase a MAC for video editing. I've been a PC guy for 15 years. I went with the iMAC because I had read many good things about it(probably just Apple propaganda) and also the MAC PRO was to be discontinued. Also the MAC Pro would have been triple the cost for what didn't seem like a whole lot more.
It's one's thing to prepackage a computer with inferior hardware(the iMAC I have is fast for most things and more than enough for 99% of the population) but to not allow us to pop open the computer and make a quit upgrade to the machine is what really makes me feel like I'm using a computer built for Grannies. I mean there is a reason my mother loves iMacs and Iphones. Amazing that I was able to upgrade my memory from 4 to 16GB but I've heard Apple has even done away with that. I get why they do it. Apple Warranty, Apple Care issues, Profit and World Domination: Apple wants a monopoly on everything.
Was great to see Adobe bounce back after the whole Flash/HTML5 thing and knock Final Cut Pro off the face of the Earth for good. People are still buying it b/c of the brand name but Final Cut is done. David Fincher used Adobe's Workflow for everything when he made The Girl with The Dragon Tattoo. Hollywood is making the shift and the world will follow. The Adobe Workflow has finally come together and there is just no way Apple can compete with Adobe Creative Cloud and an Engine that can just swap from Premiere to After Effects to Prelude to SpeedGrade to Photoshop to Story with speed for $29 bucks a month(or $49 for some). Apple better start supporting Adobe's Mercury Engine or they may have a problem. And if you're using Final Cut X, you're severely handicapping yourself. Problem is that people don't want to take the time to learn Adobe's products(steep learning curve for sure) which is where Apple's Granny software, and perhaps computers, comes in to play. Arnold Schwarzenegger once said "Milk is for babies, Real Men Drink Beer". I'm beginning to think that "Mac's are for Grannies, Real Men Use Adobe and PCs".
The major problem with Apple is you're forced to use Apple. Not sure but history has proven that people don't like to be forced into anything. Autocracies don't work. These systems eventually topple, even in the corporate world.
Amazon.com, now that's the company to emulate. What an amazing machine!
I've read that Apple may even discontinue the iMAC after 2013. Who knows?
If anyone has a solution for getting the Mecury Playpack Engine GPU acceleration to work with Premiere Pro CS6 on an iMAC 2011, please let me know. Like I wonder if you could Thunderbolt an External graphics card somehow? Or is an upgrade possible? Ahh...not worth the risk.
1) Graphcis Card - AMD Radeon HD 6970M 2048 MB (6990 would have been better or something from NVIDIA.
2) USB 2.0 Hub with only 480 Mb/sec
3) Seagate Baracude SATA I 7200 RPM drive with 3GB/s transfer rate and only a 32 GB Cach. It's ok. I would have expected at least a Western Digital Caviar Black 2 TB SATA III 7200 RPM 64 MB or the Velociraptor at 10,000RPM.
4)APPLE SSD TS256C Flash Drive. As you can see, it doesn't stack up so well against other SSD Drive.
Just average. http://www.harddrivebenchmark.net/hdd_lookup.phphdd=APPLE+SSD+TS256C

Whining and ranting about how iMacs can't do this or iMacs/orMacs can't do that is not going to get you a lot of help here.
Your "I love my MAC" is typical of the ever ubiquitous PC whiner.
If your video work needs were that computer intensive and critical , you should've done some online research and you should have budgeted for a Mac Pro.
Mac Pros are completely expandable and upgradeable unlike the iMac.
Mac Pros have much more faster and more CPU cores than the iMac line.
iMac line is limited to CPUs with 8 cores. The Mac Pros, I believe, are up to 16 core CPUs, now.
The Mac Pros can have their GPU upgraded and you even add/expand to use specialty audio/video cards.
Mac Pros are the defacto standard for real video work.
iMacs, even the high end model, is not really designed to do really heavy and intensive video work.
iMacs do do video creation and editing. Just not on the level that is needed from a more "Pro" computer.
It seems to me you are asking your iMac to do more than it was originally designed for, in terms of professional video editing.
You get a lot more out of a Mac Pro than an iMac for any real serious video, CGI or animation work.
You just didn't want to spend that much cash on one.
iMacs are not user upgradeable or friendly to user upgrades at all!!!
If you purchased a Mac Pro, you could've had that better, faster HD, better faster SSDs.
That said, I can offer no real help to but because of the nature of your post and the fact you just simply annoyed me, I feel some advice and explanations are in order
First off, you picked Adobe video editing software suite as your video creation software on the Mac. It's no secret to long-time video content creators on the Mac that Adobe products, especially those for video creation and editing are very user unfriendly on the Mac. Even though Macs are supported from Adobe, Adobe for a long time has treated the Mac and Mac users as second class citizens.
Before purchasing and installing Adobe Premiere, did you even check Adobe's site for the preferred system hardware and software requirements? Hmmm?
This is why you should KNOW what software you are going to be running on a computer first then research what computer make and model will run said software.
That's why Apple has its own apps like Aoerture, Logic and Final Cut.
Despite your ignorance in this matter, Final Cut Pro X is alive and doing well, thank you, and using this software on your iMac would kick Adobe Premier in the you know whats.
Final Cut Pro X is a complete video solution for and completely designed around the Mac.
Why are you using USB 2.0 connections for video work when you have a perfectly good FireWire 800 connection.
In case you are not aware, FireWire 800 is called so because it has a max throughput of 800 Mbps.
Your 2011 iMac can take up to 32 GBs of RAM. Not just 16 GBs.
This changed when the 2010 model iMacs came out.
Blu-ray? I believe you can buy external Blu-ray writers that work with Mac using said FW800 connection.
So you cite one movie and one videographer using Adobe Premier for your premise that Final Cut is dead in Hollywood?
Your argument that Apple locks you into everything in their world can be countered by saying Windows and Windows PCs lock you into the Windows world. What's your point?
Apple is not discontinuing their computers platforms any time soon.
All you are regurgitating is rumor. Probably from all of the PC crowd.
iMacs and professional desktop Macs are not going anywhere.
Currently, Apple is the only desktop/laptop computer maker that is still making a profit on their Macs and increasing their market share percentages for the last 5 years during which the PC market has continually slumped/dropped in its market share.

How do I know if I have Mercury Playback Engine GPU Acceleration (OpenCL)?

To anyone who can help,
BACKGROUND
I am new to Premiere Pro and just started my first project on CC 2014. A tutorial recommended I select 'Mercury Playback Engine GPU Acceleration (OpenCL)' over 'Mercury Playback Engine Software Only' in the VIDEO AND RENDERING section of the PROJECT SETTINGS window. Since the former option isn't grayed out, I'm assuming I have both to choose from, however, when I select 'Mercury Playback Engine GPU Acceleration (OpenCL), only the audio will play back in my source window; the video no longer plays back.
HARDWARE
I am on an (early 2008) Mac Pro desktop with two 2.8 GHz Quad-Core Intel Xeon processors, and two ATI Radeon HD 5770 graphics cards.
I am running OS X 10.9.5.
QUESTIONS
1. Is there a way to figure out if I actually have this 'Mercury Playback Engine GPU Acceleration (OpenCL)' thing?
2. Is opting for 'Mercury Playback Engine GPU Acceleration (OpenCL)' over 'Mercury Playback Engine Software Only' (the default) really even going to make a noticeable difference in how my 1080p 24 fps movie is rendered?
Thanks in advance to any advice offered!
Shaun

I am not realy a mac person but Premiere can only use one graphics card. Can you disable one of the cards.
Might want to read this on how MPE works:
CUDA, Mercury Playback Engine, and Adobe Premiere Pro « Premiere Pro work area

When I chose the GPU Acceleration on my general settings I only get audio and not video play back

It has been extremely frustrating for me because my computer can render files fast just couldn't read the graphics card I had so I had to unlock it. I am hoping someone on here has done something similar to help me get this to work because the only thing that I am having trouble with as far as when it is on software only is on play back. I kept dropping several frames and it was really frustrating me. I think I may have found why I am having this problem and hope someone on here can help me out.
15. Now just add the name of the card between the “Renderer string:” and the forward slash “/” to the cuda_supported_cards.txt file.
This was on of the steps that I did not understand and could be the reason why it is not working properly because I did not know how to do this.
Like I said it is letting me switch to the GPU Acceleration mode just not letting me see any video on anything in cs6.
This is the link to where I learned how to get premiere cs6 to read my graphics card http://www.studio1productions.com/Articles/PremiereCS5-2.htm
I have a GeForce GT 525M graphics card and according to that site I can get premiere to read my graphics card to help me playback without dropping frames.
I also installed the latest driver so that can not be the issue as of now. If you know the answer please help this is very frustrating.
Thanks!

See http://www.nvidia.com/Download/index.aspx

GPU Acceleration causes random frame in encode?

New Mac Pro (6 core, d500 cards, 32GB RAM, OSX10.9.4). Adobe Media Encoder CC 2014.0.1. Tested on two separate machines of the same configuration.
I have a just over 2 hour long 1080p ProRes file that I was encoding to MPEG2 for DVD. During QC of the disc, a random frame from another part of the movie was found in a spot about 39 minutes into the encode. The issue was in the encoded MPEG2 stream.
The client also wanted a lower resolution h264 proof of the video, and that was encoded on the same machine at a separate time. That had the same random frame at the exact same spot.
I encoded the preview h264 in just a few minute segment of the video around the glitch on the second Mac Pro. It showed up again. I used the same setting but turned off GPU Acceleration, and the frame is gone.
Does anyone have any ideas as to what is going on here? Obviously there is a problem with GPU acceleration on the new Mac Pro's with Media Encoder, but what could be specifically causing it and what could be done to fix this? With all of the issues in Premiere and After Effects, some of which are being caused by software updates, and the issues with the one Mac Pro needing to be replaced due to bad video cards, I feel like there is just a ton of problems that didn't exist on our outdated Mac Pro with Final Cut Pro 7.
Please let me know of any ideas to make me not doubt every encode I do on these machines with GPU Acceleration turned on. Thanks.
-Phil

Does anyone have any additional ideas on this? I heard from the CreativeCow forums that this has been a known bug with GPU Acceleration on the new Mac Pros. Is this the case? Has anyone else had this issue looked at by Adobe?

GPU Acceleration In Premiere Pro CC

Do you have it when exporting via Adobe Media Encoder?
I don't seem to. I ran some tests several weeks back which clearly showed that GPU acceleration was not working when exporting through AME, but worked fine when doing a direct Export. I ran the following test again today.
10 minutes of 1080p/24 AVCHD
ProcAmp, Gaussian Blur, Three-way Color Corrector (All accelerated, 32 bit, YUV effects.)
Export to H.264 Blu-ray, default settings. (No MRQ, no previews.)
Here's what I got.
AME GPU Off - 14:03
AME GPU On - 14:10
Direct - 6:12
As before, it's pretty clear that hardware acceleration is not working through AME. In fact, it routinely takes just a tiny bit longer with GPU acceleration on.
The first time around I ran a duplicate test with CS6, and it very clearly showed that GPU acceleration was working via AME.
So...what are your results?

Jim Simon wrote:
I suspect operator/observer error on the first go round. Mind trying again through AME?
Uh, I can, but I'm not sure what you're hoping for. The times I reported were right from the text file log that AME keeps, and they were all done last night, just at different times.
07/31/2013 04:47:46 PM : Queue Resumed
- Source File: /Volumes/Opt/Users/jvp/Library/Caches/TemporaryItems/fatt-10122012-cc.prproj
- Output File: /Volumes/Opt/Users/jvp/Desktop/front.mp4
- Preset Used: Custom
- Video: 1280x720 (1.0), 29.97 fps, Progressive
- Audio: AAC, 320 kbps, 48 kHz, Stereo
- Bitrate: VBR, 1 pass, Target 5.00 Mbps, Max 5.00 Mbps
- Encoding Time: 00:13:19
07/31/2013 05:01:06 PM : File Successfully Encoded
07/31/2013 05:01:06 PM : Queue Stopped
07/31/2013 05:39:32 PM : Queue Resumed
- Source File: /Volumes/Opt/Users/jvp/Library/Caches/TemporaryItems/fatt-10122012-cc_1.prproj
- Output File: /Volumes/Opt/Users/jvp/Desktop/front_1.mp4
- Preset Used: Custom
- Video: 1280x720 (1.0), 29.97 fps, Progressive
- Audio: AAC, 320 kbps, 48 kHz, Stereo
- Bitrate: VBR, 1 pass, Target 5.00 Mbps, Max 5.00 Mbps
- Encoding Time: 00:09:17
07/31/2013 05:48:50 PM : File Successfully Encoded
07/31/2013 05:48:50 PM : Queue Stopped

GPU acceleration is grayed out in Premiere and AE, but not in Media Encoder. However, rendering is slow in all 3 programs.

It worked fine in CS6.
Now, everytime I open a project (Pr or Ae) I get the message: This project was last used with GPU Accelerated rendering. This happens with all projects, even with those that I created in Pr/Ae CC, with GPU Accelerated rendering already disabled.
In Media Encoder, the GPU Acceleration is not grayed out, but still if I render a premiere sequence or an ae comp via ME, its very very slow. (takes 5 hours for a video that took 20 mins in CS6)
Any thoughts?
Thanks, Daniel

I think I found the problem. On the website you linked, it says:
The following notebooks are not compatible with this tool:
Notebooks equipped with switchable graphics
Toshiba® notebooks
Sony® VAIO® notebooks
Panasonic® notebooks
And I have a Sony VAIO.
When searching for drivers, I only found sites like these: AMD Radeon HD 7650M drivers
Are these legit?

How did I get better compression when using GPU acceleration?

Hello,
I was just making a short, 1:12-long video encoded as H.264 in an MP4 wrapper. I had edited the video in Premiere Pro CC, and was exporting through Adobe Media Encoder at a framerate of 29.97 FPS and a resolution of 1920x1080. I wanted to do a test to see how much GPU acceleration benefits me. So, I ran two different tests, one with and one without. The one with GPU acceleration finished in 2:09. The one without it took 2:40, definately enough to justify using GPU acceleration (my GPU is an NVidia GTX 660 Ti which I have overclocked). I am sure my benefits would be even greater in most videos I make, since this one had relatively few effects.
However, I checked the file sizes out of curiosity, and found that the one made with GPU acceleration was 175 MB in size, and the other was 176 MB. While the difference is pretty small, I am wondering why it exists at all. I checked the bitrates, and the one made with GPU acceleration is 19,824 KB/s, whereas the other is 19,966 KB/s. I used the exact same presets for both. I even re-encoded the videos again just to test it and verify the results, and the second test confirms what the first showed.
So, what I am wondering is: What is it that made this possible, and could this be used to my advantage in future productions?
In case it is in any way relevant, these are my computer's specifications:
-Hardware-
Case- MSI Interceptor Series Barricade
Mainboard- MSI Z77A-G45
Power Supply Unit- Corsair HX-750
Processor- Third-Generation Quad-Core Intel Core i7-3770K
Graphics Card- ASUS NVidia GeForce GTX 660 Ti Overclocked Edition (with two-gigabytes of dedicated GDDR5 video memory and the core overclocked to 1115 MHz)
Random Access Memory- Eight gigabytes of dual-channel 1600-MHz DDR3 Corsair Dominator Platinum Memory
Audio Card- ASUS Xonar DSX
System Data Drive- 128-gigabyte Samsung 840 Pro Solid-State Drive
Storage Data Drive- One-terabyte, 7200 RPM Western Digital Caviar Black Hard Disk Drive
Cooling System- Two front-mounted 120mm case fans (intake), one top-mounted 120mm case fan (exhaust), and a Corsair Hydro H60 High-Performance Liquid CPU Cooler (Corsair SP120 rear exhaust fan)
-Peripherals-
Mouse- Cyborg R.A.T. 7
Keyboard- Logitech G110
Headset- Razer Tiamat Elite 7.1
Joystick- Saitek Cyborg Evo
-Software-
Operating System- Windows 8.1 64-bit
DirectX Variant- DirectX 11.1
Graphics Software- ASUS GPU Tweak
CPU Temperature/Usage Monitoring Software- Core Temp
Maintainance Software- Piriform CCleaner and IObit Smart Defragmenter
Compression Software- JZip
Encryption Software- AxCrypt
Game Clients- Steam, Origin, Games for Windows LIVE, and Gamestop
Recording Software- Fraps and Hypercam 2
Video Editing Software- Adobe Premiere Pro CC
Video Compositing/Visual Effects Software- Adobe After Effects CC
Video Encoding Software- Adobe Media Encoder
Audio Editing/Mixing Software- Adobe Audition CC
Image Editing/Compositing Software- Adobe Photoshop CC
Graphic Production/Drawing Software- Adobe Illustrator CC

As I said in my original post, I did test it again. I have also ran other tests, with other sequences, and they all confirm that the final file is smaller when GPU acceleration is used.
Yes, the difference is small but I'm wondering how there can even be a variable at all. If you put a video in and have it spit it out, then do that again, the videos should be the same size. It's a computer program, so the outputs are all based on variables. If the variables don't change, the output shouldn't either. For this reason, I cannot believe you when you say "I can, for example, run exactly the same export on the same sequence more than once, are rarely are they identical in export times or file size."

Premiere CC 2014: Message on loading project from older version: This project was last used with Mercury Playback Engine GPU acceleration (CUDA)...

After installing Adobe CC 2014 I have each time a message when loading an old Adobe pro project. Message:This project was last used with Mercury Playback Engine GPU acceleration (CUDA), which is either not available or not certified on this system. Mercury Playback software will be used. I have very recent HP Zbook 15 with a NVIDIA Quadro K2100M. At webinar today it was explained how to solve this, but sound was not understandable at my machine at that moment. Help? What need I to do.

Problem is solved since yesterday via Adobe helpdesk. It appeared that the newest driver for the NVIDIA were note present. So after downloading the new drivers it work. But I think Adobe should mention those issues when they launch new versions of Adobe CC like in June.

GTX 750 Ti sufficient for GPU Acceleration in CC 2014?

Hi all,
Upgrading from a HD 5870 hopefully - just wanted to know if the GTX 750 Ti with its CUDA technologies would be sufficient for GPU accelerated applications like Pr, Ae, Sg, Ps, Lr and so on? Asking in the Pr forums because that's the application I use the most.
System specs:
ASUS P8Z68-V PRO/GEN3
Core i5 2500K @ 4.3GHz
Arctic Cooling Freezer 13
16GB RipJaws-X 1648MHz
ATI Sapphire Radeon HD 5870
OCZ Vertex 4 128GB | WD Green 2TB | WD Green 3TB
LG BH16NS40 Blu-Ray Burner
OCZ ZS 650W
NZXT Lexa S
Windows 8.1 Pro x64
Not too bothered about gaming performance. I don't want to spend a lot of money and the 750 Ti at around £100 seems a good balance between value for money and performance.
The 5870 did work fine with OpenCL and Adobe CC 2014 but for various reasons I'd like to upgrade and go back to NVIDIA.
Thanks all

I have just completed running the entire PPBM8 script with the GTX 750 Ti, and compared it to the results that I had obtained over two weeks ago with the older GTX 560 card.
GTX 750 Ti on CC 2014.8.2 (1TB Samsung F3 as project disk):
GTX 560 on CC 2014.8.1 (1TB Western Digital Black WD1002FAEX as project drive):
It appears that the first-generation Maxwell (GM107) GPU somehow improved the H.264 rendering/encoding performance compared to the older Fermi (GF114) GPU. The MPEG-2 rendering/encoding performance is practically equal with both of these particular GPUs.
Verdict? The GTX 750 Ti is the right choice for a PC that's equipped (however less than ideally) with a higher-end i5 without hyperthreading or a quad-core i7 that cannot be overclocked much if at all (and this is assuming that that PC has a sufficiently fast disk subsystem).
By the way, the GT 740 that was suggested for the OP's system (given the "Green" drives) is not a Maxwell-generation GPU at all - but a Kepler-generation GPU (in this case, based on the GK107) instead. The GT 730 with GDDR5 memory that I recommended as an alternative to the GT 740 DDR3 is based on the GK208 GPU. (And I do not recommend most GT 730s on the market as they are based on an old Fermi-generation GPU - the GF108 that debuted with the GT 430 back in 2010.)

GPU Acceleration in Lightroom CC

This is the page talking about GPU usage in Lightroom CC: Adobe Photoshop Lightroom Help | Lightroom GPU FAQ.
This is the page talking about GPU usage in Photoshop: Photoshop CC and CC 2014 GPU FAQ
As you can see, I havn't seen much details about the actual use case of OpenGL/OpenCL acceleration in Lightroom. I assume now Adobe name Lightroom "Adobe Photoshop Lightroom" now, does that mean Lightroom is using the same kind of engine? I would think the new photo merge function would be a good candidate for GPU acceleration given some use case like panorama or large pixel image rotation could be quite heavy duty. Does anyone know where to find these under the hood details?
Having this said, I wonder what is the official graphics card vendor Adobe would recommend? Perhaps nVidia?

You can also install an "old" version from april 2014 (V 14.4) which works with Lr6 after having un-installed your actual actual drivers.
You can find it here: http://support.amd.com/en-us/download/desktop/previous?os=Windows%207%20-%2064
Be aware that with this driver you could activate the GPU Acceleration but it's possible that you didn't obtain any benefit...bug or not nobody knows...
Try

Adobe Photoshop CS6 Extended 64-Bit GPU Acceleration Stopped Working

I've been using Photoshop CS6 Extended 64-bit when one day the GPU acceleration features stopped working. I closed the application and restarted it and the GPU acceleration still didn't work. I couldn't rotate the canvas or use scrubby zoom. I rebooted my system and it still wasn't working. I check my performance preferences and my graphics processor was detected with the "Use Graphics Processor" box checked. I unchecked it and rechecked but the GPU acceleration still wasn't working. I uninstalled Photoshop CS6 and reinstalled it. I got the GPU acceleration to work opening the application right after the install. I close Photoshop CS6 64-bit and reopened it and the GPU acceleration wasn't working again. I am able to use GPU acceleration features in Photoshop CS6 32-bit with no problem. I'm running Windows 7 Ultimate 64-bit Ultimate Edition and I have a GeForce 280m GTX GPU. Would there be anyone out there who can help me with this issue. Thanks.

From what I gathered on this Forum there is a good chance that it may be related to the driver – unfortunately it could be either becasuse it’s obsolete or a bad new version.
http://helpx.adobe.com/photoshop/kb/photoshop-cs6-gpu-faq.html

Error compiling movie: unknown error & Mercury Playback GPU acceleration

Hardware
2014 Mac Pro, 12GB RAM, 3.7 GHz Quad-Core Intel Xenon ES Processor, duel AMD FirePro D300 2048 MB graphics cards
Software
Mavericks (10.9.4)
Premiere Pro CC2014 (8.0.1)
I'm attempting to render out a moderately complex sequence. Raw footage was dslr h.264 MOV files. 30fps 1920x1080 from canon. It has some clips that are pulled from multi-cam sequences and a few that have warp stabilizer applied. 4 total audio tracks with some linked comps from audition. Whole thing is about 14 minutes. It should be noted that I render out similar sequences regularly without issue. However on this occasion whenever I tried to render out using media encoder ( for web h.264 MOV 720 30fps) I was getting an error at the same clip every time. Error Compiling Movie: Unknown Error. So I checked out the clip. It was one of the ones with warp stabilize. I turned that off and sent it out again. Render got further this time but hit a different clip with warp stabilize (after getting through like 2 other clips with warp stabilize enabled) and gave me the same error. I tried getting rid of cache files, saving to a local drive instead of a network drive, uninstalling and re-installing premiere even. (which btw if you check remove preferences then reinstall it def still has preferences so that's a total load.) Anyway I was doing some forum surfing and found several people going all the way back to PP 5.5 saying that the only solution they found was to turn off the Mercury Playback GPU acceleration. Tried that and it's currently rendering just fine but taking roughly 4X longer than with acceleration. The GPU acceleration is a big deal for me since our company relies on putting out a lot of volume quickly. Has anyone else experienced this problem and is it something you were able to fix without turning off GPU acceleration. Grateful for your input.

sorry I actually wrote that wrong. I am using the H.264 setting 720 30fps to create a web friendly .mp4. Alternately though I decided to watch and see if it was the same clip failing every time. It is. I went into the project and did a match frame for the offending clip. Dragged the a new version of the same content onto the timeline and copied the warp stabilize effect onto the new version. Well this time the encode got past the clip with the issue, however the next clip it hit with warp stabilize caused another error compiling movie: unknown error. I guess at this point my options are to turn off the GPU acceleration and wait for a render that takes more than 3x as long to render with software only, or to go through the whole timeline and replace the clips with warp stabilize (there are a bunch, the shooter wasn't having a great day on glidecam). Not a great solution on either end. Please let me know if I should file this as a bug report. Though it seems people have been having the same issues since version CS5.5

GPU acceleration in AE

Similar Messages

Maybe you are looking for