Premiere Pro CC Warp Stabilizer with activated Mercury Playback Engine - GPU doesn't use the Nvidia GTX Titan GPU - CUDA

Windows 7 Pro, fresh installation, include all updates
Premiere Pro CC - actual version
Gainward GTX Titan Z - actual firmware and driver
SSD Hard Drive
Intel i7/ 960/ 3.2GHz/ 32GB RAM
Mercury Playback Engine - GPU is activated.
Card is known by standard in cuda_supported_cards.txt
Selected Clip: 1920x1080i, 25fps, AVCHD/mp4
Seleceted effect: Warp stabilizer with Subspace-Warp (Standard-parameters)
Step 1: Analyse the clip
The Intel i7 is working with 90%, not the GPU
The status monitor of the Nividia-card shows 0% used performance
Playing the analysed clip (informations from the Cuda Render System):
Total render time: 26ms
Display FPS: 0.82
Scheduler FPS: 2.28
Target FPS: 25.00
Rendered FPS: 3.50
Total: 239
Dropped: 234
=> Playing the analysed clip is dropped extremly.
Step 2: Rendering the clip
The Intel i7 is working with 90%, not the GPU
The status monitor of the Nividia-card shows 0% used performance
The Warp Stabilizer is shown as a GPU-Cuda supported effect.
The GPU doesn't help the Intel i7....?!
Please help me!

Thank you for your fast response!
Warp-Stabilisation shall be a GPU accelerated effect.

Similar Messages

Adobe Premiere Pro CC crush - no Mercury Playback Engine GPU acceleration (OPEN CL)

I was an happy customer of Adobe CC till few days ago.
It were a few weeks I did not update the software in CC due to a problem with connection.
Needed to use Premiere Pro CC. It always crushes my MacBook Pro retina 2012 (16 giga ram) during export of the video. The monitor became black and there was no way to restart.
The Macbook worked smoothly with all the other softwares. Deleted CC and reinstalled everything, which was quit painful. However, at the end of the day, Premiere Pro CC works but I cannot use Mercury Playback Engine GPU Acceleration (open CL) which I used all the times before with huge advantage (exporting a 1 minute video in good quality needed 2 minutes with GPU accelerator, 20 minutes without).
When I open old project of Premiere Pro cc I read this message "this project was last used with Mercury Playback Engine GPU acceleration (OPEN CL), which is either not available or not certified on this system. Mercury Playback Engine software only will be used". There is no way to change the rendered from Project setting - Mercury Playback Engine software is the only option.
My question: is it a problem with Adobe Premiere Pro CC or with my graphic?

Ask in the Premiere forum.
Mylenium

Nvidia Geforce 670 and the Mercury Playback Engine GPU Acceleration for Adobe Premiere Pro

Will Adobe test and certify the Nvidia Geforce GTX 670 for use with the mercury playback engine GPU acceleration feature of Adobe Premiere Pro CS5 in the near future? Any advice would be much appreciated, thanks in advance for any help.

Adobe only certifies after extensive testing... For many others, with at least 1Gig of video ram, use the nVidia Hack http://forums.adobe.com/thread/629557 - which is a simple entry in a "supported cards" file - and Mac http://www.vidmuze.com/how-to-enable-gpu-cuda-in-adobe-cs6-for-mac/

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?

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.

Imac 2012 NVIDIA GeForce GTX 680MX will it work with adobe Mercury playback Engine?

imac 2012, 28" 16 gigs ram
NVIDIA GeForce GTX 680MX 2 gigs ram, will it work with adobe Mercury playback Engine for accelerated rendering in Premiere Pro & After Effects

One would certainly think so, since earlier, lesser GTX cards were supported...
http://www.adobe.com/products/premiere/tech-specs.html
Supported NVIDIA graphics cards for GPU acceleration
GeForce GTX 285 (Windows and Mac OS)
GeForce GTX 470 (Windows)
GeForce GTX 570 (Windows)
GeForce GTX 580 (Windows)

