Warp stabilizer not rendered on export

I've just exported a sequence and for some reason some of the warp stabilisation effects aren't rendered and the clip has an orange bar saying "Stabilizing" across the middle. Very odd!
Anyone have any ideas why it's done this? The sequence is over an hour long and was about to be sent to a client so it's a good thing I happened to stumble across one of them.

Perhaps you began the export before the initial processing was completed within Warp Stabilizer? Just a guess, have not encountered this before since I definitely wait on each application of that effect so I can judge the results.
Now I have to test that theory, I'm curious!
OK, just tried a test and that is exactly the issue! I dropped four short clips onto a timeline, added Warp Stabilizer to each and of course they each had the blue "Analyzing in Background" banner across them. I IMMEDIATELY went to AME and began an Export and sure enough, the blue banner was exported with the clips.
Depending on the clip, Warp sometimes makes the clip much worse and I would never export before checking the results on each clip I applied it to. The CMOS chip jello wobble sometimes becomes extreme like a funhouse mirror and then I just skip it!
Thanks
Jeff Pulera
Safe Harbor Computers

Similar Messages

Premiere Pro CS6 Warp Stabilizer not using GPU/CUDA why?

Hi,
I installed CS6 and tried the Warp Stabilizer, I undestand that only part 2 of the process (stabilize part) is GPU accelerated, but I can't get any acceleration from GPU, my GPU is idle at 1% usage (GTX580) and all the processing is going to CPU. The renderer/playback is marked CUDA so its not that.
Is there anything I'm missing?
Thanks

OK, this surprised me a bit. I have a state-of-the-art new PC with plenty of RAM, a fast processor and lots of cuda cores. See the specs here: http://www.stevengotz.com/
It took over 10 minutes to stabilize one minute of video - 1800 frames. It wasn't all that shaky to begin with, but it was handheld and therefore looks better after using Warp. There was one section that was so bad, I sliced the clip up and chose not to stabilize that part after the fact. So I thought that it might have added a little to the problem. But no. I tried just 180 frames of reasonably stable hand held video from the same clip and it took almost a minute.
Now, once the process was finished, I had no problem playing it back in realtime without rendering. But what is taking so long? I understand that there is a lot of work to do, but why isn't it using the power I have provided?
This is a screen shot of my resources about two minutes into the process.
I would love to know what I need to do to speed up this process. I get that it is working in the background. Is it possible to make it work in the foreground? I would not mind if it maxed out the RAM or the CPU or both if it would help.
edit: I just submitted a Feature Request to let Warp run in the foreground using every available resource.
Steven
Message was edited by: Steven L. Gotz to include additional information.

Themed Transitions not rendering in export to Quicktime

I just created my first imovie 09 project. I was using the Bulletin board theme and the transitions work fine with viewing in iMovie. However, when I *export out of imovie to quicktime or itunes not all the transitions render.* Especially the bulletin board transition. There are some other "standard" transitions that are not rendering either.
I am wondering if this is a bug or if maybe it is the settings like Frame per second and encoding that is some how cutting these transitions out. Since most of the transitions do render out to quicktime, I am going to guess this is a bug.
Anybody have a clue?

The file information shows:
Apple MPEG 4 Decompressor, 960 x 540, millions 16bit, 29.97 fps
I just watched the rendered quicktime again and noticed that some of the Bulletin board transitions did render later in the movie but at least one transition is not rendering. It is very strange and bit frustrating.
I am not sure what it could be since it shows in the imovie full screen preview.

Warp stabilizer not working with latest update

After latest update (updated 10/10) Warp stabilizer stopped working. Already stabilized clips in project show black / transparent in preview, besides small area left or right upper corner. Changing Video rendering from GPU acceleration to Software makes stabilized clip come back... however now it creates flickering to all stabilized clips. Deleting "Warp stabilizer" effect from clips removes flickering. What might help?
Editing with Lenovo Thinkpad, i7 2.4ghz, 8GB, Intel HD integrated graphics
Message was edited by: Mikko Lehvilä
Added picture

