Premiere Pro CS6 Warp Stabilizer not using GPU/CUDA why?

Hi,
I installed CS6 and tried the Warp Stabilizer, I undestand that only part 2 of the process (stabilize part) is GPU accelerated, but I can't get any acceleration from GPU, my GPU is idle at 1% usage (GTX580) and all the processing is going to CPU. The renderer/playback is marked CUDA so its not that.
Is there anything I'm missing?
Thanks

OK, this surprised me a bit. I have a state-of-the-art new PC with plenty of RAM, a fast processor and lots of cuda cores. See the specs here: http://www.stevengotz.com/
It took over 10 minutes to stabilize one minute of video - 1800 frames. It wasn't all that shaky to begin with, but it was handheld and therefore looks better after using Warp. There was one section that was so bad, I sliced the clip up and chose not to stabilize that part after the fact. So I thought that it might have added a little to the problem. But no. I tried just 180 frames of reasonably stable hand held video from the same clip and it took almost a minute.
Now, once the process was finished, I had no problem playing it back in realtime without rendering. But what is taking so long? I understand that there is a lot of work to do, but why isn't it using the power I have provided?
This is a screen shot of my resources about two minutes into the process.
I would love to know what I need to do to speed up this process. I get that it is working in the background. Is it possible to make it work in the foreground? I would not mind if it maxed out the RAM or the CPU or both if it would help.
edit: I just submitted a Feature Request to let Warp run in the foreground using every available resource.
Steven
Message was edited by: Steven L. Gotz to include additional information.

Similar Messages

Premiere Pro CS6 - Warp Stabilizer BUG causes project to crash

Hi!
Sometimes Warp Stabilizer causes Premiere CS6 to crash. I found out what steps cause this so hopefully a fix can be made in an update soon:
1) Add the WARP STABILIZER to a clip. It Analyzes and then is applied to the clip.
2) TOGGLE OFF the effect in the effect controls window
3) Adjust the clip duration and RE-ANALYZE while the effect is TOGGLED OFF still and Premiere crashes.
Happens every time. BUG Report was filled out.
(If the effect is toggled ON when you RE-ANALYZE it, everything works okay.)
So why not just not do this? Well, I usually don't but sometimes in the middle of working with hundred of clips I toggle on/off the effect to check certain things and then leave it off. If the clip is adjusted later or I come back and try to click ANALYZE again while the effect is toggled off, everything crashes.
That's the pop up. If Premiere doesn't allow for you to re-analyze a clip while the effect is toggled off, then the ANALYZE button should not be active or at least a popup saying "Cannot Analyze this clip while it is toggled off". Instead Premiere crashes and upon reopening the project you are forced to rename the project which fortunately is usually fully recovered.
Running 6.0.2 on a suped up 2011 27" iMac with 16gb ram and AMD 6970M 2gb video card.

I know I'm piggy-backing on an old post here, but I've just had real issues with a similar thing on Mac. Unfortunately, my Premiere CS6 is crashing and becoming totally unresponsive whenever I simply apply the Warp Stabilizer. The moment I drop it on my clip, BLAM! I get that same pop up you posted. I click 'OK,' and then nothing. Just beachbal of death until I force quit. What's more annoying is that, not only has the camera operator made the stabilizer essential, but I've been using it for the past week with no issues up till now.
At first I thought I was overloading Premiere by dropping the effect onto two clips at the same time. But I tried it one at a time and had the same problem. My recovery project files seem to be ok, but that's not even nearly the point. I simply can not use a great and essential tool. Help?

Adobe Premiere Pro CS6 (mac) will not completely launch.

After a few weeks idol my Adobe Premiere Pro CS6 (mac) will not completely launch. It tells me a serious error has occurred, it shuts down and the circle continues. I've even reloaded the app and it happens again. I did upgraded to Yosemite but I can't find anyone else having probs with Yosemite. Any ideas. No luck on the adobe site.

>did upgraded to Yosemite
CS6 is about 3 years old... even the latest Cloud versions had to have updates to be compatible... since you have "reloaded" (was that a full uninstall and reinstall?) I have no other suggestions

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 CS6 Dynamic Link not working

