Main > Software Forum
MAME Movie Maker released
<< < (94/153) > >>
brianoneill:

--- Quote from: Silver on March 01, 2005, 01:58:07 pm ---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.

--- End quote ---

Thanks for the reply.
WHen I play the vid in divx, media player or gameex it runs 2xnormal speed.
When I open it in VirtualDub and select video->frame rate, it states 59.728 as the current frame rate !?
If I change it to 30 and re-save the avi it runs at normal speed but a bit choppy.

It must be how I'm creating the avi in the first place.
Heres some of my mame.ini...

### Windows video options ###
autoframeskip           0
frameskip               0
waitvsync               1
triplebuffer            0
window                  1
ddraw                   1
direct3d                0
hwstretch               1
# screen                <NULL> (not set)
cleanstretch            auto
resolution              auto
refresh                 0
scanlines               0
switchres               0
switchbpp               1
maximize                1
keepaspect              1
matchrefresh            1
syncrefresh             0
throttle                1

### Options added by Buddabing ###
skip_warnings           1
intmakectrl             0
extmakectrl             1
noshowctrl              0
makemovie               0
minmoviestart           200
minmovielength          800
maxmovielength          10000
moviethreshold          2
movieaudio              1
movievideo              3
movieloops              2
moviesquare             0
moviecompression        -1
moviestartframe         0
movieendframe           0
moviematchlength        1
movieskipblack          1
Buddabing:

--- Quote from: Silver on March 01, 2005, 02:27:10 pm ---
--- 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").
--- End quote ---
Silver:

--- Quote from: brianoneill on March 01, 2005, 03:41:40 pm ---Thanks for the reply.
WHen I play the vid in divx, media player or gameex it runs 2xnormal speed.
When I open it in VirtualDub and select video->frame rate, it states 59.728 as the current frame rate !?
If I change it to 30 and re-save the avi it runs at normal speed but a bit choppy.

It must be how I'm creating the avi in the first place.

--- End quote ---

Hmmm. could you edit your batch.bat file to comment out the line that deletes the vdb file. (try: "rem @del %1.vdb" instead of "@del %1.vdb"). Then create a video - there will be a file called romname.vdb left in the mame directory. Could you open it in a txt editor and paste it here? You can omit the "Setcompression" lines (really long unreadable stuff).

I assume this happens with the binary from Buddabings zip and you have not modified the source etc, and I assume you have installed Xvid binary 1.03...
Silver:

--- Quote from: Buddabing on March 01, 2005, 03:46:04 pm ---I ran zookeep with -movieloops 1 and it detects a loop between frames 558 and 3291. MMM frame numbers start at zero, not one. That might cause a very small discrepancy, depending on how Vdub treats it.

MMM currently takes the start frame, divides by 29.97 and multiplies by 1000. 558*1000/29.97=18618.

I changed it to take the start frame, multiply by 2000 and divide by the frame rate. This gives 558*2000/60=18600.

That's 18 ms difference. Would that be noticible?

I thought the consensus was that the loop detection was good enough so that we didn't need it. But I'll be glad to add the matchlength by year stuff, if yousomeone works out the particulars. :)

I wonder if Avery is going to eliminate the milliseconds issue.


--- End quote ---

That would not be noticeable I do not think. I just looked at the tweaked figures you posted for zookeep - as this starts at a much later frame, the error is around 100ms - 6 frames. Even thats not massive.

I was only looking because of this error offset mentioned. Could you give me an example of where it occurs?

Matchlength - well only if its needed! I'm away for a few days and going to create a video set, then take a look to see how it does. If its mostly working with the movie match length, then we should leave it.

I have emailed Avery about this, although he mentions in the script docs he knows its really poor.....
Buddabing:

--- Quote from: Silver on March 01, 2005, 04:13:01 pm ---
--- Quote from: Buddabing on March 01, 2005, 03:46:04 pm ---I ran zookeep with -movieloops 1 and it detects a loop between frames 558 and 3291. MMM frame numbers start at zero, not one. That might cause a very small discrepancy, depending on how Vdub treats it.

MMM currently takes the start frame, divides by 29.97 and multiplies by 1000. 558*1000/29.97=18618.

I changed it to take the start frame, multiply by 2000 and divide by the frame rate. This gives 558*2000/60=18600.

That's 18 ms difference. Would that be noticible?

I thought the consensus was that the loop detection was good enough so that we didn't need it. But I'll be glad to add the matchlength by year stuff, if yousomeone works out the particulars. :)

I wonder if Avery is going to eliminate the milliseconds issue.


--- End quote ---

That would not be noticeable I do not think. I just looked at the tweaked figures you posted for zookeep - as this starts at a much later frame, the error is around 100ms - 6 frames. Even thats not massive.

I was only looking because of this error offset mentioned. Could you give me an example of where it occurs?

Matchlength - well only if its needed! I'm away for a few days and going to create a video set, then take a look to see how it does. If its mostly working with the movie match length, then we should leave it.

I have emailed Avery about this, although he mentions in the script docs he knows its really poor.....

--- End quote ---

I was looking at the end of the Zookeeper video rather than the beginning.

I was playing with Ultrastyle last night and I was able to quickly run through my big batch of videos. They mostly look great. Some of the exceptions are games that need to be run once before creating videos, zookeeper is one. And this was with the old loop detection. I'm going to cull out the ones that don't look good and rerun the batch. Then we'll see if we need any of the matchlength stuff.

I like Ultrastyle. If I can get ListGen to create Ultrastyle game lists, I may end up abandoning my plans to go back to DOS on my cabinet.
Navigation
Message Index
Next page
Previous page

Go to full version