§ ¶VirtualDub 1.8.6 released
VirtualDub 1.8.6 is out and is a stable release containing bug fixes for issues reported by users. Notable bug fixes include errors handling audio in NTSC DV type-1 files, several crashes, and a few glitches in batch mode (job control).
Those of you on the forums know that I've been pushing out experimental features as "1.8.X2" test releases. Chances are at this point that I will rename that to 1.9.0, because there is enough in it that I wouldn't want to pollute the 1.8.x branch in case there are enough fixes to warrant 1.8.7. After that I'm kind of screwed with respect to major version numbers, although I guess I'll deal with that when I get there.
Build 30009 (1.8.6, stable): [September 21, 2008]
* Wheel scrolling in the Set Text Information dialog closes the edit control.
* Save Segmented AVI now works with VBR audio.
* Animated GIF export now fails with an error if the current output format is
compressed or otherwise not supported.
* JobControl: Fixed crash when one machine attempts to run a job in
distributed mode right when another machine deletes it.
* JobControl: The filter crop mode saved in jobs was opposite from selected.
(This only affected YCbCr cropping.)
* Capture: Fixed crash when capture driver sends audio samples when
DirectShow graph is not running.
* D3D: Fixed sporadic crash on lost device.
* D3D: Fixed Direct3D errors when display debug information is enabled and a
video filter fails to initialize.
* Frameserver: Frame rate adjustments weren't always propagated correctly.
* Fixed crash when using fast/normal recompress mode without a video codec.
* Fixed divide by zero crash when loading video and a video filter in the
list is unable to initialize.
* Changing the "source rate adjustment" option no longer invalidates the
* Rendering would loop endlessly if an error occurred during video
compression and threaded compression was disabled.
* Disabling the "directly decode YCbCr formats" option works again.
* Filters: lMicrosecsPerFrame and lMicrosecsPerSrcFrame were reporting
milliseconds (broken since 1.8.0).
* JobControl: Fixed case where a non-distributed "load job list" command can
fail due to erroneously running distributed-mode code.
* JobControl: Fixed problem where dialog would suddenly close when editing
* Script: Fixed crash when removing video filter from filter chain.
* DV: Audio decoding works again with NTSC DV files (broken since 1.8.4).
What's wrong with versioning? 1.9.x is followed by 1.10.x, 1.11.x, etc.
Gregorius - 21 09 08 - 18:43
That makes sense to someone who's used to software versioning. It confuses many users who think real numbers and conclude that 1.9 > 1.10. It works better if you have the foresight to call the older version 1.09 instead of 1.10, but I didn't do that.
Phaeron - 21 09 08 - 19:21
I also think there's absolutely no problem with following 1.9.x with 1.10.x. Even if some users who check version numbers (I'm willing to bet the vast majority just grab the newest stable release without even looking at the number) get confused by it, it still makes far more sense than any alternative versioning scheme I can think of.
StarCreator (link) - 21 09 08 - 19:48
Well, just plan some UI changes and call it Vdub 2.0!
One suggestion I did once before, is to make video preview panels 'mobile': with multiple screens configurations becoming more common, that could actually be very useful.
And such a significant option would warrant a major revision (which will then implement 2.xx versioning).
Mitch 74 (link) - 22 09 08 - 09:06
IF you don't mind "Hex" numbering, there is always VirtualDub 1.A.x
roseman - 22 09 08 - 11:43
roseman ==> 
Joke apart, using HEX notation will not only confuse users more than 1.9 -> 1.10, but they may also think that you're rewriting Virtualdub from scratch, and that 1.A is an alpha release (and B = beta) and leave them utterly bewildered on 1.C ('Canned'?).
The joys of version numbering...
Mitch 74 (link) - 22 09 08 - 12:16
what i would like to see is an option which would show all the filters for example on the right side and then drag and dropping them to the timeline like adobe premeir does. its a royal pain going back and forth through the menus to change a setting and then trying to preview it. only an idea and sorry if someone else asked the same question. oh quad core support would also be nice or mp4 avc :). by the way, the program rocks.
evropej - 22 09 08 - 21:46
VDub 1.9.6 > Crash
Just upgradet to 1.9.6, and VDub now crashes every time I try to close it. The "Crash-Manager" apears, but I cannot save the report, since VDub has no writing permissions into the program directory (default in Windows VISTA!). This is also the fact WHY VDub crashes. It tries to write to the jobs file (even without planing any job), and fails to do so. In earlier versions this wasn't a reason to crash, in 1.9.6 it is...
Of course I can work around this, by giving write permision to that file/directory, but for longterm VDub should put those files into the "%AppData%\VirtualDub" directory, so that jobs can be planed on VISTA (with standard permissions) too.
Cole - 23 09 08 - 06:59
what's up with the filter writer plugin ?
I seem to remember it, but which old version
still has it?
joe - 23 09 08 - 16:16
I'll fix the bug in 1.8.7, but what I'm wondering is why you have VirtualDub in a non-writable location in the first place. It doesn't have an installer, it doesn't need an installer, and thus it doesn't land in Program Files by default, which is where the writable program directory problem usually happens. The fact that VirtualDub doesn't have an installer is the main reason why VirtualDub currently uses program-local. Adding an option to use profile-local is on the TODO list, but I'm not going to make it default as long as the app is in a .zip file. As a workaround, put VirtualDub in a local location like the desktop, and it'll run fine even as a limited user in Vista.
Depends on which one you're talking about, but VirtualDub itself hasn't ever come with a filter writer plugin. I've put out a couple of partially done ones over the years, but those should work equally well with 1.8.6 as with earlier versions.
Phaeron - 24 09 08 - 01:29
What about mpeg2 support like in VirtualDubMod ? When will be added? I am recording often from my tv card and it will be usefull. Thanx
Linkman - 24 09 08 - 15:38
Linkman - check this out:
yawnmoth - 25 09 08 - 16:21
I also run Vista and am not experiencing that problem. My .jobs file automatically ends up in "%appdata%\Local\VirtualStore\Program Files\VirtualDub" and doesn't touch the program directory path directly. Perhaps you've disabled Vista's default process virtualization (which is meant for compatibility)?
earn - 27 09 08 - 21:22
linkman, importing in virtualdubmod is 100 times faster and your plugin. ideas?
evropej - 28 09 08 - 20:15
Wow, the threading option really works!
Haven't used Vdub for ages and now (after updating my HW from single core to multi) I wanted to see how fast my new system performs.
The performance and fps was remarkedly increased when I changed the threading option to 1! My processor is Intel Core 2 Quad Q 9450 OC'd at 3,2 GHz.
I did a simple test with a 624x352 XVID .avi file. I letterboxed it with resize filter to 4:3 and then added subtitles with subtitler filter, reencoded video (ffdshow/XVID) and audio (lame). First with the setting in 0. The fps value was between 85-99 most of the time, CPU load at about 33% with two cores involved. After setting the value to 1, I got fps at 140-160 (!), and CPU load was about 54% utilizing ALL cores more or less. The overall duration dropped from ~11min30sec to 6min50sec. That's 40% less time!
(Needless to say, my old AMD Athlon 2800+ wouldn't have done it in less than 40 minutes or so)
hsode - 15 10 08 - 13:10