Warp stabilizer analyzing too much.

I have a composition that is 10 seconds long with a video clip. I added the Warp Stabilizer and shouldn't it just analyze just 3000 frames? It appears to be analyzing the entire clip even thought the comp is just 10 seconds.

Make sure you set in and out points for your video layer.
If for some reason that fails, precompose the video layer and warp stabilize the pre-comp.
Here's another hint, after Warp Stabilizing your shot RENDER it to what I like to call a DI (digital intermediate) and others call a production codec and use that in the rest of your production. You'll be much better off in the long run unless your project is extremely simple. A DI is a lossless digital copy of your original footage to be used in the production pipeline for preparation of the final digital master from which you render your digital deliverables like H.264 files for almost every digital form of delivery today.

Similar Messages

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.

Warp stabilizer analyze alert burned into output

Hello. Having a problem that I have not been able to find an answer to online. I have a clip in a timeline that has warp stabilize on it and when I export using media encoder the output file shows the analyzing bar rendered across the screen. This only happens with media encoder sequences sent from premiere. Doesn't happen if I just export from premiere. Trashed media encoder prefs but that didn't help. The clip is h264. No other effects in the clip. Any help would be greatly appreciated. Thanks! Chris

Hi RameezKhan!
Thanks for the input!
Unfortunately i can't change the renderer, software only for this mac...
I deleted the media cache and render files right before this happened so i didn't think that would be it...but I did notice that when I re-opend premiere that one clip would always need rendering again...
I deleted media and render files again and it's been fixed...
I though media encoder didn't use the render files...maybe it uses the cache and that was the fix.
Either way it's working.
Thanks again!
Chris

Warp Stabilizer Analyze Data - where does it really save?

Hello,
I had cut 4 episode documentary series on a macPro with CS6. I had used the Sub Space Warp stabilizer feature on many of the clips. All clips had been stabilized and I saved the project on our server with the projects files, preview files and Auto save files.
I then got a computer upgrade to a new macPro with more RAM - graphic - and processing power. Yay! I have CS6 and CC installed on this.
I received the final design elements to insert into the series ( the L3 and titles and credits ) and went to go and export the project off the server from this new computer.
It seems that all of the clips that I have used the Sub Space Warp Stabilizer need to be re-analyzed again, as the exports had the orange banner across the clips stating that it is being analyzed.
My question is, does Premier have to reanalyze the clips again because I have a new computer and the Sub Space warp data doesn't save with the project files but instead locally on the machine that edited the project?
If so, can I get all the project data and cache to save with the project files?
When I started this project, as with any project, I direct all the save elements and caches to a specific drive location, so various computers can work with the edit, and for efficiency. I don't think that the Sub Space Warp analyze data gets off the local computer drive... Am I wrong?
Any comments are appreciated.
Thank for your help.

I see that now as well. Yes thank you for your reply there Snarky.
I wonder why my exports had the orange analyze banner across the clips with the Warp Stabilizer on it.
You figure with that data stored in the project file, it would just load up with the project,
and when the software says "All media Loaded" - that I wouldn't have to go back to each clip and get it to re-analyze for stabilization.
So time consuming.
I hope that is is an isolated incident.
This doesn't not seem to be the case, as I am not alone.
pass warp stabilizer between computers?
Reanalyzing Warp Stabilized Clips
Thank you Snarky McSnarkster

Adobe After Effects CS5.5-Warp Stabilizer analyzes but doesn't Stabilize.

First of all,Hello everyone.I'm new around here.Hope you all having a good time.
The problem is that when I hit the Stabilize Motion button, it starts to analyze in step 1 but when it finishes and skips to step 2 , stabilizing part takes just 3 second.So in the end,it doesn't stabilize the motion,doesn't do anything to the clip.So can anyone help me with that?

The most common explanation for failed motion stabilization is the user has fialed to go through the steps properly. We know this form manyyears of answering thsi question and we know from manyyears of using the tool ourselves. It can be a bit confusing the first coule fo times you try to use it but it does work and it works beautifully. So, before we go through many posts and questions and suggestions, please review the Help section one more time and try to initiate and apply the stabilizer again. Do it slowly. One step at a time.

Warp Stabilizer for large sections of video?

Greetings,
I have a pretty strong editing rig with 24gig of memory but with CS5, I still only selectively used the warp stabilizer in After Effects for short clips I was editing in Premiere Pro. I guess both because of the link and render hassles vs. benefits and time involved. In short, I used in when I had to and it usually worked.
With having it integrated in CS6 Premiere Pro now, I was wondering how performance was and if it was feasable for using it on longer shoot segments. Say I am editing some older camcorder footage that is rather shaky. Could I take a 20 or 30 minute chunk and expect it to correct and render in a reasonable time? Is there any ballpark estimate of footage time vs. warp stabilizer analyze and finish time?
I can't wait to use this as I upgrade to CS6 but don't want to expect too much.
Thanks,
BJBBJB1

