|
|
| Abrazo |
| Posted: Oct 12 2013, 11:02 AM |
 |
|
Advanced Member
Group: Members
Posts: 775
Member No.: 28995
Joined: 5-November 10
|
I regularly notice newbies having difficulties to open non-AVI files in VirtualDub.
Every time we need to explain how to install inputdriver plugins, extra codecs, etc.
So I think about an option to set the default "Open" behaviour of VirtualDub.
If the DirectShow inputdriver plugin would be part of the installation package of VirtualDub, this could be set as default for opening files.
The Windows Operating System already contains a large number of DirectShow decoders for several kinds of files, so VirtualDub could use these.
For other files one could consider installing extra inputdrivers (like FFMpeg).
Setting the default Open behaviour should be working via selecting the preferred choice out of a list (of installed inputdrivers).
The actual behaviour could be part of this list.
We could think the same way for setting a default "Save" behaviour.
Given the fact that we can configure External Encoders, we could consider selecting one of these for the default Output format.
Thanks to Phaeron to think about this proposition. |
|
| dloneranger |
| Posted: Oct 12 2013, 11:59 AM |
|
|
Moderator
Group: Moderators
Posts: 2366
Member No.: 22158
Joined: 26-September 07
|
If the directshow plugin is in the plugins folder, virtualdub will use it automatically for any directshow type files already
Any plugin can tell virtualdub 'i can open that file' and 'how good I am at opening that kind of file'
Just for double checking, I created a new virtual machine, put virtualdub and the directshow plugin on, dragged an mp4 into it, and it just opened straight away, no problem
The guy that I assume you're thinking about (with 30 years programming experience...) just wanted a push-the-red button program, complained that this was too hard, complained about the explanations and then wanted his thread deleted
At the moment, there's no user way to prioritize input plugins though
I guess that just including the DirectShow plugin would stop some complaints, but that's just for opening the file......
Then you've still got a hundred questions about getting codecs that can encode with, configure them etc
Not to mention the can't directstream copy a file opened with the DirectShow plugin (as it returns uncompressed audio/video)
Bundling an external encoder might help for your default save idea, but then it'll just be - it's the WRONG encoder, the files are too big/small, it doesn't play on my ithing etc etc
I can totally see your points, but wouldn't it just be a case of moving the problem's newbies have around a bit?
TBH, I don't see virtualdub targeted as a beginners editor, but something they can use after they've outgrown the simple converters
And here's another thought - putting the level of difficulty right there at the start does give people the instant chance to go 'uh oh, i'm in over my head, maybe I'll try something simpler for now'
--------------------
MultiAdjust JoinWav WavNormalize FFMPeg Input Plugin v1827 UnSharpMask
Windows7/8 Codec Chooser
All FccHandlers Stuff inc. Installers for acm codecs AAC, AC3, LameMp3 |
|
| -vdub- |
| Posted: Oct 12 2013, 02:16 PM |
|
|
Advanced Member
Group: Members
Posts: 613
Member No.: 27087
Joined: 24-February 10
|
| QUOTE (dloneranger @ Oct 12 2013, 11:59 AM) | If the directshow plugin is in the plugins folder, virtualdub will use it automatically for any directshow type files already
Any plugin can tell virtualdub 'i can open that file' and 'how good I am at opening that kind of file'
Just for double checking, I created a new virtual machine, put virtualdub and the directshow plugin on, dragged an mp4 into it, and it just opened straight away, no problem |
That would likely need quicktime installed on the os, but many don't have quicktime installed. Without quicktime installed on os with Phaeron's DshowInputDriver.plugin you could open a mp4 but no video picture or aac audio will be decoded (unless os has mp4 decoded and DshowInputDriver is able to use it). Reason we have the plugins that can decode these such as fcchandler's quicktime or ffinputdriver.
There are many items on virtualdub roadmap that need coding. If this idea was implemented it would likely leave little time to do those. Maybe then the future but I don't hold out for it neither does Phaeron maybe. Given that there are many options already for decoding. Best let Phaeron do virtualdub and hopefully not to much time on his other projects  And everyone else make and keep updated decoder plugins that we use with virtualdub
I agree that always the latest DshowInputDriver.plugin should be packaged with each beta and release versions of virtualdub. That one plugin alone is best as Phaeron has full control over that. And since that I guess not many people know where to find it or that it even exists. |
|
| dloneranger |
| Posted: Oct 12 2013, 05:15 PM |
|
|
Moderator
Group: Moderators
Posts: 2366
Member No.: 22158
Joined: 26-September 07
|
| QUOTE | | That would likely need quicktime installed on the os |
Yup, though what I meant (as the important part) was that the plugin will load anything that DirectShow players can, without any messing about
(just for clarification)
--------------------
MultiAdjust JoinWav WavNormalize FFMPeg Input Plugin v1827 UnSharpMask
Windows7/8 Codec Chooser
All FccHandlers Stuff inc. Installers for acm codecs AAC, AC3, LameMp3 |
|
| Abrazo |
| Posted: Oct 12 2013, 07:32 PM |
|
|
Advanced Member
Group: Members
Posts: 775
Member No.: 28995
Joined: 5-November 10
|
Thanks dloneranger and -vdub- for your ideas about my proposition.
Sometimes it is rather difficult to make things easier...
But once one get the experience, one find out that something that was difficult in the beginning has become easy at the end...
Maybe newbies should have a little bit more patience and do a little bit more effort to learn how VirtualDub works...
I love this program anyway. |
|
| dloneranger |
| Posted: Oct 12 2013, 07:55 PM |
|
|
Moderator
Group: Moderators
Posts: 2366
Member No.: 22158
Joined: 26-September 07
|
I think the problem is that once you get past the 'push the button' level of simplicity, there's a steep learning curve
Any way of making it easier would good, but most of this just isn't 'easy'
I do think that including the DirectShow plugin would be a good idea though 
It's hard to see a down side to it
--------------------
MultiAdjust JoinWav WavNormalize FFMPeg Input Plugin v1827 UnSharpMask
Windows7/8 Codec Chooser
All FccHandlers Stuff inc. Installers for acm codecs AAC, AC3, LameMp3 |
|
