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.

Similar Messages

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

Stabilize small jump within a long clip?

I have a 5-minute clip that was shot on a tripod. 99% of the footage is stable, but the camera "jumped" once in the middle of the clip. If I apply Warp Stabilizer to the entire clip, it gets confused because of the moving subject. If I chop the clip up to isolate the jump, then it is correctly stabilized, however there is a jump cut from the shot at 100% scale to the slightly scaled clip caused by Warp Stabilizer. Thus far, the best solution I have found is to keyframe the clip leading up to the stabilized clip from 100% scale to the new scale of the stabilized section, and do the same for anchor point, then repeat the process at the end of the stabilized clip. This process can be tedious and the end result still isn't perfect. Is there a way of telling Warp Stabilizer to only work on one section of the clip?
I know this is sort of a complex question, so please let me know if I can clarify anything. Thank you in advance for your help!

As Ann says...
What would make it easier is to change the opacity on the leading clip and overlay it on the stabilized clip by one frame. If you have split the clips in an optimal place, the scaling should be fairly simple since the movement is not as quick. So make sure to split at a point where there is a slight pause in the action, just before the "jump" if at all possible. Then just line of the scale as required.
After the leading clip is scaled properly, put it back on the same track as the stabilized clip, back up to a few seconds before the split and put in a keyframe back to 100%. Reverse this process for the trailing clip.
It is not difficult, just a bit tedious.
It might be easier to do this on a new sequence, then use that new sequence like a clip in the main sequence.

AE project crashes on startup - due to Warp Stabilizer and Highlight/Shadow

I've got a head scratcher here...
Firstly, I have been working on this project file for several days with no problems. Everything was running smoothly... working, tweaking, rendering... all successful.
A couple days after doing a final render, I went to re-open the project and got these two errors, followed by AE crashing:
To the best of my knowledge, I changed nothing on my system.
I've tried removing my 3rd parth plugins (Video Copilot Optical Flares, Element, etc...) but to no avail. The program still crashes when opening this file.
I've since installed the updates to AE CS 6, but still no luck.
Removing Warp Stabilizer and Shadow/Highlight allow me to open this project file (obviously telling me that its missing both).
I've tested out both plug-ins in a different file, and I'm able to open those no problem.
I'm running this on a Mac Book Pro running OSX 10.6.8
Model Name:
MacBook Pro
Model Identifier:
MacBookPro8,2
Processor Name:
Intel Core i7
Processor Speed:
2.2 GHz
Number of Processors:
1
Total Number of Cores:
4
L2 Cache (per Core):
256 KB
L3 Cache:
6 MB
Memory:
8 GB
AMD Radeon HD 6750M:
Chipset Model:
AMD Radeon HD 6750M
Type:
GPU
Bus:
PCIe
PCIe Lane Width:
x8
VRAM (Total):
1024 MB
Vendor:
ATI (0x1002)
Device ID:
0x6741
Revision ID:
0x0000
ROM Revision:
113-C0170L-573
gMux Version:
1.9.23
EFI Driver Version:
01.00.573
Any thoughts???

We've isolated the bug that is causing this behavior. It seems to only affect instances of the Shadow/Highlight effect on an adjustment layer over layer(s) with the Warp Stabilizer.
There are a couple of workarounds:
- One is to remove the Shadow/Highlight plug-in from the plug-ins folder and then open the project (and then fix the project to not have this effect on an adjustment layer over a Warp Stabilizer instance).
- Another is to precompose the layer(s) with the Warp Stabilizer effect.
We're working on a fix for this.

Warp Stabilizer through After Effects Dynamic Link Locks up in CS6

Hey Gang,
I've been using Warp Stabilizer through dynamic link in CS5.5 without issues. However, when I go through dynamic link into AE, then apply Warp Stabilizer, AE locks up?
I can apply any other effects through this path in AE without issue, but when I try to apply WS, I get the "Analyze", but AE stops cold there.
I've tried:
-Opening new project in PP with basic 5 second clip. Then going through dynamic link into AE, and applying warp stabilizer first thing. AE locks up there with the simplest flow.
-I have the latest downloads of the entire production CS6 suite.
-If I apply warp stabilizer directly in Premiere CS6 (which I did not know previously I could do), it works fine! (Just noticed Warp Stabilizer is present in PP CS6, but not in CS5.5).
-If I try to import the Premiere project from AE, AE locks up doing that?
It appears there are multiple issues here:
1. I can't apply Warp Stabilizer in After Effects, and doing so crashes AE.
2. I can't import a Premiere project into After Effects, and doing so crashes AE too?
I'm assuming I'm going to need to download AE again?
Thank you for any help and suggestions you may have!
Derek...
Message was edited by: Derek Emmett

