![]() | This article is rated C-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||
|
Why the reference to the support of input plugins was removed? — Preceding unsigned comment added by 151.67.191.202 ( talk) 23:57, 5 July 2011 (UTC)
Does Avery Lee have a home page? Is there biographical info published somewhere? — Preceding unsigned comment added by 70.169.152.24 ( talk • contribs) 03:07, 3 November 2006 (UTC)
Editor User:Thumperward reverted my following recent addition:
However, crossfading of audio and video is not supported by VirtualDub, nor are wipe effects supported, so it is not possible to do even a basic soft fade transistion from one video clip to another. Clip-to-clip transistions in VirtualDub are always sudden and abrupt, making it unsuitable as a complete replacement for video editors such as Adobe Premiere, iMovie, or Windows Movie Maker.
Thumperward's stated reason for removing this text is:
this is personal commentary and isn't appropriate. virtuasldub explicitly claims not to be a replacement for authoring apps anyway, so it's unclear why one would think it was
My reply is that while virtualdub may state that in its documentation, this article does not make light of that detail. Instead this article says right in the first paragraph that this is video editing software, which by all normal definitions of the term, will include typical and common capabilities like wiping and fading. The fact that it does not means that it either isn't a video editing program in the normal sense, or that the lack of fading/wiping should be explicitly stated somewhere as I have tried to include as above.
Going on and on about all these cool filter effects but not mentioning the fading/wiping issue gives the reader of this article a false impression about the capabilities of the software. I believe the text should be added back but am trying to avoid an edit war and instead discuss this civilly. DMahalko ( talk) 10:11, 10 July 2008 (UTC)
Please update this article - the last release of this software is 1.8.3 . —Preceding unsigned comment added by 89.139.152.106 ( talk) 21:32, 22 July 2008 (UTC)
Can someone put the old Forks information back? I had nearly forgotten that the MPEG2 fork had support for ASF again. Useful to know, that. 69.11.4.75 ( talk) 04:38, 8 September 2008 (UTC)
a comparisson between the last version of mod, and the current version of VirtualDub would be welcome -- TiagoTiago ( talk) 13:01, 8 December 2008 (UTC)
VirtualDub has a useful batch mode worth mentioning. There a checkbox to add a job for later processing during save-as. This can also be done by creating "before" and "after" folders, chucking your uncompressed/unprocessed videos into "before" and running virtualdub with the -b command line switch and the two directories: VirtualDub -b before after
(Or, better yet, just open a fresh virtualdub, set your audio/video compression settings, and then go to F4, Edit->Process Directory) —Preceding unsigned comment added by 68.175.89.242 ( talk) 00:31, 4 October 2009 (UTC)
Very handy for tons of FRAPS videos, etc —Preceding unsigned comment added by 96.232.20.111 ( talk) 17:17, 3 October 2009 (UTC)
"but lacks features common to dedicated video editing software" - This text appears in the article, but links to the feature list of VirtualDub, rather than a supposed referenced "lacking common feature list". Opening for discussion before removal. Chopper Dave ( talk) 05:32, 28 June 2010 (UTC)
Well, VirtualDub does offer a batch processing mode, which I find very handy for processing a group of video files. This is an important and essential feature of the software and I think it should be talked about on the wiki page.
On the input side, and natively, VirtualDub is indeed limited to reading AVI files using only the built in functionality. But, VirtualDub is certainly NOT limited to AVI files. There are many "input plugins" available for virtually ANY video file format, from AVI to FLV to MP4 to MKV, you name it; as long as an appropriate codec is also installed on the system. I think the main wiki page saying VirtualDub is limited to AVI files is inaccurate and misleading. I think something should be said about how it is extended via 'input plugins' to virtually any video file format.
On the output side, and natively, VirtualDub only supports the output of AVI files. But on the menu, VirtualDub also has a "Export | Using External encoder" option. One can configure external video, audio, multiplexer "encoder sets" which neatly wrap any particular encoder/muxer with a custom command line specific for that encoder/muxer. This feature also works with the batch processor. For example, one can use ffmpeg (a popular open source codec library) and mkvmerge (a popular open source multiplexer) to encode nearly any video stream format and nearly any audio stream format and then multiplex them into an MKV (Matroska) file. However, ANY command line codec/muxer that can accept input from "stdin" can be used. I think the main wiki page should mention this "export using an external encoder" feature.
VirtualDub can also accept direct video streams from a frame server, like AVISynth. Thus, with the combination of AVISynth and VirtualDub, one has an open source, free, essentially fully featured (all be it command line driven), non-linear video editing solution.
On the support side, I think something should be said about how support is obtained for the program. There is a large body of developers and enthusiasts for VirtualDub. Like all open source software, the source code is available and developers are encouraged to debug and extend the code base. Both developers and non-developers can find quite a bit of support through the "Unofficial" VirtualDub support forum: http://forums.virtualdub.org/. For example, there are long and comprehensive topic threads on using the external encoder option, plugin and filter development and so forth.
Patrick ( talk) 14:49, 25 January 2014 (UTC)
VirtualDuB was a milestone in Open Source Developement in the ancient Era of DV-Video, when internet had just been invented. Is your attack supposed to be motivational towards improvement of the article? Cleaning up History will not make you more notable. So what IS your intention? (hint:I do not really expect your answer to be helpful here) — Preceding unsigned comment added by 79.241.138.176 ( talk) 01:31, 7 December 2014 (UTC)
I don't know if you realize it, but you're confusing an essay on software notability (an essay is the personal opinion of one or more Wikipedia editors) with a guideline about notability (a guideline represents widely accepted practices Wikipedia editors are expected to follow). I'm glad you found that book about VirtualDub -- it helps establish its notability and I had forgotten about it -- but the idea that a doom9 forum or a Softpedia entry or hundreds of plug-ins somehow help to establish notability is laughable. And Wikipedia doesn't have a notability guideline for software, let alone "official criteria". — MShabazz Talk/ Stalk 07:11, 1 March 2017 (UTC)
I assume the project has gone into inactivity, but does anyone happen to know WHY? The project was very active ~10 years ago or so. 2A02:8388:1600:C80:BE5F:F4FF:FECD:7CB2 ( talk) 19:47, 26 October 2016 (UTC)
It's BS to call HandBrake a "successor" to VDub. The main function of VDub is filtering, with capturing second, while all HandBrake does is conversion/transcoding, making it much more a "successor" or rival for other simple converters such as SUPER or XMedia Recode.
BTW, I'd like to see an official announcement that VDub is truly discontinued. In his last official post on it in 2015 [31], Avery aka Phaeton said that development by himself has only slowed down after 2013, he's willing to fix any upcoming Windows 10 compatibility issues, and that he wishes other people would take it up since it's open source. In fact, forks *ARE* stil being developed and updated (see below). Another fact that I'd call definitely noteworthy for the article is that not only do people still use VDub but they're also still developing filters aka plugins for it. Speaking of which, the most active forum on VDub and its plugins to this day is Doom9, here's its relevant sub-forum that could be linked in the article: [32]
Even though it was officially called the "Unofficial VDub Forum" until its closure in March 2015, next to Avery's own blogsite and Doom9 it used to be the main hub for VDub's development for over a decade and was also owned, maintained, and administrated by Avery under the nick of Phaeton, so maybe we could link to the version archived by Wayback for documentation? [33] After the close of the original "Unofficial" VDub forum, some members have started the Really Unofficial VirtualDub Forums at [34], with the latest posts (related to Windows 10 workarounds for the Quicktime plugin) dating to July 2016.
Also, it's not true that VirtualDubMod development ended for good in 2005 or 2006. Further development on VirtualDubMod by Chattama happened in 2008: [35] (his version/fork seems to be called "VirtualDub+"), and by bcn_246 at least as late as December 2012: [36] Another fork that remained in maintenance up until March 2015 was VirtualDub2mpgtx that basically was a combination of VDub with a tool called mpgtx: [37] It was basically to edit specifically MPEG-1 files.
Finally, there's a new VDub mod started in or before April 2015 that's still in maintenance and updated regularly well into the 4K and UHD era, and that's VirtualDub FilterMod: [38] Here's its updates and development thread on Doom9 still alive and kicking in mid-February 2017: [39]
Lastly, the article would greatly benefit from a remark about the start of VDub's lifetime in the lead and in the infobox. In any case, Avery first uploaded a version on SourceForge on August 20th, 2000: [40] -- 79.242.219.119 ( talk) 17:52, 18 February 2017 (UTC)