Hi,
Just wondered if anyone has seen issues with the Dynamic link options in Premiere Pro CS6, all the options to work with After Effects are greyed out although this product is installed.
However I only have CS5 for after effects, is this a compatibility issue or am I doing something wrong here?
Thanks in advance for any assistance.
Kind Regards
Steve

Dynamic Link only works within one version, so you can't use it between CS6 and CS5 or CS5.5 and with older versions you had to have a complete suite, not individual products.

Adobe Premiere pro CS6 effects presets not working

Presets in my Adobe Premiere pro CS6 is not working. What can I do? I need Work with Effect Presets
Message was edited by: Kevin Monahan

What do you mean "not working" What's not working? What are you wanting to do?
More information please.

I installed Premiere Pro CS6 and do not know where it is located.

Just like in the topic. I do not know how to run Premiere Pro CS6. Help pls.

Windows or Mac, part of the Cloud or from the individual purchase link... and other questions
-PPro Information FAQ http://forums.adobe.com/message/4200840

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.

Adobe Premiere Pro CS6 crashes with not finding a capable play module on a windows desktop with a AMD Radeon R9 200 series board.

I installed Premiere Pro CS 6.0 on a brand new system.
Win 8.1,
i7 3.4 GHz on an Asus Sabertooth
16 Gig memory
AMD Radeon R9 290 Graphics Board with the latest drivers and Bios.
On starting Premiere I get the (as I noticed quite frequent appearing) error message that Premiere cannot find a capable play module and the suggestion to update my video drivers.
I tried everything I found in this forum or on the web:
Installed the latest drivers
Run the program as an administrator
Updated the Graphics board Bios
Updated Premiere CS6
Started Gpusniffer in CMD-mode to find out what board it found and added that to the cuda_supported_cards.txt in the Premiere directory.
All to no avail. The app will simply not start.
The Gpusniffers report states:
Loadlibrary “n” failed
Loadlibrary “n” failed
--- OpenGL Info ---
Vendor: ATI Technologies Inc.
Renderer: AMD Radeon R9 200 series
OpenGL Version: 4.4.13084 Compatability Profile Context 14.301.1001.0
GLSL Version 4.40
Monitors: 1
Monitor 0 properties –
Size: <0, 0, 1920 1080>
Mex texture size: 16384
Support non-power of two: 1
Shaders 444 :1
Shaders 422: 1
Shaders 420: 1
--- GPU Information Info –
Did not find any devices that support GPU computation.
As I invested a lot in the CS6 Master Collection I am not considering an update tot the CC version, also because the same problem occurs in that version too.
I would be much obliged if someone has an answer that truly will work. This problem costed me the best part of two days’ work and fouled up my workflow considerably.

==========
I tried to go into display settings and disable the Intel card. (this caused low resolution which is unexceptable)
==========
This makes me think it's using that graphics "card" ( probably built into mobo ? ...called 'onboard graphics ? )
This stuff gets tricky and sometimes the only way to make windows 'recognize' the pci graphics card is to actually take it out and boot, and then put it back in...
Then you get mssg " windows detected new hardware" and you install the drivers...
usually bios gives you choice of using onboard graphics or not ( but this too is wanky sometimes...sorry to say ...)
I recently ( this past year ) had a similar sort of situation but have a desktop, where its easy for me to take off side panel and pull the pci-e graphics card and boot, and get that horrible low res default screen...turn off, install card, reboot etc...
but anyway, it sounds to me like you're notebook is using that mobile graphics driver stuff and not the radeon. Somehow you've got to make it switch to that graphics card is maybe your solution.
sorry I dont have notebook but maybe someone else here does and can help more...
good luck.
ps..its always a weird fact of life...when things aren't working 'right' something has to get done fast....
edit:
I dont know how much you know about windows stuff, but after you disable that intel thing and get your low res screen.. you DID try to update the driver for that card using 'my computer / device manager ' right ??

Premiere Pro CC - Warp Stabilizer causing "Heat Waves"

