§ ¶VirtualDub 1.9.6 released
VirtualDub 1.9.6 is now available for download. This is a stable fix-only release addressing several bugs and also some regressions introduced along the 1.9.x code line. The main intent is to try to fix all of the issues that are preventing people from migrating from 1.8.x to 1.9.x.
The current plan is to release at least one more bug-fix only release (1.9.7), and after that, I have no idea. I have some relatively largish changes pending in another code line, but at this point I don't think I'm going to want to release it as 1.9.8, in case I need to release another fix-only release in the interim... which leads to a problem because I've run out of mid-level version numbers. I'm not going to start a 1.10.x line, because I learned the hard way that everyone reads it as a decimal and thinks .10 < .9. What I should have done was inserted a leading zero so that I'd be at 1.09 instead. I could just jump to 2.0.x instead, but that seems kind of lame since I'm unlikely to have the kinds of changes that would warrant a 2.0 release. Then again, the last time I thought I was going make version 2 a big upgrade I ended up screwing up the code line so badly I had to pull a Vista and restart from the 1.4 code base, so maybe I should just bump the version number.
Maybe I should just be lazy and use build numbers.
Anyway, here's the change log for this release:
Build 32618 (1.9.6, stable): [September 19, 2009]
* Images: Fixed bug where the PNG encoder would randomly produce invalid
* Scripts: Fixed memory read crash when attempting to open a file with
* Retweaked MP3 CBR rate determination.
* Fixed rare crash when stopping a scene shuttle operation.
* AVI: 1GB option was broken for normal save operations (although it did
work for capture mode).
* Filters: Shift+Mouse color checking in preview windows works again (broken
* Filters: Fixed incorrect frame being sampled after edits were done on the
* UI: Removed "run as job" check box from Save Image Sequence dialog, since
it's now redundant with the "queue batch operation" command.
"I'm not going to start a 1.10.x line, because I learned the hard way that everyone reads it as a decimal and thinks .10 < .9"
I think this is not a big issue, because many projects (the Linux kernel team also) use that kind of version counting, so it's really not that unusual...
derJörg - 19 09 09 - 11:56
Why not switch to hexadecimal revisions and relese 1.A.0? :)
ggn - 19 09 09 - 21:29
Please add support for other containers like mkv.
dan - 20 09 09 - 03:27
9/20/09 11am cst: On Cnet downloads - I get a small file 1663k with the file name of "download" with no extension. Is this correct. If so, what do I do with it?
Thank you for your help. YOUR PROGRAM IS GREAT.
Denny Hallas - 20 09 09 - 04:10
"I had to pull a Vista"
It's a wonder this phrase isn't in common use :)
Lucas - 20 09 09 - 12:33
Just bump the new version to .12. That will be reasonably clear, apart from the random missing numbers.
nine - 20 09 09 - 12:42
I found a problem in Virtual Dub 1.9.4 and 1.9.6 versions with any third-party filters.
When I use filters "logo 1.3" or "logo 1.7 beta" (found at http://neuron2.net/logo/logo.html
) and I start the filter at specif frame (example : 200), it don't mind about previously cutted frames in the timeline, so the filter starts at frame 200 of discarded ones.
This problem don't occur in Virtual Dub versions 1.8.8 and oldest.
However, thanks for your great software !
Sorry for my bad English
Axe - 21 09 09 - 05:15
As always, Thank You for all your work.
It would appear that Fast recompress with Smart rendering is still not working.
It was working in 1.8.8 and then I try the same source and processing settings in 1.9.6 and it appears to be doing Full processing mode :-(
Sasha - 29 09 09 - 01:46
First of all a big thank you for this wonderful tool. :)
Just reporting that I'm having the same problem with third-party filters. The filters won't synchronise with/recognise the new timeline, and will move out of sync if any frame is added to/deleted from the video. It worked just fine under 1.8.8.
e.g. if you do something to say, frame 50 of a video then add another 50 frames before it, you'll have to manually re-configure the filter to frame 100 to get the originally desired effect.
Anon - 13 10 09 - 12:46
This is caused by a necessary change I had to make to the filter system in order to fix a bunch of broken cases in 1.8.8. I think you've got it backwards, though -- the problem is that after an edit you still have to enter the pre-edit number.
In 1.8.x, filters were able to receive the post-edit frame number. In 1.9.x, the filter now receives the pre-edit frame number. The reason is that in 1.8.x and earlier versions there was an ambiguity in when the edits happened -- some parts of the code treated the edits as pre-filters and some as post-filters. This caused problems when I introduced rate-changing filters into the system (deinterlacers with frame rate doubling) and it got worse with the multifetching for more advanced filters like Yadif, because it made frame caching impossible. In the end, I decided that the only way to keep things working was to drop the idea of a pre-filter edit list and make everything consistent with a post-filter edit list. So, sorry... but I had to break compatibility a little bit to move forward.
I can't change it back, but if you've got ideas on specific issues where frame numbers are confusing, I might be able to add some UI features to address them.
Phaeron - 14 10 09 - 16:21
So if I start with an intro, cut a few frames off the end of it, and append a show that starts a few minutes into its recording session, meaning I also cut a couple of thousand frames from the start of that, and wanna use fadein and fadeout, I need to include all the cut frames from the edits to make the end fadeout happen at the correct time?
Not a problem, cause the number of selected frames are displayed, just need to incorporate this check into the workflow.
^xRun^ - 17 10 09 - 16:17
I just updated my old virtualdub to latest 1.9.9 and got the same problem with logo filter.
so what's the solution? just using 1.8.8?
Evgen (link) - 26 06 10 - 10:47
Please keep comments on-topic for this entry.
If you have unrelated comments about VirtualDub, the forum is a better place to post them.