Warp stabilizer - change of directories

I'm having trouble with warp stabilizer and hope someone can help. I need to mention I'm brand new to using NLEs and am following along with tutorials for about 2 weeks to learn, so I am a very basic user.
I created my sequence by selecting multiple clip in my bin and dragging them onto the "New Item" icon at the bottom of the bin, allowing Premiere Pro to auto choose all the settings based on the footage by canceling when it popped up the window with all the many many choices about your footage format. The footage is just something I found online for the tutorial. I used "Warp Stabilizer" on a clip that was jumpy and it worked fine. I did not save, or I thought it autosaved but did not. I then installed a program called "Post Haste" which creates an organized series of folders for your projects. I did this because I am trying to learn good practices and being organized seems to be very important.
I then went to "Finder (I'm on a Mac) and moved all my files for this project into the folders that "Post Haste" created. When I restarted PPcs6 it asked me where all the files were and I went and found them all and it appeared initially that everything was working fine(or at least it looked the same), until I tried to do the Warp Stabilizer again on exactly the same clip I had before (as I mentioned I did not save). This time I got the message "Warp Stabilizer requires clip dimensions to match sequence" I should also say that my fps seems to be 24 which I'm not sure they were before. I should note that I'm in the US so I'd rather be working in NTSC and not PAL. So naturally I'm a bit frustrated and more over baffled as to what happened. I am assuming that moving the files to new folders somehow broke the settings. I did find an article on Premiere Pro Project Manager which initially makes me believe that I should have somehow set up settings before moving my files but the article was very brief and I did not really get that much from it.
So I guess my questions are: What happened? How do I fix it? Did I break/change my settings by moving my files? Did the clips change from my sequence settings to their individual clip settings? I 'm not sure what format the footage I am using was shot with/in, but since it is civil war reenactment footage I'd say it was NOT shot for PAL. So how did it move to 24fps? (isn't this PAL and should I not want 30fps?)
Is there a way for me to fix the entire timeline settings to all match the sequence or should I start again?
Any help including best practices going forward would be greatly appreciated.

If your timeline consists of different dimensions and the clip you want to stabilize does not match the sequence, just nest the clip and the add the Warp Stabilizer.

Similar Messages

HAS THE WARP STABILIZER CHANGED OR IMPROVED IN ANY MANNER IN After Effects 6.0?

It was quite an improvement over point tracking alone.
Have there been substantial further advances in the Warp Stabilizer in AE 6?
Also, has Mocha AE changed in any manner?
Thanks!
Matt Dubuque

Have there been substantial further advances in the Warp Stabilizer in AE 6?
What would be "substantial"? No, apart from a few minor workflow and performance enhacements there have been no changes.
Also, has Mocha AE changed in any manner?
You still get mocha 2.x, just a slightly newer version, not mocha 3.
Mylenium

Render Work Area/Warp Stabilizer Changes Video Duration

Hi everyone,
I'm quite new to Premiere Pro and I have no doubt this question has a simple answer.
I've put in a small video, say 5 seconds into my timeline. I then for example apply the warp stabiliser effect. I think select Sequence - Render Work Area.
But every time I do it, the full video is no longer showing. It's like it has kept the same amount of frames, but because warp stablizer (I'm assuming) has inserted frames to smooth it out, I'm only seeing a fraction of the total clip length.
So video length is still 5 seconds, but I'm now only seeing say, 60% of what was shown before.
Just for further info, I'm using a 720HD 30fps sequence, but the video in question is a 120fps from a GoPro. I wonder if that's causing the issue?
Any help would be greatly appreciated.

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

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.

Adobe Premiere CC 2014.2: losing rendered files when using warp stabilizer

Hi,
I am constantly losing rendered files when using the warp stabilizer. So far I have tried about every hint I could find on the web such as cleaning the cache, rebuilding the rendered files, creating additional sequences etc etc.
Honestly I am getting tired of using a product that isnt cheap in the first place to rent and where a bug like this apparently persists over several product versions without being fully fixed (I have had this problem throughout 2014 but according to forum postings others seem to have problems with much earlier versions as well).
I would be really grateful if somebofy has any suggestion how this can be addressed.
I am also happy to help testing fixes - if there are any fixes available.
Thanks a lot and Happy New Year!
Martin