I'm experiencing a similar thing.
2014.1 (October Update) on OSX 10.9.5
For me, Warp Stabilizer is working on regular clips. But when I try to apply it to a nested sequence, the result is exactly as you describe. Video is fully visible while analyzing and stabilizing, but once stabilized it's just black (actually, I did some tests, and it's actually transparent).
I can replicate this even with codec-agnostic footage like bars & tone.
Adobe - what's up here?
Edit: sometimes I get the top-left-corner thing, and sometimes it's completely blank. Trying to track down the pattern.

Warp Stabilization not working on Premiere Pro CS6 or After Effects CS6

I've imported a 30 second clip both on Premiere Pro and After Effects. I am using CS6. I used a Canon 600D and my footage is 23.976 and 24fps. I've tried both frames to see if it made a difference. All what happens is that it says step 1 out of 2. It finishes and tells me to analyze again. It doesn't actually make it to step 2 so my footage doesn't change and its getting frustrating. No idea what im doing wrong. HELP PLEASE?

As Rick says, it looks like you didn't update all of your software.
What version of Premiere did you have before?
What version of AE did you have before?
What version of Premiere do you have now?
What version of AE do you have now?
Exact version numbers down to the last decimal, please.
In the future, I'd suggest NOT updating in the middle of important projects.

Warp Stabilizer not in Premiere Pro CS5.5

I can't find it anywhere. I've looked in the plug in folders and it isn't there. Is there anywhere I can download it from?

It is in After Effects CS5.5. It wasn't added to Premiere Pro until CS6.

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

Where is the Warp Stabilizer plugin located in After Effects CS6 program files?

I need to delete the plugin temporarily to gain access to my project because it constantly crashes on start up due to the Warp Stabilizer.

NOt sure if you can actually remove it,but it should be in the plugins/extensions sub-folder inside the AE install folder. Anyway, try the usual troubleshooting first before taking such a radical step that may destroy AE and require a reinstall. Flush the caches, open the project with capslock and remove the effect.
MYlenium

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.

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

Projects Not Opening with Multicam and Warp Stabilizer - "[..\..\src\TickTime.cpp-207]"

Editing a sequence with multiple nested multicam clips and warp stabilizer, if I close Premiere and reopen it, it says "Premiere Pro has encountered an error. [..\..\src\TickTime.cpp-207]" repeatedly until killed by Task Manager. I have restarted the computer, cleared the media cache and deleted preferences. I can import the sequence into another project and continue editing but if I close PPro I have to create another project and import the sequence again or I get the same error. Help!

Hi Kevin!
That is great news. I had a feeling the issue would be gone in the Next PPro. The issue can be easily duplicated by following these steps in CS6:
1) User warp stabilizer on several clips (like maybe 6 or more or so).
2) Take two clips and nest them and sync them for multicam on the same timeline as the stabilized clips (NOTE: these two clips don't actually have to be sync'd...just grab any two clips, stack them on top of each other, highlight them both and right-click and choose "nest", then right-click again and "enable" multicam.
3) Save project. Close project. Re-open project and you'll get the error.
If you do that in the NEXT version, does the error come up? Also, just while I have you...if you go into the settings of Warp Stabilizer, what is the default "method"? Is it still defaulted to "Subspace Warp" or did they smarten up and realize the option "Position, Scale, Rotation" is actually MUCH more effeciet causing less wobble and less cropping of the video 90% of the time? Just curious.
Coltom Media Productions,
I feel your pain. What also stinks is that the error pops up again when you export (or I should say when you queue) up the project into AME. I originally thought the number of continues equalled the number of warps applied but that's not always the case. Although, the more warp stabilizers applied the more times you'll have to hit continue. It often goes in numbers divisible by four. Why do I know all this crazy, useless info...hours and hours of trying to "solve" the issue. Every project I do, every single week has more than 100 clips that are stabilized and multiple multicam sequences so I often have to hit "continue" on the error 300-400 times or more on EVERY project. Can't wait til the next version!
To see more on this issue you can see the original post on it here (note that the staff has recently (and graciously) led the charge to help isolate and resolve the issue):
http://forums.adobe.com/thread/956692?start=40&tstart=0
And then also, it definitely made my "Top 15 list" here:
http://forums.adobe.com/thread/1179004
Good luck!!!...oh, one more thing...the project will open...you just have to keep hitting continue. Sucks, but again, hopefully it'll be resolved soon.

