I'm using XP. Also I am curious about something. Under the "New Deshaker" installation instructions it says:
On first running if VirtualDub is in its default location, then the only other setting required will be the "Render to" folder for the temporary renders out of Vegas. Click on the Browse button to select a suitable directory. A deshake folder will be created under the temporary directory for these renders.
I am not sure what they are refering to...."Render to", because in Vegas there is not a "Render to", just "Render as", and no "browse" button. And there is nowhere in VD that I see anything about "Render To". I have an older version of VD and Deshaker (2.2) installed as a script, could that also be a problem.

Make sure your New Deshaker menu shows the script pointing to: C:\Program Files\VirtualDub\New Deshaker vds. It doesn't matter if you have the old deshaker script installed. They will both work OK.
JJK

I have no New Deshaker menu. If I want to deshake in Vegas, I select the clip, go to deshaker script, and enter, that's all. No menu is seen. If I go to C:program files/VirtualDub/VirtualDub, and bring up VD manually, there is the UI, but no Deshaker menu. I compared the old VD folder that I renamed, with the new folder, and there are some differences. In the old folder ther is a Jscript file (22 kb dated 5/25/07), and in the new VD folder there is no Jscript file at all. The following files are the ones that loaded into VirtualDub folder, when the New Deshaker/VirtualDub was loaded:
AVSETUP, MHTML DOCUMENT, VDICMDRV.DLL, VDSVRLNK.DLL, VDUB HELP FILE, VIRTUALDUB.VDI, COPYING, DESHAKER.VDS, VDREMOTE.DLL, VIRTUALDUB-COMAND LINE DRIVE, VIRTUALDUB...........ALSO DESHAKER.VDF (in the Plugin folder), and PROXY ON, PROXY OFF (in the Proxy Folder). It's not working on either computer whether it is stand alone or installed as a script though Vegas 8c.

steveandbelinda wrote: I select the clip, go to deshaker script

You mean: you select the "New deshaker" script?

yes, "tool/scripting/deshake" (through Vegas) then it runs and get the error

You have to load both "VirtualDub & New Deshaker" and "New Deshaker 1.1.0.1" . The 1.1.0.1 loads files into Sony\Vegas Pro 8.0\ Script which gives you the new menu. VirtualDub & New Deshaker files contain VirtualDub 1.88 and the Deshaker 2.4 pluggin and the New Deshaker vds file. The New Deshaker 1.1.0.1 file puts 4 files into the Sony Vegas Pro 8.0 script folder including a readme file.
JJK

I went to the New Deshaker website and downlaoded both the "New Deshaker" file, and the new VirtualDub file, and ran both of them, and what I have now is what I got from installing both of them. So should I delete all the VD and Deshaker files, new and old, and start over?
This is the website that I downloaded the files from: http://homepage.ntlworld.com/a.edmiston/deshaker.htm

I copied the New Deshaker windows file for Vegas 8 (first file listed), and the 3rd file listed (VirtualDub)

When you go to the website scroll on down to the "New Deshaker 1.1.0.1" which covers everything. The New Deshaker for Vegas 8 has been updated to 1.1.0.1.
JJK

steveandbelinda wrote: "tool/scripting/deshake"
means that you are selecting and running the old deshake and not the New Deshaker script.

Okay, I see what you are talking about. I installed the 1.1.0.1
Now I get the menu that you were talking about, but now I am getting a bunch of errors when I put a clip on the timeline/select it/tools/Scripting/Deshaker 2.. This is the error as it reads:

Despite planning for all possible contingencies Deshaker script had the following error:
System UnauthorizedAccessAcception: Access to path E://Deshaker is denied
at System IO_Error.Win IO Error (Int32 error code,string may be full path)
at system IO directory.internal createdirectory(stringfullpath, stringpath, directorysecurity dirsecurity)
at system IO.createdirectory(stringpath, directorysecurity, directorysecurity)
at New_Deshaker.entrypoint.deshake(videoevent ve)
at New_Deshaker.entrypoint.newdeshaker(objectsender, eventargs args)

I deleted all the old VD files and deshaker files, just in case there was something conflicting, but still comes up with these errors.
Even after deleting the old files, I still show the old deshake script in Vegas, and can still execute it. Deshaker 2 is also there too though.

I was getting a similar error message when I set outbound as uncompressed and inbound as NTSC widescreen. When I unchecked "Compress Inbound" the deshaker worked flawlessly. And after it worked that first time with uncompressed settings, I was able to compress inbound without any problems either. So now it's working fine.

