VirtualDub Deshaker & New Deshaker Script

Kimberly wrote on 8/30/2013, 10:52 AM
Hello All:

I installed the newest Deshaker plug-in for VirtualDub 32-bit.

It works for frameserved HDV but not for frameserved AVCHD, which is what I'm mostly using these days. When I run the Step 1 Analyze pass, all I see is a black screen and nothing seems to be happening, i.e., it does not progress on a frame by frame basis. BTW, a big thanks to johnmeyer for the step-by-step Deshaker instructions here: http://www.sundancemediagroup.com/articles/deshaker_guide.htm.

Has anyone else experienced this? Should I try the 64-bit version instead?

I have yet to work up my courage and install the New Deshaker script thingy for Vegas. I like the nifty Deshaker interface in VirtualDub.

Regards

Kimberly

Comments

wwaag wrote on 8/30/2013, 11:37 AM
I use the newest deshaker all the time with AVCHD footage, albeit the script versions. Although a pain to initially set up, it is well worth the effort since you can select the events to be "deshaked", let it do it's thing, and the "deshaked" events will be added as Takes. For me, the 32bit version of vdub works fine. In the past, I've frameserved AVCHD footage (both 1080 60i and 60P) to Virtualdub without problems as well. As a first step, once you open the signpost avi file in VirtualDub before applying the filter, can you step through it and "view" the footage? If so, then you know the frameserving is OK and the problem lies within your deshaker settings. Good luck.

wwaag

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

Kimberly wrote on 8/30/2013, 11:50 AM
The problem is within the Deshaker plug-in. I also frameserve AVCHD to VirtualDub all the time.

Might have a go at the New Deshaker script if I can find all the particulars . . .
WillemT wrote on 8/30/2013, 12:23 PM
I just tried and FrameServer does not seem to be happy with the Deshaker filter at all (any file on the timeline for me), works fine for resize etc.

I have not used the Frame Server with Deshaker before so I cannot comment if it ever worked. I use a version of the rather old script by John Meyer which I changed to work with the latest versions of Deshaker and VirtualDub.

I do not think there is a version of Deshaker that works with the 64bit VirtualDub. Also the "New Deshaker" script does not work correctly with the latest versions of Deshaker and VirtualDub. You need to render to an .avi file using an available, in VirtualDub, codec like Canopus or Cineform (or uncompressed) and use that in VirtualDub/Deshaker.

Willem.
Kimberly wrote on 8/30/2013, 1:03 PM
Hey Willem:

I copied a 64-bit plug-in from the Deshaker site, and the site mentioned where to install it in your 64-bit VirtualDub folder, but I have yet to actually find a 64-bit VirtualDub! But to what end if VD doesn't like frameserving.

64-bit Deshaker Plug-in:
http://dl.dropboxusercontent.com/u/41612696/Deshaker_64.vdf

Still struggling with the best way to do the occasional stabilization without A) installing VP 10, or B) forking over huge sums of cash that I don't have to spare right now for Mercalli : ( . Maybe rendering an *.avi and sending it to VirtualDub is the least of all evils.

Regards,

Kimberly
WillemT wrote on 8/30/2013, 1:43 PM
I just had a look at Gunnar Thalin's site and yes, you are right. There is now a 64bit version for Deshaker. I will give it a try.

If you go to the VirtualDub site you will find the 64bit version, currently at 1.9.11 - it is the second one down. Last time I tried it, nothing (at least nothing I wanted to do) was working with it yet.

Try Deshaker with an .avi render and if it seems to do what you want, we can talk about the script. The price for this at least is right.

Willem.

wwaag wrote on 8/30/2013, 1:53 PM
Just tried it again on a short AVCHD-1080 60P clip and it's working fine for me. Project settings also 1920x1080 60P. I'm using VirtudalDub 1.9.11 (32 bit) with Deshaker 3.0. Once I open the signpost avi file, I add the deshaker filter, select pass one and then run "Run video analysis pass" from the file menu. Once completed, select pass two, select codec (in my case Cineform) and then Save as avi.

wwaag

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

WillemT wrote on 8/30/2013, 2:19 PM
@wwaaq.

Just tried it and it certainly works if you select "Run video analysis pass" from the menu. It does not work if you click the "Output Playback" (third one from the left) button.

Thanks for that.

