Warp stabilizer flicker yosemite

estou usando o premiere pro cc 14 versão 2014.1 e o OSX Yosemite 10.10. Tentei exportar um vídeo agora que usei stabilizer em diversos clipes e em todos aparece um flicker. Estou usando os recursos da CUDA no projeto.

Hi Kevin,
I have the same problem as RafelRosa, but the solution you name here doesn't solve the problem.
My specs:
Macbookpro 15 inch retina end 2013,
2,3 ghz i7
16 gb ram
nvidia GT750M 2gb
OSX 10.9.5

Similar Messages

Warp Stabilizer flicker, software renderer does nothing

I started this project on CC 2014, then migrated it up to CC 2014.1. I have tried exporting a couple sequences from it multiple times, with different output codecs (uncompressed, Cineform, H.264), and all of the results are the same: flickering video and noisy audio.
I have isolated the flicker to the Warp Stabilizer-effected shots, but no sequence setting changes or conversion to Software renderer over CUDA renderer makes any difference in the output. The audio also outputs as digital noise (sounds like when you listen to a data CD in an old CD player).
It is not an option to go through and re-add all of the Warp Stabilizer effects to see what different that makes, there are too many of them on the various clips in the project.
This affects both Premiere AND Media Encoder, so it's looking very difficult to get a quality render out of this.
Please help!
====
Windows 7 64-bit PC, latest security updates
Intel Core i7-3930K CPU
64GB RAM
NVIDIA GeForce GTX 670
CC 2014.1

Hey Kevin here is my info. Let me know if I can further assist.
PP 8.1.0 (81) Build
Windows 8.1 with all the latest updates
Source footage is Canon 5D MkIII 1080p30 all-I & Gopro Hero 3+ Black 1080p60 protune
I do get an "unspecified drawing error" sometimes when applying Warp Stabilizer but not all the time
WS worked fine until I updated from CC to 2014
I'm not running any other software besides the rest of the Adobe suite. I sometimes have Chrome open while editing.
I use Red Giant Magic Bullet looks quite a lot. I also use Neat Video noise reduction, Boris Continuum, and Twixtor.
System Specs:
Core i7-4770K, Gigabyte Z87X-UD4H-CF, 32GB RAM (Crucial BLS8G3D1509DS1S100 DDR3-1600), MSI GTX 970 Gaming, Samsung 256GB 840 Pro SSD (system), WD 3TB 7200 (Media), Seagate 2TB 5900 (Exports/Cache/Previews). The current project I am editing off of a 2TB WD Passport drive via USB3.
I'm using MPE GPU acceleration. When I use software only I actually get a lot more render errors and the flicker worsens.
Previews look perfect only on final output do I see the problem. I have tried rendering with the "use previews" box checked thinking that would help but it makes no difference.
Hope we can get this solved!
Edit:
I also get an "unknown exception on frame 0 in Warp Stabilizer" error sometimes when applying WS.

Warp Stabilizer bug in new Premiere update

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

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

Warp Stabilizer Causing Jumping?

I am new to Premier Pro but I have messed with it some here and there. I have a video that is taken using a hand held camera and is at times a bit shaky. I attempted to add Warp Stabilizer (using default settings) but when I render the video it has a jumping or flicking motion. If I remove the warp stabilizer it doesn't do this.
Is this a side effect of the stabilization and how do I solve this issue?

Is this a side effect of the stabilization and how do I solve this issue?
It would be called 'Warp De-Stabiliser' if this was meant to happen!
You may need to do some more trial and error testing with your particular footage. Settings.
BTW there is a practical limit to how effective these stabilisers can be.

Flickering video with Warp stabilizer

Hi all,
I have a problem what more of you maybe have seen the past month, the flickering with warp stabilizer.
Now i already changed the renderer setting in project settings into Mercury Playback Engine to Software Only, but this didn't solve the problem.
My specs:
Macbookpro 15 inch retina end 2013,
2,3 ghz i7
16 gb ram
nvidia GT750M 2gb
OSX 10.9.5
Will update to Yosemite solve it or not?

Hi Dave
I solved my problem with the next 2 things:
- changed the renderer setting in project settings into "Mercury Playback Engine Software Only
- changed the renderer setting in media encoder into "Mercury playback engine software only
Hope this will solve your problem to.

Warp Stabilizer analysis process stopping and never ends (AE CC 2014)

I'm running the latest 2014 AE CC and I've been getting this issue running Warp Stabilizer on my clips. Intermittently, warp stabilizer analysis process would stop at certain frame and never ends. I have to quit / kill AE.
I'm running AE on 15" retina macbook pro 2013 with dedicated nvidia 750M video card, 16GB of RAM and plenty of disk space (over half a terabyte left), running Yosemite 10.10.2.
Has anyone experienced this? How do I solve this issue?

"During the analysis and solving stages, the Warp Stabilizer effect and 3D Camera Tracker effect use memory outside of the pool shared by After Effects and Premiere Pro. Therefore, you can allocate more memory to the analysis and solving phases for these effects by increasing the RAM Reserved For Other Applications value in the Memory & Multiprocessing preferences."
Thank you for that link. I'm going to check the "RAM Reserved For Other Applications" and increase the value if it's too low.

Dynamic link warp stabilizer 5.5 issues