Kevin,
Thanks for the on point link! Sigh....it still looks like it consumes a lot of resources. They recommend splitting clips at the 5 minute mark.
However, perhaps running a larger clip through the process and rendering it out in a lossless format, and then bringing it back in for editing might be the way to go.
Which, come to think of it, is what we had to do with AE!
But certainly having it integrated for short clip stabilizing is still very nice.
BJBBJB1

Warp stabilizer counting much more frames than actually exists...

Hello, everyone!
I've just installed Premiere CC 2014 and I'm having problems with Warp Stabilizer... I'm trying to use it in clip with 25s and 24fps, but when I click "Analyze" it shows 1035764 frames! Also, it will take 2560 minutes to analyze it all! Doing the math, it should have only something like 600 frames and take much less time...
I know this stabilizer is very buggy, but I couldn't find a solution for this. Can anyone help me?
Thanks in advance!

Well, for some random reason, if I replace each file for itself the bug disappear, i had to do this one by one. If anyone have the same problem, try doing this.
This solves the problem for now, but it took some time to discover and to solve it. Hope it doesn't happen again.

A command to analyze all clips onto which a warp stabilizer has been added?

Ahoi gente!
We are working on a 90 minute piece -and getting through the project manager took time and nerves. Clips are still missing in the collected project created by the project manager...
Anyway - the real question is: Is there a way to filter the clips in the timeline to only show the ones with a warp stabilizer on it? Or a command to analyze them all?
Otherwise I have to look through all of the clips and click analyze again....
Recommendations? Thanks a LOT!

Hm, I did learn some lessons in all this - but not using an NLE to manage the files...?
I thought next time we should give unique names to files instead of building up a structure of folders on the external hds, work with proxies, dividing the project in more sub projects more often to increase performance etc.
But how would you get rid of not used files instead of using the project manager? Manually?

How to "analyze" multiple clips with "Warp stabilizer"-effect preset

Is there a simple way to "analyze" multiple clips that have the Warp Stabilizer effect attached?
I have a sequence with 100 clips, which all have a customized Warp Stabilizer effect preset attached. I can attach the effect to all the clips very easily, but afterwards I have to manually press "Analyze" on each clip, which is quite irritating... Is there a shortcut?
I don’t use nesting because I have to tweak the effect-settings on some of the clips…

https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Yes, sadly custom presets with warp stabilizers don't work correctly. You have to go hit analyze manually for every clip. For you that may be quicker than changing your two settings for each clip. It is a bummer though. We actually use this effect several hundred times per week and prefer the "Position, Scale, Rotation" method in the settings but we can't use the custom preset because it doesn't properly re-analyze automatically like the default effect does. I'm not sure whether it'd be a bug report or a feature request (in my opinion it's a bug) but definitely report it to the link above.

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

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.

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.

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 Cripples My Computer

Just want to know if it's normal for the system to lock up if I apply warp stabilizer. It uses about 20-26 GB RAM out of the 32 GB installed. The clips are pretty long , though - 20 minutes or so. Obviously, it handles shorter clips without locking up. But I can't do much better than 32 GB of RAM. It doesn't really crash the computer (not yet). Eventually it does it's thing, but it does freeze Premiere for periods of time.
I am experimenting with different parameter settings to several clips. I assumed that once the clip is analyzed, I could preview different parameters without having to re-analyze.
CS6, Windows 7, i7-2600 3.4 GHz CPU, GTX580 Amp! Video card.

Trying to stabilise a clip as long as 20 minutes is inevitably going to take an enormous length of time, unless there is very little movement within the frames. It is not likely to lead to an acceptable result as the movement that is present will probably mean the excessive zoom is applied to stabilise it.
Stabilisation really only works with short clips, ideally with little movement apart from the jitter that is to be removed. Otherwise there is simply too much processing required.
If you persist, you will discover the other problem with the warp stabiliser - it rapidly generates enormous project files leading to Premiere slowing to a crawl. I hate to think what will happen here with stabilised 20 minute clips.
I rarely attempt to stabilise a clip longer than 20 seconds - ideally less than 10 secends - and have long since abandoned the Warp stabiliser even though it gives good results on certain types of clip. I stick to Mercalli 2.

Warp stabilizer analyzing too much.

Similar Messages

Maybe you are looking for