Warp Stabilizer error: Unable to acquire rendered frame

Hi,
I am trying to apply Warp Stabilizer to a clip. Analyze process starts but then halts after 15-20 frames and a pop-up appears "Unable to acquire rendered frame".
I have previously used Warp without any hitches.
Any ideas?
Thanks,
Richard

I too get this, sometimes not and the analyze just drops without a word, but most of the time I get the error. I tried on material such as: Red r3d, uncompressed fullHD/SD, mp4, canon 7D etc. pretty much all formats there is, so there isn't a problem with what type of files or what GOP structure it got. I cannot solve this even by creating a new project or reboot, I even reinstalled AE and the Matrox drivers, I tried unplugging the MXO2 mini but got the same result, so I'm pretty much done testing, I tried everything I can think of. I allocated RAM differently, shut of multiprocessing, enabled it, more RAM to few cores and then less RAM to more cores, increased cashe, disabled it.
Sometimes when I let the footage play out with RAM preview, the analyze gets to the end in the background, but whenever I just let it work for itself it drops.
So I tried everything and the error still persist. What should I do?

Can I export Warp Stabilizer Data?

I have two identical video clips, they match frame for frame, however one of them is under exposed and is a lot darker. Therefore it is a lot harder for warp stablizer to work.
Can I somehow export the data from the warp stabilizer on the clip that it works on to apply it to the under exposed clip?
I would use Mocha to stabilize the shot, but I am having difficulties with it, since it requires frames to match throughout and my shot is rotating.
Any help is greatly apprecaited TIA

If you have identical footage then you either had a motion control camera, and even then it's highly unlikely to be exactly frame for frame unless the rig was very big, heavy and expensive and your actors were robots because anything moving in the scene would throw off the warp stabilizing, or the camera was locked down and there was nothing moving in the scene. There must be some differences in the shots or there would be no need to work on the one that is under exposed.
There is nothing keeping from you from making exposure or color grading adjustments on the original clip then pre-composing or rendering a clean copy, and warp stabilizing that clip. I don't think anything else is going to work.

Warp Stabilizer Does not start.

I used Dynamic link from Premiere 5.5 to AE 5.5 Production Premium Bundle. The 4 minute project seems to be OK in AE until I used Warp Stabalize. AE Either freezes or there's a blue bar with "Stalizing in the background step (1 of 2) The CPU is not running more than 3% and nothing is happening it doesn't crash the OS. I'm useing 720x480 NTSC 29.97 mp4 clips from videos created in PPCS4. I exported a 8 sec. of one clip to DV does the same thing, nothing when Warp stabilizer is used.
I had the warp stabilizer working in another project a few days ago on this system. It was a 5 second NTSC Quicktime 4:2:2 720P clip.
8GB RAM, Windows 7 Pro 64 bit, NVidia GTX 560, Aero Off
Also is there a way to apply warp stabilizer to a few seconds of 1 clip and not the entire project that has been dynamic linked to AE?

Also is there a way to apply warp stabilizer to a few seconds of 1 clip and not the entire project that has been dynamic linked to AE?
You replace the segment with an AE comp and send that AE comp. That's even in the introduction to Warp Stabilizer video on Adobe TV, so I suggest you watch the video again. The rest is unclear, but I get the impression that you create a circular relationship somewhere by having the original DV and converted clips in teh same project. Anyway, if you change your approach, this should also not occur anymore.
Mylenium

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

Warp stabilizer not rendered on export

Similar Messages

Maybe you are looking for