Nice tutorial! You should publish it, tis set to private.

Unfortunately I do everything you suggest, match properties, create sub clip etc. In fact the stabilization works fine. The problem still is that after I open the project again, the video is CRAP. Shakes, cuts, jumps as if the corrupt.

Again if I remove the FX, add it and apply it works just fine.

I store all my media in a G-Raid drive and I've tested this on 3 machines, two desktops and one laptop all fairly new Dell Precision workstaions and one Alienware :) all with Win 7 64bit and the problem is the same.

Can you try and see if this happens to you?

By the way, I just tried it on a new clip.

Simple 5 second video, add media fx stabilization and works great, save it and close.

Opening the project, again, only one 5 sec sub clip on the project with no other effects or tracks and the video is choppy.

Remove the FX, add it again and everything works great. Save close and back to the problem.

Did you make sure your rendered to the same properties as the Project Properties? e.g. 1920x1080 29.97fps Interlaced or whatever matches your source footage? (that will be emphasized in "Stabilization - the Sequel"). Here's my principle of stabilization: When stabilizing video in Sony Vegas 11 using the internal stabilizer or Mercalli V2, best results are obtained when matching properties of source footage, project properties and render properties. If render properties must be different, render to an intermediate or a new track.

In the meantime, you can read more here: First Look at the Vegas 11 Stabilizer

...Jerry

I re-read you replies & I think I mis-understood when I made my previous post. However, I made a test project, saved it, closed it, opened it again and everything is okay. ????

Edit: Hmmmm... I was able to duplicate your problem by rendering to a MainConcept mp4 and then playing the timeline - the stabilization is gone (????). However, I almost always render to a DNxHD intermediate and that did not exhibit the problem.

Edit2: Now I can't duplicate - boy I hate this problems happen sporatically. This is beginning to feel like the "Vegas replaced my footage" issue.

...Jerry

Just tried this, but even though you've saved all the stabilization changes to the VEG file, they DON'T get saved!!!

Open up the VEG file again, and the clips that you have just stabilized are jumping around all over the place - worse than before you "stabilzed" them.

Seems to be a similar problem to the one where it fails to save the time code adjustment.

What a rubbish piece of software v11 is. Sony should be hanging their head in shame.

Well, I'm continuing to test this. There is a cumbersome workaround - once the video event is stabilized, render to a new track using a quality intermediate like MXF or DNxHD, then delete the stabilized subclip from the timeline.

...Jerry

I just went back to using Vegas 10. WAAAAY better implementation of stabilization in V10 vs V11.

Sony, seriously, for cinematographers who can't afford high-end physical stabilization of all their shots, post-production stabilization is critical.

Please consider re-introducing the Vegas 10 stabilization in Vegas 11. Thanks.

Thanks for all the feedback. I'm glad to see I'm not the only one running into this problem. I guess for my simple videos I'll stick with Vegas studio or go back to Vegas 10 for the other stuff.

Happy new year!

At least in my case, I see what was happening. I'll be the first to admit I DON'T read the manuals until I encounter a problem, so this convoluted workflow may be described within it.

Unlike in V10, Stabilize is now apparently inserted in the FX chain, and remains there after a clip is stabilized. When the project is closed and then reopened, the Stabilize plugin seems to be applying data from the motion estimation pass to the STABLE footage, causing it to be "destablized" with opposite motion than the original footage. I proved this in my case by bringing the unstabilized footage back in on a new track.

Try just unchecking the Stabilize FX in the Media FX window (or removing the plugin completely) for the clip you applied it to, and see if the clip isn't stabilized like it was when you first rendered the effect. This solved the problem for me, although if this is expected behavior for using Stabilize, Vegas has a totally new problem IMO. At least in my case, the plug in disregards the motion estimation pass used on a clip while the project remains open, but when you close and reopen, it remembers that data and attempts to use it on an already stable clip.

And if this is just happening to some and not others - or inconsistently as in my case - this is every bit as dangerous as the "replace footage" bug if we have to worry about already applied plugins randomly processing or not processing events at whim.

EDIT: Shouldn't post till I test further. Closing the project after removing or unchecking the Stabilize FX returns the clip to its original UNstabilized state. Should have expected as much. Perhaps rendering to a new track is the only way to go for now.

Isn't the Stabilizied footage rendered somewhere when you click "apply?" I'm even more confused now. Deshaker has a folder where stabilized footage goes. Does Sony's version work without rendering?

I also wish stablizing worked like it use to. After saving the project and reopening it, video is choppy and un-usable. Must take off stablization and the media looks normal again without stablizing.

Rendering the clip with stablization to a new name and replacing the old clip is a work around but you can't do that if you have alot of handheld video.

I hope Sony puts it back to a usable tool.

I notice the same problem as well, I agree pro 10 stabbilize worked better.