lr-MAME2010 editing mame.ini fails

estefan3112

Many thanks for the reply - I will give it a try, however, the problem could be somewhere else!

As a follow-up, I tried the cosmica in lr-mame2010 in Retroarch on my Mac, where I do not have user restraints. Also here lr-mame2010 does not use cosmica samples ! I tried different configurations of mame.ini, with no change. But cosmica samples definitely work under lr-mame (the current upstream version) on my Mac!

For lr-mame, it is sufficient to place the samples under [bios folder]/mame/samples, whereas [bios folder]/mame2010/samples does not work.

I will do further testing on my Mac, since other games that rely on samples and seem to work with lr-mame2010, and will then try to transpose the results to the Pi. I will report back again!

estefan3112

So here is the result of my tests: From the three games tested so far (cosmica, cosmicg and xevious), sample support in lr-MAME2010 seems to be broken. lr-MAME2013 and lr-MAME2016 (experimental) have proper sample support. Unfortunately cosmica just crawls on lr-MAME2016 (as opposed to the other games), so back to square one and no Sample support for cosmica on the Pi...

Question: Would it make sense to open an issue on GitHub regarding the missing sample support in lr-MAME2010? Many thanks.

dankcushions

@estefan3112 said in lr-MAME2010 editing mame.ini fails:

Question: Would it make sense to open an issue on GitHub regarding the missing sample support in lr-MAME2010? Many thanks.

sure! it would be a fairly easy fix for someone if they were interested, but since mame2010 lacks so much i wonder if anyone would.

estefan3112

Done: https://github.com/libretro/mame2010-libretro/issues/31

Alturis

I was just looking into this exact same problem. But furthermore, what path is the mame.ini samplepath relative to? I guess I will try putting in a full path there from root.

Alturis

@estefan3112 said in lr-MAME2010 editing mame.ini fails:

What is now the right way to proceed here? Does it make sense that lr-MAME2010 sets mame.ini into a directory that cannot be edited by the pi User?

I usually just go do a

sudo chmod a+w /opt/retropie/libretrocores/lr-mame2010/mame.ini

Then continue with FileZilla or whatever to update the file.

Alturis

@alturis said in lr-MAME2010 editing mame.ini fails:

I was just looking into this exact same problem. But furthermore, what path is the mame.ini samplepath relative to? I guess I will try putting in a full path there from root.

This didn't work for me. Anyone know where the lr-mame2010 samples path is SUPPOSED to be located? The default init setting is "samples" but where is that "samples" relative to?

UDb23

@alturis When I was trying to make overlays work in lr-mame2010, I found out
that right path for mame2010 has to be "~/artwork/".
Didn't change anything in the default mame.ini .
I wouldn't be surprised if lr-mame2010 looks for samples in "~/sample/" or "~/samples/" .

Alturis

@udb23 Thanks for the suggestion. Tried that but didnt work. Could just be a bug with mame2010 who knows.

I am currently downloading all the advmame roms now and will try rip off with that rom zip and advmame emulator. The rom I have for it currently does not seem to work at all with advmame.

movisman

@alturis

Hi,

I just tested this and by default with lr-mame2010 you have to place the samples directory in the /home/pi directory, eg.
/home/pi/samples

I just put some samples in there and it works (tested mario and zaxxon).

See here for an explanation of the paths and a workaround which improves things somewhat until the paths are sorted within the core:
https://github.com/libretro/mame2010-libretro/issues/14

You'll also notice the mame.ini is ignored until it's copied to the /home/pi directory

If you follow the advice by raelgc by copying mame.ini to the pi directory and then editing the file to point the other folders elsewhere (such as cfg, etc), you would likely end up with a mame.ini in the home/pi directory, and then you can at least tell it to put all the other folders somewhere else, perhaps trying to match up with what mame2003 does.

The paths are a mess in the core right now it seems, I can understand why as 2010 isn't really targeted for Pi users and maybe needs a bit of tweaking to sort the paths out. I am using both Pi and an x86 build so I have a use case for 2010.

Cheers