Warp Stabilizer - focus / blurring issue

I have some Canon 5D Mk II 1080p (25 frames per second) footage. A 90 second long shot on a steadycam from the back of a car following a guy on a motor bike.
There is a bit of mild shake going on and so I tried Warp Satablizer in Premier Pro CS6.0.2 (Mac OS Mountain Lion), which smoothed the shot out quite well.
But it does generate a side effect of the shot almost going out of focus for a half second or so about every 4 or 5 seconds. Looking at the footage it's as if the frames are blurring into each other as the stablizer tries to work out whats going on. I tried reducing the Crop Less - Smooth More setting to 50% and that reduced the crop but still left with the focus issue.
Any tips on how to reduce this blurring effect.

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

Similar Messages

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

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.

Can warp stabilizer ignore a portion of my film?

I work at a film archive where we use a digital scanner to capture images from 35 and 16 millimeter film frame by frame. The result is a file with what we refer to as "overscan" where the perforations and some of the information from the preceding and following frames are visible.
This works very well and turns out beautiful results, but the film will often have a slight bounce to it. I've found that warp stabilizer works very nicely to reduce or even completely do away with this bounce on clips that have an immobile camera. I do not wish to stabilize camera shake (that wouldn't exactly be preserving the work), but I do wish to stabilize this bounce.
Is there a way for shakier footage, for example, a collection of home videos we've been attempting to stabilize, to be masked off in some way so that the Warp Stabilizer focuses only on the bounce of the film itself and not the shake from the original operator of the camera? I imagine there must be some way (without point-tracking, preferably) to focus the stabilizer on the perforations or some part of the film itself rather than the footage it contains.
I've looked at the videos where keylighting is used to "outsmart" the Warp Stabilizer's assumptions about foreground, but unfortunately that doesn't exactly work for my particular problem.
Any help is very much appreciated.

No, unfortunately not. At this point there is no way to differentiate between different types of shake e.g. by ways of additional trackers or mask paths like you can do in some plug-ins. It's an all or nothing thing.
Mylenium

Warp Stabilizer Output Issue

Ever since the update to Premiere Pro when I go use warp stabilizer all it outputs is a small rectangle at the top with a small piece of footage inside of it. I've tried tweaking the settings and resetting my preferences but it always comes out with the same result. It works out when I use After Effects, but that can be pretty inconvenient considering the render time and what not. What am I doing wrong here? Heres an image of the output.

Hi Gjhobbs13,
Please check the below discussion and check if it helps.
https://forums.adobe.com/message/6826226#6826226
Regards,
Vinay

Premiere Pro CC's Warp Stabilizer BUGS...see for yourself. (7.0.1 & 7.1)

