Warp Stabilizer in Premiere CS6 is excellent

I shot some video from a helicopter over Iguassu Falls in South America recently. The clips were unuseable UNTIL
CS6 came along with Warp Stabilizer.
The link below shows how effextive the Stabilizer effect is.
http://youtu.be/mhNplx5tBQU

Thanks for you comments. Cam shake is a big devil for us amateurs. I have upgraded from a large Sony FX1 to a tiny tiny Panasonic TM700
and have major problems shooting hand held without shake, even though the cam has a good stablizer.
It is just that the cam is so tiny. So now I use a little "mealeable" tripod, 2 arms are my handle and the third arm dug into my tummy.
Really should use a full tripod, but how inconvenient when travelling.
Then I look at all the fellow travellers who are not into the hobby like I am. Some poor audience????
Now I have the CS6 Premiere Warp Stablizer. but but lots of changes to the Premiere workspace, especially the timeling area.
Do not know if I like the changes YET!! We shall see.
Thanks again

Similar Messages

Best way to warp stabilize between premiere cs6 and AE cs6

I have a sequence with many clips, some with different speed (warp stabilizer doesn't work with speed in premiere CS6) whats the best way to stabilize these videos that are in different speeds?
Another question, in CS 5.5 I used the warp stabilizer in 1080P clips on a 720p composition (with fit to composition) this way I warp stabilizer could zoom/crop the video without loosing quality. Now premiere CS6 has warp stabilizer but I can use a 720P sequence with a 1080p video, warp stabilizer won't accept it.So whats the best way to do this in premiere CS6? (to get 1080p video stabilized in 720p sequence) or I can just stabilize in 1080p and export the final video to 720p and I will have the same quality?
Thanks

You can make a new sequence from that 1080p file, stabilize it, nest it, then copy and paste it into your 720p project. This way you won't need to export it beforehand.
I notice this topic is old, but it may help someone.
Best,
Bogdan

Warp Stabilizer in Premiere Pro CS6

I was glad to see Warp Stablizer in PP so that it would not require AE. However, I found it to destabilize (no pun intended) Adobe Media Encoder such that the video would fail to render and I couldn't retry without restarting the computer. After about four or so reboots, I tried removing the Warp Stablizer effect from one of my nested sequences and suddenly the render succeeded.
FWIW, I don't know if it's related, but the sequence setting was 720p but the nested sequence that had the warp stabilization applied to only one clip therein was 1080p.
I do have GPU hardware acceleration enabled (not that Warp Stabilizer uses it that I know of).
Is this a known issue, and does anyone have any suggestions for a workaround other than going back to using AE a la CS5.5?
Also, on a side note does anyone know what process I need to kill after a failed render like this so that I don't have to keep rebooting? The dynamiclinkmanager process got rid of a hung Media Encoder on exit but didn't resolve the hung Media Encoder on restarting to render.
Jon

Have you tried rendering just that shot out to a file without the rest of the sequence? If you can do that then you can reimport that shot in to Premiere and use it 'ready-stabilized'.
We've exported several sequences that have lots of Warp Stabilizer clips and not seen the problem (yet!).

Warp stabiliser in Premiere CS6 crashes

Hi
Been playing with Premier CS6 since downloading yesterday.
I am getting regular crashes (windows tells me premiere has stopped working)
I add a clip onto he timeline, I add the warp stabiliser, analyise then play back - I go back to effects to change some warp settings, and the crash occurs.
Anyone else seeing this before I report to adobe
Thanks
Chris Anderson

Project file WITHOUT Warp Stabilizer on my clip was 3.5MB. WITH Warp Stabilizer it jumped to 7.6MB....
Now you're seeing it...
Here's where I realized something was amiss: I had a less than two minute sequence, all hand-held footage, that I wanted to stabilize. There were only about 6 or 7 clips in the sequence, and no other effects. I dropped Warp Stabilizer on the clips, and let it analyze... it took awhile, but I was OK with that. When it was done, despite Warp Stabilizer being a GPU-accelerated effect (after analysis), most of the clips were red bar. Hmm...
So, thinking maybe I just needed a restart, I saved my project. And I waited. And I waited some more. About a minute later, my project final stopped saving. Weird. So I tried to do something in the Timeline... and it was like running through a tar pit.
I killed off Pr, and went to check my project file... it was over 50MB... for a 7 clip, less than two minute sequence. That's a problem. When I finally got the project open again, I purged all the Warp Stabilizer instances, and saved a new copy of the project. This time, it was about 1.3MB. That is a HUGE difference, all attributed to Warp Stabilizer. Needless to say, I'm very reluctant to Warp Stabilizer do its damage to my project files, regardless of how good the output is.
So, let this be a cautionary tale. If you think you'll only need to stabilize a few seconds here or there, or you're totally cool with working in a completely different project to stabilize your footage (though look how well that worked for me), go for it. Fair warning...

Trouble with Warp Stabilizer in Premiere Pro

I have one simiple clip that I keep trying to stabilize and I can't see the effect. I've had this problem for months with several different projects with no luck. It goes through the motions of analyzing and stabilizing but won't show the resulting effect. It just freezes on various last graphics seen.
I've tried matching sequence settings, tried nesting the sequence into a separate sequence and can't seem to see the stabilized video. It just freezes on one frame, or a gray screen or holds whatever was the last video in the program frame. It even shows the desktop sometimes. When I turn off the effect the clip plays fine (unstabilized). I'm trying to stabilize a time lapse I shot on a windy day... so it was bouncing around a little. I've tried moving all of the scratch disks to another drive that was clear and free of space. I'm still getting nothing in playback.
Any help is appreciated.

That worked! You rock Bob Peru! Thanks so much for the reply!

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?

Warp Stabilizer CS6 scales down last frame

Hey,
Every time I add the Warp Stabilizer in Premiere Pro CS6, it auto-scales the footage, except for the last frame. It just changes to 100% again, so I'll just have to cut it off. Any others experiencing this issue, or any ways to solve it?
Thanks in advance.
Edit: turns out it's probably not the warp stabilizer, but the position. When I adjust the position, the same thing happens, and since the stabilizer changes the position, the position will probably be causing the issue. Keyframing is disabled.

This strikes me as a bug that hasn't been corrected.
Is there a way to see if it has even been reported? (I don't want to add a redundant bug report).
I'm having what I think is the same- or similar - problem in PPro CC.
Machine: Windows 7 Pro,
i7-3930K @ 3.20 GHz with 32 GB memory
nVidia GeForce GTX 670.
Both CC and CS 6 installed.
I have a single clip of video footage exactly 19 seconds (00;00;19;00) long in Track V1.
I have added the Warp Stabilizer effect to Track V1, let it analyze and stabilize, and when playing, the last frame is "chopped off" by a noticeable percentage.
When selecting the Effect Controls tab, the Opacity keyframe icon is "active", though still set at 100%.
I lowered the clip Opacity, moved the pointer a few seconds to the left via left-arrow, and re-played.
The last frame is still chopped off.
I returned the clip Opacity to 100%, moved the pointer a few seconds to the left, and re-played.
The frame is still chopped off.
This "solution" appears to have no effect for me.
I also need the Timecode effect for this same clip, and have noticed strange things with it.
Although my footage in Track V1 is exactly 19:00,
- AFTER I've added the Warp Stabilizer effect to Track V1, AND
- have added an Adjustment Layer to Track V2 in the sequence, AND
- have added the Timecode effect to the Adjustment layer in Track V2,
when I point to the last frame, the Timecode effect shows 18:29, not 19:00. After moving 1 frame to the left, i.e. hitting left-arrow once. the Timecode also shows 18:29. so the Timecode is showing the same numbers twice.
It seems that the Timecode effect is somehow "losing track" of what frame is being displayed.(Is it "counting from '1' instead of '0')?
Any help available in this?
I've even gone so far as to:
1) change, i.e. lower, the Opacity, save the project, then return the Opacity to 100%, then saved the project again; last frame still "chopped off".
2) once the opacity was lowered, I've also rendered the sequence, saved the project, then returned the Opacity to 100%, and re-rendered, but the problem remains.
3) I even "cleared" both the Warp Stabilizer effect from the footage clip, AND the clip from within the sequence, then added the clip back to the sequence WITHOUT the Warp Stabilzer effect, then pointed at the final frame, and that final frame is STILL chopped off.
For this project, I'm "sticking" with CC, because I'm working on it from both my home studio and another location which has only CC.
I haven't checked CS6 to see if the Warp Stabilizer and Timecode effects are working correctly, but both seem to have gone a little "haywire".
Is there some other way to fix the problem of the last frame being "chopped off"?

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.