I'm using Premiere Pro CC 2014 and when I apply Warp Stabilizer to certain clips I get this weird heat-wave, shimmer-like effect. For the life of me I can't figure out why this is happening. I've tried singling out every variable that I can but nothing matters.
You can see what I'm talking about here: Dropbox - With WS.mp4
And here is the clip without WS applied: Dropbox - Without WS.mp4
The clips I'm trying to stabilize are actually pretty stable already so it shouldn't be an issue for WS normally. It doesn't seem to make a difference whether they're in a 720 timeline or 1080.
I've tried every setting in WS that I can, including 'detailed analysis' and 'enhanced reduction' on Rolling Shutter Ripple. The only thing that kind of seems to help is applying the rolling shutter repair plugin but even then it's still somewhat choppy.
The shots themselves don't have any noticeable rolling shutter ripple (slow moving grass shot on a monopod) and they look great UNTIL I add Warp Stabilizer and they get the weird effect. Even though the clips are already pretty stable, I just want to add WS to smooth some of these clips out a little bit. When I replace the clips with an AE comp and WS in AE it's fine! But I want to figure out why this is doing it inside Premiere so I don't have to use dynamic link every time I want to use WS.
I just got this machine, maybe that has something to do with it...I have no idea.
System info:
Mid-2011 27" iMac
3.4 GHz Intel Core i7
12 GB 1333 MHz DDR3
AMD Radeon HD 6970M 1024 MB
OS X 10.9.5
Adobe Premiere Pro CC 2014.1
Shot on a 5D Mk. III with either a 24 (1080p) or 60 (720p) frame rate and resolution.
Can anyone help? Thanks