Hi Catherine,
Welcome to the Adobe forums.
Please try the steps mentioned below and check if it works for you.
1. Launch Premiere Pro and create a Project, go to File menu>Project Settings>Renderer and change the Renderer to Software only mode, delete previews if you get a prompt and then try to import the clip.
2. If step 1 fails or the Renderer is already on Software only mode, go to Start Menu and search for Device Manager, go into Display Adapters and Right click on the Graphics card to select Update driver software option, on the next screen choose "Browse my computer for driver software", then choose "Let me Pick from a list..." option and from the list select "Standard VGA Graphics adapters. You might need to change the screen resolution of your screen and once done restart the machine again.
Launch Premiere Pro and import the clip to check.
Regards,
Vinay

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.

FR: Big yet incredibly simple improvement to Warp Stabilizer

I love the Warp Stabilizer effect in PP. It's great! But depending on the footage and the effect's settings, sometimes it can actually make things worse. This means that any time this effect is used, users must review of the results after the effect finishes analyzing the clip.
Here's the problem:
Analysis takes a long time, often far too long for a user to stop editing and wait to review the results. In my case, I keep editing, but often I forget where my stabilized clip for review is located. In a multicam sequence, where every video clip occupies the same track, there's little to no visual cues to remind me where the Stabilized clips are. Setting an in and/or out point as temporary markers can work if you have up to two Stabilized clips. But what if you just stabilized 5 clips, and you want to keep editing while they're being analyzed? How do you visually recognize which clips they are? All current solutions add work for the editor, such as moving stabilized clips up a track and then back down after approval of the effect's results, etc. If you have transitions between a Stabilized and an adjacent clip, or clips on a track above it, the situation gets worse.
Here's the (incredibly simple) solution:
Give us a visual color cue any time a clip has the Warp Stabilizer effect added to it! This could be done through a new user selectable color category in the Preferences window's 'Label Defaults' panel.
It's interesting to note that while 8 different colors can be set in the Label Colors tab, only 7 are currently used by PP in the Label Defaults tab, so setting a unique color to this new eighth item should be even easier to program.
Adobe, this would make a great little addition to your next PP update!
What do others think?