I'd love to hear from Adobe Staff on this one. Hopefully they can focus on fixes over features for the next update, especially for one it's most touted effects.
Warp Stabilizer works great at stabilizing clips in Premiere Pro CC...but I'm beginning to learn that it's quite buggy. The two bugs below simply cripple the user experience when you use the effect a lot like we do. Here's a link to a sample project with just 2 clips (around 1 minute in length each) on two separate timelines with each clip stabilized using the Warp Stabilizer effect. It's only a sample/test project meant to show the issue which can be MUCH larger in a longer/bigger project. Relink to any longer media and you'll quickly see what happens when you have multiple warp stabilizers applied to a Premiere Pro CC project and how problematic it can be.
https://dl.dropboxusercontent.com/u/105331144/Warp_Stabilizer_SAMPLE_Project.prproj
See for yourself.
Two VERY Annoying BUGS and One Unfortunate Feature:
BUG #1: (It affects 7.0.1 and the new 7.1 Release/Update)
1) With GPU Acceleration Enabled and both sequences open, once the timeline render bar has turned yellow, hit save.
2) Now toggle to the 2nd sequence and you'll notice a delay/freeze as the render bar switches back to red and then yellow again.
3) Now toggle back to the other sequence and you have the same thing occur. Then, you can toggle back and forth with no delay...until...the project saves (or auto-saves) again...and then the delay/freeze will happen all over again.
4) Side Note: Even when you right-click on the sequence in the Project window, there's a delay. Right-click on a sequence with no Warp Stabilizers and the drop down list pops up immediately.
What's the Big Deal?: When you have tons more warp stabilizer effects applied to multiple sequences, not only does it take a while to save, but when it does, you are forced to wait while Premiere Pro freezes momentarily. This affects AUTO-SAVE too!!! The more warp stabilizers, the longer the wait. Our sequences have delayed up to 30-40 seconds depending on how much we've used warp stabilizer in each sequence. Imagine if you have Auto-Save set to every 30 minutes or less, well that means that every 30 minutes or less you'll be forced to stop while premiere freezes up for 30-40 seconds or so (depending on how much this effect is used). Other effects do NOT have this issue.
BUG #2: (It affects only the new October Release/Update of Premiere 7.1...this issue is NEW and does NOT occur in 7.0.1!!!)
1) Take the above project into Premiere Pro CC 7.1 (again, this does NOT occur in the previous 7.0.1 release) and hit FILE>EXPORT>Media.
2) You'll notice a delay while the EXPORT SETTINGS popup opens.
3) Toggle to different "FORMATS" in the export settings window and there's more delays every time the format is switched.
What's the Big Deal?: Again, this is a small sample project. When you have a much bigger project with lots more Warp Stabilizers applied to many more clips this "delay" can extend up to several minutes!!! Yes, on a recent project over an hour with MANY warp stabilizers applied to lots of clips, it took 7 minutes for the Export Settings window to pop up after hitting EXPORT>Media. And there was about a one minute delay now when switching formats. This occurs whether GPU Accleration is enabled or not. It ONLY occurs on Premiere Pro CC 7.1
UNFORTUNATE FEATURE #1:
We obviously use Warp Stabilizer A LOT. It's a great effect. The above bugs cripple the user experience. This last issue isn't a bug, but rather a default setting on Premiere Pro's warp stabilizer that should be changed. Within the settings of Warp Stabilizer there's a section called "Method". The default setting is "Subspace Warp". That sounds pretty cool. But in practice, and we have had lots of practice (eg. THOUSANDS of clips stabilized in just the last few months alone (no exaggeration)), we've found that switching the default method to "Position, Scale, Rotation" is a MUCH more effective way to stabilize a clip. Most of the time it cuts down on that "wobble" that you might see in complex moving clips...but more importantly, 9 out of 10 times it crops the video either the same or less than when you use the default method. By "crops less" I mean that the "Auto-Scale %" is less. Of those 9 times, I'd guess 7 or 8 of them would crop in on the video less while the other 1 or 2 times there would be no change to the Auto-Scale %. Less scaling = better.
What's the Big Deal?: Well, as cool as Subspace Warp sounds, our numbers don't lie. Again, we use this effect on HUNDREDS of clips every week. When you have to go into hundreds and hundreds of clips every week and keep switching the setting so the effect will work better, it gets old real fast. We end up wasting so much time doing this but it's worth it because the results are undeniable. Why not create a CUSTOM PRESET???! Well, that'd be nice if it worked...but it doesn't. The problem with a custom preset like that is that when you drop it on a clip, it doesn't activate/analyze the clip automatically so you have to manually go into the settings and hit analyze which negates any time saved. It's be great if the default "method" was simply changed to Position, Scale, and Rotation. Or at the very least, it'd be great if one could create a custom preset that would automatically activate/analyze the clip it's dropped on (just like the original effect does).
(BONUS FEATURE: It'd also be nice to have the ability to set a "max scaling %" too so you never crop in more than a preselected amount...but first things first...fixes over features.)
NOTE: I'm on a 2011 suped up iMac running OSX 10.8.5

[r]Evolution wrote:
Would it help to Render these Warp Stabaliized clips instead of leaving them in the sequence w/ the Effect applied?
Any way to "Batch" Warp Stabalize your media before editing so the effect is not needed during the edit?
Sounds like you guys could benefit from having your shooters use a "Stabalizer".
Thanks for the rendering tip rEvolution. Rendering the clips does help with BUG#1, however, I'm not sure if it would truly save us any time because of the constant need to render and rerender tons of very short clips with this effect as we make adjustments to the edit. Warp Stabilizer is GPU Accelerated so playback is really smooth which is great but why does saving a project have any effect on this and cause it to freeze up? And then it works great...until the next time the project is saved. Using any other effect, there is no issue (that I've found) when a project is saved or auto-saved.
Rendering unfortunately has no effect on BUG#2 in Premiere 7.1 (again, this bug/issue did not occur in Premiere 7.0.1)
Regarding "batch" stabilizing...I'm not entirely sure what you mean. We do stabilize dozens of clips at a time before editing because it's imperative for us to know which clips (the sections we've pulled) will stabilize effectively. And then once the longer edit is complete we end up pulling all the best shots from that long sequence and copy/paste it to another sequence to make a 2nd shorter edit.
To say we've gone back and forth about the use of stabilizers would be an understatement. The fact is that we've spent almost 4 years creating a unique way to shoot based almost entirely around the effectiveness of warp stabilizer. It's taken years of trial and error but our style of shooting effectively allows us to mimick and thus replace the need for stabilizers, sliders and cranes. The extra freedom allows us to get MUCH more varied coverage of live events. It's different, I know, but it's fun and rewarding having a unique style. Granted the extra work is passed on to the editing side, but it's worth it IMO especially if these issues were addressed/fixed.
Regarding the "unfortunate feature" I mentioned, I would be satisfied knowing the default method works great for others if one were simply able to apply a custom preset of the clip with the adjusted method and it activated automatically and began analyzing the clip without the need to manually go into settings and hit analyze. That would be nice.
Thanks again for your input.

Warp Stabilizer glitch

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

Although it's easier (more convenient) to accomplish the mission in After Effects, you can do it in PrPro as well:
1. Nest your shaky footage.
2. Within the newly created nested sequence apply Garbage Matte onto the footage to separate the woman on the foreground. E.g. draw Eight-Point Garbage Matte around the woman.
3. Create a Color Matte, pick e.g. R:7 G:7 B:9 to more or less match its colour to your footage background and drop this Color Matte above your footage with Garbage Matte.
4. Copy Garbage Matte from the footage and paste onto the Color Matte, delete or disable Garbage Matte on the footage. Optionally apply Fast Blur effect onto the Color Matte and dabble with Blurriness value so as to soften (feather) Matte's edges, adjusting Garbage Matte points if necessary.
5. Jump back to your master sequence and apply Warp Stabilizer onto the nested sequence, formerly your shaky footage. Set Stabilization to No Motion.
6. When done, switch to your nested sequence, disable the Color Matte eyeball, switch back to the master sequence, enjoy.

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.

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

OpenCL warp stabilizer renders in a small box in the top left corner

Hi everyone,
I have just built a new computer with the following specs:
Premiere 8.1.0 (81) build
i7 4790s haswell-refresh,
16gb Corsair RAM (4x4 DDR3 1600),
Gigabyte Z97MX Gaming 5
2x A-Data SP920 128gb SSD
Sapphire Radeon HD 7750
Windows 8.1 Pro CZ
Now I know this is a very weak configuration compared to other builds here, but I had hoped it would work fine for my amateur Full-HD workflow of clips mostly under 30mins.
The problem is; when I enable OpenCL acceleration, then all clips with warp stabilizer become about 1/4 of the preview window; it carries over to the final render. I have tried this both with the AMD card and without it (having OpenCL enabled with the Intel HD4600). No avail.
Now the funny part is that I used to have this same card running in my previous system; running on an obsolete Gigabyte UD3 with Core i5 750 in it and... IT WORKED! It was with the same Premiere version, running on the same OS. I've ditched that computer just a few days ago, but my new computer has this inexplainable problem.
The build is not the issue, as I had the computer tested and everything is stable with decent temperatures.
I am also having quite a lot of crashes while editing, but I think that's due to the infamous RedGiant suite which as I read on the forums is likely to blame. It's ok, i just need to save often. Would Neat Video be better? Does anybody know?
Another problem is the sluggishnes and lags when my clip reaches beyond 30 mins; I don't think that's ok, my videos produced with EOS M should not be anything demanding for this setup; when I monitor the ram usage, it never gets above 8gb (and yes, I have allowed CC to use up to 13gb of the total ram); also other resources are almost idle during editing.
The sluggishnes and lag is however even worse in SpeedGrade; over there when I move any slider, I need to wait for seconds! It somehow improves over time, but again, I just have an opinion now that this software suite is very very badly made. I am happy I am not using this to make money...
Please correct me if I'm wrong and any links that could help me resolve the problems are super-welcome.
regards,
Jan

Thanks for the report. We believe we have identified the issue and are working on a fix. For now the workaround is rendering in Software mode.
Best,
Peter Garaway
Adobe
Premiere Pro

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

Warp Stabilizer in Premiere Pro CS6

I was glad to see Warp Stablizer in PP so that it would not require AE. However, I found it to destabilize (no pun intended) Adobe Media Encoder such that the video would fail to render and I couldn't retry without restarting the computer. After about four or so reboots, I tried removing the Warp Stablizer effect from one of my nested sequences and suddenly the render succeeded.
FWIW, I don't know if it's related, but the sequence setting was 720p but the nested sequence that had the warp stabilization applied to only one clip therein was 1080p.
I do have GPU hardware acceleration enabled (not that Warp Stabilizer uses it that I know of).
Is this a known issue, and does anyone have any suggestions for a workaround other than going back to using AE a la CS5.5?
Also, on a side note does anyone know what process I need to kill after a failed render like this so that I don't have to keep rebooting? The dynamiclinkmanager process got rid of a hung Media Encoder on exit but didn't resolve the hung Media Encoder on restarting to render.
Jon

Have you tried rendering just that shot out to a file without the rest of the sequence? If you can do that then you can reimport that shot in to Premiere and use it 'ready-stabilized'.
We've exported several sequences that have lots of Warp Stabilizer clips and not seen the problem (yet!).

Warp Stabilizer crashes in After Effects CC (OS X)

Every time I try to use Warp Stabilizer, I get the following crash.
1. I select a track, open up the Warp Stabilizer VFX panel, and click "Analyze".
2. The blue "Analyzing in Background" banner appears. At this point, After Effects locks up and becomes unresponsive.
3. Looking in Console I see "com.adobe.Adobe Analysis Server.application[285]) Job appears to have crashed: Abort trap: 6". A crash report is saved. Here is a report: http://pastebin.com/RTnjNW28. Pertinent extract:
Application Specific Information:
abort() called
terminating with uncaught exception of type dvacore::filesupport::dir_create_exception: $$$/dvacore/filesupport/DirCreate=The directory '@0' could not be created. Please check the parent directory protection or permission rights.
4. Within After Effects itself, after several minutes, the error "Could not launch the Adobe Analysis Server. (515) (25 ::101)" appears. After Effects then becomes responsive again.
This is on a fresh install of After Effects CC, installed via the Creative Cloud app. Version 12.2.0.52.
I have tried this on 2 different Macs: a 2013 MacBook Pro and a 2011 Mac Mini. Both with latest OS X 10.9.1. I also tried on the preview release of OS X 10.9.2. I have tried with several different source videos, of different formats.
I have no virus scanner, or other such apps installed. I have tried disabling all running background apps. I tried turning off FileVault. Rebooted several times. Same result every time.
Is there any fix? Any help greatly appreciated.

It seems that this issue is caused by some folders being created with the wrong permissions set. This morning, a new version of the Creative Cloud desktop application was released that fixes this issue.
See this article for more information:
http://blogs.adobe.com/kevinmonahan/2014/02/12/prevent-crash-on-export-with-premiere-pro-c c-adobe-media-encoder-cc/
That article doesn't mention After Effects specifically, but I'm reasonably sure that the same fix will help here.
Let us know either way.

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.

Warp Stabilizer - focus / blurring issue

Similar Messages

Maybe you are looking for