Andy E's New Deshaker

Grazie wrote on 5/2/2009, 2:37 AM E's new Deshaker[/link]

The Easy Menu has passed the "Grazie-Test" for simplicity and accessibility . . .

ANDY thank you . . and of course THANK you john Meyer for testing and assisting Andy . ..

What a Team we have with us . . And Vegas - 'cos of all the Team-Vegas it just gets better and better . . !!



Andy E wrote on 5/2/2009, 12:38 PM
There's now a version that fixes a couple of issues.
Golfer wrote on 5/2/2009, 5:53 PM
Andy, is this update for 8 only? Or will this work for Vegas 7 also.
UlfLaursen wrote on 5/2/2009, 10:34 PM
Thanks for making it and sharing it :-)

Jim H wrote on 5/2/2009, 11:08 PM
This plug-in is so simple it's crazy. I just ran it on some really bad hand held video with lots of camera motion tracking a runner just to see what it would do. I've been using Deshaker for a while now (since Vegas V4 I think) Pretty amazing. Seems much faster and very stable. Andy, has there been other improvements other than just a conversion for V8?

Thanks for doing this. Here's the results of my experiment ( I didn't crop it so you can see the deshaker in action):


Andy E wrote on 5/2/2009, 11:11 PM
is this update for 8 only? Or will this work for Vegas 7 also.

Currently only for 8.0b & c. It won't run under 8.0a either.

However, I am thinking about seeing if I can get it working under Vegas 7 since the original Deshaker script did.
Andy E wrote on 5/2/2009, 11:17 PM
There have been some additions to the filter itself - it's now at V2.4. The new parameters are:

Discard motion of blocks that move greater than 1000 pixels.
Remember discarded areas to next frame
Rolling camera percentage

In addition, the improvements in the filter's multi-threading/multi-processor capabilities have made it run much quicker (as you've noticed).

There's some other stuff as well which you can read about here:

The original Deshaker script had V2.0 in it, so it's anything after that.
Jim H wrote on 5/3/2009, 12:01 AM
Thanks Andy.

I thought it would be neat to render both versions side by side or one above the other as the case may be. I've seen people post some really strange aspect ratios on Vimeo so I thought I'd try it. The original project was 1440x1080 so I doubled the height and cut the whole thing in half to reduce the file size. So the new project was 720x1080 rendered it at 720 x 1080. I didn't change any other settings yet the rendered video looks squashed in from the sides. This sort of problem always baffles me. Anyone got a clue what I did wrong?

I think it would be fun to experiment with "banner" video, but it's no good if my video gets distorted.
Jim H wrote on 5/3/2009, 12:07 AM
BTW, when I activate the deshaker script it launches right into the process without any input screens. How does one employ the various options when using as a vegas plugin?
wm_b wrote on 5/3/2009, 1:00 AM
When I installed this version it put a new script in my scripts menu called New Deshaker. Maybe you just selected the previous Deshaker script.

ritsmer wrote on 5/3/2009, 1:08 AM
Jim: are you sure that you use the New Deshaker script with a D-icon in front of it in the Vegas Scripting drop down menu?
douglas_clark wrote on 5/3/2009, 4:17 AM
Jim H: The colors (especially reds) look very oversaturated in your "deshook" version, compared to original. Are you using a levels, curves or color corrector fx before and/or after using Deshaker? Or is Deshaker causing the color changes?

I have experienced level/color changes going through Deshaker, on digicam MJPG video footage. This may be due to color space (Studio RGB vs Computer RGB) for the input video.

Does anyone know if VirtualDub and/or Deshaker are assuming Studio RGB or Computer RGB for the input video, or doesn't it matter?

Home-built ASUS PRIME Z270-A, i7-7700K, 32GB; Win 10 Pro x64 (21H2);
- Intel HD Graphics 630 (built-in); no video card; ViewSonic VP3268-4K display via HDMI
- C: Samsung SSD 970 EVO 1TB; + several HDDs
- Røde AI-1 via Røde AI-1 ASIO driver;

JJKizak wrote on 5/3/2009, 5:12 AM
Uncheck the "Progressive Interlaced option". And make sure your script points to the vds file in VirtualDub folder.
Jim H wrote on 5/3/2009, 7:12 PM
Doug, I was playing with the saturation adjust effect on the master track that's why the reds are blown out. Not sure if deshake doubled the effect or not...could be.

I was using the old deshake script. funny, I did not think it would work in v8. I tried the correct script with the "D' icon for New Deshaker and I did get the options dialog.

So do you think the old script still worked in v8 because the new deshaker was also installed?
TLF wrote on 5/3/2009, 11:37 PM
It doesn't work for me. It does everything it should, but Vegas reports the file as 'Media Offline'. I can locate the file, but Vegas can't play it.

Andy E wrote on 5/4/2009, 1:48 AM
In your Vegas Pro 8 directory (C:\Program Files\Sony\Vegas Pro 8.0) there should be a file called "New Deshaker.log". Either PM me or post the contents in the relevant thread in the Vegas Script forum ( and I'll take a look.

Grazie had a similar problem (which might be linked to different codec choices out of Vegas to VirtualDub and back again). I tend to use only uncompressed in and out .

TLF wrote on 5/4/2009, 6:23 AM
It seems to be related to the resultant file type. KM Player will replay it without any problems, and looking at the media properties it looks like it YUV. Don't know why Vegas won't play it. I suspect I may have to reinstall vegas...