| Main > Software Forum |
| MAME Movie Maker released |
| << < (105/153) > >> |
| Buddabing:
--- Quote from: papaschtroumpf on March 08, 2005, 02:12:15 pm ---yes I agree that --- End quote --- |
| donnyj:
If I understand what papaschtroumpf is saying, he wants to double the resolution of the game itself. Doubling the resolution of the PNGs is only going to display at the same quality as before. papaschtroumpf: I haven't found a game yet that the COMPLETE loop extends beyond 20,000 but I am sure a few do.... I believe the best solution currently available would be to extend the minimum frame number... Buddabing: how does MMM work? If I knew a game had the same title sequence, but a different between sequence pattern: T = Title Screen Loop T {demo with fighter plane1} T {demo with fighter plane 2} T {demo with fighter plane 3} T {demo with fighter plane 1}.... What would be the best way to detect the end of the loop after plane 3, but before it restarts the loop for 1 again? Skip to near the end of plane 3 with minmoviestart or minmovielength or something else? Donny |
| donnyj:
Problems please confirm or rebuke these issues... I ran the # movies that: select * from gamedata where screen not like 'vector' and status like 'good' and gamelist_working like "Yes"; format: gamename : Correct/Wrong : Frame Start ( Round(29.97*SetRange/1000) ) [, correct is <frame#>] 1941 : Correct : 860 (28695) 1942 : Wrong : Reported 640 (21354), correct is 5 1943 : Wrong : Reported 5010 (167167), correct is 551 1943kai : Correct : 551 (18385) 1945kiii : Wrong : Reported 52 (1735), correct is 45 19xx : Wrong : Reported 4082 (136202), correct is 1961 2020bb : Wrong : Reported 231 (7707), correct is 222 3countb : Wrong : Reported 231 (7707), correct is 222 3wonders : Correct : 667 (22255) 4dwarrior : Correct : 17 (567) 4enraya : Correct : 204 (6806) 4in1boot : Wrong : Reported 133 (4437), correct is 110 4psimasy : Wrong : Reported 416 (13880), correct is 366 64street : Wrong : Reported 195 (6506), correct is 9 720 : Wrong : Reported 148 (4938), correct is 111 88games : Wrong : Reported 504 (16816), correct is 248 8ballact : Wrong : Reported 264 (8808), correct is 24 Why are we using Setrange () at all? |
| Silver:
Well I'm not sure about the correct/incorrect values. Setrange/Addrange: Its possible these have changed in recent Vdub updates, but all the docs for scripting only go up to Vdub 1.5.10, and AddRange does not even exist in those. However, if I recall correctly (cant test right now) we need both so that we can edit the audio to match. ie we include ALL the pngs in the AddRange when we load vdub, so that we have synced audio/video. Then we tell Vdub only to process what we want with the Setrange command, and it trims BOTH the audio and video. If we only used Addrange, say starting from frame 500, we would then have to externally trim the wav file correctly. In fact this was how we did it in the original version of MMM by using AviSynth to sync and trim the the video and just feed it into vdub for compressing (Vdub did not support pngs then). I've emailed about this before (to the Vdub author) and can only hope he allows us to use a frame number in Setrange so we can avoid this silly x29.97 fudge. |
| Buddabing:
--- Quote from: donnyj on March 08, 2005, 09:40:32 pm ---If I understand what papaschtroumpf is saying, he wants to double the resolution of the game itself. --- End quote --- |
| Navigation |
| Message Index |
| Next page |
| Previous page |