Hello Mylenium,
thank you for your input. Naturally I would expect if my work flow in CS5.5 works great, I would not have to make any changes in CS6 to accomplish the same task. With that said, I made it as simple as possible for CS6 AE to handle the Warp Stabilizer effect, and it crashed? If I went directly back to CS5.5, no problems at all in AE (same source footage, but of course different projects). When I first tried CS6 AE it appeared to work fine, even when doing Warp effects. So when I ran into the issue I saw above, I started thinking it was possible the update I did to AE may have caused some other issue. By the way, the projects I open in both CS5.5 vs. CS6 were independent, meaning, I did not convert a CS5.5 job to CS6, etc... (See notes below).
My setup is standard:
i7 960
16G mem
Nvidia Quadro 4k
Footage is Canon 5D Mkii 1080p
All drivers up to date.
-I think going back and forth between CS5.5 and CS6 may have caused some issues? When I rebooted my system, CS6 AE seems to work fine when applying Warp Stabilizer effects again.
-What I did find more interesting and effective, was that CS6 Premiere has Warp Stabilizer right in its own effects now! Works great in the premiere flow and plays back far better then going through the Dynamic Link with After Effects! When playing Dynamic link effects back in Premiere, I'm sure everyone sees performance issues in the playback. However, in at least with applying Warp Stabilizer directly in Premiere, the playback performance is much better.
Thank you
Derek...

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.

How do I keep Warp Stabilizer and aeselflink from filling my swap space?

Hello,
I'm running the lastest version of AE on OS X, when I try and run warp stabilizer on a composition, aeselflink grows the virtual memory it uses (> 50GB) until it fills my swap space and causes my machine to hang, because the hard drive is full.
Running AE's Edit->Purge options has no effect on the amount of virtual memory used. I have to quit AE to get aeselflink to quit and free the memory used. How can I limit the virtual memory used by aeselflink to something reasonable?

I'm not aware of a way to control this in any more detail, but this stuff obeys the settings you make in the Render Multiple Frames Simultanuously prefs if used. Otherwise it will use factory defaults which should never use more than 4GB. Anyway, the behavior you see is highly irregular no matter what. Sounds like a memory leak, so maybe you can provide more info, including which AE version, what footages etc.
Mylenium

Warp Stabilizer crashes in After Effects CC (OS X)

Every time I try to use Warp Stabilizer, I get the following crash.
1. I select a track, open up the Warp Stabilizer VFX panel, and click "Analyze".
2. The blue "Analyzing in Background" banner appears. At this point, After Effects locks up and becomes unresponsive.
3. Looking in Console I see "com.adobe.Adobe Analysis Server.application[285]) Job appears to have crashed: Abort trap: 6". A crash report is saved. Here is a report: http://pastebin.com/RTnjNW28. Pertinent extract:
Application Specific Information:
abort() called
terminating with uncaught exception of type dvacore::filesupport::dir_create_exception: $$$/dvacore/filesupport/DirCreate=The directory '@0' could not be created. Please check the parent directory protection or permission rights.
4. Within After Effects itself, after several minutes, the error "Could not launch the Adobe Analysis Server. (515) (25 ::101)" appears. After Effects then becomes responsive again.
This is on a fresh install of After Effects CC, installed via the Creative Cloud app. Version 12.2.0.52.
I have tried this on 2 different Macs: a 2013 MacBook Pro and a 2011 Mac Mini. Both with latest OS X 10.9.1. I also tried on the preview release of OS X 10.9.2. I have tried with several different source videos, of different formats.
I have no virus scanner, or other such apps installed. I have tried disabling all running background apps. I tried turning off FileVault. Rebooted several times. Same result every time.
Is there any fix? Any help greatly appreciated.

