Main > Software Forum
MAME Movie Maker released
<< < (55/153) > >>
Buddabing:

--- Quote from: papaschtroumpf on January 30, 2005, 05:54:32 pm ---
--- Quote from: Buddabing on January 30, 2005, 04:48:27 pm ---Now I have to go and port everything over again now that .91 is out.

--- End quote ---

I could spend my entire spare time upgrading rather than playing if tried to keep up with MAME. In fact the only reason I upgraded from 0.88 is MMM, now I may have to do it again? Aaarg!
I haven't looked at the code and patches so I'm not sure if I can keep up with MMM by diffing the code or I'm better off upgrading to 0.91 when you release MMM for 0.91.

I guess I could probably jsust upgrade MAME itself without worrying about keeping the ROMS, screenshots, flyers, etc... in sync with the MAME version, since that's where I spend 99% of the upgrade time.

--- End quote ---

Yeah, I hear you, which is one reason my cab still runs 0.78.

It turns out that the key file that most of the MMM code is in (common.c) didn't change from version 0.90 to 0.91. So it will be very simple to port MMM. The interface code to CPMaker is in artwork.c, which didn't change either.

Long story short, look for "BuddaMAME" v0.91 very soon.
donnyj:

--- Quote from: Buddabing on January 30, 2005, 04:41:22 pm ---
--- Quote from: donnyj on January 29, 2005, 11:05:53 pm ---suggestions for listgen:

put the default makemovies.bat "script" in the filters.sql file as an example

do the syntax checking BEFORE loading all the data files (so errors bomb out faster)

question:

how would I reverse the sort order?
--- End quote ---

--- End quote ---
Buddabing:
I have uploaded a new version of MMM which supports the -moviestartframe and -movieendframe parameters.

When using -moviestartframe and -movieendframe, MAME ran at 38.5 fps when capturing the frames for defender. Using the original loop detection, MAME ran at 34.7 fps. That's about 10% faster, your mileage may vary.

They've changed the compile environment so that version 0.91 of MAME won't compile anymore on my machine. So MMM 0.91 will be delayed somewhat.

Silver:
I've been playing around a fair bit with png's and mng's recently. I was wondering if it is easy to alter the zlib compression level used when mame creates a png image?
Buddabing:

--- Quote from: Silver on January 31, 2005, 12:36:50 pm ---I've been playing around a fair bit with png's and mng's recently. I was wondering if it is easy to alter the zlib compression level used when mame creates a png image?

--- End quote ---

Yes, in fact I did so when I was investigating calculating the MD5 from the image data instead of the image file.

Here is the relevant code from png.c:

int png_deflate_image(struct png_info *p)
{
   unsigned long zbuff_size;

   zbuff_size = (p->height*(p->rowbytes+1))*1.1+12;

   if((p->zimage = (UINT8 *)malloc (zbuff_size))==NULL)
   {
      logerror("Out of memory\n");
      return 0;
   }

Navigation
Message Index
Next page
Previous page

Go to full version