Main > Software Forum

MAME Movie Maker released

<< < (145/153) > >>

Buddabing:

--- Quote from: Silver on September 29, 2005, 08:16:38 pm ---
On another note - Due to vdubs highly annoying nature of needed the starting point measured in milliseconds, but the end point in frame number, can you remind me how exactly calculate the start time point? Do you take the exact framerate of the game in use, divide by 2 (as we are making 30fps vids from 60fps games) and mulitply by the number of frames? Or did you assume all games were 60fps? I'm asking as I need to reverse calculate all the start frames from a millisecond reference....

--- End quote ---

From the code:

The SetRange value is calculated by the nunber of frames to skip times 33.3667. This is equal to #frames to skip/29.97*1000.

Some bad news. MAME version 0.100u3 came out and my -makemovie option is not in it, so it looks like that code was rejected. It's possible, though, that they just haven't looked at my submission yet.

Silver:
I've heard some people say that code submissions can take a long time to get through. In fact I think I read in the FAQ somwhere that you should wait a while, and if its still not present email and ask and they should be happy to explain why...  I think the key thing is not to start hassling straight away - its only been a very short time since you sent that off I think....

Re: Setrange

Thanks, I should be able to make a complete boundry.txt for all games from that (as a  starting point anyway).

Skadar:

--- Quote from: Buddabing on September 29, 2005, 11:41:54 am ---
--- Quote from: Skadar on September 29, 2005, 10:48:02 am ---Feel free to ignore this post completely, but I just can't help it...

18 pages of incredibly hard work for what?  What is the point of all of this?  You guys are doing all of this in order to display a small movie in your MAME front end while you are selecting a game??  Wow.  Seems like you've got time and effort to burn.

I understand the DIY-fever, but this seems a little over the top.

--- End quote ---

Hey, I like your purple cab. My cab is purple, too.

Please don't belittle other people's projects. It's a form of thread crapping.

--- End quote ---

Sorry about that.  I re-read my original post and it appears much harsher than what I had intended.  I also thought about what I had said in a much broader context and realized that without experimental projects like this there probably wouldn't be much forward movement in any hobby or niche interest.

Cheers.

Buddabing:
I've got a functioning mng to avi process now.

1) Run the patched MAME (not BuddaMAME) with the -makemovie option, long enough to get a demo loop. Or just run it with the -ftr option.

2) I wrote a program mng2pngs which splits the output mng from MAME into a series of pngs.

3) I wrote a second program pngs2vdb which detects the loop and creates the VirtualDub script.

4) Run VirtualDub just like normal.

This process takes much much longer per movie than BuddaMAME does, because there is a lot of wastage with creating the mng and splitting it back up.

Once the code is complete I'll upload is somewhere and it can be incorporated into the moviebatch.exe program.

It uses the open source libmng, libpng, and zlib libraries.

Silver:

--- Quote from: Buddabing on September 30, 2005, 05:04:31 pm ---This process takes much much longer per movie than BuddaMAME does, because there is a lot of wastage with creating the mng and splitting it back up.

--- End quote ---

I was afraid of that. Do you think Mamedev would accept an option to spit out pngs? It already happens in screenshot capture (f12) so all you need is for it to happen every frame, and with -ftr we could do the same process missing out the mng?

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version