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?

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.

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?

AME Adobe Media Encoder Cuda GPU Acceleration not activated, How do I activate it

Mac Pro Early 2009 4.1, Processor 2.93 GHz Quad-Core Intel Xeon, Memory 16 GB 1066 MHz DDR3 ECC, Graphics NVIDIA GeForce GTX 680 2048 MB, Software OS X 10.9.2 (13C64)
Adobe CS6 suite up to date all programs as of 3-18-14
NVidia Cuda Driver 5.5.47 installed, Open CL and GL capable
I read this article http://blogs.adobe.com/kevinmonahan/2013/09/13/enabling-cuda-for-the-mercury-playback-engi ne-in-the-macbook-pro-retina/. it shows GPU acceleration through AME (see below). In my AME que window I do not see this

Todd:
(edit)
Just reread - sorry, CS6 vs CC.
What about AME CC?
http://blogs.adobe.com/kevinmonahan/2013/09/13/enabling-cuda-for-the-m ercury-playback-engine-in-the-macbook-pro-retina/
So, CUDA acceleration in AME and OpenCL is supported. Anyway to monitor this? I get FAILED when I try either (on a box with nVidia, or a box with AMD).
Found this: http://helpx.adobe.com/media-encoder/using/whats-new-media-encoder-7-1.html#gpu-accelerati on
GPU acceleration
Adobe Media Encoder now takes advantage of GPU for rendering purposes. Both CUDA and OpenCL are supported. The latest release of AME uses the GPU for the following renders:
Scaling (HD to SD; SD to HD)
Timecode filter
Pixel format conversions
Deinterlacing
Aspect ratio changes
All effects in the Effects tab
GPU accelerated effects in Premiere Pro
If you are rendering a Premiere Pro sequence, Adobe Media Encoder will use the GPU render preference you have set for the project. All GPU rendering capabilities of Premiere Pro are utilized.The limited set of GPU renderable tasks in Adobe Media Encoder is only for renders that originate in Adobe Media Encoder.
If you are rendering a sequence with native sequence support, the GPU setting in AME is used and the project setting is ignored. In this case, all GPU rendering capabilities of Premiere Pro are utilized directly in AME.
If your project uses 3rd party VSTs (Virtual Studio plugins), the GPU setting in the project is used. The sequence is encoded through headless Premiere Pro just as in earlier versions of Adobe Media Encoder. If Enable Native Premiere Pro Sequence Import option is unchecked, headless Premiere Pro will always be used and the GPU setting is used.

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

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."

Sorting, timecode positioning, cropping bug, GPU acceleration, AU support

There doesn't seem to be a way to sort the items in the queue. I added 126 videos to encode and it is terribly annoying to look at them all as a huge bubble rather than a single line with disclosure triangle.
There are no options for repositioning timecode burn-in. The title-safe options are in an awkward location, and the other options put it flush against the edge of the frame.
The cropping function looks proper in the preview but the export is actually applying it as a padding operation and strecting the cropped region to fill the fram unproportionally. Also, for some reason the crop affects the timecode burn-in and scales it as well as crops it off. I'd like the timecode placed in the letterbox area. Because of this bug, my workaround was to use Photoshop to create a 1920x1080 PNG with a 2.35 letterbox. I then used the watermark effect with full alpha to impose it onto the footage. In doing this I noticed another bug that resulted in a small artifact from the matte's edge at the line from black to transparent, almost like a scaling artifact even though there was no scaling applied.
Is there GPU acceleration? It is incredibly slow compared to Adobe Media Encoder on the same computer.
It would be awesome to have support for AU plugins to be used as effects on the audio track. The included peak limiter worked ok for the most part to boost volume, but I'd like to be able to use more professional plugins to do this. A LUT video effect would be great too.

Use this link for Compressor Feedback. http://www.apple.com/feedback/compressor.html
Here is an article on hardware acceleration.
Russ

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 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

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.)

No GPU Acceleration or MPE benefit (FX3800)