Time Warp Effects in Premiere Pro CS6

Enabled Time Warp Effects in Premiere CS6: Ctrl+F12, TimeWarpFilterEnabled > true.
http://translate.google.ru/translate?sl=ru&tl=en&js=n&prev=_t&hl=ru&ie=UTF-8&eotf=1&u=http %3A%2F%2Fwww.efxi.ru%2Fmore%2Fpremiere_pro_cs6_time_warp.html

Works on my Android Nexus 7.
Anyway, here it is:
Turning Time Warp effect
Consider the example of the inclusion of qualitative change speed with the aid of the Time Warp (creating the effect of "stretching" the time or time warp) in the program Adobe Premiere Pro CS6. As we all know by default, this effect has been disabled in the version of Adobe Premiere Pro CS5, but you can turn it on. Press the keyboard shortcut: Ctrl + F12 and panel Console, switches to Debug Database View:
Paragraph TimeWarpFilterEnabled instead of trying to drive a false true. Restarting the program Adobe Premiere Pro CS6.

Warp Stabilizer Questions

Hello,
I have been using Warp Stabilizer in the CS6 release of Premiere Pro. I've noticed 2 things:
1) I have a sequence with a clip using Warp Stabilizer effect that has been rendered. If I add a clip directly after it and add a cross dissolve transition, it requires the entire first clip to be re-rendered. On complex stabilizations, this can take hours to days. Is there any way to have it only require a re-render of the impacted portion of the clip instead of the entire thing?
2) If I set my work area to a complex clip (synthesize edges, detailed analysis) with Warp Stabilizer and render the entire work area, it appears the efficiency goes down. I'm not sure how this is possible, but the estimates of completion time (and watching the elapsed time vs percentage compete) seems to indicate that it may exist. If I segment the work area to smaller regions in the clip and work my way through it, the total clock time to complete seems to be much faster. In one example, it seems to go from 80+ hours down to about 12 hours. In both cases it takes 100% of the CPU (8 cores) and a large portion of the ram (8-9+ GB). I believe the performance options are set correctly.
Any suggestions?
Regards,
Jonathan

