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.

 
What Vd Should Have & Virtualdubmod Already Had, This is my list of important differences
« Next Oldest | Next Newest » Track this topic | Email this topic | Print this topic
XYZ
Posted: Oct 22 2007, 11:27 AM


Advanced Member


Group: Members
Posts: 48
Member No.: 22012
Joined: 27-August 07



1. More user-friendly manipulation with many audio streams (it should be considered from the start, especially now when VD 1.7.X is in developement). This means, there should be a way for user to add / delete / move up/down selected audio stream with descriptive display of audio characteristics for all audio streams.

2. Audio demultiplexer should be in Audio menu (not such File / Export / Raw audio) and an extension of saved files should be automatically determined from the audio content (MP3, AC3, PCM). The Save WAV option also should be moved to the Audio menu. It is inconsistent that the import audio file option is in Audio menu, and the export is in File menu.

3. Generally speaking, the File menu is overloaded and too confusing, VirtualDubMod have it more compact. Save old format AVI and Save segmented AVi should not be in the menu, but as options in the Save As dialog.

4. Possibility to remember preferred video mode (Direct stream copy, ...) in Preferences menu. Defining keyboard shortcuts also could be interesting.

5. Maybe added support for subtitle streams... or AviSynth script editor...

My next suggestions, not found in VDM: all Preview options (input, filtered, output from start) should be moved to Go menu; they have more similarities with navigation behavior of this menu. Also, recently opened files should be inside of a File sub-menu. Currently, if I have recently opened files with too long path, the File menu is too wide and covers full screen.

Please, don't get me wrong. VirtualDub is already great program, and this is only friendly suggestions in hope that it could be even better.
 
     Top
phaeron
Posted: Oct 23 2007, 08:24 AM


Virtualdub Developer


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



Added to ideas file... except for the moving of the MRU list to a submenu. I hate it when programs do that. Not going to happen.

Avisynth editor is also not likely to happen, mostly because I doubt it's worth the effort for me to pack in a partly outdated editor that at most tracks syntax for some version of Avisynth eight versions back. I'd rather just put in auto-reload and let you provide the editor.

 
    Top
XYZ
Posted: Oct 23 2007, 09:18 AM


Advanced Member


Group: Members
Posts: 48
Member No.: 22012
Joined: 27-August 07



Thank you very much for considering my suggestions. I am not insisting on this, especially not on MRU or AviSynth... just mentioned.

But now, I have another thing on my mind in connection with AviSynth. Your program is great, but there are many situations when users need something more which could be done only with AviSynth. Unfortunately, this program is a "little" complicated for beginners and it would be great if VirtualDub could make easier for them to use some of its elemental possibilities. Maybe something as opening AVS templates in VirtualDubMod. Nothing fancy, just support for AVISource and DirectShowSource.

In my opinion, best approach to creating AviSynth scripts for beginners has FitCD. If you did't tried it yet, please do it. With it, user could load AVI/MPG/WMV..., resize it to specific resolution, set aspect ratio, set deinterlacer... without typing a single line of the code. I know that VirtualDub has all this possibilities with its filters, but AviSynth could open many file formats which VirtualDub still cannot, even with new input plug-ins. I think, if you implement something like this, many users would be very happy.
 
     Top
XYZ
Posted: Oct 24 2007, 01:09 PM


Advanced Member


Group: Members
Posts: 48
Member No.: 22012
Joined: 27-August 07



I forgot to explain how I imagined this AviSynth thing. I suppose that you know about VirtalDubMod's AVS templates, but just in case if you didn't tried it yet, I'll try to explain it as short as possible.

VDM has a combo box "Use AviSynth template" in the Open File dialog box with several items: if user choose [none], then behavior is same as within VD - program will load a file directly. But, if user choose AviSource, DirectShowSource or some another item from this combo, program create temporary AVS file with mentioned AviSynth statement and its argument is a file selected in Open File dialog. In this way, user could open any file in VirtualDub which is supported by AviSynth without typing any line of the script.

This is very nice, but user still need to choose some AVS template. Many beginners even don't know what is an AviSynth, and especially not which is a difference between its loading statements. Here is how FitCD works. When user load a file, program check its extension and create AVS script with corresponding loading statement - if file is standard AVI, the statement is automatically set to AVISource, and if a file is MPG or WMV, the statement is set to DirectShowSource - user even don't need to choose loading statement.

Maybe best approach would be a combination of this two. So, here is my new suggestion. VirtualDub could have same combo box as VirtualDubMod, but with added one new item, let say [automatic], with same behavior as it is in FitCD.
 
     Top
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
3 replies since Oct 22 2007, 11:27 AM Track this topic | Email this topic | Print this topic

<< Back to VirtualDub Development Forum