| Main > Software Forum |
| MAME Movie Maker released |
| << < (141/153) > >> |
| Howard_Casto:
You guys know my feelings on mngs. They are pure crap. Not because the end result is bad (it's actually quite good), but because nothing can play it. Mng doesn't have a standard at all, that's the problem. Getting mng creators to agree on a standard is like getting visual pinball authors to agree on a naming convention. ;) I was thinking that even the loop detection could be done externally. Mame would spit out pngs (or even an mng) right? Well those could be compared as they are being outputted by an external app, and the app could simply terminate mame once it detects a loop, remembering the frame it stopped on and deleting any extras that might occur before mame quits. Again, this isn't the best solution for the end user, but it could be for anyone maintaining a list of start/stop frames. |
| cdbrown:
Silver - the vcodec.dat that is produced by your batchmaker. I set the X max 128 and Y mas to 96 and the following is produced VirtualDub.video.filters.instance[0].Config(320,256,0,0,320,256,0x000000,"1 1 1 2 128 96 100 0 0 1 1 4 4 2 2"); I notice it still has 320,256 references - does this have any bearing on the smart resize. Also after a few tests, Quantiser=3 seems to provide a good quality video at a good encode rate (for 005 18kbps, 3in1semi 26kbps) and the file size is reasonable. However 1941 encodes at 104kbps and looks fairly crap. |
| Howard_Casto:
1942 would look like crap.... think about it, you just set the res to 128x96 and it's a vertical game. :) |
| cdbrown:
ahah - I've got you on two points HC. First was talking about 1941 (not 1942) and the smart resize plugin used in vdub keeps the games original aspect ratio and resizes it to keep it below the res u set. So for 1942 (using your example) I had it set to a max output 128x96, the original res is 224x256 and output is resized to 110x96. However - it still looks crap |
| Silver:
--- Quote from: cdbrown on September 29, 2005, 02:20:47 am ---Silver - the vcodec.dat that is produced by your batchmaker. I set the X max 128 and Y mas to 96 and the following is produced VirtualDub.video.filters.instance[0].Config(320,256,0,0,320,256,0x000000,"1 1 1 2 128 96 100 0 0 1 1 4 4 2 2"); I notice it still has 320,256 references - does this have any bearing on the smart resize. Also after a few tests, Quantiser=3 seems to provide a good quality video at a good encode rate (for 005 18kbps, 3in1semi 26kbps) and the file size is reasonable. However 1941 encodes at 104kbps and looks fairly crap. --- End quote --- Hi yes, this is simply the plugin recording all the options in its config - several of them are grayed out when you select certain other ones. I actually just shoved the 320/256 in there as in my tests it has no bearing. The important ones are the 128/96 later on (along with the others). regarding quality. Quantiser variations may not be the best option - if its easier I can stick in some manual "target bitrates" if that helps. Try having a manual play with compression settings in Vdub/Xvid to see what you are after. I will say that knocking the resolution down to that size looks fairly dodgy with no compression whatsoever to me on some games. The resize filter definately has an impact. In theory I think Precise Bicubic should be the most 'detailed' but nearest neighbour may be better than you think because there is no smoothing going on.... I hate to say it, but this may be one of the reasons MNG was used, as it can be losslessly compressed quite effectively at low resolutions compared to a mpeg4 codec like Xvid. There lots of settings to try yet though..... Also, remember you can always change the filter.sql part of listgen to create a batch for vertical and then a batch for horizontal and have differnt res settings... In fact I should be able to include this option in the batch creator.... |
| Navigation |
| Message Index |
| Next page |
| Previous page |