When using the CS6 Premiere Pro Warp stabilizer it starts to analyze but doesn't start to convert after it has finished analyzing.
- Add the Warp Stabilizer
- Blue bar over picture shows up "Analyzing in Background (Part1 of 2)
- Prozess finishes but nothing happens (Source does not get corrected, orange bar never shows up)
- Another blue bar shows "Click Analyze to begin"
When pressing Analyze the process starts over again without any result.
The used footage is some mxf from a Canon C300
The used PC gots 8 cores, 32GB Memory
Update:
When using a different Clip, or if i shorten the problematic clip, it seems to work now ![]()
Info to problematic clip:
File Path: xxx.MXF
Type: XDCAM-HD Movie
File Size: 44.5 MB
Image Size: 1920 x 1080
Frame Rate: 25.00
Source Audio Format: 48000 Hz - 16 bit - Mono
Project Audio Format: 48000 Hz - 32 bit floating point - Mono
Total Duration: 00:00:07:05
Pixel Aspect Ratio: 1.0
Compression Type: MPEG 4:2:2
Because the first few files did'nt work at all and some only do by changing the lenght in the comp, which is not really an option.
I also marked the update status when i got it working for some files.
After all it still doesn't work for some files as it should.
I hope there's an fix soon to come...
Having the same problem with Warp and MXF (just applied updated patch files from Adobe this morning before starting.). MXF footage, 1250 frames. 8GBs RAM. Lots of RAM available according to task manager (2.5 GBs free). Can't get past the Click to Analyze phase (I ran analyze twice). So I went ahead and exported to MXF setting. Got to 99% and is stuck there, with 0 time remaining. However, TM shows it's still "running".
When I cancel nothing happens, CS 6 does not respond, eventuallly crashes, and I restart.., found the footage that was being converted in the Acobe Project directory, but it is not converted and shows Click Analyze to Begin banner on the whole bit (G). Fun!
Back to CS 5.5 and wait for fix?
Shot on MX105
XDCAM-HD Movie
File size 264.6 MB
Image size 1280x720
Frame Rate: 29.97
Compression type: MPEG 4:2:2
Duration: 42:15 (42 seconds)
Windows 7 Ultimate
SP1
Dell
Studio XPS8100 i7 870@2.93 GHz
8 GB RAM
CS 5.5 seems to be working fine, though I don't have PS installed on it, so have to move all footage needing to be converted to my Mac, PITA.
Thanks in advance. Hope this helps Adobe!
FWIW
Win7 CS6 24gb ram i7
During the weekend I used Warp Stabiliser on a single avchd clip of 4 mins..6 secs duration. ( Effect Default settings)
The entire process took approx. 12 minutes per minute of footage and was successful.
I exported the clip as an intermediate from the project I had set up just for this stabilising task..
Issue then was...it was taking a very long time to save the project...so I cancelled it. (Did not have time to wait for it)
Project size bloomed from 384kb to 17325kb
Disparity between the warp stabilizer in AE and the one in PrPro should reported as bugs so that they can be fixed. Inherent warp-stabilizer problems, like inordinately long rendering times or project size mushrooming should be reported as feature requests so that the effect can be optimized in future versions.
Warp stabilizer is a useful effect but it still has some serious limitations at this time. For best results, it's good to keep your clip size shorts and be judiciosu about what type of content you're applying it to.
Shooterz, my comment was not aimed directly at you. I only hit reply to your comment out of convenince. It's good to know what your user scenario was. I have some long clips (10-20 minutes) that I have tries to stabilize for essentially the same reason (because the represented one contiguous shot), and have had enormous difficulties getting them to complete successfully.
All: There are already bugs logged against such perfrmance limitations, which is why I suggested that those sort of things should really be logged as enahncement requests... but if you log them as bugs anyways, no harm. (I was going to clarify my earlier post as such, but for some reason the 'edit' option is currently unavailable to me on this thread.
The same here. The stabilizer works fine in After Effects. The same shot in Premiere does not give any result after the rendering. The rendered result is not transfered to the timeline. (the 3D cameratracker is not really working in either program)
EDIT: I found I need to render the timeline (by pressing enter) to render the effect again. So, the analyzer stabilizes everything, but doesn't apply the results unless you render the timeline, again.
This means twice the render time, compared to After Effects. I think it's a program coding error.
GeoffVane wrote:
The same here. The stabilizer works fine in After Effects. The same shot in Premiere does not give any result after the rendering. The rendered result is not transfered to the timeline. (the 3D cameratracker is not really working in either program)
EDIT: I found I need to render the timeline (by pressing enter) to render the effect again. So, the analyzer stabilizes everything, but doesn't apply the results unless you render the timeline, again.
This means twice the render time, compared to After Effects. I think it's a program coding error.
Check your Project size? Premiere has a problem with Warp Stabilizer where it will increase your project to unmanageable sizes. Premiere will slow down to a crawl.
So that is why my project file is heading for 600,000 KB on a 25 minute single timeline !
Project save/autosave is odd, sometimes it is OK, others it seems to take forever.
I too have Mercalli and get good results there. I find that Warp is successful only on fairly static clips, and even there, I have had some odd results, e.g. an unexplained zoom in mid-clip, and some alarming jello effects where there is moving water in the clip.
I could not help laughing at Jim's remark. I remember showing my 20 minute video of our trip to Italy to my brothers way back in 2002. In fact, it was my first Premiere project. I had the sense to cut it way down from 20 one hour tapes to 20 minutes. My oldest brother may have thought he was being a little insulting with his remark, but I was overjoyed. He said "It looks like a PBS travelogue." That was, of course, exactly what I was going for with the video and the voiceover.
In any case, I was able to use Warp Stabilizer this weekend on some footage of a children's birthday party. I can't show the results because of the subject matter. Not that they were doing anything wrong other than savagely beating a poor Super Mario Brother's pinata, but I don't have a release for them all.
I was a bit surprised at how long it took. I have a state of the art PC, and apparently the GPU doesn't help. I liked the results, but I sure would like to know what resources the effect utilizes. This is a screenshot of what it looked like about two minutes into the 11 minute process (the effect window estimated 8 minutes) for stabilizing a 60 second video (1800 frames). I think maybe I will start another thread to inquire about this. The CPU wasn't even breathing hard, the hard drives I am using for cache are in RAID0 - so should be reasonably fast. Hmmm. I wonder?
It depends on the footage you shot, however, perhaps if you slice the footage up into smaller portions - using natural breaks where a transition or breakaway to b-roll might take place, then you can apply Warp to shorter clips. Probably with a lot less problem. Give it a try. I read about doing that in the Help files - although technically it was for After Effects 5.5
-- Steven
I have 6 approximately one minute clips that need the warp stabilizer applied, then all six will be produced into one video. A comment was made to do each clip individually, save, and then combine the individually stabilized clips back into the project, or something to that effect.
I have the CS6 Master Collection, so what I need to know is some specifics as to what application is best to use to stabilize the individual clips, and what extensions to save-as before bringing back into PrPro for the final additions/transitions and then exporting the project.
I use a Windows 7 Pro CPU (64-bit OS, AMD Phenom II x 4 925 Processor 2.80 GHz), 8 GB RAM memory, 8 GB exFAT ReadyBoost. All clips were shot in HD. I'm somewhat green and your good advice will be much appreciated.
Thanks,
Ken ![]()
Ken,
That is not exactly what was meant by breaking up the footage.
Put all of the clips on the same timeline if you wish. Just apply the Warp Stabilizer to each one. It will take some time to analyze the footage, and you probably ought to think about what you want to do with any sections that are really too shaky to properly fix. Usually a little B-roll takes care of that, or use time remapping to create some slow motion for the area just before the problem footage, so you can possibly cut out the offending frames. Or use a snapshot.
One minute is a lot of frames. However, sometimes you have no choice.
Some footage is just too terrible to use. Don't try to save it. Just use the Stabilizer of slightly shaky footage. Slightly. OK?
No need to use any other programs. No exporting until the project is finished.
North America
Europe, Middle East and Africa
Asia Pacific