Comments

Jim H wrote on 4/5/2009, 6:13 PM
Do you need to uninstall the old deshaker and VB before install?

Any serious bugs yet on this version 1.0.0.1?
Andy E wrote on 4/6/2009, 1:19 AM
Do you need to uninstall the old deshaker and VB before install?

Assuming you meant VD (VirtualDub) then no, you shouldn't need to.

Any serious bugs yet on this version 1.0.0.1?

None reported as yet.
ritsmer wrote on 4/7/2009, 1:32 AM
Any serious bugs yet on this version 1.0.0.1?

:-)

I have used the New Deshaker in 3 projects now.
Deshaked nearly 200 clips - and it works like a dream.
ritsmer wrote on 4/8/2009, 12:29 AM
Hi Andy:

a "nice to have" addition would be that if you select multiple media on the timeline then your script only deshakes the video media and not the other media.
I normally mix video with stills in jpg, bmp etc. and got a surprise seeing what Deshaker makes out of them - i.e. some of them were made 80 percent darker and at others Vegas hangs for ever trying to render after the deshake.

The video media could be avi,mp4,mpg,mpeg,m2t,mts,mov,wmv etc.
Andy E wrote on 4/8/2009, 1:12 AM
Shouldn't be too difficult - don't know why I didn't think of it before.

I could have done it as a quick fix for you but I'm right in the middle off adding a VirtualDub-style "Select video compression" dialog, so it'll have to wait until that's done for release.
zcheema wrote on 4/8/2009, 6:16 AM
Have installed as required in default folders.

But I get an error when running
(the old one still works)
Any clues, thanks...

"The located assembly's manifest definition does not match the assembly reference"

System.IO.FileLoadException: Could not load file or assembly 'Sony.Vegas, Version=8.0.0.217, Culture=neutral, PublicKeyToken=3cda94b1926e6fbc' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'Sony.Vegas, Version=8.0.0.217, Culture=neutral, PublicKeyToken=3cda94b1926e6fbc' ---> System.IO.FileLoadException: Could not load file or assembly 'Sony.Vegas, Version=8.0.0.260, Culture=neutral, PublicKeyToken=3cda94b1926e6fbc' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'Sony.Vegas, Version=8.0.0.260, Culture=neutral, PublicKeyToken=3cda94b1926e6fbc'


at System.Reflection.Assembly._GetExportedTypes()
at System.Reflection.Assembly.GetExportedTypes()
at Sony.Vegas.ScriptHost.ScriptManager.Run(Assembly asm, String className, String methodName)
at Sony.Vegas.ScriptHost.PrecompiledScriptManager.Run()
at Sony.Vegas.ScriptHost.RunScript(Boolean fCompileOnly)
jetdv wrote on 4/8/2009, 7:00 AM
Looks like you're running 8.0b and it was probably compiled under 8.0c. Update to 8.0c and I'll bet it runs.
Andy E wrote on 4/8/2009, 7:51 AM
it was probably compiled under 8.0c.

Yes. The Sony.Vegas reference the assembly is compiled with is 8.0.0.260 which is 8.0c

ritsmer wrote on 4/8/2009, 9:11 AM
I could have done it as a quick fix

Do not. It is only a "Nice to have" :-))

Looking forward to your next update.
Andy E wrote on 4/8/2009, 10:30 PM
zcheema,

I've released an update to (hopefully) allow use under 8.0b. If you haven't already updated to 8.0c and don't want to perhaps you could try it out. I cannot test it myself since I don't have 8.0b installed - I have simply recompiled the assembly against the relevant Sony Vegas references which I manually extracted from the Sony setup,

For anyone on 8.0c there's no point in installing since there are no functional changes.

1.0.0.2 9th April April 2009. Bug fix release.

Fix: Recompiled with Vegas 8.0b to be backwards compatible.

http://homepage.ntlworld.com/a.edmiston/deshaker.htm
MarkWWW wrote on 4/9/2009, 12:16 PM
I can confirm that the new version now works fine with V.8.0b. Many thanks.

Mark
Andy E wrote on 4/9/2009, 1:11 PM
Mark,

Thanks for that information. I'll make it part of the standard build.
zcheema wrote on 4/10/2009, 5:11 AM
Hi Andy, thansk for taking the time out and trouble to make a version for 8b, I have installed it it works like a dream.

I did go to 8c but had some render issues so came back to 8b and as 8b seemed OK realay so I have stuck with it.

version 9 next,