Yikes
Installed CS5 (Full Paid Version) yesterday. Shaking it down today.
Everything is working at light speed except.....
I do not get any GPU Acceleration or MPE benefit from the QUADRO FX3800 (or PPRO).
As soon as I apply any GPU accelerated effect (eg Ultra, Levels etc...) .
or Scale down a P in P - I get a RED RENDER BAR
This is a minimal sequence with Vid 1 :color bars, Vid 2: mxf 720p green screen scene, Vid 3: 720p mxf for PNP
Thought it was the Driver - updated to latest (NVIDIA 8.17.11.9759 - 16/4/2010)
Did not resolve it!
Flicked between Hardware and Software acceleration - no difference.
Any suggestions from the team ?
Intel Core I7 930 2.8 GHz - Socket 1366 (8MB L3 cache)
Asus P6T Deluxe V2 1366 DDR3 - Sata II Raid Express Gate SLI +CrossfireX 2xGB Lan 8 Channel Sound 2 x 1394a ATX Motherboard
Corsair1600 6GB Triple Channel Kit (6x2GB) 12GB
LEADTEK FX3800 NVIDIA QUADRO graphics card
Western Digital 300GB SATA2 Velociraptor HD (10,000rpm) - system drive
plus 3 x 1 TB HDDS - space for 5 more internals
24x DVD/CD BENQ
Antec P183 Advanced Black Super MidTower (3 x variable speed fans)
550 w PSU
BENQ M2700HD Widescreen LCD 27 inch Monitor / 2ms / 50,000:1 Contrast
Windows 7 Professional 64-bit OEM

I was the one who posted it because that is what our Nvidia rep said. He said the Quadro 3800 would have the same
3 layer limit as the 285GTX due to the 1GB ram on both cards. If that is incorrect then the information they gave me was incorrect.
BTW I will forward them this thread and ask them why they informed me otherwise. Thank you for the heads up.
Oh one last thing. Nvidia and Adobe stated the limiter was put in place because of the 1GB Frame buffer size limited performance in CS5 and they could only ensure performance with effect for 3 layers. If the Quadro FX 3800 is unlimited then that is completely false. Since the Quadro FX 3800 has a 260GPU in it and has 1/3 the ram bandwidth of a 285GTX then how does 1GB on the 285GTX require the limiter but the 1 GB Quadro card does not. This means Adobe is completely working with Nvidia to sell more Quadro FX cards and the limiter is a completely dishonest way to do it.
Note - After checking my email and speaking with my Adobe rep I changed the post. It was only our Nvidia rep that reported the limiter on both.

Mac Pro GPU Accelerator

Premiere CS3 and AE are not fast at all at rendering. I believe this is because its rendered on the CPU. A few questions on this..
- I heard final cut uses the GPU to render, is this true?
- In premiere is there a way to switch to GPU rendering, not just "GPU Acceleration" which doesn't seem to do much.
- Is this technology simply just too new?
- I have the ati radeon 1900xt. Would I benefit from a newer card? Or would that allow pure GPU rendering? Is it a matter of having a different graphics card, or is it software settings, drivers, etc. that hold back the GPU for video renders?
I also saw this, http://elementaltechnologies.com/products.php?id=5 is this the only way?

