Welcome Guest ( Log In | Register )


Important

The forums will be closing permanently the weekend of March 15th. Please see the notice in the announcements forum for details.

 
Virtualdub 1.5.2 Is Released!
« Next Oldest | Next Newest » Track this topic | Email this topic | Print this topic
Spire
Posted: May 5 2003, 02:19 AM


Unregistered









VirtualDub 1.5.2 is released!

Come and get it!

Change log:

Build 16188 (Version 1.5.2): April 30, 2003

Features added:
  • Converted help from WinHelp to HTML and updated dialog help to current feature set.
  • Added frame rate conversion to arbitrary frame rates.
  • Added logging to report non-fatal warnings during operations.
  • MPEG parser detects and reports timestamp discontinuities.
  • Added limited error concealment capabilities to input handlers.
  • Optimized audio filters a bit and added tap count control for lowpass, highpass, and resampling filters.
  • Added "new rate" audio filter to relabel an audio stream with a new sampling rate without resampling.
  • Incomplete audio format headers that are rejected by ACM MP3 codecs are automatically fixed with the required fields (the infamous "tag 0055" problem).
  • Added workaround for AVI1 files with MP3 audio being detected as MP3 files by Windows Media Player 8.
Features removed:
  • Removed coach dialogs. Not helpful enough and too outdated to maintain.
Bug fixes:
  • Fixed capture free space indicator being limited to 4GB under Windows 98 (regression in 1.5 series).
  • Fixed crash when job queue could not be flushed to disk.
  • VDFs that contained multiple filters were only showing the last filter in the library (regression in 1.5 series).
  • Fixed crash when attempting to direct copy a video stream with an abnormally large BITMAPINFOHEADER (>16K). Added code to detect and correct such mistakes.
  • Fixed hang in audio filter graph editor when placing output filter with autoconnect on and no place for it to attach.
  • Fixed livelock at end of operation when lowpass/ highpass audio filters were in use.
  • Fixed internal error when attempting to start an incomplete audio filter graph (unconnected pins).
  • Fixed garbage wLanguage/wPriority values being written to audio AVI track headers when converting an MPEG-1 file.
  • Fixed crash when attempting to load an AVI stream with an invalid sample rate (zero or infinite). Added code to guess and substitute a reasonable value.
  • Fixed small memory leak in "smoother" video filter.
 
  Top
fccHandler
Posted: May 5 2003, 03:37 AM


Administrator n00b


Group: Moderators
Posts: 3961
Member No.: 280
Joined: 13-September 02



There have been quite a few bug reports about 1.5.2, so right now I recommend waiting for 1.5.3. I don't remember where I read it, but I think Avery Lee said it would be released within a week. (And of course I'll upgrade my MPEG2 version as soon as I have the code for 1.5.3.)

--------------------
May the FOURCC be with you...
 
     Top
phaeron
Posted: May 5 2003, 06:05 AM


Virtualdub Developer


Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02



Yup, I messed up the dubbing engine in a few different ways, and thus 1.5.1 is the current "stable" release. These are the known bugs so far:

1) Pipeline isn't always flushed at completion -- causes ~10-15 frames to be dropped.
2) Interleaving broke at the last minute when I rewrote the code to fix segmentation, so it always does 1-per-frame.
3) Direct stream copy is broken when frame segments are deleted. (This is probably the most embarrassing one.)
4) Position control doesn't update properly during playback when segments are deleted. Essentially the same bug as #3.
5) Job system always reports warnings. This one broke when I added "marker" type entries in the wrong spot.
6) Frame masking doesn't work at the beginning of a segment -- most notably, at the beginning of the timeline. This is actually quite an old bug that went unnoticed and probably affected the "scan for bad frames" command.

These are fixed in the 1.5.3 codebase now and are ready to deploy when everything looks stable. My offer to send betas out to people who are affected or want to help stabilize 1.5.3 still stands. Actually, switching to a public experimental/stable alternation release cycle is looking really good right now, since people are much better at testing releases than I am.

(Incidentally, the reasons for most of these bugs are not so much that I added new code, but that I tried to clean up old code that was held together with duct tape and hotglue. I love duct tape, but boy does it leave a mess.)
 
    Top
endorphin
Posted: May 5 2003, 11:47 PM


Advanced Member


Group: Members
Posts: 112
Member No.: 3488
Joined: 4-April 03



If you like duct tape, you might like baling wire too. I haven't tried hot glue lately myself...

Thanks for all the hard work. I'd test the 1.5.3 beta but my video editing hours just dropped off dramatically as work and outdoor play have taken over the month of May.
 
     Top
fccHandler
Posted: May 6 2003, 04:36 AM


Administrator n00b


Group: Moderators
Posts: 3961
Member No.: 280
Joined: 13-September 02



@phaeron:
As you implied, you could release it "as is" and the users will let you know if it doesn't work. That seems to be DivXNetwork's strategy these days; the only difference is they charge money for their stuff. tongue.gif

--------------------
May the FOURCC be with you...
 
     Top
phaeron
Posted: May 6 2003, 06:13 AM


Virtualdub Developer


Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02



