|
Mamesaver 2.0 released
#378527 - 09/10/18 10:23 PM
|
|
|
Hi,
I'm one of the contributors to Mamesaver, a Windows-based MAME screensaver which plays random MAME games at at specified intervals. We're super excited to announce the release of version 2.0 which, apart from a few licks of paint and a bunch of bug fixes, introduces multi-monitor support, hotkeys, in-game information, customisable fonts, better power management, and better game management.
I run Mamesaver at work and it's a fantastic distraction and really fun to show off games that might have been forgotten.
Mamesaver can be downloaded here, or you can build it yourself. Mamesaver is open source and released under the MIT Licence.
Feature requests, pull requests and bug reports are always welcome!
|
|
|
|
Re: Mamesaver 2.0 released
[Re: nullPainter]
#378529 - 09/10/18 11:49 PM
|
|
|
you know if it works with hyperspin ?
|
|
|
|
Re: Mamesaver 2.0 released
[Re: agard]
#378530 - 09/11/18 12:41 AM
|
|
|
Quote:
you know if it works with hyperspin ?
In what way? The screensaver executes MAME itself, so isn't designed for any front ends (it technically is the front end).
Whereas the path to the executable can be arbitrarily changed, it expects correct handling of MAME -listxml, -showconfig, etc. commands.
Edited by Matt Painter (09/11/18 12:56 AM)
|
|
|
|
Re: Mamesaver 2.0 released
[Re: nullPainter]
#378532 - 09/11/18 02:16 AM
|
|
|
as it stands at the moment my hyperspin just randomly selects a game but just plays the video in the theme for each game it doesn't physically load the game so i'll have to look into it to see if hyperspin can do what i want but i bet it can't without messing my Mame up
|
|
|
|
Re: Mamesaver 2.0 released
[Re: agard]
#378534 - 09/11/18 02:20 AM
|
|
|
Note that this is primarily a screensaver - but with hotkeys enabled, you can play the game from within the screensaver.
|
|
|
|
Re: Mamesaver 2.0 released
[Re: nullPainter]
#378542 - 09/11/18 09:31 PM
|
|
|
does it works only with command line mame? seems to do nothing with mameui executable
Edited by Solstar (09/11/18 09:32 PM)
|
|
|
|
Re: Mamesaver 2.0 released
[Re: Solstar]
#378544 - 09/11/18 10:29 PM
|
|
|
> does it works only with command line mame? seems to do nothing with mameui executable
Yes, it does only work with the command-line MAME.
|
|
|
|
Re: Mamesaver 2.0 released
[Re: nullPainter]
#378549 - 09/12/18 09:01 AM
|
|
|
> > does it works only with command line mame? seems to do nothing with mameui
> executable
>
> Yes, it does only work with the command-line MAME.
Hmm i tried with command line mame but i have this error
https://imgur.com/a/b9h138X
and..yes, before you ask, obviously the path is indeed correct
https://imgur.com/a/3zVAcpi
|
|
|
|
Re: Mamesaver 2.0 released
[Re: Solstar]
#378550 - 09/12/18 10:03 AM
|
|
|
> Hmm i tried with command line mame but i have this error
Thanks for reporting this! What version of MAME are you running? If you are able, can you go to the Advanced tab, enable debug logging, try it again, and send the relevant contents of the log file which will have been created in %temp%\Mamesaver?
Older versions of MAME had a different XML file structure returned from -listxml, so I suspect this may be it if your path is correct.
There's no reason why we can't add support for old versions if it's something which is important to people.
Edited by Matt Painter (09/12/18 10:09 AM)
|
|
|
|
Re: Mamesaver 2.0 released
[Re: nullPainter]
#378551 - 09/12/18 11:33 AM
|
|
|
> > Hmm i tried with command line mame but i have this error
>
> Thanks for reporting this! What version of MAME are you running? If you are able, can
> you go to the Advanced tab, enable debug logging, try it again, and send the relevant
> contents of the log file which will have been created in %temp%\Mamesaver?
>
> Older versions of MAME had a different XML file structure returned from -listxml, so
> I suspect this may be it if your path is correct.
>
> There's no reason why we can't add support for old versions if it's something which
> is important to people.
its actually the latest mame, 201. the folder is called "mameold" because i discern between command line (old) and ui( new) folders.
here's the log
2018-09-12 11:31:22.630 +02:00 [INF] Mamesaver started with args /p,132382
2018-09-12 11:31:22.817 +02:00 [DBG] Stopping screen cloning
2018-09-12 11:31:22.821 +02:00 [DBG] Stopping activity hook
2018-09-12 11:31:22.823 +02:00 [DBG] Container disposed
2018-09-12 11:31:24.289 +02:00 [INF] Mamesaver started with args /c:1312984
2018-09-12 11:31:27.076 +02:00 [DBG] Getting MAME rompath
2018-09-12 11:31:27.076 +02:00 [INF] Invoking MAME with arguments: -showconfig
2018-09-12 11:31:27.082 +02:00 [DBG] MAME started; pid: 12524
2018-09-12 11:31:30.211 +02:00 [DBG] Stopping screen cloning
2018-09-12 11:31:30.314 +02:00 [DBG] Stopping activity hook
2018-09-12 11:31:30.315 +02:00 [DBG] Container disposed
2018-09-12 11:31:30.498 +02:00 [INF] Mamesaver started with args /p,132382
2018-09-12 11:31:30.829 +02:00 [DBG] Stopping screen cloning
2018-09-12 11:31:30.833 +02:00 [DBG] Stopping activity hook
2018-09-12 11:31:30.834 +02:00 [DBG] Container disposed
|
|
|
|
Re: Mamesaver 2.0 released
[Re: Solstar]
#378552 - 09/12/18 11:38 AM
|
|
|
> its actually the latest mame, 201. the folder is called "mameold" because i discern between command line (old) and ui( new) folders.
That's a bit concerning. It was tested with a version from a year ago and 0.200. I will take a look in the morning.
> here's the log
Was that the entire contents of the log? There should have at least been something about building the games list.
In any case, I'll take a look first thing. Thanks again.
Edited by Matt Painter (09/12/18 11:40 AM)
|
|
|
|
Re: Mamesaver 2.0 released
[Re: nullPainter]
#378553 - 09/12/18 12:01 PM
|
|
|
> > its actually the latest mame, 201. the folder is called "mameold" because i discern
> between command line (old) and ui( new) folders.
>
> That's a bit concerning. It was tested with a version from a year ago and 0.200. I
> will take a look in the morning.
>
> > here's the log
>
> Was that the entire contents of the log? There should have at least been something
> about building the games list.
>
> In any case, I'll take a look first thing. Thanks again.
yes, that's all there is on the log, it happens as soon as i click on "rebuild list"
maybe its because i have set multiple rom paths?
|
|
|
|
Re: Mamesaver 2.0 released
[Re: Solstar]
#378554 - 09/12/18 03:21 PM
|
|
|
> yes, that's all there is on the log, it happens as soon as i click on "rebuild list"
>
> maybe its because i have set multiple rom paths?
I was wondering that. I did add code in this version to parse multiple ROM paths, but my parsing mightn't be up to snuff. I'll check that as well, but are you able to share your rompath configuration in the time-being?
|
|
|
|
Re: Mamesaver 2.0 released
[Re: nullPainter]
#378555 - 09/12/18 04:02 PM
|
|
|
> > yes, that's all there is on the log, it happens as soon as i click on "rebuild
> list"
> >
> > maybe its because i have set multiple rom paths?
>
> I was wondering that. I did add code in this version to parse multiple ROM paths, but
> my parsing mightn't be up to snuff. I'll check that as well, but are you able to
> share your rompath configuration in the time-being?
Sure.
taken from the .ini
EDIT.: even by setting only one path, i still got the same error
rompath "roms;E:\MAME 0.195 ROMs (merged);E:\MAME 0.190 ROMs (merged)\MAME 0.190 ROMs (merged);E:\MAME 0.198 ROMs (split)"
RE_EDIT: i think the naming might be the reason.
i just put some roms inside the root default "roms" folder. and it works fine this way
Edited by Solstar (09/12/18 04:29 PM)
|
|
|
|
Re: Mamesaver 2.0 released
[Re: Solstar]
#378557 - 09/12/18 08:18 PM
|
|
|
> EDIT.: even by setting only one path, i still got the same error
> rompath "roms;E:\MAME 0.195 ROMs (merged);E:\MAME 0.190 ROMs (merged)\MAME 0.190 ROMs
> (merged);E:\MAME 0.198 ROMs (split)"
>
> RE_EDIT: i think the naming might be the reason.
>
> i just put some roms inside the root default "roms" folder. and it works fine this
> way
Thanks for the investigation - I have a pretty good idea what the bug is. I'm splitting the rompath by semicolon, but I'm not expecting the whole combined path to be quoted. Therefore, I'll be trying to fetch the "roms directory (including speech mark). If, in the time-being, you put speech marks around the individual sections, Mamesaver should work. Not sure what MAME will do though! Does MAME even need quotes?
I'll raise and fix the issue soon (and identify why there was no logging) and have a chat to the maintainer about a patch release.
Thanks again for your help; really appreciated.
|
|
|
|
Re: Mamesaver 2.0 released
[Re: nullPainter]
#378559 - 09/12/18 09:17 PM
|
|
|
> > EDIT.: even by setting only one path, i still got the same error
> > rompath "roms;E:\MAME 0.195 ROMs (merged);E:\MAME 0.190 ROMs (merged)\MAME 0.190
> ROMs
> > (merged);E:\MAME 0.198 ROMs (split)"
> >
> > RE_EDIT: i think the naming might be the reason.
> >
> > i just put some roms inside the root default "roms" folder. and it works fine this
> > way
>
> Thanks for the investigation - I have a pretty good idea what the bug is. I'm
> splitting the rompath by semicolon, but I'm not expecting the whole combined path to
> be quoted. Therefore, I'll be trying to fetch the "roms directory (including speech
> mark). If, in the time-being, you put speech marks around the individual sections,
> Mamesaver should work. Not sure what MAME will do though! Does MAME even need quotes?
>
> I'll raise and fix the issue soon (and identify why there was no logging) and have a
> chat to the maintainer about a patch release.
>
> Thanks again for your help; really appreciated.
No prob, thanks to you for being so supportive. Glad to be of any help. I'll wait for future releases, meanwhile i'll jus stick the default roms folder
|
|
|
|
Re: Mamesaver 2.0 released
[Re: Solstar]
#378583 - 09/14/18 12:17 AM
|
|
|
> I'll wait for future releases, meanwhile i'll jus stick the default roms folder
No release just yet, but a heads-up that this has been fixed. In the meantime, you can download the latest build of the screensaver from here:
https://ci.appveyor.com/api/buildjobs/ej...2FMamesaver.scr
Or the installer, if you're confident or have confirmed that all is now well:
https://ci.appveyor.com/api/buildjobs/ej...2FMamesaver.msi
My suspicion was correct - Mamesaver was tripping up on the speech-marks. I've also added logging for these sort of issues, and nicer error handling if a ROM path just doesn't exist. I also added a bunch of tests for what is hopefully every permutation of acceptable paths 
Edited by Matt Painter (09/14/18 12:29 AM)
|
|
|
|
Re: Mamesaver 2.0 released
[Re: nullPainter]
#378585 - 09/14/18 02:41 PM
|
|
|
> > I'll wait for future releases, meanwhile i'll jus stick the default roms folder
>
> No release just yet, but a heads-up that this has been fixed. In the meantime, you
> can download the latest build of the screensaver from here:
>
> https://ci.appveyor.com/api/buildjobs/ej...2FMamesaver.scr
>
> Or the installer, if you're confident or have confirmed that all is now well:
> https://ci.appveyor.com/api/buildjobs/ej...2FMamesaver.msi
>
> My suspicion was correct - Mamesaver was tripping up on the speech-marks. I've also
> added logging for these sort of issues, and nicer error handling if a ROM path just
> doesn't exist. I also added a bunch of tests for what is hopefully every permutation
> of acceptable paths
Avast didn't like your last release at all...
Had to deactivate it to test your screensaver.
I reported a false positive.
|
|
|
|
Re: Mamesaver 2.0 released
[Re: remax]
#378591 - 09/14/18 10:26 PM
|
|
|
> Avast didn't like your last release at all...
>
> Had to deactivate it to test your screensaver.
>
> I reported a false positive.
Interesting! Is this for the links in the previous post to the Appveyor build server? Those are independent to the GitHub releases and are builds created per git commit. Pretty unlikely that Appveyor itself would have a virus, but it will have built in the identical (bog standard) fashion. FWIW, McAfee was fine.
In any case, thank you.
We'll be squashing another little bug and formally releasing 2.0.1 soon.
|
|
|
|
Re: Mamesaver 2.0 released
[Re: nullPainter]
#378595 - 09/15/18 03:40 PM
|
|
|
> > Avast didn't like your last release at all...
> >
> > Had to deactivate it to test your screensaver.
> >
> > I reported a false positive.
>
> Interesting! Is this for the links in the previous post to the Appveyor build server?
> Those are independent to the GitHub releases and are builds created per git commit.
> Pretty unlikely that Appveyor itself would have a virus, but it will have built in
> the identical (bog standard) fashion. FWIW, McAfee was fine.
>
> In any case, thank you.
>
> We'll be squashing another little bug and formally releasing 2.0.1 soon.
Yeah, the Appveyor links. Didn't try the github ones.
|
|
|
|
Mamesaver 2.0.1 released
[Re: Solstar]
#378613 - 09/17/18 08:39 AM
|
|
|
Mamesaver 2.0.1 has been released! Hope this solves your game list rebuilding issue. Let me know
|
|
|
Index 
Threaded 
Mamesaver 2.0 released
Reply
[Re: 