Mercury Playback Engine GPU Acceleration

I was an happy customer of Adobe CC till few days ago.
It were a few weeks I did not update the software in CC due to a problem with connection.
Needed to use Premiere Pro CC. It always crushes my MacBook Pro retina 2012 (16 giga ram) during export of the video. The monitor became black and there was no way to restart.
The Macbook worked smoothly with all the other softwares. Deleted CC and reinstalled everything, which was quit painful. However, at the end of the day, Premiere Pro CC works but I cannot use Mercury Playback Engine GPU Acceleration (open CL) which I used all the times before with huge advantage (exporting a 1 minute video in good quality needed 2 minutes with GPU accelerator, 20 minutes without).
When I open old projects of Premiere Pro cc I read this message "this project was last used with Mercury Playback Engine GPU acceleration (OPEN CL), which is either not available or not certified on this system. Mercury Playback Engine software only will be used". There is no way to change the rendered from Project setting - Mercury Playback Engine software is the only option.
My question: is it a problem with Adobe Premiere Pro CC or with my graphic? How to fix if is due to the software.
thanks

giacomonovara wrote:
--- GPU Computation Info ---
Did not find any devices that support GPU computation.
Any idea of the meaning?
It means your nVidia GPU isn't active. Either it's toast, or OS X has turned it off for some reason. My laptop is nearly identical to yours, and this is what my output is:
# /Applications/Adobe\ Premiere\ Pro\ CC/Adobe\ Premiere\ Pro\ CC.app/Contents/GPUSniffer.app/Contents/MacOS/GPUSniffer
--- OpenGL Info ---
Vendor: Intel Inc.
Renderer: Intel HD Graphics 4000 OpenGL Engine
OpenGL Version: 2.1 INTEL-8.26.34
GLSL Version: 1.20
Monitors: 1
Monitor 0 properties -
   Size: (0, 0, 2880, 1800)
   Max texture size: 16384
   Supports non-power of two: 1
   Shaders 444: 1
   Shaders 422: 1
   Shaders 420: 1
--- GPU Computation Info ---
Found 1 devices supporting GPU computation.
OpenCL Device 0 -
   Name: GeForce GT 650M
   Vendor: NVIDIA (Apple platform)
   Capability: 1.2
   Driver: 1.2
   Total Video Memory: 1024MB
See the difference? The nVidia GPU is listed.

I cannot enable Mercury Playback Engine GPU.. I have a FirePro W9100..

As the title states, I cannot seem to enable Mercury Playback Engine GPU..
I have a FirePro W9100, and the option to shift from software only to GPU is disabled. Any ideas?
I purchased the W9100 solely for use with Premiere, and help assist with GreenScreen rendering..
I have the latest driver pack from AMD, and I'm running Premiere Pro CC 2014 (all updated).
I'm banging my head against the desk with this one, and any help greatly appreciated!

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

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

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

Mercury Playback Engine GPU not available