Been messin around with the demo while I patiently wait for my upgrade to 5.5 and I've come across an issue with the warp stabilizer when sending multiple clips from the timeline to and from PPro 5.5. If I send out a clip, use warp stabilizer in AE and save the project the results are fantastic and it's right there on the timeline. Groovy.. Until I send another clip out. The second clip looks great in AE... stabilizes fine. Save project as new name in AE, exit... back to PPro and the clips will be the same! It'll duplicate the first stabilized clip! Sometimes I can delete the instance from the timeline, and drag the AE comp from the bin back to the timeline and it'll work until I do another clip then it'll be a duplicate again. Also, sometimes it'll flicker from one comp to the new comp and back again. Like it's confused about which comp to play in PPro. I'm hoping that when I export it'll be fine, but this seems quite serious.
I've tried dumping the cache, cleaning out the project, saving the AE comp projects to different folders and drives. Doesn't seem to matter.
Oh... btw.. specs:
i7 970
Asus P6x58D-e
24GB G-Skill 1600 kit
C: Revodrive 2 120GB SSD
D: WD Black 1TB for apps (not Adobe apps, they are on the SSD)
E: WD Black 2TB for video
I: Removable dock with 1TB Samsung spinpoint F3
F: LG BDR
MSI GTX 560 Ti OC (Works great with MPE modified .txt file!)
Win 7-64 Pro (because of 24GB)

This bug has nothing to do with Warp Stabilizer, it affects all DL's and has been around from the beginning.
It is a PITA. If you keep all your compositions in the "same" AE project it seems to work better. If you do a "save as" and rename AE project the bug will appear again.
Also DL's are always "un-linking" for some reason in CS5, CS5.01, CS5.02 and CS5.03.
I hope CS5.5 fixes this issue.

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 VFX, did you know

I have been using After Effects 5.5 [AE] for a while and this is about Warp Stabilizer is After Effects CC [Ae]. Yes Warp Stabilizer in [Ae] is about 3 times faster that [AE] and also offers some very good added features. Sometimes you need the added features, other times you do not.
But did you know:
While you cannot run multiple instances of [AE] or [Ae] on a single computer, if you have [AE] and [Ae] both installed, you can run both of them on a single computer because they are separate programs. So now you can do two things at once including Warp Stabilizer.

Yes, both Warp Stabilizer and the 3D Camera Tracker run as separate, external processes that send their results back to the main After Effects application when they're done.
Details here:
memory and storage tips for Warp Stabilizer and 3D Camera Tracker
Regarding the speed improvements: You say that you've noticed a 3x speedup. We've found that the speedup varies a lot depending on the characteristics of the footage being processed, so I wouldn't count on it being 3x in all cases. I think that our marketing materials ended up saying that the speedup was ~80% (so nearly a 2x speedup) across all of our various tests.

Steps to send a clip to AE to utilize Warp Stabilizer VFX then back to Premiere Pro CC

So I use Warp Stabilizer for about 200 clips per project. It's effectiveness has shaped how I shoot. It's awesome. Now there's VFX in AE...Can someone layout the steps involved in the following:
a) Taking a clip from Premiere Pro CC and sending it to After Effects CC (I'm not that versed in using AE having not used it in quite a while)
b) Then how to apply the new Warp Stabilizer VFX (I assume just go to effects>distort>WarpStabilizerVFX ???) ... (if there are tutorials on how exactly to use it, especially detailing exactly how to utilize the new feature of isolating what in the frame is to be stabilized that would be great too)
c) Then how to send it back to Premiere Pro CC. (I'm guessing I just save it and let dynamic link take care of the rest?)
I've tried right-clicking on a clip and selecting "replace with AE composition" (is that what I should do?), then applying the effect but I get a "warp stabilizer VFX analysis doesn't work with Collapse Transformations" message so I stopped. If it makes any difference, the majority of my footage is shot at 60p and then interpreted and edited at 23.976fps. Thanks!
NOTE TO STAFF: I've said it before and I'll say it again as someone who uses warp stabilizer several hundred times per week, I still think the default "method" in the settings should be "Position, Scale, Rotation" instead of Subspace Warp because it works FAR better (less wobble and less scaling about 90% of the time). Can't help myself I had to bring that up again here.

a) Select a clip in PrPro timeline, right-click and choose 'Replace With After Effects Composition'. Take care of handles if you might need them (that's rather general tip).
Warning about Collapse Transformation switch indicates that you have 'Scale to Frame Size' option enabled for your clips in PrPro timeline. If that was done intentionally, you can simply toggle the Collapse Transformation switch (small sun icon) off. If not, rather disable 'Scale to Frame Size' for your clips in PrPro timeline.
b) Quite a boring but covering almost all necessary details tutorial on basic work with Warp Stabilizer in AE CC from Adobe TV:
Some advanced techniques from Lynda.com
and Mathias Möhl:
c) When you're happy with your work in AE and going to lock it, render a digital intermediate out of AE, import it into PrPro and replace your dynamically linked composition in the timeline with that DI (see this good old thread on Dynamic Link workflow, pay attention to Todd's comments).
If you leave the 'Include Project Link' checkbox in the Output Module Settings dialog enabled while rendering your DI, you can easily get back to appropriate AE project so as to maybe tweak some settings: just select your DI in PrPro timeline, right-click and choose 'Edit Original'.
Mind the bloating issue, keep the amount of applied Warp Stabilizer instances in a single AE project reasonable.

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.

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.

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

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

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

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

Warp stabilizer flicker yosemite

Similar Messages

Maybe you are looking for