Warp Stabilizer dropping

I have tried dropping the Warp Stabilizer on a number of different types of media files, 7D, uncompressed 1080 25p, 23,97, interlaced, progressive, mp4, Red r3d, DNxHD, Animation... you name it. Sometimes I get an error "Unable to aquire rendered frame" which pops out three times after eachother before dropping the analyze part. Other times, it just stops without any message at all, going back to "press analyze to start analyzing".
It's frustrating because I need to babysit a lot of rendering and I often have to reanalyze after it drops out right in the end. I have set up the RAM accordingly to each thread and everything and other functions within AE seems to work fine, just not the warp stabilizer.
I have searched for answers and just found another thread in here that speaks of the "Unable to aquire rendered frame" message, but no answers in there.
So what is this? Maybe it needs to be patched?

My system specs are:
Intel i7 3,7 Ghz
16 Gb RAM
Geforce GTX580 3Gb
Primary disk: Intel SSD
Win 7 Pro
AE is up to date, footage as mentioned is from a lot of sources, so source files doesn't matter.
It's stored locally and are streamed through a 6Gb/s eSata.
It dops out randomly whenever it analyzes. If I babysit it and press "analyze" every time it drops out of analyzing, then after a while I seem to get it analyzed, but I can't sit infront of it if I have a lot of clips going through stabilization.

Similar Messages

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.

How to apply warp stabilization to the same clip used twice in the same timeline

If I use the same source clip in a timeline (say 3 or 4 different sections of the clip by dropping the same clip on the timeline and just trimming it differently) and want to stabilize them all, how do I do that? The first instance of the clip lets me use warp stabilization, but then when I try to apply it to later instances of the same clip in the timeline, it says I can't do that. How do I apply the stabilization to later instances of the same clip in the timeline?
Thanks

After trimming the clip just apply the warp stabiliser to it without copying and pasting. You can't copy and paste the warp stabiliser because it needs to analyse the pixels of each clip everytime its applied.

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.

Applying Warp Stabilizer transitions?

I have some experience with warp stabilizer in After Effects.
After having watched the Warp Stabilizer tutorials for After Effects (thank you to community for links)
After Effects Help | Tracking and stabilizing motion
REMOVING TIMELAPSE CAMERA SHAKE: ADOBE PREMIERE TUTORIAL - YouTube
and having played with them in Premier Pro, I find it does a great job of stabilizing the time lapse footage. However, I still notice a slight jerk during the transition from one daily video to the next because each video/day is stabilized independently of the next. The video does not move much from one day to the next so this would only be a few pixels, but it is still noticeable. Is there a way to create a "stabilizing transition" from one day to the next so that in the last 2-3 seconds of the video, the warp stabilizer shifts the image to align the last frame of day one with the first frame of day two? Can I have to trick Premier Pro into doing this by placing the first picture of the second day into the folder of pictures from the first day or is this more painful than necessary? Is there a way to drag and drop a Warp Stabilizer effect across multiple videos in the timeline at once so that the cropping and rotating is done while considering all of the video files? I realize this could result in significantly more cropping than if each video was stabilized individually..
I would prefer to not have to place all of the images in one folder as I would have to rename them for the Import Sequence function to work properly and because there are about 5 months worth of daily folders.
Schwizer

There is no KBSC for adding an effect to a clip.
If you want to add the warp stabilizer (or any effect) to all clips in the timeline: select all the clips and double click on the effect.

How to make the warp stabilizer analyze interlaced (upper + lower field) instead of progressive?

I am having a little problem since I am new to Premiere pro.
Until now I always used the warp stabilizer in After Effects for single shots in need of that. But this time, I was handed a project that requires a whole lot of stabilization. My plan is to drop the whole timeline (FCP 7/ProRes422 HQ Interlaced) via XML into Premiere Pro and apply the effect there to multiple clips.
PROBLEM: When I do this, the warp stabilizer always (no matter how I interpret the footage or set the sequence) analyzes the footage progressively. At least that is what the effect preferences tab says during analysis.
In After Effects I always see which field is beeing analyzed (it is indicated by a L and an U behind the frame count). Not so in Premiere Pro. Here it always seems to analyze full frames.
I made a test and compared the results from After Effects and Premiere Pro: The file generated in Premiere Pro is much softer then the one out of After Effects even though I export both with the same output settings.
Any help would be greatly appreciated !
Regards, franse

I just verified and the Description for Products (and possibly other objects too) are stored in table COMM_PRSHTEXT.
The relevant Data element is COMT_PRSHTEXTX which has the domain PRSHTEXT40.
If you look at this domain you have a parameter "lowercase" which is available as a flag option.
The explanation about this Flag is the following:
Lowercase letters allowed/not allowed
If this flag is set, upper case and lower case are distinguished when you enter values with screen masks.
Otherwise all the letters entered will be converted to upper case when you enter values with a screen mask.
This mechansim is in effect for all the fields referring to this domain.
Solution would be to verify if for this data-element the same Domain is used.
If yes, you can flag this option in the domain.
this should solve your problem.
kind regards
davy pelssers
please reward if helpful.

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.

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.

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?

Black Magic and Warp Stabilizer