Willem.
Kimberly wrote on 8/30/2013, 2:47 PM
Ha! a breakthrough (I think?) ! ! !

If I add 60i, it works.

If I add 24p or 60p and call it Progressive, it doesn't work. If I call it Interlaced, it works.

If I add 24p or 60p and call it Progressive, and then run the analysis from the menu, it works! (Well it appears to be working -- first pass analysis is running even as we speak).

How strange. But I cannot complain too much as the price is certainly right.
Kimberly wrote on 8/30/2013, 3:06 PM
@wwaag:

How to you select the render codec in VirtualDub? When I choose Save As AVI, I don't have that option.

Regards,

Kimberly
amendegw wrote on 8/30/2013, 3:17 PM
"How to you select the render codec in VirtualDub?"Sorry to barge in, but I just happened to stumble upon this thread. Try Video->Compression:



...Jerry

System Model:     Alienware M18 R1
System:           Windows 11 Pro
Processor:        13th Gen Intel(R) Core(TM) i9-13980HX, 2200 Mhz, 24 Core(s), 32 Logical Processor(s)

Installed Memory: 64.0 GB
Display Adapter:  NVIDIA GeForce RTX 4090 Laptop GPU (16GB), Nvidia Studio Driver 566.14 Nov 2024
Overclock Off

Display:          1920x1200 240 hertz
Storage (8TB Total):
    OS Drive:       NVMe KIOXIA 4096GB
        Data Drive:     NVMe Samsung SSD 990 PRO 4TB
        Data Drive:     Glyph Blackbox Pro 14TB

Vegas Pro 22 Build 239

Cameras:
Canon R5 Mark II
Canon R3
Sony A9

Kimberly wrote on 8/30/2013, 3:27 PM
Thank-you to Willem, Wwaag, and Jerry.

One of the really great things about this Forum is the willingness to help others. This pushes me to look for solutions beyond "It doesn't work, I give up."

Now I must fuss around with some stabilized media and see if it will give me the results I'm seeking. If the results are good, I'll be back with questions galore about the script.

Regards,

Kimberly
wwaag wrote on 8/30/2013, 3:30 PM
Glad it is working for you. I if you look at the documentation http://www.guthspot.se/video/deshaker.htm, you will see "To ensure maximum processing speed at all times, use File/Run video analysis pass instead."

Here is another tip I learned before using the scripted version inside Vegas (thanks to WillemT). At that time, I would deshake a region consisting of multiple events. The only problem is that if the end of one event and beginning of the next are very similar, deshaker sometimes doesn't detect the change and strange things would occur. To get around this, go into Vegas, change the time to absolute frames and then view Edit Details (alt-6). Then copy the column with the starting frame numbers for the events of interest . Using these frame numbers, the Deshaker Log file could be appended to "force" a new event to begin within Deshaker. Once appended, then run Pass 2. If memory serves me correctly (it's been quite awhile), I used Excel to convert frame numbers into the format readable within the Deshaker Log. If you have any interest, I can try to re-construct the exact procedure.

wwaag

Yes, I did use Excel. If there is interest, I will put the file on dropbox. It's really very simple.

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

Mark_e wrote on 8/31/2013, 3:32 PM
thx for thread :) for a free pluging deshaker has exceeded my expectations! Took this deliberately hand held shaky shot tonight and ran it through after reading up on best settings etc. just 7 secs of each but pretty impressive. (well I was impressed with it :) ) Had to use 64bit version of vdub and deshaker we getting errors with 32bit was working on 1080p uncompressed avi


Robert Johnston wrote on 8/31/2013, 5:12 PM
The "New" Vegas Deshaker script modified by John Meyer in 2009 is not fully compatible with the 64-bit version of VirtualDub 1.9.11. The command line parameters for VirtualDub have been updated by Gunnar, but the Vegas script has not been updated to reflect the changes. You would be passing wrong information from the script to VirtualDub.



Intel Core i7 10700K CPU @ 3.80GHz (to 4.65GHz), NVIDIA GeForce RTX 2060 SUPER 8GBytes. Memory 32 GBytes DDR4. Also Intel UHD Graphics 630. Mainboard: Dell Inc. PCI-Express 3.0 (8.0 GT/s) Comet Lake. Bench CPU Multi Thread: 5500.5 per CPU-Z.

Vegas Pro 21.0 (Build 108) with Mocha Vegas

Windows 11 not pro