§ ¶1.6.8 released; 1.6 is now the stable branch
VirtualDub 1.6.8 is now out. With the release of this new version, the 1.6 branch has now become the "stable" branch, for which changes will be restricted mostly to bug fixes. One major bug was fixed with this release (filter list corruption), and the remainder of the application should function like 1.6.7. Please keep the bug reports coming so I can roll up any fixes into a 1.6.9 build.
Currently, in the 1.7 branch, I'm working on rewriting the filter systems. There are actually four audio/video filter systems in 1.6, the old audio/video filter systems, and the new A/V filter systems. Of these, the old audio filter system didn't permit external plugins, and the new video filter system never went live in 1.6. I've already removed most of the old audio filter system and shunted its functions through the new audio system, and am currently working on getting existing video filters wrapped and running in the new video filter system. This is important for allowing video filters to run asynchronously, as currently the video filter chain is monolithic and can't really run multithreaded or cross-process (which would be required for 32<->64 support).
Changelist
Build 23567 (1.6.8, stable): [July 3, 2005]
[bugs fixed]
* Fixed occasional crash if display panes are refreshed while editing the
filter list.
* Fixed hang if VirtualDub is the active application and attempts to refresh
the display panes when a display mode switch occurs.
* Display panes did not always update properly when seeking if Direct3D mode
was enabled and updating the frame took a lot of CPU time.
* Direct3D display mode could be activated if checked even if the option was
grayed due to DirectX support being disabled.
* Capture: Fixed crash if capture is attempted with audio enabled but audio
isn't present or is in an incompatible format.
* Reversed direction of mouse wheel action to be consistent with Windows.
* Hex editor's Extract Segment command would sometimes extract the wrong
segment due to repainting the main pane during the extract.
* CLI interface app didn't exit if console was empty prior to invocation due
to overzealous Explorer detection. This is now only done if no arguments
are supplied.
* Fixed crash in MPEG-1 parser when encountering a pack with a too-short
length, such as zero.
* Audio codec errors sometimes reported the wrong source of the error (i.e.
decompressor vs. compressor).
[regressions fixed]
* Pixel shaders were disabled in Direct3D bicubic mode due to debug code
mistakenly left in.
* MRU list sometimes didn't resort properly when reopening a recently opened
file.
Comments
Comments posted:
Wow ! Finally a stable successor to 1.5.10. Great job !!
Parker Lewis - 04 07 05 - 13:12
_Hex editor's Extract Segment command would sometimes extract the wrong segment due to repainting the main pane during the extract._
Looks like it wasn't just me, then (I thought I kept typoing the offsets)! It's a very useful little utility - I used it recently to manually extract some pictures from a SmartMedia card (or rather, a disk image of the card) where Windows and the camera had conspired to eat parts of the directory tree. A standalone version of the hex editor would be very nice.
BoggyB (link) - 04 07 05 - 16:06
I've had a problem already with this stable version.All I did was select "Exit Capture Mode" and windows shutdown with a blue screen stating that it had to take action before critical damage was caused to my Operating system,starting to dump memory.
I hard rebooted and found that my modem drivers were messed up and couldn't connect to the internet,so I had to reinstall the drivers.
The earlier experimental versions didn't even do this much damage.
Luke - 04 07 05 - 19:09
A blue-screen in XP means that you had a driver fail; userspace programs like VirtualDub cannot normally cause this directly. The system event log may indicate which driver tripped the bug check. If you were using a really early 1.6 series version, it's possible that this is the first time you are using a version capable of DirectShow capture, and thus are exercising an entirely different driver path than you were before.
Phaeron - 04 07 05 - 20:50
Best Job ! Thank you !!!!
SovA - 05 07 05 - 04:44
The problem I reported must have something to do with my video card drivers(ATI AIW 9800 Series).All the way through the system event viewer theres:
"Warning" Source:ati2mtag Category:WDM
The serious error just tells me:
Category (102)
Description:
Error 100000d1,parameter1 ffffffdc,parameter2 00000002,parameter3 00000000,parameter4 f6ad3afe
Its not Virtualdub's fault obviously.Sorry for the previous post.
Dont know how I'm going to solve this one.
Luke - 05 07 05 - 09:57
Luke,
Prob.s with ati2mtag might be more common bug -- have had warnings in event log & with service not shutting down with winxp in latest driver version. New one usually appears 10-12th on month if you can use as is till then.
mike - 05 07 05 - 13:33
Nice job
thank you very much for all the effort that u did to make this version stable. i'll try it :)))
hope we will get a AMD64 stable version too.
Anwar - 05 07 05 - 15:59
Luke: I believe that 100000d1 is the bugcheck error IRQL_LESS_THAN_OR_EQUAL, but that generally doesn't tell you anything more than "driver fscked up."
Anwar: I always build the AMD64 version at the same time as the 32-bit version, for both experimental and stable releases. The 1.6.8 AMD64 version is available from the same place. Now whether it's actually stable or not... it has the same bugfixes as the 32-bit build, but it's compiled with a prerelease compiler (the post-VC8-beta-1 compiler from the latest Platform SDK) and it hasn't gotten nearly as much usage, so I wouldn't be surprised if there are some bugs specific to the AMD64 version. If you find any, let me know.
Phaeron - 06 07 05 - 03:05
I really like VD's hex editor, but if I could please make a small request: sometimes I want to whack off a couple of bytes from the start and/or end of a file, so I put the cursor at the start of the segment I want to extract and select the option from the menu, but if, for example, I only want to take a few bytes off and fill in the total file size in the "length" dialog box, it doesn't just extract until the end of the file - I first have to take off the bytes from the start that I don't want to keep before it will show the save file dialog box. So, this is kind of tedious to do each time. It would be nice if there were 3 dialog boxes, one for the start of the segment, one for the length and one for the end. What would be really great would be if there were also 2 buttons to set the start and end of the segment to extract while walking through the file. Anyway, hope you'll consider it.
Yuri - 06 07 05 - 06:54
A thing of beauty. Thank you once again!
Steve - 06 07 05 - 08:23
Mike,
The ATI Catalyst 5.6 drivers do seem unstable,will have to wait for next release.
Phaeron,
Yes I do remember the blue screen showing:
IRQL_LESS_THAN_OR_EQUAL
Luke - 06 07 05 - 10:00
The Fixes are great specially the 'change display mode hang'. I just have some points i hope would be taken
into consideration:
- YVU9 decompression 'i think' is broken
since V1.6.6.
When i try to open previously YVU9 encoded clips, the displays are blank and VD reports on the status line for each frame:
"VideoSourceAVI:uncompressed frame 'n' is short (expected xxxxxx bytes, got xxxxxx)"
The same clip can be opened normally in V1.5.1 as well as TMPGenc, Adobe premier, etc...
- Cosmetic: the mouse wheel don't work on frames in 'croping pane.'
Thanks for all your work and efforts in
this wonderful program.
John I. - 08 07 05 - 01:44
To diagnose your YVU9 problem, I need to know the frame size of the video and the actual byte size values in the error message.
Phaeron - 08 07 05 - 02:06
Thanks for responding so quickly.
The full error message is:
“VideoSourceAVI:uncompressed frame ‘n’ is short (expected 921600 bytes, got 345600)”
John I. - 08 07 05 - 02:26
Uh, I need to know the frame size (width x height) of the video too....
Phaeron - 08 07 05 - 02:57
Frame size (width x height) = (640 x 480)
John I. - 08 07 05 - 15:57
Okay, I've been able to reproduce the bug. It happens because apparently the biBitFields member of the video format in your file is set to 24 rather than the true bit depth for YVU9, which is 9 bits/pixel. I'll fix this for 1.6.9. In the meantime, you can force VirtualDub to defer to a video codec by disabling YCbCr direct support in Options > Preferences > AVI.
Phaeron - 09 07 05 - 17:33
Why doesn't version 1.6.8 handle MPEG 2/VOB files just like version 1.5 used to do?
I can't load and edit these files as before and use frame server.
rgds
sfalcon
sfalcon - 09 07 05 - 17:34
The official version of VirtualDub has never handled MPEG-2 files, although some third parties have made modified versions that do.
Phaeron - 09 07 05 - 17:39
Thanks, I applied what you suggested and
VD 1.6.8 can now handle the old YVU9 encoded clips.
I have one more question. I'm a regular reader of the VD FORUM and would like to participate in its various categories, 'bugs, suggestions, etc..'
But I remember reading sometime ago here
or in the FORUM that people with hotmail
accounts are not accepted. Is there any clue how this can be fixed ?
Thanks again
John I. - 09 07 05 - 21:59
Sorry, but we've disabled registration with Hotmail accounts because of the high rate of bounced email. Please use an alternate address for forum registration.
Phaeron - 10 07 05 - 05:27
Is it only hotmail or any free account ?
John I. - 10 07 05 - 19:27
There is one more observation to 1.6.8
and not in 1.5.1.
Using 'Condional' filter with/without
a clip gives a garbled list of filters.
John I. - 12 07 05 - 15:31
