|
|
| jsallen |
| Posted: Oct 13 2013, 07:02 PM |
 |
|
Advanced Member
Group: Members
Posts: 30
Member No.: 33725
Joined: 4-December 11
|
To me, one of the biggest obstacles to use of VirtualDub is the need to gather files from multiple sources to achieve an installation which will read most common video file types and output files with optimal compression.
Yesterday I bit the bullet, so to speak, and spent most of a day, until 2:30 AM, pulling all the pieces together, making repeated tries until I finally had a VirtualDub 64-bit installation which would read .MP4 and .MOV files (and probably many others, as I included the input filters for them).
All the items in the VirtualDub folder are freeware. Is there any problem with creation and posting of a .zip archive which would include
* the entire VirtualDub folder with subfolders, to be simply extracted and dropped into the user's Program files folder,
* links to where to download other files (e.g., QuickTime, XVid, ffdshow, AACACM, AC3ACM) that are needed to implement input and output? Those files which are freeware also could be included in the archive.
* A readme file describing how to install the different components, and requesting donations to software authors who have asked for them
* Licensing information.
I'd be happy to assemble such an archive but I'd want it to be tested. There should be a few version (32-bit, 64-bit, stable, beta) and it should be updated from time to time.
Could this be posted on virtualdub.org? If not, might it be posted elsewhere? I could post it on my own site, if needed. |
|
| dloneranger |
| Posted: Oct 13 2013, 09:33 PM |
|
|
Moderator
Group: Moderators
Posts: 2366
Member No.: 22158
Joined: 26-September 07
|
There could be 'issues' with copyright and legality that the author of virtualdub doesn't want to be involved with
Hunting down permissions etc alone could be difficult, especially when some of the authors are untraceable (eg fcchandler)
Last time I looked even common things like Lame and XVid are not strictly speaking legit for redistribution
Software patents, gotta love software patents..........
--------------------
MultiAdjust JoinWav WavNormalize FFMPeg Input Plugin v1827 UnSharpMask
Windows7/8 Codec Chooser
All FccHandlers Stuff inc. Installers for acm codecs AAC, AC3, LameMp3 |
|
| jsallen |
| Posted: Oct 14 2013, 03:03 AM |
|
|
Advanced Member
Group: Members
Posts: 30
Member No.: 33725
Joined: 4-December 11
|
OK -- the enxt best thing is a step-by-step installation guide. I've posted one for my installation of 64-bit VirtualDub here:
http://forums.virtualdub.org/index.php?act...t=60#entry94286
But -- I'm sure this could be improved on and also, there are pitfalls to avoid. For example, at one point I installed the K-Lite Codec pack and the VirtualDub input filters stopped working. I suspect that was because of the 32-bit ffdshow which K-Lite installed. I uninstalled K-lite and installed the latest 64-bit ffdshow. OTOH there are probably file formats I can't access in some apps because I don't have the needed input filters.
Actually I checked and I now at last can open .ASF files from the Aiptek DVR which helmetcamera.com used to sell. A little message box, "constructing ASF input block" informs me that fcchandler's WMV input filter now manages that. Good show. I've always had to convert thsoe files externally.
But now the DirectShow Input Driver only opens AVI files (not much help, that!) and I still can't open the .MTS files from Canon HD camcorders. If I install something which might work for them, (for example, the ffmpeg input driver currently under development), something else or everything else might stop working.
One possibility would be alternative installations in different folders. That's easy enough but when there are turf wars between external codecs, that is more difficult.
I'm also concerned about external components I installed for VirtualDub preventing files from opening or saving in other apps.
My next step is to install VirtualDub 64-bit with the ffmpeg input driver on a machine which is about to come back from repair, but it would be good to have a step-by-step installation procedure for that too.
|
|
|