I don't have answers for you. Sorry. But I have seen that once before on a clip I stabilized. Much like the grass shot you show in your mp4. Mine was of a guy sitting at a pool and the bright plants behind him where flickering like a heat wave/desert-like effect. Only one clip had it and it made me go "hmm...never seen that before." I stabilized hundreds of clips in that project and that was the only clip with that heat wave thing happening. I was on 7.2.2 at the time. And eventually went to 8.0.1 with no change. It didn't bother me enough to do anything about it so I left it. It was shot at 1080p60 from a Panasonic PX270. Strangely I have the same computer as you (except I have 16gb of ram and I'm on 10.8.5). That is very interesting to me that it worked great in AE. Interesting indeed. I'll follow this thread in hopes of a revelation. Fortunately, I don't see that issue much or I'd be screwed.

Premiere Pro CS6 Project Files Not Recognised by Windows

Gidday, I hope someone can help with this problem. Premiere Pro(and After Effects) have worked perfectly on my laptop up until now. Saved PP projects are not recognised by Windows 7. I can open a new project but once I save it, it is not recognised and won't open and I can't reset either as the default programs for those files. The applications are visible in the start menu so it is very strange as all were working fine last week and nothing has been done to the laptop in the meantime.
Anyone else come up against this problem?
Thanks
Steve

Steve, I just had this happen as well.
I used the Programs section of the Windows Control Panel to initiate an uninstall. On Adobe's Unistall setup screen (or whatever it may be called) I selected to uninstall PP only. When it was done I restarted and then installed PP only. And then it was back to "normal."

Premiere Pro CS6 - audio plugins not engaging until roughly 1 second into clip

This is a strange issue I've been having with Premiere CS6, running on a Mac Pro. Anytime I add effects to audio, whether it is denoiser, highpass, eq, etc, the effect doesn't engage until roughly 1 second into the clip.
It doesn't matter if I render it or export it. The problem still occurs. In the past my solution has been to drag the audio out past the 1 second threshold, apply the effect, export just the audio, bring it back into premiere, re-align the new audio and export. What a pain!
Definitely a problem I've never had with Avid or Final Cut! Does anyone know if there is a way to fix this problem?!

It's a long-standing bug with certain audio effects. Please do let Adobe know you want it fixed.
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
In the meantime, you should do that kind of work in Audition instead.

Premiere Pro CS6 Constantly Crashing

I am having the worst time using Premiere Pro CS6. The program is constantly crashing, saying it has encountered a serious error and has to close. This is happening during the most basic operations like scrubbing the timeline or pressing play. I am using footage strait from my Canon 7D (h.264) with no effects or filters. I have all the latest updates to the software and my computer. No other programs are open during these errors. I'm using a 2011 MacBook Pro i7 8GB RAM with AMD Radeon HD 6750M 1024 MB and OSX 10.7.4.
I wanted this to be an alternative to FCP 7, but so far it is not working out.
Any ideas?

Happening to me too. Constant "serious error" crashes, usually when I'm doing hardly anything at all. One project was working with just a couple images and it was particuarly awful. Like you, H264 footage are a common thread.
I'm a Mac Pro 3,1 2x2.8GHz Quad-Core, 10.7.3 (will try updating), 8GB RAM, GTX285, 6.0.1 and CUDA 4.2.7. GPU Driver Version says 7.18.11 270.05.20f02.
As it stands I can't get anything done. My experience w/ CS6 so far has been to finish one project (2 tracks of DV, one of H264) that was originally started in CS5, and I don't really remember having any problems. Software worked much better than CS5 actually. Tried another one from scratch, same setup, but I encountered the H264 media pending bug that's been reported elsewhere and had to give up, go back to CS5. Project I mentioned above, I could barely do anything w/o the program crashing. This fourth project, another 2 DV/1 H264, I haven't encountered any problems playing back the footage yet, but this is when the software because very unstable.
My console is FULL of "invalid drawable" errors
5/30/12 2:40:09.845 PM Adobe Premiere Pro CS6: invalid drawable
5/30/12 2:40:09.846 PM Adobe Premiere Pro CS6: invalid drawable
5/30/12 2:40:09.988 PM Adobe Premiere Pro CS6: invalid drawable
5/30/12 2:40:09.993 PM Adobe Premiere Pro CS6: invalid drawable
5/30/12 2:40:10.017 PM Adobe Premiere Pro CS6: NSAlert is being used from a background thread, which is not safe. This is probably going to crash sometimes. Break on _NSAlertWarnUnsafeBackgroundThreadUsage to debug. This will be logged only once. This may break in the future.
5/30/12 2:40:21.354 PM com.apple.launchd.peruser.502: ([0x0-0x5a05a].com.adobe.AdobePremierePro[603]) Exited: Terminated: 15
5/30/12 2:40:23.049 PM com.apple.spindump: Premiere Pro [603] didn't gather enough samples to report (only 3 samples)
5/30/12 2:40:26.594 PM [0x0-0x71071].com.adobe.AdobePremierePro: --- OpenGL Info ---
5/30/12 2:40:26.600 PM Adobe Premiere Pro CS6: invalid drawable
5/30/12 2:40:26.601 PM [0x0-0x71071].com.adobe.AdobePremierePro: Vendor: NVIDIA Corporation
5/30/12 2:40:26.601 PM [0x0-0x71071].com.adobe.AdobePremierePro: Renderer: NVIDIA GeForce GTX 285 OpenGL Engine
5/30/12 2:40:26.601 PM [0x0-0x71071].com.adobe.AdobePremierePro: OpenGL Version: 2.1 NVIDIA-7.18.11
5/30/12 2:40:26.601 PM [0x0-0x71071].com.adobe.AdobePremierePro: GLSL Version: 1.20
5/30/12 2:40:26.601 PM [0x0-0x71071].com.adobe.AdobePremierePro: Monitors: 2
5/30/12 2:40:26.601 PM [0x0-0x71071].com.adobe.AdobePremierePro: Monitor 0 properties -
5/30/12 2:40:26.601 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Size: (0, 0, 2560, 1600)
5/30/12 2:40:26.601 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Max texture size: 8192
5/30/12 2:40:26.601 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Supports non-power of two: 1
5/30/12 2:40:26.613 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Shaders 444: 1
5/30/12 2:40:26.613 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Shaders 422: 1
5/30/12 2:40:26.613 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Shaders 420: 1
5/30/12 2:40:26.646 PM Adobe Premiere Pro CS6: invalid drawable
5/30/12 2:40:26.647 PM [0x0-0x71071].com.adobe.AdobePremierePro: Monitor 1 properties -
5/30/12 2:40:26.647 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Size: (2560, 0, 1360, 768)
5/30/12 2:40:26.647 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Max texture size: 8192
5/30/12 2:40:26.647 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Supports non-power of two: 1
5/30/12 2:40:26.652 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Shaders 444: 1
5/30/12 2:40:26.652 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Shaders 422: 1
5/30/12 2:40:26.652 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Shaders 420: 1
5/30/12 2:40:26.660 PM [0x0-0x71071].com.adobe.AdobePremierePro: --- GPU Computation Info ---
5/30/12 2:40:26.660 PM [0x0-0x71071].com.adobe.AdobePremierePro: Found 2 devices supporting GPU computation.
5/30/12 2:40:26.660 PM [0x0-0x71071].com.adobe.AdobePremierePro: CUDA Device 0 -
5/30/12 2:40:26.660 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Name: GeForce GTX 285
5/30/12 2:40:26.660 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Capability: 1.3
5/30/12 2:40:26.660 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Driver: 4.02
5/30/12 2:40:26.660 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Total Video Memory: 1023MB
5/30/12 2:40:26.661 PM [0x0-0x71071].com.adobe.AdobePremierePro: OpenCL Device 1 -
5/30/12 2:40:26.661 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Name: GeForce GTX 285
5/30/12 2:40:26.661 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Capability: 1.1
5/30/12 2:40:26.661 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Driver: 1
5/30/12 2:40:26.661 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Total Video Memory: 1024MB
5/30/12 2:40:26.662 PM [0x0-0x71071].com.adobe.AdobePremierePro:    Not chosen because it did not match the named list of cards
5/30/12 2:40:47.412 PM Adobe Premiere Pro CS6: GetDYLDEntryPointWithImage(/System/Library/Frameworks/AppKit.framework/Versions/Current/A ppKit,_NSCreateAppKitServicesMenu) failed.
5/30/12 2:40:48.188 PM Adobe Premiere Pro CS6: invalid drawable
5/30/12 2:40:48.198 PM Adobe Premiere Pro CS6: invalid drawable
5/30/12 2:40:48.205 PM Adobe Premiere Pro CS6: invalid drawable

CC wont let me re-download premiere pro CS6! HELP!!

Hello all,
So i previously had all of the CS6 Family installed on my computer. Something went wrong with Adobe Encore and it wouldnt open so i uninstalled Premiere Pro and Encore CS6.
After un-installing i restarted my computer and opened Creative Cloud.
When looking in the find new apps section to re-download Premiere Pro CS6 i could not find it. I filtered the search and selected previous versions but the only apps it says it has in previous versions in are Bridge, Edge Animate and Gaming SDK.
I checked in the my apps section to double check it was definitely un-installed. I can see Premiere Pro CC but CS6 is not showing up anywhere!
Ive tried looking for other links on the adobe website but it just gives me the option to buy a subscription (which i have already payed for) or download the trial.
Ive looked endlessly on forums for a solution but no joy so far.
I desperately need to get to the bottom of this as i need Adobe Encore for work.
PLEASE HELP ME!!!!

Hi,
Please uninstall your creative cloud desktop app and re-download it from the below link:-
Creative Cloud Help | Creative Cloud for desktop
and then follow the same steps that you have been following.
Hope that works for you.
Regards
Sarthak

Uninstalling Premiere Pro CS6

So, I don't remember exactly why, but I deleted the Premiere Pro CS6 folder and emptied my trash. I am on a Mac, and was wondering how do I go about uninstalling Premiere because the uninstallation program was in the CS6 folder. Also, creative cloud says it's up to date so there's no way I can reinstall it yet. Please help a brother out.

If you are on a MAC (one of the newer OS) it is kind of in a weird spot>>> go to your Applications folder > Utilities > Adobe Installers and you should find all the "uninstallers" there... just click on what you need, but if you are uninstalling Premiere Pro CS6 (and do NOT want to uninstall ENCORE) remember to DE-select it from the uninstall list!

Premiere Pro CS6 Warp Stabilizer not using GPU/CUDA why?

Similar Messages

Maybe you are looking for