Let's assume 5 components are active in a single processing operation (MPEG2 decoder -> Avisynth -> VirtualDub -> filter -> DivX). If each has a 20% chance of failing, the user has a 1-in-3 chance of actually accomplishing a task, and for the 2-in-3 chance of failure, each component author has a 60% chance of receiving a bug report for which another component is implicated. While releasing continuous open alphas and betas might sound good, it introduces a ton of headaches for everyone. Even on the Linux kernel, which is arguably the most successful large-scale OSS project to date and does frequent public development releases, some minimal checks have to be made to ensure that the released kernel doesn't, oh, eat the root filesystem on first boot.

(There are actually rather large holes in the probabilistic analysis above, the largest one being that failures in VirtualDub are likely to prevent the other components from even starting. But I'm sure you get the point.)
 
    Top
ChristianHJW
Posted: May 6 2003, 09:40 AM


Advanced Member


Group: Moderators
Posts: 1768
Member No.: 2
Joined: 7-July 02



There is another thing to consider for Avery when releasing a new version, with respect to the high number number of downloads Virtualdub is creating with every release, and this is that sourceforge.net recently seemed to suffer from its own success, they had a lof of server problems recently and i see this this as an indication that all the high number downloads, like emule, gimp, Virtualdub, VirtualdubMod, etc. are putting a lot of stress on the servers, even with the big number of excellent mirrors it has to handle released files ...

@phaeron : feel free to use this forum here to distribute a small number of alpha versions into the limited circle of people that are reading here all the time, we have done that with TCMP and matroska and found it to be a good way of testing things in a broader audience before actually releasing them ...

--------------------
Visit the unofficial Virtualdub support forum on http://forums.virtualdub.org - help to reduce the big number of emails Avery Lee is getting every day !!
Support matroska as container and Gstreamer as the only truely open, x-platform multimedia platform ....
 
       Top
Stone-D
Posted: May 6 2003, 12:48 PM


Unregistered









W A R N I N G

Be very careful about doing that. Whatever your intentions, links to a new alpha would 'leak' out and appear on major release info sites. Look at the problems Opera suffered as a result of such releases.
 
  Top
Suiryc
Posted: May 6 2003, 11:00 PM


Developer of VirtualdubMod


Group: VirtualdubMod Team
Posts: 222
Member No.: 468
Joined: 10-October 02



QUOTE (ChristianHJW @ May 6 2003, 03:40 AM)
... they had a lof of server problems recently and i see this this as an indication that all the high number downloads, like ... VirtualdubMod, etc. are putting a lot of stress on the servers ...

high number dowloads
lol we aren't part of the high number downloads softwares as VirtualDub or eMule tongue.gif

--------------------
OGM tools, VirtualDubMod [SourceForge : Tracker/DL] (FAQ)
Don't forget the Needed DLLs for VirtualDubMod. Post bugs/requests in our Tracker.
We give 100% of your donations to the Open Source community
 
      Top
phaeron
Posted: May 7 2003, 02:49 AM


Virtualdub Developer


Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02



I'm not concerned about alphas leaking out -- I mail enough private alphas out for testing that I know it's not, and even if one did, it's not much different from someone hacking changes on themselves and releasing the modified version (which is permitted by the GPL). Not only that, but in the entire time I've been doing so I think only one person has ever asked for the source code changes for their alpha version.

As for bombing SourceForge, that's a primary reason I take pains to keep the size of the VirtualDub binary releases down. I've had people argue that I shouldn't compile some parts for size optimization and use UPX, and why not just throw in XYZ libraries... but they don't realize that killing your primary download site is not a good thing. I'm tempted to look into P2P methods of delivery, specifically BitTorrent.

@Suiryc: That may change if you do too good of a job on subsequent releases. Nandub was right behind VirtualDub in the SF download ranking list for much of its time of popularity. smile.gif
 
    Top
Pamel
Posted: May 7 2003, 09:35 PM


matroska team member


Group: Moderators
Posts: 151
Member No.: 1353
Joined: 15-December 02



It sounds like an excellent idea to use BitTorrent. I don't think it would be good to use it as the only source, but pointing to it as the primary source would be pretty spiffy.

Can anyone think of a drawback to using BitTorrent as the listed primary download source?

What about expirementing first with VirtualDubMod to see if it would be feasible?

--------------------
Please take anything I say with many many grains of salt. I can't tell the difference between my AVI and a hole in the ground.
 
      Top
flloyd
Posted: May 9 2003, 01:01 AM


Unregistered









eMule would also be another great way to distribute the files. All you need to do is put the eMule link on the download page and it will quickly spread.
 
  Top
endorphin
Posted: May 9 2003, 08:58 AM


Advanced Member


Group: Members
Posts: 112
Member No.: 3488
Joined: 4-April 03



If you haven't checked out Shareaza (http://www.shareaza.com) -- in its latest release it supports Gnutella, Bittorrent AND eMule all in one. I have found server-free success in releasing some of my homemade ski videos to friends using Shareaza. Only the first three or four had to download the entire file from me, and after that my computer only needed to serve insignificant fractions of it from time to time as the release multiplied across the circle of friends and their friends.
 
     Top
0 User(s) are reading this topic (0 Guests and 0 Anonymous Users)
0 Members:
12 replies since May 5 2003, 02:19 AM Track this topic | Email this topic | Print this topic

<< Back to News / Announcements