Very good idea, Emp3r0r! In fact, I had a similar idea some time ago, when I noticed I would like to keep trace of what settings I used for my past encodings, and that I'm too lazy to write or type all that stuff manually. (But, honestly, often when I think "should I suggest this or that", I finally decide to keep quiet - most of my ideas result out of a sudden "brainstorm" and are often not useful at all, and so even some good ideas might get lost.) However, I'm glad to see you had this idea and realized it. Thank you!
Emperor, that's really a good idea! But I've 2 proposals: 1) can you make it a GUI so it's noob friendly? We could include that into our builds then and if a problem occurs, the user just would use the startmenu shortcut, choose output format and filename/directory and gets a nice file with the settings... 2) the output as is now is really nice, but it's hard to read. Can you try making it a "simple" text-table, e.g.: Mode: 2pass 1st pass Dummy 1st pass: on Dummy 2nd pass: off Desired size: ... and so on, so have some more lines of it's own? (like for nandub reports if you can remember them). You could condense 2 options on a line or so, but some more cr/lfs would help readability much. Thank you for this nice program! Regards Koepi
@koepi: Sure, I'll go ahead and modify the XSL stylesheet to produce columns of settings. In fact, My first stylesheet did that but there are so many settings it took up lots of room. The GUI will take 5 seconds but as far as including it with XviD, that may cause too many problems because it requires XP SP1 or .NET framework (everyone got that yet?). Although, I do think it would be a valuable addition to benefit developers and users/testers (such as iago ;)). If anyone has a vision of exactly how the output should look for here in the forum, I'll create a stylesheet for you. Show me some examples please!
Ok, I finally found 5 secs to create that GUI you asked for. [edit] Newer Version Available (look further down) [/edit] There is a visual studio.net project included with sources if you wish to peek. Sorry for no comments. I modified the stylesheet too. I wish others would make stylesheets because I think XSL is easy to understand. Enjoy. example output Settings for XviD (11/1/2002 6:13:49 AM) Mode: 2 Pass - 1st pass Discard 1st Pass: OFF Motion Search Precision: 6 - Ultra Quantization Type: MPEG FourCC Used: XVID Max I-frame Interval: 240, Min I-frame Interval: 1 Lumimasking: OFF Interlacing: OFF Greyscale: OFF B-frames: Disabled Min I-frame Quantizer: 2, Max I-frame Quantizer: 31 Min P-frame Quantizer: 2, Max P-frame Quantizer: 31 Max Bitrate: 10000kbps, Max Overflow Improvement: 60%, Max Overflow Degradation: 60% Start Credits: OFF, End Credits: 186190-196155 Encode credits in greyscale: OFF Credits I-frame Quantizer: 23, Credits P-frame Quantizer: 21
@Koepi and Nic: Currently I am looking in the Windows system directory for xvid.dll and getting the creation time of that file to figure out the date of the build. So I have the date but I'm still lacking who built it. Maybe another registry entry named build would fix this problem. Then we could produce the following output: XviD Settings (Koepi's Build 11/1/2002 6:13:49 AM) or XviD Settings (Nic's Build 11/1/2002 6:13:49 AM)
@Emp3r0r, Thank you for your useful program, but I still can not run the program since I don't have .Net framework installed on my machine. I think I have to download that .NET framework from MS which its size is about ~21MB big :( That's BIG!. :( Is that possible to port it to stand-alone .exe ?
Yes I know it is big, but look how small the exe is. In the long run it will be more efficient but for PRE-Service Pack 1 XP machines it is not. Sorry.