Log in

View Full Version : VirtualDub 1.5.0 released


hakko504
17th February 2003, 08:06
The long awaited (and severely delayed) v1.5 is finally here.

Download here. (https://sourceforge.net/project/showfiles.php?group_id=9649)


Release notes:Notes:
If you download the P4 build, you will need the main archive as well for the help files.
You will need bzip2 as well as unzip in order to unpack the source distribution.
Mapconv, verinc, disasm, Sylia, and NekoAmp are now part of the main source distribution and thus you do not need to download them separately anymore. The help file has not changed and thus there is no auxsrc distribution for 1.5.0.


--------------------------------------------------------------------------------
Changes:
Build 15584 (Version 1.5.0): [February 16, 2003]
[features added]
Can add a single job to the batch list with syntax: /p[input_file],[output_file]
Filters are now loaded and unloaded on the fly to circumvent TLS (thread local storage) selector limits.
Cropping bounds can now be dragged via the mouse.
Improved, friendlier crash diagnostics.
Basic audio filter support (no plugin support yet, though). The pitch shifter sucks.
Increased accuracy of audio/video timing by switching from microsecond to rational calculations.
Changed font on dialogs to enable ClearType on XP.

[features removed]
Deleted outdated 3x3 average filter -- it has been superceded by "blur."

[bug fixes]
New MPEG audio core (Priss) -- fixes decoding errors in layer I and layer III audio and adds SSE polyphase support.
Fixed motion JPEG decoding bugs when padding is present before markers.
Fixed crash in SSE2 code when decoding MPEG-1 file odd width in macroblocks.
Fixed crash in SSE2 resize routine when doing 4-tap vertical resample with odd width.
Fixed swapped UVs in About dialog box. ^^;
Fixed sync errors in MPEG-1 playback when decoding an audio stream which flips the copyright bit between frames or switches layer III bitrates (VBR).
Fixed "Frame not found" errors in MPEG-1 decoder when GOP is longer than 128 frames.
Rewrote resampler clip determination code again. Hopefully this one will be Bug Free (tm).
Fixed spurious errors at end of operation when saving WAV file.
Outputted configuration files and job scripts now include the correct audio filename when a .wav file is selected through a script.
Fixed AVI segmented output creating short files when working from MPEG-1 source or when IVTC is active.
Image import filter wasn't caching frames.
Fixed a couple of Get*() script calls that were declared incorrectly internally and didn't work (thanks to Cyrius).
Blur filter now handles cropping properly.

Belgabor
17th February 2003, 11:24
Just before anyone starts asking, we are already working on VDubMod 1.5.X. This will take some time, as we practically have to readd our modifications. Avery did a major source reorganization, so this won't be a quick diff update as with the 1.4.X updates. Be patient with us :)

sillKotscha
17th February 2003, 12:08
Originally posted by Belgabor
This will take some time, as we practically have to readd our modifications.

and than, does it sing, dance and whistle in the dark? :D

cheers Sill

hakko504
17th February 2003, 12:32
Originally posted by sillKotscha
and than, does it sing, dance and whistle in the dark? :D No, but Avery has promised something like that in v2.0 ;) which was supposed to be released :In a year or so.

Avery Lee, March 2001

midiguy
17th February 2003, 19:04
cool! looks really nice! I will test out some of them audio filters later. now I will need is the ability to laod AVIsynth filters from within virtualdub, and for virtualdub to allow filtering without converting to RGB (ie: fast recompress with fitlers)! that'd be real slick!

killingspree
17th February 2003, 20:17
just wondering if it supports YV12? didn't see it in the changelog, but maybe it's kind of a hidden feat?!? (:

regards
steVe

leadman584
18th February 2003, 01:19
Hidden feet I think. Older version handles Avisynth 2.5 fine.

unimatrixzer0
18th February 2003, 05:06
when I go into capture mode, and capped something, the thing that says how much disk space I have left is blank now. wondering if thats a glitch or if its just me?

Thanks!

unplugged
18th February 2003, 21:38
Honestly, I still can't realize that VirtualDub and VirutalDubMod projects does not converge yet... :(

Why? What's wrong with one unique solid project?
I think may be an huge job the modifications that from time to time are needed to give it the "Mod" most-wanted features, especially when re-linking the Ogg/AVS/general cool stuff after VirtualDub source gets changes in its structure (when it happens). Plus this could bring up new annoying (adaptation) bugs and take away even more time for developers.
Any word by authors is appreciated. :)

Atamido
19th February 2003, 02:04
Originally posted by hakko504
No, but Avery has promised something like that in v2.0 ;) which was supposed to be released :
Last I heard, Avery cancelled VirtualDub 2.0. He was doing a complete rewrite to use the newer DirectShow interface instead of the outdated vfw.

Unfortunately, DirectShow doesn't allow the level of control that vfw does, opting to place a lot of the automation within DirectShow. Because of this, you loose the level of control that you had with vfw. And, last I heard, Avery decided not to do the VirtualDub 2.0 that he was working on because he couldn't get that same level of control.

Perhaps if a system like UCI (http://uci.sourceforge.net/) was produced, then Avery could make the new version with the control that he wants?

Leuf
19th February 2003, 05:40
Originally posted by unimatrixzer0
when I go into capture mode, and capped something, the thing that says how much disk space I have left is blank now. wondering if thats a glitch or if its just me?



For me it gave a time/disk space, but it was wrong. It said I had 5 mins time remaining and 2 gigs free, I had ~45 gigs. I went back and capped with 1.4.13 instead just in case.

Also just noticed saving a segmented avi it labeled the file as .0.avi instead of .00.avi, which is a little odd.

Edit: Just to further caution on this point, the misnaming of the segmented avis causes all sorts of problems, not the least of which is if you then load the avi back into vdub it only loads the first segment without a peep of warning about not finding the next segment. Just a word of warning so you don't waste a couple hours of encoding like I just did.