Precomposing & Cropping & Warp Stabilizer? *Beginners Question*

Hi guys,
I'm new to AE and have been trying to follow instructions from this link (http://www.sinusdigitalus.de/2011/05/06/my-first-test-with-the-new-adobe-cs55-warp-stabili zer/)
I've taken out the important bit here -
"i´ve imported my sequence and applied the warp stabilizer on it. the first instance of the stablilizer was to stablize only the movement of the position, scale and rotation with a crop but with no rescale to keep the image quallity. i´ve precomposed the shot and resized the comp with the new dimentions of the shot after the crop. on this i applied a new warp stabilizer and this time i´ve stabilized the perspective also with crop but no rescale. again precomposing and rescaling the comp to the new dimensions. then i applied a third warp stabilizer on this new comp and did it again. this time with the subspace stabilization."
- As he mentions at the begining, it's not an indepth tutorial so where I'm tripping up is the precomposing and cropping.
I'm trying to stabilise a jpeg sequence using this guy's method (he passes it through Warp Stabilzer 3 times).
When I hit the Precomopse button it gives me 2 options and a box to tick whether or not to open new composition, which ones do I pick? And when that's done, how do I crop it so it's applied to the whole jpeg sequence before I use Warp Stabilzer agiain?
Thank for your help.

Not tried it but could you make a 2.7k sequence and warp stabilise that, using stabilise only or stabilise and crop. Then add this sequence to the 1920x1080 sizing to suit.

