List of GPU accelerated Effects in CS5

Is there a list somewhere of the effects that are GPU accelerated in CS5? Can someone provide a list or tell me if the following specific effects are GPU accelerated.
1) Fast Color
2) 3 Way Color
3) Color Balance RGB
4) Horizontal Flip
5) Crop
6) Auto Color
7) Auto Contrast
8) Auto Levels
9) Shadow/Highlight
10) Cross Dissolve Transition
11) Dip to Black Transition

Harm Millaard wrote:
6 - 8 should never be used!.
With the exception of Shadow/highlights all are supported. If you want to know more, try the trial or consult the help file.
You will need to look at you projects/needs to determine what to use and what to NEVER use.
The comparison is easily done... put one of the 'Autos' on your clip and see what it looks like. If it's satisfactory... leave it. If it's not satisfactory... remove it!
example:
I was taught to ALWAYS use a Mask when Chromakeying... but I can't even remember the last time I have used one. For me, there's no need to.
Although the underlying aspect of editing is similar... the means by which we achieve our end result(s) are usually very different. This fact rings very apparent by looking at any thread of 'how did they do this'. You will see many different answers that achieve the same/similar results... none of which is probably exactly how they got the look that posed the question.
-- It's all subjective and the final answer is based on what works for you and may even be seperated on a use-by-use basis. If the 'Autos' give you satisfactory results (in real-time) go for it... if not... don't. They may work this time but not the next -and Vice Versa.

Similar Messages

GTX 470 lack of GPU acceleration

Windows 7 64-bit, 8GB RAM, MSI-branded GTX470, NOT gaming, using with Adobe CS5 applications. CS5 applications are updated to loatest patches.
I've read a few other posts but I still have some questions:
1) If the hardware monitor provided with my GTX 470 is correct, and during effects rendering in Premiere and in transcoding in Encore with AME, GPU % used is about 1%, is that expected?
2) I posted a question on the NVIDIA forum regarding my inability to add Premiere Pro CS5 and Encore CS5 to the list of GPU-accelerated applications using the NVIDIA Control Panel. The *CS4* applications are listed but Control Panel does not allow me to add CS5. I uninstalled CS4 some time ago, before I added the GTX 470.
3) Today when I attempted to load a Premeiere Pro project, I get a message saying that Mercury GPU acceleration "is not available on this system" and "software only" mode will be used. What changed? Any way to recover?
So basically two sets of questions:
a) Shouldn't transcoding use GPU acceleration? Shouldn't rendering in Premiere Pro use it? What else should I expect to NOT use GPU acceleration, aside from video effects, which are pretty clearly marked.
b) Is there a trick to configuring either CS5 or GTX470 to allow GPU acceleration to be used?

Some effects are hardware accelerated, these are CUDA effects, because they use the CUDA engine on the video card. Others are not.
The GPU usage during transcoding is dependant on the source material and the export format. For instance if you start with HD (1920 x 1080) material and transcode to 720x576 SD PAL, the scaling is done by the video card (CUDA enabled). If there is no scaling during the transcode, then there is no assistance from the video card.
The faster the CPU and the memory, the more work can be done by the GPU, but if the CPU is slow, the video card is constantly waiting for the CPU. A Phenom II X4 is pretty slow, so the GPU is waiting for the CPU and will show low usage.
Look at the Background Information page at the PPBM5 Benchmark

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.

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.

GPU acceleration not activated on linux/intelivybridge

Firefox has alaways been slow on my intel ivybridge celeron ( ubuntu 14.04) and here is what I get from the about:support
How could I activate the GPU acceleration ? it works on Chrome.
Graphics
Adapter Description Intel Open Source Technology Center -- Mesa DRI Intel(R) Ivybridge Mobile
Device ID Mesa DRI Intel(R) Ivybridge Mobile
Driver Version 3.0 Mesa 10.1.3
GPU Accelerated Windows 0/1 Basic
Vendor ID Intel Open Source Technology Center
WebGL Renderer Intel Open Source Technology Center -- Mesa DRI Intel(R) Ivybridge Mobile
windowLayerManagerRemote false
AzureCanvasBackend cairo
AzureContentBackend cairo
AzureFallbackCanvasBackend none
AzureSkiaAccelerated 0

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.

Nvidia GeForce GTX 650 Ti Mecury GPU Acceleration CS5.5

Hi all!
I am having problems with my GTX 285, so i am looking to upgrade it. I have found the GeForce GTX 650 Ti card quite cheap, but i need to know, does the Premiere Pro CS5.5 Mecury GPU Playback engine support this card? It ain't listed in the list of supported cards, but it's an Nvidia card so i just wanted to be sure I also need to know: is the new cards on the list, that was added in CS6 also supported on CS5.5?
Thank you in advance
/gammarik