Hi Jonathan,
I hope you get a good answer from the gurus at ADOBE on this one. I use ProDADS Mercalli V2+ Stablizer in Cs5.5.2 with 4 cores Xeon processor, i suggest you trial it as I have had no issues with the exception of cutting the clip after stablization, do it befor hand. I was thinking of upgrading to 6.1 ?
Good luck

Warp Stabilizer - PP or Ae?

I have always been wondering if all CS6 products share the same render engine.
To be more specific, will I obtain the same results if I use Warp Stabilizer in Premiere Pro and AE?
I am about to render a short r3d 4K media, and I would like to achieve the best possible results with Warp.
Therefore I have been trying to choose between AE or Premiere, asking myself if there will be any visible difference between the two outcomes.
Thanks

Warp stabilizing depends on the clip more than on the app used. It's a good tool for some shots but it's not a cure all and the more movement in the shot, the more warping is required, the more the shot will deteriorate.
As far as I know Warp Stabilizer in PPro is identical to WS in AE on the back end. I usually use AE's Render Cue to render to production codecs because I know the controls and it seems to work a little more efficiently for some tasks but PPro has the another pipeline to render and uses AME to build the render. AE also can use AME but I'm not sure what would give you the best results.
Stabilizing a shot is usually the least of the treatments I put on my work. Color grading is the most important visual part of any of my projects after composition and blocking. I think you're worrying too much about this. Both should work just fine.

Color & Stabilization between Premiere & AE

