Warp stabilizer freak out

[Ivan Myles]

To resolve in Premiere:

– Create a new sequence that matches the clip’s settings.
– Apply warp stabilizer to the clip.
– Insert the new sequence into you main timeline. You should be able to change scale, frame rate, etc of the embedded timeline as though it were the original clip.

If you are only positioning the clip (as opposed to warping), a better option is the motion stabilizer function in After Effects. It lets you control the target point, add/change the target within the clip, and edit the stabilization keyframes. In addition, the sequence does not need to be the same resolution or frame rate as the source footage. The process is as follows:

– Open a new project in After Effects.
– Import the clip and insert it on a new AE sequence.
– Apply the Tracker > Stabilize Motion effect. Modify/edit until you are satisfied with the results.
– Optional: Increase the project bit depth to 16- or 32-bit.
– Import the AE project to Premiere and insert it on your main timeline.

[Todd Vanslyck]

Actually the sequence does match the clip settings, that’s what’s so confusing. Otherwise I wouldn’t be able to apply the effect in the first place. I have a hunch it may have something to do with MB Looks. I’ve got another sequence not using Looks but MB Mojo and they’re not losing anything.

Dell T76000 Dual 8-core 2.4 GHz
NVIDIA Quadro 2000
NVIDIA Tesla c2075
Adobe Premiere Pro CS6
After Effects CS6
Cinema 4d r12

[Ann Bens]

Nest the clip with the effects then apply the Stabilizer.
See if that will help.

———————————————–
Adobe Certified Expert Premiere Pro CS6
Adobe Community Professional

[Dan Sakols]

Im very interested to hear how this plays out. Im just moving off FCP 7 because of frusteration with smoothcam, and plug ins like Mercalli and Lock and Load. Preliminary tests with PP and Warp look really promising…id freak out too if stuff starts jumping around or clips get radically zoomed in even for a light touch of stabilization.

dan

[Todd Vanslyck]

Nesting the clip did not work

Dell T76000 Dual 8-core 2.4 GHz
NVIDIA Quadro 2000
NVIDIA Tesla c2075
Adobe Premiere Pro CS6
After Effects CS6
Cinema 4d r12

[Jeff Pulera]

Nobody likes work-arounds and extra steps, but obviously the combo of effects applied don’t play well together. If none of the other suggestions resolve the issue, it might be easiest to do this – apply WS to the clips in question, and then EXPORT that area of the timeline to a new clip. Import that clip and drop it over the originals, THEN apply your other effects to that.

Others may chime in and say “Yes, but the generational loss and recompression….”. Probably not a Hollywood production and no one will notice. Been doing this kind of workflow for years for various reasons.

Thanks

Jeff Pulera
Safe Harbor Computers

[Todd Vanslyck]

I haven’t had too many problems with WS until now. I’m suspecting more and more it’s something to do with Magic Bullet Looks.
That dang plugin…

Dell T76000 Dual 8-core 2.4 GHz
NVIDIA Quadro 2000
NVIDIA Tesla c2075
Adobe Premiere Pro CS6
After Effects CS6
Cinema 4d r12

[Todd Vanslyck]

I’ve considered that but it’s such a royal pain in the arse! I have quite a few of them spanning over a large project.
grumble grumble

Dell T76000 Dual 8-core 2.4 GHz
NVIDIA Quadro 2000
NVIDIA Tesla c2075
Adobe Premiere Pro CS6
After Effects CS6
Cinema 4d r12

[Michael West]

I’ve used Warp Stabilizer on a 75 minute film transfer now with warp and weave problems. It was very difficult as it doesn’t seem to have scene recognition. I cut the project into scenes, applied Warp Stabiliser to one clip, adjusted, then turned off, copied and pasted parameters to all clips, then activated and rendered each clip one by one requiring a great deal of time (more than a month). One thing I found helpful was to click the detailed analysis box. Afterward I used the standard motion adjuster to position the clips back into frame lines; highly unsatisfactory.

[Casey Culver]

Any chance you’re shooting 60P (59.94) frame rate? I’m getting the same problem but worse.. But if I do 23.97, it doesn’t get screwy – wonder if there’s a frame rate bug…