It seems that this issue is caused by some folders being created with the wrong permissions set. This morning, a new version of the Creative Cloud desktop application was released that fixes this issue.
See this article for more information:
http://blogs.adobe.com/kevinmonahan/2014/02/12/prevent-crash-on-export-with-premiere-pro-c c-adobe-media-encoder-cc/
That article doesn't mention After Effects specifically, but I'm reasonably sure that the same fix will help here.
Let us know either way.

Warp Stabilizer bug in new Premiere update

Made the mistake of updating mid-project. Now Premiere warp stabilizer isn't working and causes rendered frames to flicker to black. Tried the stabilizer on new projects with same results. Contacted tech support and they said "this is being rushed to get fixed". Anyone else having this problem?

Mark -- No need to test for me, that scenario perfectly describes my original problem.
And from the System Information report:
Intel Iris Pro:
Chipset Model:    Intel Iris Pro
Type:    GPU
Bus:    Built-In
VRAM (Dynamic, Max):    1536 MB
Vendor:    Intel (0x8086)
Device ID:    0x0d26
Revision ID:    0x0008
Displays:
Color LCD:
Display Type:    Retina LCD
Resolution:    2880 x 1800
Retina:    Yes
Pixel Depth:    32-Bit Color (ARGB8888)
Main Display:    Yes
Mirror:    Off
Online:    Yes
Built-In:    Yes
DELL P1913:
Resolution:    900 x 1440 @ 60 Hz
Pixel Depth:    32-Bit Color (ARGB8888)
Display Serial Number:    75VDV3211D6U
Mirror:    Off
Online:    Yes
Rotation:    90

Warp Stabilizer progress status

