| Main > Software Forum |
| MAME Movie Maker released |
| << < (107/153) > >> |
| Buddabing:
--- Quote from: papaschtroumpf on March 06, 2005, 03:14:44 pm --- --- Quote from: Buddabing on March 06, 2005, 12:52:36 pm ---It might be smart to run each game for a few frames before generating the movies so that the nvram is generated. There was a method for doing this previously in this thread. --- End quote --- anyone knows what the option is off hand? I haven't founf it in the thread yet or in the windows.txt file from MAME. EDIT: the -ftr option is what I was looking for, finally found it in WINDOWS.TXT I added "mame %1 -ftr 120 -window -resolution %2" before the call to mame that actually generate the movie. Adds a few seconds to the process but it's not that big a deal. I could even check for the presence of an .nv file in the nvram directory to avoid this step when the game has been ran. --- End quote --- I've added the -ftr 100 nvram generator and a check for %1.nv into the batch.bat on the first page. Good suggestion! |
| donnyj:
--- Quote from: Buddabing on March 09, 2005, 10:08:13 am ---I'll look at your frame number issue. --- End quote --- Any luck? |
| donnyj:
Buddamame: Did you fix the aspect ratio issues or did mamedev? Because now all my screenshots are MUCH better? |
| Buddabing:
--- Quote from: donnyj on March 15, 2005, 11:22:23 am ---Buddamame: --- End quote --- |
| 2600:
Buddabing, I may have found the bug and that I think will start you in the right direction. If you run it with the a log on, you'll notice that you check the MD5 sum on every other frame. So for a 10 frame match you have to actually run 20 frames because you are checking every other frame. You identify the correct end frame when you start matching, but somewhere after I assume is a miscalculation based on the fact that you are on frame 20 instead of 10. Hopefully this is descriptive enough, I'm in a hurry. |
| Navigation |
| Message Index |
| Next page |
| Previous page |