| Main > Software Forum |
| MAME Movie Maker released |
| << < (29/153) > >> |
| Buddabing:
--- Quote from: Silver on January 11, 2005, 07:16:34 pm ---@Buddabing Well you could change to the "job-running" mode of virtualdub using the script file you have now, although you would have to re-introduce all the line beginning with "\\" that you don't need for script execution. I think a batch solution might be more workable, and allow people to opt-out of it should they wish to be alerted to errors. Vid encoding: I've found another (could this be the last?) encoding issue - what I had hoped that games wouldn't do, does - they change resolution on the fly. The only game I have that does this is 'cbaj'. Its one of this ones that changes resolution during start up, but it seems to do it later on in the attract mode too. The attract for this game goes: show a white animated logo, a demo game, the white logo again, --- End quote --- |
| Buddabing:
Hello, I've also updated version 0.89 with the latest and greatest code. The zip file, including source and binary, is here. (EDIT: link removed) Please post any bug reports, feature requests, etc. to this thread. |
| Howard_Casto:
--- Quote from: Silver on January 13, 2005, 06:18:34 am --- --- Quote from: Howard_Casto on January 13, 2005, 05:25:12 am --- Keep in mind that video frames in any of the hardware accelerated front ends are treated as textures. --- End quote --- --- End quote --- |
| Silver:
--- Quote from: Howard_Casto on January 13, 2005, 06:11:12 pm --- Well anything that uses hardware aceleration which means that mamewah, a gdi based fe is safe. Basically Dragon King, 3dArcade, Kymera and anything that'll use the movie as a texture will suffer. --- End quote --- Ah, I did not realise that! --- Quote ---By square I mean a 1:1 ratio. Peter and myself use the aspect ratio of the snapshot to fix the ratio back upon playback, I dunno how other fes do it. Multiples of 16 aren't as important as they used to be. Your video card would have to be really frikkin old to have to worry about that. However, being under the maximum texture size your card can handle, (which is a multiple of 16) is important. Btw, if your pc is farily modern, you shouldn't have to worry about these things at all. I am aware of how some poor souls in this community try to scrape by with a 300mhz pc though, so I thought I would mention all of this in case budda wants to add options for that type of rendering. Back when the original 3darcade videos were being made, peter and myself argued over this point a lot. I prefer high quality and ghetto users can deal with it, while he takes the conservative route. As the years, have passed, however, I seem to have softened towards those people who don't invest enough money in their pc. ;) --- End quote --- Well now that the sources are out, its perfectly possible to modify the source to change .vdb file created to compress/resize/filter in pretty much anyway you like. I have no idea if Buddabing would or would not like to add this functionality. If anyone wants to do these kind of changes, the 2 ways I suggest: 1) create uncompressed videos (as one of buddabings options) and then run another session of virtualdub in the batch to recompress/resize etc.. as desired. I recommend doing it as part of the batch loop as otherwise you would need ridiculous amounts of storage to create them all first.... 2) Better option: find where the .vdb file is created in buddabing's source patch and alter as desired. To find out what you want, run virtualdub and set it up with filters etc.. for what you want (resize etc..) then save it as a job. Looking in the virtualdub.jobs file will show you the text you need to include in the vdb file. If anyone is very keen on 2), and Buddabing wants to leave it, I can help with an appropriate virtualdub script. Or Buddabing if you want to add another option for lower quality (ie reaspect/resize everything to 256x256 so it works well as a texture) I can fire over the required script changes. |
| Buddabing:
--- Quote from: Silver on January 13, 2005, 06:48:57 pm --- --- Quote from: Howard_Casto on January 13, 2005, 06:11:12 pm --- Well anything that uses hardware aceleration which means that mamewah, a gdi based fe is safe. Basically Dragon King, 3dArcade, Kymera and anything that'll use the movie as a texture will suffer. --- End quote --- Ah, I did not realise that! --- Quote ---By square I mean a 1:1 ratio. Peter and myself use the aspect ratio of the snapshot to fix the ratio back upon playback, I dunno how other fes do it. Multiples of 16 aren't as important as they used to be. Your video card would have to be really frikkin old to have to worry about that. However, being under the maximum texture size your card can handle, (which is a multiple of 16) is important. Btw, if your pc is farily modern, you shouldn't have to worry about these things at all. I am aware of how some poor souls in this community try to scrape by with a 300mhz pc though, so I thought I would mention all of this in case budda wants to add options for that type of rendering. Back when the original 3darcade videos were being made, peter and myself argued over this point a lot. I prefer high quality and ghetto users can deal with it, while he takes the conservative route. As the years, have passed, however, I seem to have softened towards those people who don't invest enough money in their pc. ;) --- End quote --- Well now that the sources are out, its perfectly possible to modify the source to change .vdb file created to compress/resize/filter in pretty much anyway you like. I have no idea if Buddabing would or would not like to add this functionality. If anyone wants to do these kind of changes, the 2 ways I suggest: 1) create uncompressed videos (as one of buddabings options) and then run another session of virtualdub in the batch to recompress/resize etc.. as desired. I recommend doing it as part of the batch loop as otherwise you would need ridiculous amounts of storage to create them all first.... 2) Better option: find where the .vdb file is created in buddabing's source patch and alter as desired. To find out what you want, run virtualdub and set it up with filters etc.. for what you want (resize etc..) then save it as a job. Looking in the virtualdub.jobs file will show you the text you need to include in the vdb file. If anyone is very keen on 2), and Buddabing wants to leave it, I can help with an appropriate virtualdub script. Or Buddabing if you want to add another option for lower quality (ie reaspect/resize everything to 256x256 so it works well as a texture) I can fire over the required script changes. --- End quote --- I can add an option which will make the vdb script trim the video to 256x256. I have no objection. I would like Silver to create a sample vdb that I can use. I presume we want to trim off the longer side and then reduce (or expand if less than 256?) the movie. I would prefer that we not have a zillion different builds of this build of MAME floating around, because people will want the "help desk" to solve all their problems, and it will be considerably more difficult if everyone has their own non-standard build. |
| Navigation |
| Message Index |
| Next page |
| Previous page |