Notice this in that link:
*NVIDIA Quadro* graphics processing unit (GPU)
However,
NVIDIA Quadro FX 5600 Featuring a massive 1.5GB frame buffer of GDDR3 memory, the NVIDIA Quadro FX 5600 is the ultimate workstation-level graphics card. It’s ideal for industrial-strength 3D design work, modeling, animation, and stereo 3D visualization. One of the most advanced graphics cards available, it has an integrated stereo 3D port, so you can use stereo goggles for stereo-in-a-window visualization applications. With two dual-link DVI ports, you can connect two 30-inch Apple Cinema HD Displays. - Apple Store
The Quadro FX 5600 ($2700) does feature more video memory (1.5GB vs 512MB). And, according to one Maya guru, the extra memory (and superior memory management code) of the Quadro workstation cards becomes useful for frame buffering in Maya. This is especially true for redraw of multiple views of the same complex 3D model.
This has been enhanced further by Quadro FX 5600's new integrated memory allocation which allows the card to dynamically allocate on-board RAM to whatever task is at hand rather than have specific hard wired allocations. So rather than say a maximum of 40% of total on-board RAM dedicated to the texture buffer the card can ramp up and down from 80% sharing with the immediate needs of the other buffers. http://www.barefeats.com/york2.html
*Radeon 3870* (requires 10.5.3+)compared to X1900
http://www.barefeats.com/harper16.html
Other things to look at that you can do:
More RAM, faster drives and scratch RAID, updating to 10.5.4 (the Radeon 3870 and Nvidia 8800GT both require 10.5.3+).
http://www.adobe.com/go/kb401089
http://homepage.mac.com/boots911/.Public/PhotoshopAccelerationBasics2.4W.pdf
The GTX 280 or Radeon HD 4870 X2, (Windows only, don't work in OS X due to lack of EFI firmware).
ATI has optimized their Mac Edition drivers and firmware for the Radeon 2600 XT and 3870 so that they run Core Image effects much faster than comparable nVidia cards including the GeForce 8800 GT and Quadro FX 5600.
http://www.barefeats.com/harper19.html
GPGPU will probably see more use in the future. Adobe plans to add such a feature to the next version for Windows ("*CS4 Stonehenge*") http://www.tgdaily.com/content/view/37643/128/

How to disable GPU acceleration, really?

I disabled GPU acceleration from settings menu but it is not effective.
I did it from "''about:config''" menu "''gfx.direct2d.disabled -true''" but also not working.
I did disable for all extension to check them but still have problem.
The problem is firefox using my GPU on maximum clocks even for a '''simple page scrolling'''.
It causes GPU clocks go up and down continuously, and VGA cooler also speeds up and goes down which creates cooler noise fluctuation.
It is really irritating.
Only thing I can do is to run firefox in windows xp compatibility mode.
But this is just an interim solution.
Now I updated version 11 and this still not fixed.
I wrote about this problem a few times but still nothing.

GPU accelerated pages=0 means Firefox is not using acceleration. The spike in the GPU clock when scrolling could be the Windows graphics acceleration. You can also try to file a detailed report [https://bugzilla.mozilla.org/ here.]

De-interlacing not working on output using AME and MPE GPU acceleration

Hi
These days I normally shoot progressive video so have not noticed this issue before. However, we recently shot a large project at 1080i. Now at the stage of outputting web-ready H264 versions of multiple timelines (200+).
The timelines are also 1080i but we are outputting to H264 1080p - so obviously we want to deinterlace on output.
The problem I am having is that Adobe Media Encoder is NOT deinterlacing on output - the encoded file is flagged as progressive but exhibits combing artifacts all over it. We are running CS5.5 on a Windows 7 PC with an NVIDIA Quadro 4000 gfx card - Mercury PE with GPU acceleration. We also have a Mac without a qualified graphics card running CS5.5 with software only MPE.
On the Mac we are outputting with no issues - final output is deinterlaced as expected. On the PC I tried any number of combinations to try and get deinterlaced output (even deinterlacing the clips on the timeline) but no matter what I did it STILL ended up with combing issues. As a last resort I switched the project setting MPE GPU acceleration off (to MPE software only) and tried again. Guess what? Perfect deinterlaced clips from Media Encoder.
The only problem is that the clips take about 10 times longer to render without the GPU acceleration which with the number we have to get through is a real issue.
Can anyone suggest a solution? Anyone else got this issue? Is it a hardware combination problem? Its really annoying to have to disable MPE acceleration on output, one of the major selling points of having this system.
Thanks
Rob

Setting each clip's field options to Always Deinterlace is the only way I know to get around this bug. It works for me even in an interlaced sequence, but you said it didn't work for you. If you haven't yet, try copy/paste into a matching progressive sequence and then set the Always Deinterlace option for the interlaced clips.
Jeff

PP CS6 crashes when GPU Acceleration (CUDA)/ (OpenCL) enabled?

Ever since enabling GPU Acceleration in PP on my Late 2012 15" Macbook Pro (Non Retina) I keep having my computer randomly crash while I'm editing (to the point where it either restarts its self, or freezes such that I have to).
I can't think what else the reason would be if it's not the GPU acceleration, as it seems to have coincided with this.
My Macbook's specs are:
> 2.3Ghz CPU
> 500GB SSD (MacHD)
> 256GB SSD (in optical drive - Scratch Disk/ Exports)
> 16GB Ram
> Nvida GeForce 650M 512GB (most up to date CUDA drivers)
Any thoughts on this would be greatly appreciated! Thanks.

On two different AMD graphics cards, the same thing: http://translate.google.com/translate?sl=ru&tl=en&prev=_t&hl=en&ie=UTF-8&u=http://www.efxi .ru/more/premiere_pro_cc_multi-gpu_amd.html With two Nvidia doing well so that PCIe bus there is no problem.

GPU Acceleration causes random frame in encode?

Similar Messages

Maybe you are looking for