I am working with 6.0, Footage is P2, Sequence is Black Magic Progressive @ 29.97 / 1920x1080. Black Magic board is Decklink 3d Extreme.
Black Magic Drop Down in "New Sequence Setting Box" shows no 1280x1080 option which is P2. All Black Magic options are 1920x1080, progressive or interlaced.
When I drop the Warp Stabilizer onto a clip (P2) I get the message:
"Warp Stabilizer requires clip dimensions to match sequence"
How do I get around this, using the Black Magic Sequence and P2 footage?

With CS6, you shouldn't. Any sequence should output via the hardware just fine. Though I've never used that hardware, so I can't comment specifically on how to get that going. See if this helps.
http://tv.adobe.com/watch/cs6-creative-cloud-feature-tour-for-video/get-better-playback-pe rformance-with-mercury-transmit/

Warp Stabilizer error: Unable to acquire rendered frame

Hi,
I am trying to apply Warp Stabilizer to a clip. Analyze process starts but then halts after 15-20 frames and a pop-up appears "Unable to acquire rendered frame".
I have previously used Warp without any hitches.
Any ideas?
Thanks,
Richard

I too get this, sometimes not and the analyze just drops without a word, but most of the time I get the error. I tried on material such as: Red r3d, uncompressed fullHD/SD, mp4, canon 7D etc. pretty much all formats there is, so there isn't a problem with what type of files or what GOP structure it got. I cannot solve this even by creating a new project or reboot, I even reinstalled AE and the Matrox drivers, I tried unplugging the MXO2 mini but got the same result, so I'm pretty much done testing, I tried everything I can think of. I allocated RAM differently, shut of multiprocessing, enabled it, more RAM to few cores and then less RAM to more cores, increased cashe, disabled it.
Sometimes when I let the footage play out with RAM preview, the analyze gets to the end in the background, but whenever I just let it work for itself it drops.
So I tried everything and the error still persist. What should I do?

Warp stabilizer not rendered on export

I've just exported a sequence and for some reason some of the warp stabilisation effects aren't rendered and the clip has an orange bar saying "Stabilizing" across the middle. Very odd!
Anyone have any ideas why it's done this? The sequence is over an hour long and was about to be sent to a client so it's a good thing I happened to stumble across one of them.

Perhaps you began the export before the initial processing was completed within Warp Stabilizer? Just a guess, have not encountered this before since I definitely wait on each application of that effect so I can judge the results.
Now I have to test that theory, I'm curious!
OK, just tried a test and that is exactly the issue! I dropped four short clips onto a timeline, added Warp Stabilizer to each and of course they each had the blue "Analyzing in Background" banner across them. I IMMEDIATELY went to AME and began an Export and sure enough, the blue banner was exported with the clips.
Depending on the clip, Warp sometimes makes the clip much worse and I would never export before checking the results on each clip I applied it to. The CMOS chip jello wobble sometimes becomes extreme like a funhouse mirror and then I just skip it!
Thanks
Jeff Pulera
Safe Harbor Computers

Warp Stabilizer glitch

Hey guys,
So a friend is having me color correct her footage for a project. She gave me her hard drive so I am directly editing from the video files on her drive (a transfer would take over five hours for all the videos).
When I go to color correct, the warp stabilizer glitches and crops the footage down to a small rectangle on the left of the screen. This has been going on for some time with my own projects, but I figured it was just a setting mishap on my part. However, she says the files look fine on her computer.
Attached is a screenshot of the working space as well as the settings for the warp. Has anyone else had this issue? It's incredibly frustrating because now I know it's only happening on my version of Premiere.

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.

Warp Stabilizer Stuck?

I was trying to finalize a show and dropped the Warp Stabilizer into one of the clips. Its about a 5 minute clip. On my very fast computer with 16GB of memory it took 20 min to "analyze" and it has been "stabilizing" for 2 hours. I tried getting out of the project to see if I could kill it off but when I reloaded it went right back to "stabilizing". Is this normal? From all the previews I knew it wasn't real time but if this is typical I can't imagine using this thing.
I see folks commenting on the speed but nothing like 3 hours for 5 min. clip.
What should I be expecting? I would like to stabilize one more clip in the video but I'm almost afraid to use this thing now.

Trim a clip to 10 seconds and try that. If it takes 10 minutes, then you know you are stuck with a 60:1 ratio and you have decisions to make.
Also, take a look at the video. If one part of it is really, really bad, you might want to exclude that part. Perhaps if you bumped the camera. That might be part of the problem.
Just for reference, I just stabilized 10 seconds (300 frames) in six minutes. The analysis took the six minutes, the second step was probably no more than 10 seconds, if that. I was expecting longer and looked away from the stop watch for a few seconds.
And my PC is quite fast, thank you very much!
So, if it is still stabilizing, you have a problem. Create a new project, use a 10 second clip. That should give you a baseline if the stabilizing doesn't get stuck again.

Warp Stabilizer is not Analyzing

Warp Stabilizer was working fine. But, I started a new project today and when I add it to a clip it doesn't start automatically analyzing. It says "click analyze to begin" but when I click analyze in the effect control it appears to start for about a second and then stops and stops and reverts to the blue line statement "click analyze to being"...

I ran into the same problem today and got it fixed. It appears for some reason my clip wasn't working because of clip length (or something along those lines). Nesting the sequence didn't work, neither did restarting premiere and/or computer; but when I scaled the clip back it worked like a charm. I tried this a few times until I got back to the clip length I was originally hoping for and it works. Looks like some random blip that occurred when I dropped the file down.
Best of luck,
-Luke

Warp Stabilizer dropping

Similar Messages

Maybe you are looking for