VirtualDub (video editor)

[saber]

Download: http://downloads.sourceforge.net/portab ... .8.paf.exe

[nedurnan]

The latest update is available for download.

http://portableapps.com/apps/music_vide ... b_portable

[Midas]

For lack of a better option, I'm creating the present topic as the official one for VirtualDub (http://www.portablefreeware.com/?id=19) discussion...

VirtualDub is a video capture/processing utility for 32-bit and 64-bit Windows platforms (98/ME/NT4/2000/XP/Vista/7), licensed under the GNU General Public License (GPL). It lacks the editing power of a general-purpose editor such as Adobe Premiere, but is streamlined for fast linear operations over video. It has batch-processing capabilities for processing large numbers of files and can be extended with third-party video filters. VirtualDub is mainly geared toward processing AVI files, although it can read (not write) MPEG-1 and also handle sets of BMP images.

Download VirtualDub latest release (currently v1.10.4.35491) from sourceforge.net/projects/virtualdub/files/virtualdub-win/.

[Midas]

Joe's comment (www.portablefreeware.com/index.php?id=19#comment27580) in VirtualDub Portable database entry deserves some attention, IMHO...

BTW, a ready-made configuration file for yaP launcher is available from http://www.rolandtoth.hu/yaP/configs/VirtualDub.ini.

[Joe]

Thank you for starting this topic Midas. That is what I should have done but I'm just not accustomed to commenting in the forums. I'll try to remember to do that in the future.

Anyway, good news! joby_toss posted a solution, or rather, a way to make the Portable Apps launcher start the 32-bit application rather than the 64-bit one. See... http://www.portablefreeware.com/index.p ... mment27582.

Due to these issues, I would like to recommend some amendments to the VirtualDub listing:

1. A hyperlink to joby_toss' comment for users who want to use 32-bit plugins.

2. Just as mention is made of the Portable Apps Plugin Pack, I believe some mention should be made of the FFMpeg Input Plugin which is available at http://sourceforge.net/projects/virtual ... putplugin/. It is really a much better alternative, and it is stealth (as far as I can tell).

[webfork]

Let's break this down step by step because any entry edits need to be very easy to understand and follow.

A hyperlink to joby_toss' comment for users who want to use 32-bit plugins.

Why would someone want to use 32-bit plugins? Who should do that and why?

Just as mention is made of the Portable Apps Plugin Pack, I believe some mention should be made of the FFMpeg Input Plugin which is available at http://sourceforge.net/projects/virtual ... putplugin/. It is really a much better alternative, and it is stealth (as far as I can tell).

Mention how? Can you draft something up?

[Joe]

This is the recommendation from the developer of VirtualDub...

It is recommended that you use the 32-bit version unless you have a specific need for 64-bit execution, as the 64-bit version cannot use 32-bit codecs or plugins.

