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.

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?

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

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.

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.

Premiere Pro Metadata & iXML/BEXT for Broadcast WAV files

Hi.
For feature film workflows, we depend greatly on the iXML and BEXT chunk in broadcast wave files.
As far as I can see, the XMP metadata "engine" (don't know of a better word) doesn't "see" the iXML and BEXT chunk in broadcast wave files.
Is there a particular workflow/workaround where the iXML and BEXT metadata show up in the "Metadata" tab in Premiere Pro.
Thanks!

mrmr450 wrote:
I see, thanks for the response.
I know there is a plug-in that allows FLAC files to be played in iTunes, so I'm wondering if there is some kind of 3rd party app that could solve this WAV metadata issue?
I have never heard of such a plug-in, and kind of doubt there is one, but perhaps a search would turn something up.
By the way, iTunes does not "lose" the tag data, it just fails to display or do anything with it. The tag data is still there if you use that same WAV file in another program.
Or am I just running into a brick wall here?
Maybe.
The more typical way to use WAV files is to embed the relevant information into the filename, which is always available. In iTunes, for any file which it thinks has no tags, the exact filename is displayed in the Name field.

Premiere Pro CC - Warp stabiliser issues

Hi,
Hopefully someone can help me out.
In Premiere CC whenever I apply warp stabaliser to a clip when It's finished stabalising it puts the clip in the top left corner. the clips moves around as if its being stabalised.
Any ideas?
Thanks.

Warp Stabilizer bug in new Premiere update

Warp Stabilizer Causing Jumping?

I am new to Premier Pro but I have messed with it some here and there. I have a video that is taken using a hand held camera and is at times a bit shaky. I attempted to add Warp Stabilizer (using default settings) but when I render the video it has a jumping or flicking motion. If I remove the warp stabilizer it doesn't do this.
Is this a side effect of the stabilization and how do I solve this issue?

Is this a side effect of the stabilization and how do I solve this issue?
It would be called 'Warp De-Stabiliser' if this was meant to happen!
You may need to do some more trial and error testing with your particular footage. Settings.
BTW there is a practical limit to how effective these stabilisers can be.

Premiere Pro cc 2014 crashes cause of plug ins

I have removed all my red giant plug ins but i still get this error message and then a crash??
[/ppro801/releases/2014.03/shared/adobe/MediaCore/MediaLayer/VideoFilterHost/Src/AEVideoFi lter.cpp-1225]
any ideas how to fix it
i also removed all the video effects from the entire sequence and still crashes

Hi,
What is the version of mac osx that you are using?
Please follow this step.
Click on GO- Go to folder- ~/library-application support and rename the adobe folder to old adobe
now go back to ~/library and then go to preferences and rename the adobe folder
go to documents and rename the adobe folder
By doing this you would loose your synced settings, customized keyboard shortcuts and customized effects.
Thank You
Arjun

Premiere Pro CC's Warp Stabilizer BUGS...see for yourself. (7.0.1 & 7.1)

I'd love to hear from Adobe Staff on this one. Hopefully they can focus on fixes over features for the next update, especially for one it's most touted effects.
Warp Stabilizer works great at stabilizing clips in Premiere Pro CC...but I'm beginning to learn that it's quite buggy. The two bugs below simply cripple the user experience when you use the effect a lot like we do. Here's a link to a sample project with just 2 clips (around 1 minute in length each) on two separate timelines with each clip stabilized using the Warp Stabilizer effect. It's only a sample/test project meant to show the issue which can be MUCH larger in a longer/bigger project. Relink to any longer media and you'll quickly see what happens when you have multiple warp stabilizers applied to a Premiere Pro CC project and how problematic it can be.
https://dl.dropboxusercontent.com/u/105331144/Warp_Stabilizer_SAMPLE_Project.prproj
See for yourself.
Two VERY Annoying BUGS and One Unfortunate Feature:
BUG #1: (It affects 7.0.1 and the new 7.1 Release/Update)
1) With GPU Acceleration Enabled and both sequences open, once the timeline render bar has turned yellow, hit save.
2) Now toggle to the 2nd sequence and you'll notice a delay/freeze as the render bar switches back to red and then yellow again.
3) Now toggle back to the other sequence and you have the same thing occur. Then, you can toggle back and forth with no delay...until...the project saves (or auto-saves) again...and then the delay/freeze will happen all over again.
4) Side Note: Even when you right-click on the sequence in the Project window, there's a delay. Right-click on a sequence with no Warp Stabilizers and the drop down list pops up immediately.
What's the Big Deal?: When you have tons more warp stabilizer effects applied to multiple sequences, not only does it take a while to save, but when it does, you are forced to wait while Premiere Pro freezes momentarily. This affects AUTO-SAVE too!!! The more warp stabilizers, the longer the wait. Our sequences have delayed up to 30-40 seconds depending on how much we've used warp stabilizer in each sequence. Imagine if you have Auto-Save set to every 30 minutes or less, well that means that every 30 minutes or less you'll be forced to stop while premiere freezes up for 30-40 seconds or so (depending on how much this effect is used). Other effects do NOT have this issue.
BUG #2: (It affects only the new October Release/Update of Premiere 7.1...this issue is NEW and does NOT occur in 7.0.1!!!)
1) Take the above project into Premiere Pro CC 7.1 (again, this does NOT occur in the previous 7.0.1 release) and hit FILE>EXPORT>Media.
2) You'll notice a delay while the EXPORT SETTINGS popup opens.
3) Toggle to different "FORMATS" in the export settings window and there's more delays every time the format is switched.
What's the Big Deal?: Again, this is a small sample project. When you have a much bigger project with lots more Warp Stabilizers applied to many more clips this "delay" can extend up to several minutes!!! Yes, on a recent project over an hour with MANY warp stabilizers applied to lots of clips, it took 7 minutes for the Export Settings window to pop up after hitting EXPORT>Media. And there was about a one minute delay now when switching formats. This occurs whether GPU Accleration is enabled or not. It ONLY occurs on Premiere Pro CC 7.1
UNFORTUNATE FEATURE #1:
We obviously use Warp Stabilizer A LOT. It's a great effect. The above bugs cripple the user experience. This last issue isn't a bug, but rather a default setting on Premiere Pro's warp stabilizer that should be changed. Within the settings of Warp Stabilizer there's a section called "Method". The default setting is "Subspace Warp". That sounds pretty cool. But in practice, and we have had lots of practice (eg. THOUSANDS of clips stabilized in just the last few months alone (no exaggeration)), we've found that switching the default method to "Position, Scale, Rotation" is a MUCH more effective way to stabilize a clip. Most of the time it cuts down on that "wobble" that you might see in complex moving clips...but more importantly, 9 out of 10 times it crops the video either the same or less than when you use the default method. By "crops less" I mean that the "Auto-Scale %" is less. Of those 9 times, I'd guess 7 or 8 of them would crop in on the video less while the other 1 or 2 times there would be no change to the Auto-Scale %. Less scaling = better.
What's the Big Deal?: Well, as cool as Subspace Warp sounds, our numbers don't lie. Again, we use this effect on HUNDREDS of clips every week. When you have to go into hundreds and hundreds of clips every week and keep switching the setting so the effect will work better, it gets old real fast. We end up wasting so much time doing this but it's worth it because the results are undeniable. Why not create a CUSTOM PRESET???! Well, that'd be nice if it worked...but it doesn't. The problem with a custom preset like that is that when you drop it on a clip, it doesn't activate/analyze the clip automatically so you have to manually go into the settings and hit analyze which negates any time saved. It's be great if the default "method" was simply changed to Position, Scale, and Rotation. Or at the very least, it'd be great if one could create a custom preset that would automatically activate/analyze the clip it's dropped on (just like the original effect does).
(BONUS FEATURE: It'd also be nice to have the ability to set a "max scaling %" too so you never crop in more than a preselected amount...but first things first...fixes over features.)
NOTE: I'm on a 2011 suped up iMac running OSX 10.8.5

[r]Evolution wrote:
Would it help to Render these Warp Stabaliized clips instead of leaving them in the sequence w/ the Effect applied?
Any way to "Batch" Warp Stabalize your media before editing so the effect is not needed during the edit?
Sounds like you guys could benefit from having your shooters use a "Stabalizer".
Thanks for the rendering tip rEvolution. Rendering the clips does help with BUG#1, however, I'm not sure if it would truly save us any time because of the constant need to render and rerender tons of very short clips with this effect as we make adjustments to the edit. Warp Stabilizer is GPU Accelerated so playback is really smooth which is great but why does saving a project have any effect on this and cause it to freeze up? And then it works great...until the next time the project is saved. Using any other effect, there is no issue (that I've found) when a project is saved or auto-saved.
Rendering unfortunately has no effect on BUG#2 in Premiere 7.1 (again, this bug/issue did not occur in Premiere 7.0.1)
Regarding "batch" stabilizing...I'm not entirely sure what you mean. We do stabilize dozens of clips at a time before editing because it's imperative for us to know which clips (the sections we've pulled) will stabilize effectively. And then once the longer edit is complete we end up pulling all the best shots from that long sequence and copy/paste it to another sequence to make a 2nd shorter edit.
To say we've gone back and forth about the use of stabilizers would be an understatement. The fact is that we've spent almost 4 years creating a unique way to shoot based almost entirely around the effectiveness of warp stabilizer. It's taken years of trial and error but our style of shooting effectively allows us to mimick and thus replace the need for stabilizers, sliders and cranes. The extra freedom allows us to get MUCH more varied coverage of live events. It's different, I know, but it's fun and rewarding having a unique style. Granted the extra work is passed on to the editing side, but it's worth it IMO especially if these issues were addressed/fixed.
Regarding the "unfortunate feature" I mentioned, I would be satisfied knowing the default method works great for others if one were simply able to apply a custom preset of the clip with the adjusted method and it activated automatically and began analyzing the clip without the need to manually go into settings and hit analyze. That would be nice.
Thanks again for your input.

Improvements concerning Warp Stabilization Premiere pro CC?

Are there Premiere Pro CC Warp Stabilization improvements regarding speed (faster stabilization) and file size (project)?
Thanks for the appreciated feedback
Rene

Thanks Steve...for what it's worth, I'd still like to say that a more effective "method" (in the warp stabilizer settings panel) to have set as DEFAULT would be "Position, Scale, Rotation" instead of "Subspace Warp". The latter may sound cooler, but 9 out of 10 times the former method does a better job at BOTH creating less wobble and cropping the video either the same or less than subspace warp. I stabilize 100-200 shots per project/per week so I know this feature inside and out. I'm excited for the new VFX and thank you for helping with the project bloating, but I still believe making "Position, Scale, Rotation" the default method would be wise. Just a thought.

What is FCPX 10.1 equivalent of Premiere Pro Warp Stabilizer ?

Hi there,
I saw some youtube tutorial where Adobe's Premiere Pro inbuilt effects called Warp Stabilzer is quite good in stabilizing some handheld videos.
I have some video clips taken handheld since I did not bring along the tripod. It looks shaky, how do I correct/minimise the shakiness in PCPX 10.1 ?
Does FCPX 10.1 has equivalent of Premiere Pro's Warp Stabiliser ?
Thanks

FCP X has its own stabiliser. See this tutorial:-
http://www.larryjordan.biz/fcpx-image-stabilization/

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

When is Adobe going to fix Warp Stabilizer?

I asked this question back in February but I only got one reply. Warp Stabilizer may provide decent footage stabilization, but it is incredibly poorly coded, especially when compared to Mercalli Pro, or the Edius 7 Pro stabilizer, which I believe is a lite version of Mercalli Pro. One would think that since it was introduced at least 3 years ago (I can't remember if the first version it came with was CS6 or a previous one), Adobe would have troubleshot it and fixed its terrible performance. I mean, we're not talking about a stabilizer that is half as slow as Mercalli Pro. Warp Stabilizer is 14.5 times slower than Mercalli Pro. These are times for one minute of footage, the same footage in both NLEs:
Edius Pro 7 Stabilizer: 29 seconds
Premiere Pro Warp Stabilizer normal analysis and solving: 12 minutes 16 seconds
Warp Stabilizer detailed analysis and solving: 14 minutes 28 seconds
This is on a six core i7 3930k CPU with 32 GB of RAM and two GTX770 cards with 4 GB each (even though WP doesn't use the graphics card for analyzing and solving, only for playback)
And the terrible analyzing and solving times are not the only problem. If you decide to run WP on a long clip, say 13 minutes long, even after the two hours that it takes to analyze and solve, the next time you open that project, be prepared to not be able to use Premiere for who knows how long. I say who knows because about 30 minutes ago I opened Premiere, loaded the project, and it froze completely when it was loading the footage files. For the last half hour, Premiere has been stuck with the spinning circle mouse pointer. Task Manager shows that Premiere has zero CPU usage and about 3 GB of RAM usage. So it's doing nothing at all, just frozen because Warp Stabilizer is one of the worst coded pieces of software not only from Adobe, but from any company.
Putting aside the terrible analyzing and solving times, and the eternal wait next time you load the project, there's the fact that as soon as you use WP on a few clips, or on one long clip, saving times are unbearably slow.
So I'm just asking, what makes a company with the huge resources Adobe has, not only launch a plugin that performs so terrible, but also doing nothing to fix it for three years or more?

In this case, yes, I have a 13 minute long take that I have to stabilize. However, the original footage clip is a few minutes longer, so I'm not trying to stabilize the full clip, only most of it.
I could spend a lot of money on the plugin, but I usually don't have a lot of footage that needs stabilization. Besides, I already have the plugin that came bundled with Edius 6, so I just use that when I need to. However, since Adobe advertises Warp Stabilizer as part of Premiere, and the plugin is absolutely dreadful, it seems to me that it's false advertising. I would much rather use WP in my Premiere project rather than having to load the footage in Edius and then export to a gigantic file to avoid losing picture quality.
As for drive space, I have two 3 TB very fast hard drives that have plenty of empty space. Besides, Mercalli Pro in Edius analyses and solves this long clip in about ten minutes, as opposed to the over two hours WP needs for the same clip. In fact, in Premiere I only applied WP to part of the clip, when in Edius I loaded the original AVCHD clip so I can just do a replace in Premiere and have the same ins and outs.

Premiere Pro CS6 - A low level exception has occurred in ImporterMPEG

Hi Adobe Community,
I'm having a bit of an issue with the ImporterMPEG.prm plugin for Premiere Pro CS6 that's causing playback and exporting issues.
Computer Specs: Win7 PC, NVIDIA GeForce 6150SE nForce 430 graphics card
Description: After playing back video for a while, Premiere will eventually start repeatedly reporting "A low level exception has occurred in ImporterMPEG". The preview player will be completely frozen, and I'll be unable to export. The exporting will fail with a generic "Unexpected error" message.
This issue has only started a week ago. Until now, I've been able to use Premiere Pro CS6 with no issues. If possible, I'd like to avoid upgrading to CC 2014, because the CS6 version was working fine before.
So far, I've tried a few things:
• Deactivating and reactivating (which, by the way, apparently doesn't help subscription users like me, per my recent chat with Adobe support on this issue)
• Uninstall and reinstall (I didn't know about the CC Cleaner tool at the time, so I haven't tried a clean uninstall yet)
• Change the Preview File Format in Sequence Settings (from I-Frame Only MPEG which had worked since I installed the software over a year ago to Microsoft AVI)
• Crying silently to myself (this did not help, the computer is cold and cruel)
• Clearing out the media cache (which I'd never done before and let it get up to ~75GB without me noticing)
• Moving the plugin from its location in Program Files, hoping that maybe Premiere Pro would notice it was missing and to try to find a new fresh one (it didn't work)
So far, only the Preview File Format change seemed to bring relief, but the bad behavior came back after about a week.
I'm thinking maybe the ImporterMPEG.prm plugin got corrupted somehow? The one notable thing I can remember with the computer in the last few weeks was a power event that shut down my computer unexpectedly. I think I had Premiere Pro open at the time.
If it's relevant, I mostly work with .AVI, .MP4, and .TS files in my projects, all varying resolutions and FPS. I'm usually working with about 1GB of files in a project, very rarely more than 2GB.
Has anyone else had this issue? Or, even better, has anyone else resolved this issue?
Thanks!

But really, the real solution for me was to not update Premiere Pro CS6 after a reinstall. The most recent updates just do not like my computer, I guess.
Figured I should post this solution here in case anyone in the future has this problem. (relevant: xkcd: Wisdom of the Ancients)
-Sam

Premiere Pro CC - Warp Stabilizer causing "Heat Waves"

Similar Messages

Maybe you are looking for