|
|
| DarrellS |
| Posted: Jun 18 2013, 05:46 PM |
 |
|
Advanced Member
Group: Members
Posts: 567
Member No.: 1061
Joined: 28-November 02
|
An option to clear the vdprof file that you're using so you can experiment with new encoders without having to muck up the vdprof file that you're using at the time. As it is, you have to delete all the encoders and encoder sets to create a new vdprof file for new encoders that you are experimenting with.
Maybe, when you choose to export a vdprof file, an option to remove it from the current list. With this option, you could create and save separate vdprof files for each file type that you are working with and import them and export them separately.
...or a separate GUI that is not part of Virtualdub that you can store in the tools folder just for creating encoder sets that you can experiment with without messing up your default vdprof file. Either way, you would need an option to remove the current vdprof file to load a new one. As it is, if you try to load another vdprof file that has some encoder sets that the current file already has, Virtualdub refuses to load it.
I have a few vdprof files that I have created in the last three years and I don't have a clue which one to load unless I open them in notepad (I do have a Default one that just has the essentials).
Maybe if Virtualdub didn't load the vdprof file at startup and you had the option to load whichever vdprof file you needed at the time. If you were encoding x264 then you could load your x264 vdprof file or if you were just experimenting trying to get an encoder set to work, you could load that vdprof file.
|
|
| -vdub- |
| Posted: Jun 18 2013, 10:57 PM |
|
|
Advanced Member
Group: Members
Posts: 613
Member No.: 27087
Joined: 24-February 10
|
@ phaeron some more posted here Post # 6
External Encoders needs updating making it easier to use for everyone |
|
| phaeron |
| Posted: Jun 30 2013, 09:04 PM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
Sorry that I haven't had much time to put into this stuff... but yeah, I know where you're coming from. Having the encoder settings hosted in the Registry made it easier to bootstrap the system, but I think I'm going to look into putting in support for loading directly from the .vdprof files rather than having to copy them into the Registry.
|
|
| meowmeow |
| Posted: Nov 14 2013, 02:01 PM |
|
|
Advanced Member
Group: Members
Posts: 98
Member No.: 37160
Joined: 21-September 13
|
| QUOTE (DarrellS @ Jun 18 2013, 05:46 PM) | | ...or a separate GUI that is not part of Virtualdub that you can store in the tools folder just for creating encoder sets |
Thinking about it
Expand external encoders with configurable presets to support all past and future versions 
Example format: encoder "X" has "N" options:
1:prefix(--color):integer(-100,100),
2:prefix(--level):text("low","high"),
5:prefix(--format):text("mkv","mp4"),
3:prefix(-q):float(0,1),
4:prefix(-m):float(0,1),
6:prefix(--filter):set:integer(-1,1):text(","):float(0,10)
...
Or something alike to allow user reprogram GUI |
|