I have a feature film that's edited with many shots stabilized with the warp-stabilizer in Premiere.
I'm now doing color correction with Colorista and Looks, but those two work better in AE (AE allows keyframing and masking, Premiere doesn't). The frustrating thing is that every shot i import into AE starts all over with stabilization. It takes forever if i have to let AE re-stabilize everything and most annoyingly, even with the same Warp-Stab settings, sometimes crop/framing ends up a little different. That's especially frustrating as after finishing color correction, i'm back to premiere and realize that the shot framing has changed...
Please someone suggest a workaround. I spent all day and color corrected 2 minutes so far, this is taking ages!!!

CM is never simple and trust me, it is a lot easier today than it was 10 years ago. Regarding these issues, there is no simple answer here, I'm afraid. Premiere shows you a preview and you should take that very literally. It is in most cases not color exact which relates to chroma undersampling being used in many footage types and possible Gamma shifts plus however your monitor is mis-tweaked. Premiere however recognizes a monitor profile and can correct for it, if one exists and is assigned. Still, if it is just a generic factory profile and not a specific manual calibration profile this doesn't help you in any way. Also note that some Premiere effects and transitions do not operate in RGB to begin with, but use YCbCr/ YUV as their color space, as has been common for eons in video editing... So you see, a whole lot of complication. The simple truth here is, that the only true verification of video output still comes from an external monitor and scopes. AE on the other hand has a full color metrics engine. how to set that up is explained in a few documents on the help pages. it doesn't realyl solve your problem, since if you don't calibrate your monitor, the colors technically would still be off, but it might give you some more insights in what you need to do to improve your predicatbility...
Mylenium

Warp Stabilizer Doesn't Render

Hi, I've been having trouble lately using Warp Stabilizer in Premiere CC 7.1. I had used the effect many times successfully, then it suddenly stopped working. It analyzes the clips without problem, however it seems to get stuck on the "Stabilizing" phase. It just sits there. As I try to playback the clip in the timeline, it simply shows up as black video in the viewer. The space above the clip on the time line is yellow. Has anyone experienced anything similar? I've done a full uninstall and no luck. I don't have any other problems in Premiere Pro CC 7.1 right now.
Steve

I've had some problems with the effect completing, but usually only on clips what were especially long or demanding (like 4k with lots of movement). Additionally I have either encountered or read of others encountering these issues:
With OpenCL Rendering on, stabilized effect rendering does not complete
Large amount of memory is somtimes used when during Warp Stabilizer analysis phase (which is probably the root cause of the first problem I mentioned)
Long progress pause (minutes) during auto-save while applying Warp Stabilizer
Hang when saving project after extending warp-stabilized clip and re-analyzing
Those don't all necessarily occur reliably, but they have happened for some users. I'm not necessarily saying they;re causing or even related to what you're seeing, but perhaps they offer some clues. In any case, it doesn't sound like an issue that would be addressed by uninstall/install, but it could be addressed by doing things like clearing your media cache, checking your available memory, etc...
The workaround I would have suggested is to use AE if possible which it sounds like you did successfully already.

AE Warp Stabilizer (C5.5) Vs. Premiere Pro Warp Stabilizer(CS6)

Was wondering what folks experience was in CS6 with WS in Premiere Pro ?
Is it the same WS as in CS 5.5 in AE ? Has it been improved ?
My expereince with WS in CS5.5 (AE) has been very hit and miss. Some scenarios it works very well, others it tends to "warp" the footage so that it appears to be a disco scene on speed.
Any CS6 folks care to chime in ?
Thanks.

It seems that Premiere CS6 stabilizer is identical to AE CS5.5
Sometimes it helps to use Detailed Analysis, but in my case it did not work. I have a boat in the storm because stabilizer hooked to the moving object. I would like Adobe to add the ability to mark some key points, because full auto is not a professional style of work. However, even if I'll do a feature request it will not be implemented until CS12. I would be very surprised to see some improvements in CS6.5/CS7, but it is not Adobe style. This issue is known for 2 years from now and it is sad that they think about features quantity, but not feature quality (in terms of functions).
Sorry for being emotional, but 2 bugs for one project is too much for me for today.
However, I would like to thank them for adding Adjustment Layers. Saves time a lot.

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.

Warp Stabilizer in Premiere CS6 is excellent

Similar Messages

Maybe you are looking for