Gammarik wrote:
Also, do Premiere use the CPU? I have a quite fast CPU (6 cored 2.7 GHz AMD chip), so if it does, i am pretty sure that it would be able to cover performance the loss from the GPU.
Thanks
/Gammarik
Sorry to say this but your AMD CPU is not a fast CPU when it comes to video editing. If you search around on our 1100 record data base of PPBM5 benchmarks the fastest AMD single chip unit ranks at 502 out of those 1100 tested configuration. This is because AMD does not have some of the latest SSE 4.2 instructions on the chip. This is why Intel is so highly recommended for video editing. If you are using any of the MPE accelerated effects or features an you want the highest quality encoding with minimum encoding time you need an nVidia GPU

Adding GPU Accelerated Cuda Effects is suddenly very laggy?

Hello Adobe Experts,
I am appealing for some help with an issue that has bugged me for a little while. The best way to explain it is to show you the problem in a short 4 minute video which I will post below for those who have the time to take a look. Failing that my description is beneath the video.
Essentially, I upgraded to Premiere Pro CS6 from CS5.5 and discovered GPU acceleration. Wow! I subsequently was due to upgrade my iMac and bring in the specs to make the most of this technology, especially within colour correcting and grading. The new machine we got is a 2012 Mac Pro 12 core (2 x 6 cores 2.4Ghz) with 32 GB Ram and a Nvidia Quadro 4000 for Mac (2GB). It also has an SSD drive as the OS boot and applications drive so hoping that things would be super quick.
For a time they were, I can remember adding the Fast Color Corrector effect to a video clip and dragging the wheel around and everything would move in realtime, the program monitor was updating as I moved the mouse within the colur wheel. It was smooth and silky which I just loved as it meant that colour correction/grading would be now very easy to accurately dial in a look quickly and then move to the next clip. Plus no need to render afterwards either, hooray!
Then recently, and I am not sure what has caused this, it stopped working as well?!? I still don't have to render the clip after adding the effect or making a change to the parameters, however the process of making the change has become slow, unresponsive, laggy, delayed, laboured or any other similar adjectives. Now when I drag the mouse in the colour wheel the update happens in delayed steps and it is certainly anything from smooth and silky anymore. The problem with this is that it is very hard to accurately and quickly move the parameters around and make those fine adjustments which in turn slows down the process greatly.
I am really keen to know the following:
Does anyone else with a similar system have these issues?
Is this just how it is? (Trouble is I remember it being much faster and more responsive. Also I watched Maxim Jago at a workshop and he didn't seem to struggle with these issues when showing off GPU acceleration and adjusting effect parameters, even during playback)
Is it a hardware issue? Does my GPU need to be faster or is it not being correctly allocated to Premiere Pro?
Is it a software issue? Is it something that has come about in more recent versions of Premiere Pro?
How can I go about resolving this issue?
So far I have tried a fair few things like resetting preferences, ensuring the GPU acceleration in the 'Memory' preferences tab is turned on, clearing media caches, removing and reinstalling Premiere Pro et cetera.
If any experts from the community can help or indeed anyone from Adobe can help me resolve this issue, or at least feed back thoughts and comments, then I would be so grateful.
Best wishes,
Alex

Hi Maxim and JFPhoton,
I'll try and come back to all those points:
To JFPhoton-
which version of PPro are you using......CCloud, or CS 6 ? - CC Latest version
is your RAID setup configured in RAID 0......what were test results for speed ? Three internal HDD 3TBs striped together for maximum throughput. Speed results =
To Maxim Jago-
Yes I have reset the preferences. I have also unisntalled Premiere and then reinstalled it. Also completely reinstalled my OS just in case.
Playback is running at full res and has been since I got the machine - never had an issue from the start and then all of a sudden..... meh!
I have three internal HDDs (3TB) striped together in raid for maximum throughput which are pretty quick (speedtest above). I did try to check this though by putting source content onto my boot drive which is an SSD and then trying to see if issue exists in this case which it does. I also tried transcoding to other codecs than h.264 and the problem is still present.
Yes there is a fair bit of software running in menu bar. Used to have iStats running which I have removed now and problem still persists. Others I wouldn't think should be taxking the GPU. Although I will try quitting out of everything none essential.
Definitely up to date on most recent version of PPro
The Quadro 4000 was superb once I first got it. As mentioned above, I could perorm all the edits to the mentioned effects with ease at full res whilst plyaing back and everything working fine! I just wonder however if the card may have developed a fault or need cleaning out of dust or something? (quite a lot of dust present when I last opened the side door). Is there a way to check this?
Same problem persists across different projects and codecs.
As I just mentioned to Maxim, I wonder if my GPU has developed a fault? The reason I say this is because sometimes my monitor doesn't come on correctly (just shows a black screen) and I have to turn on and off again. Also, sometimes within Premiere I have an issue where I resize a window and I get 'ghosting' of that window as I drag. Did also previously have an issue changing between colour correction workspace and editing workspace. The workspace simply wouldn;t change and everything was completely unresponsive. I just wondered if anyone knew a way to check the GPU without taking it out of the machine or indeed if this might be the cause of my problems?
Thank you so much for taking the time to respond. I really really appreciate it.
Best wishes

GPU Acceleration Cards For Premiere Pro CS5

Hello:
I am ready to invest in a GPU accelerated graphics card that will speed up playback and use the Mercury Playback Engine in GPU mode.
From what I could find on the Adobe site, these are the cards that are supported for Premiere Pro CS5
Supported NVIDIA video cards for GPU acceleration (CS5):
GeForce GTX 285 (Windows and Mac OS)
GeForce GTX 470 (Windows)
Quadro 4000 (Windows and Mac OS)
Quadro 5000 (Windows)
Quadro 5000M (Windows)
Quadro FX 3800 (Windows)
Quadro FX 4800 (Windows and Mac OS)
Quadro FX 5800 (Windows)
Quadro CX
Can anyone give me a recommendation from your own experience? Is the list of cards above still valid?
Thanks,
Rich Locus

So... before I go out and spend $650 on a GeForce GTX 680, it is this simple to make it work in CS5?
Yes.
(1) Make sure the card has at least 1GB of VRAM (which the GTX 680 has).
(2) Edit the cuda_supported_cards.txt to add one line: GeForce GTX 680 (starting in column 1)
(3) Install the card?
Do step 3 before step 2.
Also, you can simply delete the cuda_supported_cards.txt file
and achieve the same result.
Will Premiere Pro recognize that I have the card and immediately take advantage of the GPU capabilities, or do I have to change options?
You will need to specify:
"MPE GPU Acceleration" in your Project Settings:
If you do not have a supported card (or have not applied the hack),
this option will be greyed out.

Mercury Playback GPU acceleration in CS5.5 not available, Mercury Playback Software only available

Getting a warning screen each time I open an existing project in PP CS5.5 that says GPU acceleration is not available on my system...when it has always in the past. Editing on a HP Z400 with the NVidia Quadro 2000. I can't figure out how to get GPU acceleration going again. The software only option makes for a painfully slow and clunky edit. Any ideas are gladly welcomed. Hot and heavy deadlines looming...you all know the drill. The warning window I get reads "This project was last used with Mercury Playback Engine GPU Acceleration, which is not available on this system. Mercury Playback Engine Software Only will be used." And there is only an "okay" button to close the window. Also when I try to start a new project GPU Acceleration option is not accessible...defaults to the software setting and it's grayed out.

Hi Joe,
Have you updated your video drivers lately? Any OS updates?
Thanks,
Kevin

Nvidia or Radeon for Photoshop CS5/6 for GPU acceleration

Hi there-
Im buying a new videocard for my photoshop PC, and Im trying to figure out if Photoshop supports GPU acceleration on both Nvida and Radeon cards. Ive heard in the past that it only supported CUDA (Nvidia). I currently use CS5, but will update to CS6 at some point.
Thanks,

From a pure quality perspective - and you should know I develop OpenGL graphics software myself - I find ATI/AMD's display drivers to be more consistently of good quality. Both companies flub driver releases occasionally, as they focus primarily on computer game development, but ATI seems to deliver "golden" versions, which just work right with Adobe products, more often. I have had to work around problems in display drivers from nVidia more often.
Also note that Photoshop and company tend to prefer single video cards, rather than dual/multiple GPU arrangements sometimes found inside certain video cards, or creatable by the user by buying multiple cards. Many modern video cards can support multiple monitors on a single GPU.
If you do choose one or the other video card, also keep in mind you'll want to make sure you don't push your computer's power supply past its design limits. I like the ATI x670 line (e.g., the current VisionTek ATI Radeon HD 6670 1GB DDR5) because it balances power consumption against GPU performance, and doesn't emit "on the runway" fan sounds. Don't get me wrong, these cards are plenty fast, but they don't even require a separate power connector.
-Noel

Cannot use GPU acceleration with 64 bit CS5 under 64 bit Windows 7 with two cards ATI & nVidia

Subject sums up the problem, but here are the details:
My ATI is a 5850, and I have drivers 10.6 installed. That's my primary card connected to my main monitor.
The second card is an nVidia GTS 250 connected to my second monitor with 258.96 drivers.
CS5 does not detect my GPU(s), hence, does not enable GPU acceleration. It says:
"Graphics hardware acceleration is unavailable. You will need to upgrade your video driver and possibly your video card" both of which are obviously wrong, since I have the latest CS5 supporting drivers installed for two cards that can run GPGPU applications!
Any suggestions?
Thank you.

function(){return A.apply(null,[this].concat($A(arguments)))}
nzkiwi wrote:
I'm curious about whether the requirement to support HLSL Shader Model 3.0 is a big part of what is holding back GPU acceleration support for ATI cards in Adobe products. It seems that HLSL Shader Model 3.0 is NVidia/Intel proprietary, whereas GLSL is an open standard like OpenGL.
What ATI support do you find being held back? Just curious. I ask because I have a 2 year old ATI 4670 card that supports Photoshop nicely. The Catalyst software seems to have embraced whatever's necessary to run Photoshop.*
-Noel
* That said, I see a specific bug where sometimes the 32 bit drivers on my x64 system will not be recognized by Photoshop 32 bit as OpenGL-capable at Photoshop startup. I've reported it to ATI, and they seem to have taken it seriously, so I expect a fix in a future version. The 64 bit drivers always satisfy Photoshop's needs, so I'm sure it's not a design deficiency but just a lil' ol' bug.

Premiere CS5 - Graphics cards for GPU acceleration

Hello everyone
In the system requirements under "Supported NVIDIA graphics cards for GPU acceleration" are the following graphics cards listed:
     GeForce GTX285
     GeForce GTX470
why are only these two GeForce Cards supported?
Why are the other NVIDIA cards like
     GTX460
     GTX480
     GTX560
     GTX570
     GTX580
not listed?
What about support of SLI configuration?
What is better, a 2 x GTX470 configuration or a single GTX580 ?
Thanks for your responses in advance.
Regards
Urs

The guys at Studio One did some tests and wrote this interesting article:
http://www.studio1productions.com/Articles/PremiereCS5.htm
It seems that the RAM speed (DDR5 v/s DDR3) is more relevant than any other factor...
The GTX 470 has more cuda cores than a lot of the more expensive cards... go figure?!

I have Premiere Pro CS5. I just had to switch out my hard drive and even though nothing else changed, Premiere is not allowing me to use the GPU acceleration mode. It's grayed out. It was working fine before I switched out the hard drive. What do I do?

The specs on my computer are correct for GPU acceleration. It has been working fine but my RAID 0 drive failed and I replaced it and now Premiere no longer recgonizes it. I am assuming I need to reset something but I can't figure it out. What do I do?

You will need to reapply the cuda hack, see Ann's answer:
Re: How to activate Cuda with a quadro k2000 into premiere cs6

Cannot enable Mercury Playback Engine GPU Acceleration

Cannot enable Mercury Playback Engine GPU Acceleration.
Just bought a Asus GeForce GTX 560 Ti just so that I can use the graphics acceleration on Adobe Premiere Pro CS5.
Followed every step in most tutorials such as this great one http://vimeo.com/13440307 and yet the Mercury Playback Engine GPU Acceleration option is still faded out.
http://www.urbanistgame.com/wp-content/uploads/2012/06/Cuda-supported.gifAdded the last two lines as wasn't sure if it required "Ti" it only came up as "supported" in the cmd after the "Ti" so I'm guess that's what it required.
You can see in bold I've set the Multi-display/mixed-GPU acceleration option to "Compatibility performance mode"
   Splash screen confirms Version as 5.0.3 (update to enable Mercury Playback Engine GPU Acceleration).
After all that the "Video Rendering and Playback" option is still faded out.
Any ideas? System Information
List of installed Nvidia programs
Hope someone can help.

PROBLEM SOLVED.
I reinstalled CS5 on the bookdisk and it worked fine. Spent 9 hours trying everything else its really was the only thing left and the last thing I wanted to do.
Results:
Rendering a 32min clip with Gaussian Blur effect
Before CUDA it took 4 hours and hence my move to purchase a CUDA card.
After CUDA 23mins! using Encoder
Question:
I noticed that the GPU is not stressing that much still. Only running at 30% activity???

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

List of GPU accelerated Effects in CS5

Similar Messages

Maybe you are looking for