Log in

View Full Version : Strange error in VDub 1.6.10


STC-Fan
20th September 2005, 17:03
I'm attempting to carry out a 2-pass XviD encode of an AVI I capped from my graphics card's S-Video VIVO port, and every time I start executing the jobs, I recieve the following incomprehensible error on both passes:

http://homepage.ntlworld.com/menace-59/vdub_error.png

Throughout this I've been using the Analogue Capture Guide on this site, and since it didn't mention this error, I had a search on these forums (and the official VDub forums, and Google) for that error message, but I couldn't turn up anything. The funny thing is, I've actually managed to do this before, it's just that every other time I've tried, I get this error. Also, I just decided to hop over to a beta version of XviD (1.1.0 beta 2, Koepi's build), but I don't think that's it, as I'm pretty sure I got this error with the earlier stable release as well (1.0.3).

Help would, of course, be appreciated. =P

stephanV
20th September 2005, 17:08
That seems like an error in the jobfile, each command must be ended with a semicolon (;).

Check the jobs file in the VirtualDub directory if this is actually the case.

STC-Fan
20th September 2005, 17:18
Ahh, found it now - all the commands are ending in semicolons in the .jobs file, but an old error's crept in again. Basically, I found an error recently with the "Border Control" filter (which I use to chop off the head switching noise at the bottom of VHS recordings) - what happens is that, when you save the processing settings, it looks like this in the .vcf file:

"VirtualDub.video.filters.Add("Border Control - 2.34");
VirtualDub.video.filters.instance[1].Config(0, 0, 524288, 0, 0, 0, 0, 0, 1, 31551368, 1244256, 4760181, 31037224));"

Note the (obviously incorrect =P) double bracket at the end - it turns out that this error (which I have to manually fix every time I save a .vcf with that filter) has crept into the .jobs file for both passes. Fixing it in there as well has now sorted it out, so it's encoding properly now. Thanks for the help :)