Jim Simon wrote:
Your request calls for easy visual recognition of that one effect, mine calls for easy visual recognition of any effect, which I feel would be far more useful to far more editors.
Be as it may, even though I highly doubt that editors need an easier way to determine which clips have any effect applied in general, WS clips would still have to have a different color, otherwise editors wouldn't be able to differentiate WS effects from any other old effect that simply does not require the editor pause or return later to see the results. I've explained this pretty clearly but it seems you're determined to not get it.
Jim Simon wrote:
Or, if you don't want to wait for the effect to finish, add it after editing, as most editors do with most effects anyway. Then you'll have the time to wait to see the results.
Adding effects is part of editing, or isn't it? In case you don't know, editors work differently. If I want to add effects as I do my cuts, what's wrong with that? The software should be intelligent and flexible enough to accommodate a user's workflow. And if it isn't, then it should be improved. If you're an advocate against this kind of progress and think users should adapt to and accept a programs limitations, rather than speak up, which version of Premiere are you using? 4.1?
Jim Simon wrote:
Mark them, as you can do now.
The whole point of this thread and FR is for Premiere to remove steps from our workflow! Still don't get it, do you?
It seems that every time I expose a limitation in Premiere or an area for improvement, you suggest that I should change my workflow rather than have the software improve in a way that could benefit countless other editors. At this point, I really have to ask... what's in it for you Jim? What's your point?
"Then you'll have time to wait to see the results" Is that what you do, wait 10 minutes for a long clip to finish analyzing so you can see the WS results? You're just sounding more and more ridiculous IMHO. It would be nice if overall you made more intelligent contributions to my threads.
Frankly, I'm getting tired of this nonsense Jim. If you have something intelligent to say, please, by all means. If you don't, please stop diluting the message of my threads with your nonsense arguments/comments. If you want all clips with effects applied to them to be labeled with the same color, and thus make WS clips visually indistinguishable (which is the current problem I'm asking Adobe to fix), go ahead and start your own thread.

Warp stabilizer cropping/position issue?

So I don't think I've ever had this issue and I'm wondering if has to do with using it on a 13" macbook, since i've never had this issue on my iMac, but when I place the warp stabilizer effect the clip turns into a small cropped corner like so in the photo. This happens with any clip even if I try to adjust the stabilizer settings. Any help would be appreciated!

Hi mlhidalgo,
Please go to File > Project settings > General and change the GPU Acceleration to Mercury Playback Engine software only. After you will click ok, it will ask you to delete previews or keep previews. Choose Delete previews and see if it helps.
Also, please report if you have Intel Iris graphics.
Thanks!
Rameez

5 things which should be improved in the Warp Stabilizer

1. Performance.
When stabilizing any footage I always ask myself: "What the heck is he doing there?!" not even a single core is really working hard. It looks like an idle background process The GPU is idle as well, as the analysis pass is only run on the CPU.
This maybe okay if you still need much work to do in Premiere. But often, the next steps DEPEND on the stabilization and you have to WAIT and WAIT and WAIT...
It's just painful to imagine that, running a machine with 8 cores, more than 8 times the amount of video material COULD be analyzed.
The free Deshaker for Virtualdub actually uses more cores (even though not at 100%) but analyzes at about 20-21fps compared to the Warp Stabilizer at about 4-8fps.
Admitted, the Deshakers results aren't nearly as good (especially with rolling shutter, which can be configured though, but you don't always know the right percentage for the cam you're using).
This also applies to opening projects with much stabilization data. It opens... and opens... rarely any disk activity and rarely any CPU or GPU activity. Again: WHAT IS HE DOING THERE? Just waiting for the clock itself?! Or is he sending it all to the NSA? That at least would explain the unneccesary delay:P (just kidding!)
2. Stabilization data.
For me, I wouldn't have any problem with storing it just inside a project folder or a separate file. Just add a checkbox into the plugin settings:
[x] Store stabilisation data in separate file/folder.
This may be then called [projectName].stabilization
Inside that folder, there will be maybe one file for every effect used in the project.
...or you can use the old way, if you don't have so much stabilization work to do.
3. Small bugs.
When using "stabilize only", the resulting frame, at least in Premiere Pro, has a HUGE "DC offset" sometimes. This is a term from music producing, but exactly fits in here. You can clearly see it when there are still images that shouldn't receive much of stabilization. They're somtimes shifted far out of the viewing frame, leaving big black borders, so you have to manually adjust the frame position to fit back into a "neutral" position. This could be resolved to let the whole correcting curve undergo something like a "low pass filter" which will try to keep the resulting frame SOMEHOW centered.
In this image above, from a longer clip, there isn't much motion at all. But you can see how far the offset from the actual video frame is. I have to do this for almost every video, also after I change the "smoothness" setting.
4. More control
I would LOVE to be able to disable "zoom detection", because it gives me lots of "Vertigo Effects" in many cases.
I heard this has been alredy addressed for CC.
5. Improvements / new features
One thing I always do with every stabilized video:
Instead of synthesize edges, which takes AGES to render, I just do the following:
I place the same clip, unstabilized, behind the stabilized clip (stabilized, borders only) and give the stabilized clip softened borders with "rough edges". This even still renders fine on the GPU.
This would make a great option for the stabilizer. Just call it "overlay over original with blurred edges" or something like that.
This has worked extremely well for any stabilized footage so far and isn't nearly as disturbing as the synthesized edges.
I'm considering to join the Creative Cloud, because unless I do this I don't expect to see any improvements in my old and out-dated Premiere PRO CS6...

https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform to file a feature request... insert a reference to this message link

Possible to turn OFF "Rolling Shutter Ripple" correction in CS5.5 Warp Stabilizer?

Is Rolling Shutter Ripple redcution on by default in CS5.5 Warp Stabilizer? Can I turn it off?
I am having some strange results trying to stabilize some night-time astro timelapse sequences I shot from a moving car. There seems to be some warping and "zooming" of parts of my frame, regardless of which stabilization options I choose -- motion, no motion, scale-crop-rotate, subspace, etc. I've tried every combination possible, including the various border options. The only thing I can think of, at this point, is that the Rolling Shutter correction function might be struggling to deal with frames shot from a moving car at 4/10ths of a second at night. Is there any way to turn off the rolling shutter compensation?
Thanks!

Thanks Jim.
The source stitched 176 frames for my test are about 1gb. So trying to get to the bottom of it without someone having to dl them (and it will take a while to put them up). The 8 frame version shows the same effect happening, just exaggerated. But its a fair call to assume maybe it would not happen with enough information to work with.
The original http://dl.dropbox.com/u/7070604/full_ae_1080.mov I had tried at the time using detailed analysis as well to see if it fixed the issue, and the results were very similar.
I'd also found that using subspace warp instead of PSR (position, scale rotation), or even just P (position) seemed to generate some additional warping there in the output, and certainly for my footage did not result in making it better.
However, I have re-run the full footage starting from frames not a movie using detail analysis and subspace warp since you running that over the originally processed 1080 footage seemed to do a pretty good job.
The results are here : http://dl.dropbox.com/u/7070604/full_ae_1080_warp.mov?dl=1
You can see the warp is really messing it up, and the zooming is not fixed. Left hand side easiest place to see it.
Note I've found putting ?dl=1 on any of the links actually downloads them for anyone having issues with it simply playing in their browser. The way I am visiually checking any of these for issues (as many are at 1fps) is to load them into quicktime, change it to View, loop. Then In quicktime 7 holding FFWD. In quicktime 10 hitting forward until it runs at 8x. Looping at 8x is where you can really see the issue.
The files I had not broken out seperately that are in the source files upload were the results in after effects just using the 8 frames. Here they are seperately.
http://dl.dropbox.com/u/7070604/1080_rez_p.mov?dl=1
Position only.
http://dl.dropbox.com/u/7070604/1080_rez_psr.mov?dl=1
Position scale rotate.
http://dl.dropbox.com/u/7070604/1080_rez.mov?dl=1
Unstablized.
I presume even with subspace warp you get the same results or worse using these 8 frame files.
If you ignore the extra warping/twisting in the new file, you have the same results as the original http://dl.dropbox.com/u/7070604/full_ae_1080.mov?dl=1
played at 8x. The easiest place to see it is the mid left side where you can see it zooming in and out. The fact that it really only starts happening a 3rd the way through makes me think its simply not dealing with the changes in zoom, or the later pan changes in the source file. It wierd the photoshop processed version comes out fine though.
I was really hoping it was a case of, "ah, I see why it can't deal with those 8 frames, it really needs a manual tracker/stablizer doing x,y,z" But of course I'd be even happier with a tweak to the automated warp stabilizer.
If I do a 2nd run on the sample file http://dl.dropbox.com/u/7070604/full_ae_1080.mov I notice selecting P, or PSR does not fix it. Selecting Perspective or Subspace (which probably includes perspective) seems to go a long way and have a similar result.
Leads me back to thinking selecting subspace on the original footage just warps it, selecting P or PSR fixes all but the zooming thing, and then reprocessing with perspective is tackling the persective in isolation which it could not effectively do before. I don't know if that is because you cannot select P&R without S scale. Or because AE's perspective adjustment cannot work effectively with images that have scale variences in them or ?
I've now run the ouput from a frames start via P and PSR. Brought them back in and prosessed with subspace and P and PSR. Results seems to be no better. There is some special sauce here somewhere with the reprocessing. Maybe its the codec I am going out to in the middle, maybe its the aspect ratio, maybe its ???
Might be time to u/l the full source files I guess.
Thanks for sticking with me.

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.

Warp Stabilizer in Premiere CS6 is excellent

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

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

Warp stabilizer and speed can't be used in same clip. explain error message please.

Learning - from how to capture to how to do basic edits.
Trying to use warp stabilizer on some hand-held footage and got the red "NO" message.
Can I still do this, or did I do my edits in the wrong order as in I should maybe have used warp stabilizer first or something.

I have used various stabilisers over the past ten years, and have always found that the best stabilisation results are achieved with the raw footage, unless this has very low contrast. In that case it pays to apply a levels effect first.
I always export my stabilised clips to an intermediate file using a "lossless" codec before importing that new file into my project to replace the original footage. I use the free download UT codec for this. I have tried Lagarith and the free Avid DvxHD, but have had problems of one sort or another with each.
Speed changes never work well when the clip needs stabilising, in my experience.

Warp stabilizer - change of directories

Similar Messages

Maybe you are looking for