Hi,
I need to get an alert when the stabilization process is complete.
So i try this :
i am reading the first three text labels on the effects panel :
During analysis:
the first label is empty
the second label display alternatively
Time remaining : 41 seconds
or
64 % (frame 70 of 188)
the second label display :
Stabilization
During stabilization:
the first label is empty
the second label display
188 frames @ 0:00:21:18
and the third label display alternatively
Stabilization ..
(the number of dots and spaces varies)
When stabilization is complete :
the first label is empty
the second label display
188 frames @ 0:00:21:18
and the third label display
Stabilization
So i can read the label and deduce the process state.
// in a scheduled task
function checkStabProgress()
var effect = currentComp.layer(1).Effects.property(1);
var label = effect.property(1).name;
var label2 = effect.property(2).name;
var label3 = effect.property(3).name;
if(label == "" && label2 != "" && label3 == "Stabilization"){
alert("Stab Complete");
It's seems to be a crappy way and sometimes an alert prompt before stabilization complete.
Is there a better way to do what i do ?
like event listener ? or something more clean and formal ?
thanks ++

Although it's easier (more convenient) to accomplish the mission in After Effects, you can do it in PrPro as well:
1. Nest your shaky footage.
2. Within the newly created nested sequence apply Garbage Matte onto the footage to separate the woman on the foreground. E.g. draw Eight-Point Garbage Matte around the woman.
3. Create a Color Matte, pick e.g. R:7 G:7 B:9 to more or less match its colour to your footage background and drop this Color Matte above your footage with Garbage Matte.
4. Copy Garbage Matte from the footage and paste onto the Color Matte, delete or disable Garbage Matte on the footage. Optionally apply Fast Blur effect onto the Color Matte and dabble with Blurriness value so as to soften (feather) Matte's edges, adjusting Garbage Matte points if necessary.
5. Jump back to your master sequence and apply Warp Stabilizer onto the nested sequence, formerly your shaky footage. Set Stabilization to No Motion.
6. When done, switch to your nested sequence, disable the Color Matte eyeball, switch back to the master sequence, enjoy.

When trying to use warp stablizer in premiere warp stabilizer required clip dimensions

this is the full error.
warp stabilizer required clip dimensions to match sequence
i dont know how to make it know the dimensions
i know in after effects i would jjust drag it and cick analize

Thanks. I am not sure that the sequence did not match the footage, as they are all the same, and match what the file into says as compared to what the camera they were shot with shows, but I seem to have apparently not properly 'imported' the file into my project in the first place. I watched a video and saw the 'scrub' function working on clips that were drug into the project, so I thought you could just drag clips into the project pane, and that is how I got clips into the project. I can scrub them, place them in a sequence, and even make a DVD or BRay disc. However even though this technique seemed to work, as noted I could not apply the warp stabilizer. So, I played around a bit more since my posting, and found a particular discussion and essentially tried the idea you suggest, to 'import a clip into a new sequence'. Sure enough, when the clip was imported, it opened in its own new sequence, and when I tried Warp stabilizer, it actually started working! Finished up ok. The clip was nicely stabilized, very nice. So essentially it seems that the act of officially importing the clip caused the proper sequence settings have been accepted, as opposed to simply being readable by the user when looking at the clip sequence data (via the pull down menu).
So now I wanted to put that stabilized sequence into my project. I could not 'copy and paste' it as it was from the sequence it which I had imported it, but I saw a new 'stabilized version of the file' in the project files area that did not have any direct video associated with it. And this was the repaired video! So, I place it in my project, it shows up with a green tint, and plays fine. However, I cannot get it to 'render' when I click on the red 'line' above and hit the return key. This same action worked when the original file was warp stabilized, and I could get the red line to turn green after the render. However, I can not get it to render in my project. What am I missing? And thanks in advance for the help. I am getting there.....

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

Projects Not Opening with Multicam and Warp Stabilizer - "[..\..\src\TickTime.cpp-207]"

Editing a sequence with multiple nested multicam clips and warp stabilizer, if I close Premiere and reopen it, it says "Premiere Pro has encountered an error. [..\..\src\TickTime.cpp-207]" repeatedly until killed by Task Manager. I have restarted the computer, cleared the media cache and deleted preferences. I can import the sequence into another project and continue editing but if I close PPro I have to create another project and import the sequence again or I get the same error. Help!

Hi Kevin!
That is great news. I had a feeling the issue would be gone in the Next PPro. The issue can be easily duplicated by following these steps in CS6:
1) User warp stabilizer on several clips (like maybe 6 or more or so).
2) Take two clips and nest them and sync them for multicam on the same timeline as the stabilized clips (NOTE: these two clips don't actually have to be sync'd...just grab any two clips, stack them on top of each other, highlight them both and right-click and choose "nest", then right-click again and "enable" multicam.
3) Save project. Close project. Re-open project and you'll get the error.
If you do that in the NEXT version, does the error come up? Also, just while I have you...if you go into the settings of Warp Stabilizer, what is the default "method"? Is it still defaulted to "Subspace Warp" or did they smarten up and realize the option "Position, Scale, Rotation" is actually MUCH more effeciet causing less wobble and less cropping of the video 90% of the time? Just curious.
Coltom Media Productions,
I feel your pain. What also stinks is that the error pops up again when you export (or I should say when you queue) up the project into AME. I originally thought the number of continues equalled the number of warps applied but that's not always the case. Although, the more warp stabilizers applied the more times you'll have to hit continue. It often goes in numbers divisible by four. Why do I know all this crazy, useless info...hours and hours of trying to "solve" the issue. Every project I do, every single week has more than 100 clips that are stabilized and multiple multicam sequences so I often have to hit "continue" on the error 300-400 times or more on EVERY project. Can't wait til the next version!
To see more on this issue you can see the original post on it here (note that the staff has recently (and graciously) led the charge to help isolate and resolve the issue):
http://forums.adobe.com/thread/956692?start=40&tstart=0
And then also, it definitely made my "Top 15 list" here:
http://forums.adobe.com/thread/1179004
Good luck!!!...oh, one more thing...the project will open...you just have to keep hitting continue. Sucks, but again, hopefully it'll be resolved soon.

What is Warp Stabilization File Extension

When I archived my project to an external hard drive the warp stablization was no longer applied to the clips, so it appears I will be to restablize all clips. Where are the data for warp stabilization files stored, what is their extension, and can they be archived with a project?

We use this effect all the time and pass the project file to various computers who each have their own separate copy of the media and there are no issues or need to re-analyze the clips. It was my understanding that it's built into the project file like Jim said because when we apply the effect our project size jumps from under 1mb to sometimes 70mb or more...granted we use a couple hundred of these effects per project which brings into play all new issues (http://forums.adobe.com/thread/1278013). But yeah, I've never had to restabilize clips when opening the project on a different computer with a different copy of the media, etc.

Warp Stabilizer Causing Jumping?

Similar Messages

Maybe you are looking for