I will go try that. Nope don't do anything for me. The box was already unchecked. I tried everything that I can think of. This is getting very very aggrivating. It doesn't even work as a stand alone on my other computer anymore either for some reason.

I figured what it was. The file that I was trying to deshake was on a cd that was left in the drive. I thought that the file was on the hard drive. BUT, I copied the file to the hard drive, put it on the timeline, and deshaked it, and when it is done the top track (deshaker one) dissapears, and the original file on the timeline says "media offline".
I go to my vdub render folder that I entered in the deshaker menu, and the folder is empty. This is wierd. Do I just give up and buy Mercalli? I like if free, but what a headache.

Mine is Deshaker.vds (not "NewDeshaker.vds") if that makes any difference.

The "keyletter" is the "r" at the end.

Old deshaking program everything is "deshake"

New Deshaker program everything is "...deshaker"

I deleted everyting that had to do with Deshake/NewDeshaker. Then re-installed VirtualDub & Deshaker.exe, and NewDeshaker 1.1.0.1
It seems to work, but upon entering a "Render To" directory, it does not work. It created a folder named "deshake" in My Documents directory. No matter how many times I change it, it goes where it wants, and that is to that deshake folder in My Documents. I did one clip and it did some deshaking, but with alot of pixelation. Now is there also any reason that I should install the NewDeshaker 8.1.0.2, and was the latest update?

As you can read half way down in this thread:

http://www.sonycreativesoftware.com/forums/ShowMessage.asp?MessageID=650939&Replies=45

8.1.0.2 is a bugfix release. Absolutely necessary.

Having used the deshaker/New Deshaker for years I can say that there is no pixelation at all in the deshaked output.
It is just deshaked to your settings (btw. standard settings do a fine job in most cases).
If you see some pixelation then it must come from a wrong setting in the "Compress inbound". Maybe try to deshake without Inbound compressing first - then you have the deshaked result in full avi on the TL.

Okay, I think that I have it ironed out, but still some issues. You said "If you see some pixelation then it must come from a wrong setting in the "Compress inbound". Maybe try to deshake without Inbound compressing first". The box that is labeled "Compress Inbound" is unchecked already .
Also, I set the "render to" directory to "virtualdub render files", and it still creates a "deshake" subdirectory. I really appreciate the time and patience you have spent with me on this issue.

:-)

What is your input media format? and what is your project format? and - at the end - what format do you render to?

Also, I set the "render to" directory to "virtualdub render files", and it still creates a "deshake" subdirectory.

(Back from a 2 week holiday, there seems to be slight more problematic activity on the Deshaker front than expected.)

Not quite sure what you mean by "virtualdub render files". Is that a folder on your system? Anyway, the script will always create a "deshake" sub-folder under whatever path you specify in the "render to" box. This is for the temporary files rendered out of Vegas - they will be deleted (assuming no problems occurr) on completion of the process and that's why it's empty.

The deshaken files, however, will end up in a "deshake" sub-folder under the folder your video file resides in (which is why it failed when you still had it on CD - the script couldn't create the "deshake" folder on the CD.

Are you still getting pixelation problems?

Yea still quite a bit. Not good enough that I would want to put in my finished wedding production. When I put a file on the timeline, then go to start the script, it adds another video track on top of the original. Once it gets done, the top video track disaperars, and the video track that is on the timeline says "Media Offline". I use the preset settings on the Deshaker menu, and I even bumped up the Motion Smoothness to 5000, and it's still real messed up. I just don't understand, I see video of people running and holding their cameras and it take most of the shake out. I have a little limp (very little), and can't even take that out. I put the clip on YouTube to let you see what I am working with (just as a practice piece)

I put your video into deshaker, and this is the result (link good for seven days):

Deshaken Video

Your video has some fairly "violent" camera movements, and you will notice that at the extremes of these movements that the video momentarily pops in and out of focus. This is a well-documented problem that is caused by the fact that when the camera moves using the standard 1/60 second shutter, the video frame is blurred, just like what happens when you don't hold a still camera steady when shooting at low shutter speeds. If you know you are later going to use Deshaker, try to shoot at a higher shutter speed (tough to do indoors, however).

I was actually pretty amazed how well Deshaker handled the camera jerking, the pans and the other issues. However, there are a few places where the edge compensation doesn't work perfectly. The "secret" is to go back to the original take, and then cut the event just before and after the problem areas. Then deshake each of the new events. The VERY important secret is that Deshaker always leaves the first and last frame of each event exactly as it was. Thus, you can always split an original (non-deshaken) event, deshake each of the new events, and they will join perfectly at the split.

[edit] If you can't play MP4 files, download the free VLC player and it will play them.