I've been reading through forum postings and have not found a solution, so I apologize if there is a solution posted elsewhere.
I have a 27" iMac (late 2012) with NVIDIA GeForce GTX 680MX graphics card running Mac OS 10.8.5.
I'm using Adobe Premiere Pro CS6.0.3, and when I updated my OS to 10.9 Maverick, I began to experience several problems, including:
The dreaded spinning beachball and "Premiere not responding."
"This project was last used with Mercury Playback Engine GPU Acceleration (CUDA) which is not available on your system. Mercury Playback Engine Software Only will be used.
Video files - I think they were all .MOV - became "squished" to the top of the Program Monitor (movie only took up about 1/3 of program monitor window).
After a long chat with Adobe Support, he indicated that the update to 10.9 Maverick was the problem, so I:
Updated to Premiere 6.0.5, but that did not fix any of the issues.
Logged in as "Root," which worked for a while but I also received 3 "Premiere encountered problem and must shut down."
Deleted preferences, repaired permissions, basic troubleshooting practices, etc, but problems persisted.
No help.
Eventually I restored my computer from a Time Machine backup to a day prior to the OS 10.9 update, and this seemed to fix all the issues. So I was back to Mac 10.8.5 and Premiere 6.0.3.
But the .MOV-compressed-in-the-program-monitor problem began to surface again (see photo below).
So I updated to Premiere to 6.0.5 (but not my OS - it's still 10.8.5), and the "Mercury Playback Engine" error is back.
And the .MOV files are still compressed in the Program Monitor. I have a project that I completed in 6.0.3, but is now messed up in 6.0.5.
Help please. Is the only solution downgrading to Premiere 6.0.3, and if so, must I do a clean install of the program from the DVD?
Thanks,
RW Harris, Director of Training
Express Oil Change & Tire Engineers
Birmingham, AL

harris1966 wrote:
Thanks so much for your quick responses.
@Kevin, the strange thing is this: Express purchased this iMac and the Adobe Creative Suite back in January of this year, and the computer and software have worked flawlessly since that time.
It was only after upgrading, first to Mac OS 10.9 Mavericks (which I later downgraded back to 10.8.5), and then to Premiere 6.0.5, that I began experiencing problems.
Prior to these upgrades, I never received the "Missing Renderer" message, nor did I experience any lagging problems or problems relating to .MOVs in the Program Viewer.
Hi Randy,
I'm sorry. I really don't know the answer to your question, or how that happened. All I know is that the card is not supported for CS6. I guess we have a mystery on our hands.
harris1966 wrote:
Any insight on why I never experienced problems until upgrading software?
Sorry, it is behaving as if your text file was hacked prior to you receiving the computer. After you updated the OS, a new text file without your card was created. Your card would not be listed in that file because it is not supported.
harris1966 wrote:
Are you saying that PP doesn't support NVIDIA 680 MX cards "now that the software is at 6.05"? Or PP doesn't support that card at all, under any software version?
The card is supported for Premiere Pro CC, but not prior to that.
harris1966 wrote:
Again, thanks so much for your help.
You're welcome!
Thanks,
Kevin

When will newer EVGA video cards be approved for Mercury Playback Engine GPU Acceleration?

I built my system for video editing, Windows 7 Ultimate, i7 920Mhz, 24Gb RAM, ASUS Rampage III Extreme motherboard and EVGA GeForce GTX 570 video card. I decided to upgrade my video card to EVGA 660Ti with many more CUDA processors and 3GB memory, but when I rendered some video I got this message "The 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 it seemed the rendering was slower. Even though the EVGA newer Video cards have more memory and processor power and more CUDA cores and score better on Windows Experience Intex, Adobe does not approve them and say they use Merecury Playback Engine GPU Acceleration. Why? The Quadro cards are much more expensive have less memory, fewer CUDA cores but are rated higher by Adobe for Premiere and rendering, why is that? What gives? Why are the EVGA cards that seem more powerful and less expensive rated lower than the Quadro cards? Will this ever change?

LOL!
Hunt

What do I do?: Mercury Playback Engine GPU Acceleration missing

After using Premiere Pro for about 2 months, this morning I get the message "Mercury Playback Engine GPU Acceleration Missing"
Not sure what to do?

Can you please provide more info. You can use this post for guidance FAQ: What information should I provide when asking a question on this forum?
First question is
- Have you tried re-installing the CUDA driver?
Thanks,
Peter Garaway
Adobe
Premiere Pro

Missing Mercury Playback Engine GPU Acceleration after computer crash. How can I get it back

Hi, I'm missing Mercury Playback Engine GPU Acceleration after computer crash. How can I get it back? I had my husband update my graphic driver. How what do I do? When I check the project settings > general, it still has the field of Mercuy Playback software only grayed out.

restart your computer and retry.
if that fails and you have a mac and premier, How to Enable Premiere Mercury Playback GPU Acceleration CUDA on iMac

The Next Version of Premiere Pro CC - Warp Stabilizer

With the recent post of what's coming in the next version of PPro CC, I was sad to see no mention of Warp Stabilizer. As amazing of an effect as it is, it needs a bit of help. I know there are improvements and fixes that probably weren't mentioned in the post so I'm still holding out hope. We use Warp Stabilizer more than anyone I know. Several hundred times per week. Yes, per week, no exaggeration. Over the last few years, we've built an entire style of shooting around the strengths of this awesome effect that emulates the use of a slider, steadicam and crane all without having to have them. So we've become really familiar with its PROS and CONS.
Here is a short list of SEVEN things that should be addressed with regards to warp stabilizer within Premiere Pro CC to maximize its effectiveness (and yes we did submit multiple Feature Requests for these so far to no avail):
FIrst and foremost and by far MOST IMPORTANT to us - Allow users to create a CUSTOM PRESET with any altered settings that will engage (or begin Analyzing/Stabilizing) automatically when added to a clip!! This is huge. If you double click on Warp Stabilizer with a clip selected, it is applied to that clip and begins the process of stabilizing that clip. However, the vast majority of the time we need to alter the settings of the effect. If we create a custom preset, that's all fine and good, but when we add that to a clip, it does NOT begin stabilizing. Instead you have to manually go into the Effect Controls for each clip and select ANALYZE. Huge waste of time when adding this effect to hundreds of clips. PLEASE FIX!
BUG when saving projects!!! - If this is not a bug, it needs to be fixed because it's awful. - If you have more than one sequence with multiple warp stabilizations added and GPU ACCELERATION IS ENABLED, then after you SAVE a project (or if it auto-saves) when you toggle between the two sequences you are hit with a delay or freeze while the render bar goes from Yellow to Red...and finally back to yellow again. No work can be done during this delay/freeze. The more stabilized clips, the longer the delay. For us, on our larger projects this delay is sometimes 30 seconds to almost a full minute! Once it turns back to yellow, you can toggle between sequences without the delay...but as soon as it saves again...and you toggle between sequences, the delay hits again. If this is a bug, or somehow a result of Premiere Pro's way of CACHING projects after it's saved, then I sincerely hope it's fixed asap. It's awful!
The third is more of a feature request than a fix - Add the ability to set the maximum scale to work WITH the smoothness control so that if you never want your clips to scale more than say 105%, you can set that and have Warp Stabilizer stabilize the clip and adjust the "smoothness" percentage from the default "50%" down to whatever it needs to be in order for that clip to be fully stabilized and scaled to no more than 105%. Correct me if I'm wrong, but this is not possible currently. Right now we have to manually adjust each clip if it is initially scaled too much by dropping down the Smoothness %.
Another great feature would be the ability to manually keyframe the scaling so that if you have a longer clip that starts fairly steady, then needs to be smoothed out a bit more in the middle, before it ends relatively steady again, you can slowly and seamlessly ramp up the stabilization/scaling so that the whole clip doesn't have to be scaled to make up for the misgivings of one portion of the clip.
Minor bug - sometimes when you have extended the length of a clip, the clip needs to be re-analyzed again. However, the "analyze" button is often greyed out. You need to click away from the clip and then click on the clip again to make that button appear again. Nothing big, but still, a small bug.
After Effects Warp Stablizer VFX feature carried over - It would be nice to carry over to Premiere the ability to isolate what in frame is supposed to be stable (sometimes someone nodding their head can trick the effect into thinking that it's the camera shaking). Great to have it in AE, but would be nice to carry over to Premiere Pro CC.
Finally, I've always believed that no matter how cool "Subspace Warp" sounds, it is not as effective as "Position, Scale & Rotation". This SHOULD be the deafult "method" within the Warp's settings. I'd say 95% of the thousands and thousands of clips we've stabilized we ended up switching the "Method" within the settings to "Position, Scale & Rotation" because it either scaled the shot less or created less "wobble" in the resulting stabilized clip. I know everyone shoots differently, and sometimes Subspace Warp is the way to go, but we have stabilized all sorts of shots with great success by simply switching this setting. Granted...if #1 on this list was taken care of we could then easily have this set as our default setting.
Hopefully this list either reaches someone within Adobe that can do something about them or at the very least inspires others to write feature requests and bug fixes as we have. Even resolving #1, #2 and #3 would be HUGE and would save our editors probably 10 hours per week. It's an awesome effect, far better than "smoothcam" on FCP7, it just needs a little love.

CoSA_DaveS wrote:
All good points, thanks for posting.
For #1, you can make this work in AE at least. This tip is from my colleague DanW:
If you make a preset by only selecting the values you change (and not a preset for the whole effect) then it will auto-analyze on apply.
Simplest way: apply WS, make edits, hit UU to reveal changed params, select all "i-beams" in the Timeline, drag them to the Effects & Presets panel.
For #4, you can get manual control over the scaling by setting Framing to Stabilize Only, and then keyframe Additional Scale to taste. At one point we were going to try to automate this, but found automatic scaling to be very subjective as to the best way to handle it.
For #6, Warp Stabilizer will not track areas with zero alpha channel. So you can pre-mask the input to reveal just the parts you want to stabilize. Do this inside a nested sequence, with Warp Stabilizer applied downstream (in the outer sequence). The just-announced masking & tracking capabilities of the next CC version should be handy for this.
-DaveS, Adobe Dynamic Media, Advanced Product Development
Hi DaveS!
Great to hear that you guys are taking a look at this list. Hope it helps make it better. #1, #2, and #3 are by far the biggest time killers for us so hopefully they'll be able to be fixed/resolved within Premiere soon.
Regarding your note about #1: Allowing this functionality within Premiere specifically would be very helpful. Would it be possible to eventually allow Premiere to auto-analyze when a saved custom preset is applied to a clip? I tried it in AE as you suggested, and couldn't figure it out. But realistically we use Warp Stabilizer on so many clips that round tripping literally hundreds of short clips to AE would be just as time consuming as going into the settings in premiere for each one and adjusting the parameters. We usually adjust the method and then adjust the smoothness scale so that it doesn't "Auto-Scale" more than 104%. That's where our #3 suggestion would help. I didn't quite understand how to make a preset of specific changed values. I tried, but couldn't follow DanW's suggestion. Granted, I'm not that great with AE. I really just use it for the Warp VFX's ability to isolate what in frame is stabilized (hope that comes to Premiere one day) and that's about it. And I really only have to do that a couple times per project. Anyway, I'm sure I'm doing DanW's suggestions wrong but regardless, I'm not sure it would save us much time when we have several hundred individual little clips that would all need to be sent to AE. Any hope for adding this auto-analyze functionality (hopefully allowing a custom preset on the whole effect and all it's adjusted parameters) in Premiere CC?
Regarding your note about #4: That is a valid work around for now. I appreciate that thought. Thanks!
Regarding your note about #6: I think I half understand what you described. I'd have to try it. Although, as I said before, the AE way of doing it is ideal and I just hoped that ability to show the tracking points and delete them over time would come to Premiere CC one day. When the next CC comes out I'd love to try this masking method although I think I'll have to claify exactly what you want me to do just to be safe. Is there no hope to port this added functionality that's in AE's Warp VFX over to Premiere's Warp Stabilizer? Again, not the end of the world for us. I'd rather #1, #2 and #3 be addressed inside Premiere Pro CC for now.
Fixing the first 3 on this list would be HUGE time saver for us.
Thanks again DaveS to you and the rest of the Adobe team for looking into this list. Very much appreciated.

Premiere Pro CC Warp Stabilizer with activated Mercury Playback Engine - GPU doesn't use the Nvidia GTX Titan GPU - CUDA

Similar Messages

Maybe you are looking for