Similar Messages

  • Few Warp Stabilizer workflow questions

    I'm looking for the best workflow with warp stabilizar, because it consists in 90% of my edit work.
    This is my workflow at the moment:
    Start to add my trimmed clips in the Premiere timeline
    Right click the shaky clip and select "replace with AE composition"
    In AE I right click the clip and select "Stabilize Motion", while analyzing I do step 2 with other clips
    Once all the analisys/stabilization of all clips is completed I select "Render entire work area" in Premiere and check out if results are ok
    If ok I add transition between clips and proceed with the color correction
    I Select "Render Effects in work area" to have a preview of the final work..
    Render sequence to file.
    Usually the operation #6 of my workflow renders much faster, but doing that on stabilized clips it takes a lot more time.
    Is my workflow correct or should I do all other edits before replacing the clip with AE composition ?
    Is there a faster way to manage stabilized clips ? (exporting a new file from AE once stabilized.. ?)
    If I need to re-trim the stabilized clip should I just do it in Pr , render again, and the analysis will be done in automatic ?
    Thank you!!

    When I stabilize a shot that I have in premiere there are two workflows.
    I copy the shot in Premiere in the timeline. I then open up After Effects and paste the shot. In the shot comp I extend the length of the composition to give me "handles" then stabilize, add to the render cue, render to the codec that I'm using in Premiere Pro (usually ProRez 422 HQ or ProRez 444) and replace the shot in Premiere. If you know how long your handles are, mine are mostly 60 frames, then it's very easy to re-sync the edit with room for transitions.
    If there are multiple shots or layered shots in Premiere I'll marquis select everything involved in the sequence and use the Replace with After Effects Composition option. This gives me an AE comp with all of the shots selected including room for transitions if they are in the Premiere Project. If the shot that needs stabilizing is long I'll Pre-compose it in AE, Add handles in the pre-comp, render the pre-comp in AE and replace usage. If it's just a short shot I'll just let dynamic link take care of the AE project.
    I hope this helps. Every project has a slightly different workflow, but in most cases, I'm rendering heavy effects shots in AE and replacing them in Premiere. That's the nature of the work that I do most of the time.

  • Warp Stabilizer 4K to HD - does PPcs6 interpolate first then downsize when using "stabilize, crop, autoscale?

    I am using CS6. I have warp stabilized my 4K footage and want to output to HD at the best quality I can. I have two choices: I can either have warp stabilizer "stabilize, crop auto scale" then I simply render to HD or I can set "stabilize, crop" and then get rid of the black border (crop) using AME in export settings. So my question is: If I use option 1 does PP interpolate the footage and then "downsize" to HD thus reducing quality? Or Does PP make all the calculations "in one go" so the footage isn't actually interpolated then reduced? I hope I have explained this clearly - though I fear not :-) Thank you for any comments. Paul

    I've been experimenting exactly the same.  My conclusion is that stabilize, crop, auto scale does indeed crop the video first, then rescale back to the original frame resolution. So there is some loss of quality.  I've been working on 4K video and warp stabilizing first (no crop, no auto scale), then cropping as a nested sequence to HD (with key-framing to follow the action).  Depending on the amount of crop, what the video content is, and because you're starting with 4K footage to begin with, it's debatable as to whether the final HD rendered output is visually any different whatever method you choose.  I guess you'll only find out by trial and error.
    Steve

  • Warp Stabilizer crops bottom of video if videos layers are beneath it for no reason.  Why???

    Warp Stabilizer crops bottom of video if videos layers are beneath it for no reason.  Why???
    remove the layers beneath and it's fine.  Hopefully adobe addresses this issue asap to save all of us a good amount of time.

    I have noticed similar: apply crop to a layer and with all settings at 0 a line of underlying video can be seen at the bottom.

  • 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

  • How to shoot 1080p/60, output to 720p/60, so Warp Stabilizer or zoom/crop has no quality loss?

    I'm new to AE, and making a painful transition form FCP to Premiere, so please be patient, I don't understand many of the subtalties of these apps yet.  :-)
    Also, please forgive the long explaination, I'm having trouble articulating the problem...
    I'm shooting in 1080p/60, AVCHD.  I plan mainly to output to 720p/60.
    The idea being, that if I need to warp stabilize footage, or zoom/crop, I can do so without any quality loss.
    I don't want to edit the project in 1080p/60, because if I stabilize it, and it blows up the image, it will result in quality loss. Then when I scale down for final output, that pixilated/crapified footage will be present just in scaled down form.
    I don't want the footage to be scaled down first, then, when I stabilize it, I'm blowing up 720p footage (thus defeating the whole purpose of doing this) and once again, outputting pixilated/crappified footage.
    What are the steps / workflow to set up Premiere and the stabilizing shots in AE, such that I'm working in 720p, but using the 1080p footage, so that extra resolution is available when I need to crop, zoom, stabilize, etc. the footage... and can do so without any quality loss?  It would be great to have that ability to zoom in on elements in post, almost 2x, and not see any loss of quality.
    Thanks in advance!
    -Jason Wallace

    100% positive.  There is a family of lesser known Prosumer Panasonic cameras (my particular model is the TM700) that record 1080p/60.  It's a 3-chip, CMOS, that genuinly records at that resolution and frame rate.  Has audio input, headphone output, shoe mount, zebra stripes, touch screen, good battery life, and a manual focus ring (fly by wire, can be set for exposure, framerate, or focus).  Also has very good low light capabilities, that are much better than the published specs would lead you to believe.  The firmware is a bit goofy, and was clearly designed by engineers, not people who have ever shot video.  For example some things that should be easily accessible, are buried in menus, while other useless "fluff" features are front and quickly accessible.... but if you can live with a few stupid firmware compromises, it's absolutely AMAZING bang for the buck, and well under $1k to buy.
    Note: if I'm not mistaken, the camera can only output via HDMI 1080i/60, but for absolute certain the video files being recorded are genuine 1080p/60. (This has lead to some confusion and forum arguements as to whether the camera is actually 1080p/60)
    This was one of the main reasons for my moving from FCP to Premiere, as Premiere Pro handles the 1080p/60 AVCHD files, while FCP requires they first be transcoded and inflated to a intermediate codec.
    -Jason W

  • Warp Stabilization crops to letterbox?

    I cant quite put my finger on just what is going on here,
    but I think Warp Stabilisation is pulling a bit of a weird crop job on my footage.
    The letterboxing effect seems to increase as I decrease the maximum scale slider.
    What im doing is replacing a clip with an after effects composition in premiere pro,
    and then simply dragging the warp stabilizer ontop of the footage to let it do its thing.
    Any advice or ideas on whats going on?
    Running windows 7 64bit, AE version 10.5.0.253, PP version 5.5.0.233

    Youre indeed right about there being lots of movement, this is the start of a video with a small airplane darting off.
    Your arguement that maximum scaling is too small doesnt seem to hold up to my problem though.
    If I increase the maximum, the letterboxing gets even worse.
    My goal is to get a steady shot of an aircraft in the air.
    Tracking points dont seem to take hold of them, and warp stabilize also seems to get confused.
    The only program that can do it flawlessly is deshaker in virtualdub.
    How I wish I had that plugin for Premiere Pro.

  • Warp stabilizer crops clip off screen - help!

    Adobe Premiere Pro CC - most current update.
    When I apply the Warp Stabilizer effect, it crops/moves the clip almost completely off screen in the preview window. It also remains this way when I export.
    I am uploading dslr footage with these properties:
    File Path: /Users/Braedin/Desktop/Banff trip/Friday/MVI_9850.MOV
    Type: MPEG Movie
    File Size: 52.5 MB
    Image Size: 1280 x 720
    Frame Rate: 59.94
    Source Audio Format: 48000 Hz - 16 bit - Stereo
    Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
    Total Duration: 00:00:10:03
    Pixel Aspect Ratio: 1.0
    I then slow down footage to 40% to a 24fps look (orginally 60fps)
    I then "Nest" the footage to be able to apply the Warp Stabilizer effect.
    This is what it looks like without applying warp stabilizer:
    This is what is looks like after applying warp stabilizer and rendering the clip:
    These are the properties of the "Nested" clip with Warp Stabilizer:
    Nested Sequence 03
    1280 x 720
    00;00;04;22, 59.94 fps
    48000 Hz - Stereo
    Finally, here are my current Sequence Settings in which I am having the issue:
    Any help would be greatly appreciated as I suspect its an issue with sequence setting.
    Thanks,
    Braedin

    If you have a Retina Macbook Pro you can download the latest NVIDIA drivers from their website, which will enable you to use CUDA GPU acceleration in Premiere Pro, which fixed the problem for me, and is faster to render etc than Software Only.
    More info at this link, which also contains a link to the NVIDIA drivers:
    Enabling CUDA for Premiere Pro and After Effects in the MacBook Pro Retina

  • Warp stabilizer crops bottom of video!

    When I try to stabilize some footage shot with my GoPro Hero 3 Black, warp stabilizer crops off the bottom of the video and greatly reduces the res of the video.
    The steps I am following:
    Import video using GoPro Cineform software (This leaves me with an .mp4 file)
    Create new sequence from clip in CS6
    Apply warp stabilizer to section of the clip
    Render
    Watch - and the clip has the bottom 1/3rd cut off and the video looks out of focus.
    I cant for the life in me figure out what is going on! Please help!
    Thanks

    So, the first image is jsut before it gets to the stabilized section....
    Then, as soon as it reaches the selected area that has had the warp stabilizer applied the bottom is cut off!
    Am I missing something stupid here?
    Thanks

  • Warp Stabilizer Questions

    Hello,
    I have been using Warp Stabilizer in the CS6 release of Premiere Pro.  I've noticed 2 things:
    1)  I have a sequence with a clip using Warp Stabilizer effect that has been rendered.  If I add a clip directly after it and add a cross dissolve transition, it requires the entire first clip to be re-rendered.  On complex stabilizations, this can take hours to days.  Is there any way to have it only require a re-render of the impacted portion of the clip instead of the entire thing?
    2) If I set my work area to a complex clip (synthesize edges, detailed analysis) with Warp Stabilizer and render the entire work area, it appears the efficiency goes down.  I'm not sure how this is possible, but the estimates of completion time (and watching the elapsed time vs percentage compete) seems to indicate that it may exist.  If I segment the work area to smaller regions in the clip and work my way through it, the total clock time to complete seems to be much faster.  In one example, it seems to go from 80+ hours down to about 12 hours.  In both cases it takes 100% of the CPU (8 cores) and a large portion of the ram (8-9+ GB).  I believe the performance options are set correctly.
    Any suggestions?
    Regards,
    Jonathan

    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

  • Best way to warp stabilize between premiere cs6 and AE cs6

    I have a sequence with many clips, some with different speed (warp stabilizer doesn't work with speed in premiere CS6) whats the best way to stabilize these videos that are in different speeds?
    Another question, in CS 5.5 I used the warp stabilizer in 1080P clips on a 720p composition (with fit to composition) this way I warp stabilizer could zoom/crop the video without loosing quality. Now premiere CS6 has warp stabilizer but I can use a 720P sequence with a 1080p video, warp stabilizer won't accept it.So whats the best way to do this in premiere CS6? (to get 1080p video stabilized in 720p sequence) or I can just stabilize in 1080p and export the final video to 720p and I will have the same quality?
    Thanks

    You can make a new sequence from that 1080p file, stabilize it, nest it, then copy and paste it into your 720p project. This way you won't need to export it beforehand.
    I notice this topic is old, but it may help someone.
    Best,
    Bogdan

  • When is Adobe going to fix Warp Stabilizer?

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

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

  • 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.

  • 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.

Maybe you are looking for