[Source: http://virtualdub.sourceforge.net/]

Why would someone want to use 32-bit plugins?

At present, many plugins exist in 32-bit but not 64-bit.

Who should do that and why?

Users who have 64-bit systems but who want to run the 32-bit version of VirtualDub because there are a greater choice of plugins.

I wish it wasn't so but that's the reality.

Mention how? Can you draft something up?

What do you think about this...

VirtualDub is a video capture/processing utility. It lacks the editing power of a general-purpose editor such as Adobe Premiere, but is great for video capture and transcoding via third-party video codecs. Addition of the FFMpeg Input Plugin will allow VirtualDub to open most formats.

64-bit users who wish to run VirtualDub with 32-bit plugins should follow this suggestion by joby_toss.

VirtualDub Portable is a PortableApps.com format wrapper for VirtualDub. Alternatively, X-VirtualDub is also available.

The forum software doesn't allow hyperlinks but you should get the gist.

[Edit]
The "How to extract" instructions would have to be amended too. Something like this should work...

1. Download the self-extracting EXE and extract to a folder of your choice
2. Optionally, unzip the FFMpeg Input Plugin and copy the plugins32 and plugins64 folders to VirtualDubPortable\App\VirtualDub and VirtualDubPortable\App\VirtualDub64.
3. Launch VirtualDubPortable.exe

[JohnTHaller]

If folks are interested, I could add a setting into VirtualDub Portable to force it to run in 32-bit mode. I switched it to a dual mode app at the request of several users originally.

[joby_toss]

Having the freedom to choose is always a good thing. Thank's!

[Joe]

If folks are interested, I could add a setting into VirtualDub Portable to force it to run in 32-bit mode. I switched it to a dual mode app at the request of several users originally.

Nothing whatsoever is wrong with a dual-mode app. The real problem is when an app doesn't give me a choice because it knows what is best for me.

[JohnTHaller]

Nothing whatsoever is wrong with a dual-mode app. The real problem is when an app doesn't give me a choice because it knows what is best for me.

As a general rule, most apps in dual mode should run in 64-bit mode on 64-bit OSes and there's no need to give the user a choice. Things like jkDefrag or Peerblock where the 32-bit version won't work on a 64-bit OS; or 7-Zip where the 64-bit version outperforms the 32-bit version by a large margin and there's no downside; or RawTherapee where the publisher recommends against using the 32-bit version at all.

There's really only one situation among our released apps where it makes sense to give a choice. And that's when the 64-bit version of an app doesn't support 32-bit plugins and there are tons of 32-bit plugins without 64-bit counterparts... a situation where it'd normally make sense to only release a 32-bit version... but there are also lots of users that want the increased performance of the 64-bit version instead of the 32-bit compatibility... exactly as we're seeing here

[Joe]

...that's when the 64-bit version of an app doesn't support 32-bit plugins and there are tons of 32-bit plugins without 64-bit counterparts...

Are you saying you were aware of this but made the decision to give 64-bit users performance over the ability to use 32-bit plugins?

[webfork]

...that's when the 64-bit version of an app doesn't support 32-bit plugins and there are tons of 32-bit plugins without 64-bit counterparts...

Are you saying you were aware of this but made the decision to give 64-bit users performance over the ability to use 32-bit plugins?

I don't know if you intended it here, but I need you to get away from the accusatory thing. Try something like: "Hey John, how about adding something to the UI to give 64-bit users the option to use 32-bit?"

[JohnTHaller]

I don't know if you intended it here, but I need you to get away from the accusatory thing. Try something like: "Hey John, how about adding something to the UI to give 64-bit users the option to use 32-bit?"

Which is exactly what I offered above, since this is the first time anyone has brought up the issue with 32-bit plugins in VirtualDub. Most VirtualDub Portable users are fine with the set of plugins we make available as they include both the 32-bit versions and 64-bit versions in the download pack and cover all the standard formats most users seem to want. Most users don't seem to use plugins from other locations, so this hadn't come up before.

[Joe]

I don't know if you intended it here, but I need you to get away from the accusatory thing.

I'm really sorry if anyone should take it like that. All I did was ask a question and John could have simply replied “No. I wasn’t aware that 64-bit users wouldn’t be able to use 32-bit plugins” or whatever is the case.

Which is exactly what I offered above, since this is the first time anyone has brought up the issue with 32-bit plugins in VirtualDub.

Don’t get me wrong. I am glad that you offered but I also think no one ever raised the matter because previous users were none the wiser.

Most VirtualDub Portable users are fine with the set of plugins we make available as they include both the 32-bit versions and 64-bit versions in the download pack and cover all the standard formats most users seem to want.

That sounds like you are referring to this Plugins Pack: http://downloads.sourceforge.net/portab ... e?download. Sorry if I wasn’t clear. That Plugin Pack is another matter. What I meant was many plugins are available only in 32-bit - there are no 64-bit versions. For example...

Histogram Equalization (http://rationalqm.us/histogram.html)
Unsharp Mask (http://neuron2.net/unsharp/unsharp.html)
MSU Denoiser (http://compression.ru/video/denoising/index_en.html)

There are no 64-bit versions of these plugins and it is the same with many others. As you so aptly put it ”...there are tons of 32-bit plugins without 64-bit counterparts...”

Most users don't seem to use plugins from other locations, so this hadn't come up before.

Hopefully we are talking about the same thing here. Nevertheless, have you considered that many users may not even be aware that if they were able to use VirtualDub 32-bit then much more plugins would be available to them? That they may be able to do what they couldn't before? My own thought is users should be made aware of the facts so that they can make an informed decision. With that in mind, I believe displaying a prominent notice on the VirtualDub page would be most helpful to potential users.

Sorry to have taken so much time to respond but I went to the trouble of running some tests. I created a simple set of processing settings and saved it. I then loaded these settings on both the 32-bit and 64-bit of VirtualDub in turn and tested an 8 minutes video clip. I was shocked to find that the 64-bit version actually took around 11% more time! I couldn’t believe it so I ran two more tests on different video clips and both times the 64-bit version took between 11% and 13% longer. Whether or not it is generally true for 64-bit applications to outperform their 32-bit counterparts, it certainly isn’t the case here. Try it yourself and see.