| Main > Software Forum |
| MAME Movie Maker released |
| << < (93/153) > >> |
| donnyj:
--- Quote from: 2600 on February 28, 2005, 11:28:25 am ---...the XVID binary I had downloaded (Nic's Binary) instead of the one I believe Buddabing originally suggested www.koepi.org I'm sure it was just a setting somewhere, but by default Nic's resulted in huge files and the aspect ratio was screwed up on playback. I played the video back on a different player that used a different codec and it displayed correctly. Don't know if this needs to be added to the first post --- End quote --- The link to the working xvid codec that creates MUCH smaller (2 megs instead of Nic's 50 megs on 005) is Latest stable binaryXviD-1.0.3-20122004.exe (621kb) |
| Silver:
RE: Xvid. If people stick to the latest Stable binary it should be fine. I have not messed with the others.... Regarding the '11beat' hanging problem, it is a VERY good idea to get the latest catver.ini file in your Buddamame dir and in the filter.sql file include the sql filter to EXCLUDE unplayable games from your batch. If you want to run a lot, this will avoid lots of problems. The correct syntax is: select * from gamedata where catver_category <> 'Unplayable'; I'm going to do a run on parents-only of a complete .92 romset (.93 mame is buggy), so long as the game is not listed as unplayable. |
| brianoneill:
Hi. I've started creating movies to use in gameex fe. The problem I have currently is that the completed videos are running at what seems double speed ! Anyone run into this in there work creating videos ? Cheers, Brian. |
| Silver:
I've just made some videos now and they are fine - are you checking them in a standard media player or in a FE? All the video's are created at 1/2 the original games frame rate. So for a 60fps game we only make a video of 30fps. If played back at 60fps, obviously this would double the speed.... However, all the videos are matched to the length of the audio by Virtualdub, so come out looking fine. |
| Silver:
--- Quote from: Buddabing on February 23, 2005, 11:45:13 am ---The AddRange line tells Vdub where to end the movie. So AddRange(0,3291) tells Vdub to end the movie at frame 3291. The SetRange lines tells Vdub where to start the movie. This value is in milliseconds. To get this value, MMM takes the starting frame number, divides by 29.97 frames per second and multiplies by 1000 milliseconds per second. It does appear that the movie runs slightly offset from where it should be. I'll experiment with it to see if anything should be changed. --- End quote --- I was thinking about this "slightly offset" problem. It could be due to how you are calculating the start point in milliseconds (which even the Vdub author agrees "is stupid"). To calculate the start point accurately you will ideally need to use the frame rate of the game (and halve it), as some games run at slightly different speeds (57/60/63fps?) - is this info availble in mame? Also, if most games are 60Hz, you would want to divide by 30 not 29.97. For example, looking at zookeep: with a start frame of 2774 and it is a 60fps game, the difference is around 100ms, or 6 frames... so currently the video is starting 100ms after the beginning of the detected loop.... On a seperate note, I have been playing with matchlength feature. Are you still planning to add a filter based on year? |
| Navigation |
| Message Index |
| Next page |
| Previous page |