Once again Thank You.
JJKizak wrote on 4/11/2009, 7:26 AM
Installed on V8.0c in Vista 64. The old one worked ok but now I get at the 50% point "Error during script execution at line 1, column 3 variable "MZ" not found." Tried putting VirtualDub in program files, program 86 files and no change. The Deshake is in program 86 files. What is wrong? The old program was installed on the "C" drive under Deshaker. The file is HDV 1440 x 1080
JJK
Andy E wrote on 4/12/2009, 1:48 AM
Sorry but I'm slightly confused. Are you using the old one or the new one?

There is no variable MZ in the old script as far as I'm aware and I don't remember declaring one in the new one either.
JJKizak wrote on 4/12/2009, 5:39 AM
I'm using the new VirtualDub 1.8.8 with Deshaker download. I removed the old one (Virtual dub 1.6.18 and Deshaker on "C" drive) to a different folder. Does it matter which drive folder it is installed to like the old one had to be installed on drive "C" by itself. I tried it on program files and program 86 files and it gives that error message at the 50% point. The old one works just fine.
JJK
JJKizak wrote on 4/12/2009, 7:31 AM
The complete error measage:
"Null reference exception object not set to an instance of an object"
"at New_Deshaker.entrypoint.deshake (videoevent ve)"
"At New_Deshaker.entrypoint.NewDeshaker(object sender,eventargs args)"
JJK
Andy E wrote on 4/12/2009, 12:53 PM
Unfortunately, I don't run Vista on any of my boxes - only XP 32-bit, so I am unable to check whether this is a Vista issue. 'Perhaps someone else will be able to chime in here to confirm whether or not they are also having problems on Vista (32-bit or 64-bit) with deshaker.

Can you confirm whether you are using 1.0.0.1 or 1.0.0.2?

Edit: I have a minor update in the works. I think I'll delay releasing that slightly to add some proper logging to the release.



JJKizak wrote on 4/12/2009, 3:56 PM
I'm using 1.0.0.1 but have not tried 1.0.0.2 yet. Actually I have both the old version (John Meyer) and the new version installed at the same time. During the install I had to add to the New Deshaker target folder (x86) after the word "program files" so it would install to the proper directory. Had to do the same with the VirtualDub.
The old version still works fine.
I noticed that there is no "js" file installed with the New Deshaker so I can't compare the two scripts in notepad.
JJK
zcheema wrote on 4/13/2009, 3:12 AM
Have just tried the script on some slow motion and it seems to make the clip really smooth , much better then the Vegas way of doing it. I used a 505 reduction the ran the script and it looks really smooth.
JJKizak wrote on 4/13/2009, 6:05 AM
I tried 1.0.0.2 and it did not work, same results with 1.0.0.1.
JJK
Andy E wrote on 4/13/2009, 9:05 AM
Ok JJK. I'm working on adding some logging to the next release. A couple of things...

a) What is your "render to" folder?

b) You said at the 50% point you are getting the error. What exactly do you mean by the 50% point? (it might help show how far along the process is reaching before failure)

Andy
JJKizak wrote on 4/14/2009, 5:44 AM
Andy_E:
My render drive is "D".
The 50% point is the end of the first render and the error I believe is at the start of the second render. (VirtualDub second pass)

This may help---Getting the John Meyer version to work in Vista 64 all of the log file strings had to be changed in the js script file so that the file would be directed to a certain drive. Example: After a long string of numbers you see "deshaker.log" then another long string of numbers after that. Between those long strings of numbers insert "M:\\visvirdub\\deshaker.log" where "M" is the drive you want to use for logging and in my case it is "M". This was inserted in place of "deshaker.log" and the John Meyer script started working fine.

I hope this helps.
JJK
johnmeyer wrote on 4/14/2009, 7:57 AM
Between those long strings of numbers insert "M:\\visvirdub\\deshaker.log" where "M" is the drive you want to use for logging and in my case it is "M". This was inserted in place of "deshaker.log" and the John Meyer script started working fine.Yes, I think others reported that as well. Apparently Vista locks writing to the C: drive (or at least to the root) for security reasons.

As for the other errors, I sent a PM to Andy after I tested his script with Vegas 8.1 running under Vista 64. Initially it failed as was already reported, but I found that the problem was caused by his script not assigned an outbound render template because it failed to find familiar template names. The solution is to make sure to NOT leave the outbound render template area blank, but instead choose a template. The very last one listed (I think it says "default") is the uncompressed template and this is the one I would recommend choosing. If you choose that, Andy's script works just fine with 8.1 under Vista.

This is yet another instance of Sony Madison engineers changing things arbitrarily and breaking workflows, scripts, etc. This was not done to improve anything; it was simply changed. It is one reason I seldom visit or post here anymore, and gave up writing scripts.