Possibly new faster deshaker

ritsmer wrote on 3/30/2009, 11:01 PM
Gunnar Thalin has released a new version (2008-11-15) of the great deshaker.
I just downloaded and tried it: because of the change to multiprocessor support it ran 3-4 times faster than the old version on my machine - and also it did not make all other apps unresponsive for long times.

Could one of you script gurus (John Meyer?) possible change the famous John Meyer Deshaker script to work with the new version?
it will mean surprising performance for all.

(I also posted this in the Vegas Script forum)

Comments

Andy E wrote on 3/31/2009, 12:21 AM
Hi,

Long time lurker, first time poster. I'm just in the process of testing a rewrite I've done of the Deshaker script that uses the latest VirtualDub version (1.8.8) + deshaker (2.4) combination.

I've added a user interface to it to allow changing the parameters (and saving the changes). There are a few enhancements I was planning to make to it including presets, the ability to apply a different preset to a particular event and also mimicing the VirtualDub compression dialog. At the moment it defaults to uncompressed or you can provide a fourcc code (e.g. "dvsd" for DV-AVI) but can't configure the encoder).

To circumvent the latter, you can optionally compress inbound via a Vegas render using a template of your choice and that will be added as the take instead of output from VirtualDub.

I was going to wait until I'd finished all of the above but if there is interest I could release what I've got in the interim in the next day or so. I'm just completing a DVD that uses it in anger for the first time.

It may also be possible to replace the Deshaker.vdf in the plugins directory with the latest version and use it "as is" with the old script (take a copy of the old one first). The new parameters added by the latest filter are all at the end of the list of 1s and 0s etc.

I'll release it on the scripting forum rather than here.
JJKizak wrote on 3/31/2009, 5:24 AM
AndyE:
Will you add the log file changes for it to work in Vista as we had to do?
JJK
Andy E wrote on 3/31/2009, 5:55 AM
If you can point me in the direction of these required log file changes I'll happily do so :-)

(although I won't be able to test anything on Vista as it's XP only for me at the mo')

OK. I've done a quick search. The temporary directory for rendering to (out of Vegas) is part of the setup dialog for the script itself (along with templates, virtualdub location etc). The log file location is part of the Deshaker filter setup.

Upshot is these locations can be specified before actually kicking things off.
JJKizak wrote on 3/31/2009, 6:21 AM
In the Deshaker script there are 12 very long lines with the word "log" somewhere in the middle with numbers after it. Change and insert the wording preceding the word "log" to read beginning to the drive you want to log to to "D:\\visvirdub\\deshaker.log". The drive in my case is "M". You must still use the wording at the beginning and end of each line which is extensive. Check a previous thread dated 2/7/2008 9:07:38 PM from John Meyer.
JJK
ritsmer wrote on 3/31/2009, 6:37 AM
Hi Andy -

I would be grateful to get a copy of your work at its present state -

Thanks
Einar Ritsmer
tonyatl wrote on 3/31/2009, 8:28 AM
What work flow do you use? Take the raw file deshake it thru virtual dub and run it thru vegas?
Andy E wrote on 3/31/2009, 8:51 AM
As per my post above, the location of the log file can be overridden from its default which in this case is "the current directory". On XP when running this saves the log in the same directory as VirtualDub rather than the original script which specified the root of the C: drive.
Tom Pauncz wrote on 3/31/2009, 5:10 PM
Hello Andy,

I, too, would be most interested in your work as its right now. A copy or a link would be much appreciated.

TIA,
Tom
Andy E wrote on 4/1/2009, 5:50 AM
I shall be setting up a download page this evening (UK time). I'll post a note here but the link will be in the Scripting forum.
dreamlx wrote on 4/5/2009, 1:08 AM
Hi,

I have not yet tested your script, but I have read the webpage. I will test it soon. I have seen that on the web page you refer to the orginal script. Remember to read the disclaimer of the original script in case you want to commercialize this one. Also I would be happy to see somewhere on your webpage and in your script that the original script was written by David Arendt and that there have been many enhancements by John Meyer.

Bye,
David Arendt
Andy E wrote on 4/5/2009, 2:51 PM
Hi,

David,

It's not in my nature to attempt to make money off the work of others that was provided free of charge. There will be no commercialisation of what I've produced.

Your comment is a fair one and I'll add some suitable wordage to the download page and also an about box on the software that thanks the original authors for their efforts.

Andy.
Brad C. wrote on 4/29/2009, 4:51 PM
Need some computer help again.

After downloading the .exe's I go to unzip them to their predestined locations in the program files folder with winzip self-extractor but I keep getting an error:

Could not create "C:\Program Files\VirtualDub" - unzip operation cancelled.

It did the same for New Deshaker 1.0.0.3.

Am I doing something wrong? Any help or work arounds would be appreciated.
Andy E wrote on 4/29/2009, 10:48 PM
Brad,

It sounds like WInzip doesn't have permissions to create the VirtualDub folder

New Deshaker goes in C:\Program Files\Sony\Vegas Pro 8.0\Script Menu by default. No need to create this folder since it should already exist.

What operating system are you on? Vista 64?

32-bit programs (AFAIK) are placed in C:\Program Files (x86) instead of C:\Program Files.

Can you navigate to where Sony Vegas Pro is installed on your computer and locate its Script Menu folder? Extract the files to that location.

Also VirtualDub can be installed anywhere as long as you set up New Deshaker to point to that location.

Hope that helps.

Andy.
jabloomf1230 wrote on 4/30/2009, 5:41 AM
The best thing about the plug-in is the rolling shutter correction. It's now been optimized, so that you can adjust the option, depending on the make and model of your camcorder.