MAME/FBNeo Trim/Clean up Rom Set

What is a good way and alternatives to clean up a MAME /Final Burn Neo rom set? I’ve tried using Launchbox but that does not work on Linux even with Wine. They even ask for a email just to download it. Its been a common thing asked there are those who do not wan either a bunch of clones, mahjong games or the Adult pornographic games in those sets.

1 Like

Clrmamepro is maybe your best bet. You can download dat files for fbneo here: https://github.com/libretro/FBNeo/tree/master/dats

I do things a bit more manual with powershell.

Rob

1 Like

I looked at the dat but it has clones listed in it. Are there any that have the 1G1R (1 Game 1 Rom) dat as well? Since I’m dealing with Arcade roms in FBNeo, is the dat mentioned the correct one for me that will get rid of the clones, prototypes, betas and adult games in my FBNeo Set? What about “All Killer No Filler” dats, are those compatible with other MAME versions or is there a dat for each MAME version?

" FinalBurn Neo (ClrMame Pro XML, Arcade only).dat"

1 Like

Have you tried this tool?:

You can get the actual catver.ini from the progettosnaps website:
https://www.progettosnaps.net/catver/

2 Likes

No I havent I did do some research and there is not much for us Linux users. I did come across a MAME Set Rebuilder which does work on Linux. I tried ClrMamePro but it requires a exe file and the process was kind complex for me and it didn’t work for me. Another for Linux I found is a JRomManager which was not simple to use.

Mame Set Rebuilder which was very easy to use and simplistic did sort out my roms into clones, Parents, Parents Bios needed. I have an example below. The example was a Non-Merged MAME 2010 version with a MAME 2010 dat from

But another problem came up is that the hash algorithms changed on my Roms, that now do not get recognized by the dat provided in Lakka OS/Retroarch.

1 Like

Use the manual scan method: “Import Content - Manual Scan”

Set “Content Directory” to your rom folder (e.g. /Mame 2010/roms/parent)
and “System Name” to “MAME 2010”
EDIT: use the “mame2010.xml” dat file for “Arcade DAT File” to get proper naming and to omit bios files so that they are not listed in the playlist.

Can you give me the command line output of: “$ unzip -z 1941.zip” to compare with my rom?

EDIT: I would suggest to use split set as it saves you some space on your hdd.
Put your roms and bios files in the same folder.

2 Likes
  • Length Date Time Name

  • 131072 2021-07-11 23:41 41e_31.rom
  • 524288 2021-07-11 23:41 41_32.rom
  • 524288 2021-07-11 23:41 41_gfx7.rom
  • 524288 2021-07-11 23:41 41_gfx3.rom
  • 279 2021-07-11 23:41 buf1
  • 131072 2021-07-11 23:41 41_18.rom
  • 131072 2021-07-11 23:41 41e_30.rom
  • 131072 2021-07-11 23:41 41e_35.rom
  • 65536 2021-07-11 23:41 41_09.rom
  • 279 2021-07-11 23:41 sou1
  • 279 2021-07-11 23:41 rom1
  • 524288 2021-07-11 23:41 41_gfx1.rom
  • 131072 2021-07-11 23:41 41_19.rom
  • 524288 2021-07-11 23:41 41_gfx5.rom
  • 279 2021-07-11 23:41 prg1
  • 279  2021-07-11 23:41   ioa1
    
  • 131072 2021-07-11 23:41 41e_36.rom Size: 3474803

CRC: 51818737

as for the Dat do you mean I can add it to Retroarch/Lakka or that it should be used in that MAME Set Rebuilder program I used? I used the xml version from that link you posted for MAME 2010 in that program I mentioned.

2 Likes

Yes, in RetroArch/Lakka you add games to playlists with “Scan Directory”, “Scan File” or “Manual Scan”.
There you can use your mame2010.xml dat instead of the RetroArch database

1 Like

Picture thread:





1 Like

Thank you, that did the trick, I feel stupid for not noticing the dat in Manual Scan even though I have used Manual Scan plenty of times already.

1 Like

Options in Linux without modifying the RomSet.

Options modify the romsets in Linux.

  • QMC2 was a great option, but that project is currently stagnant. :confused:

  • JRomManager is one of the best Roms handlers. OpenSource, native for Linux and multi-platform. It is very easy to use and you can create the sets you want.

1 Like

Some Time ago I’ve developed an RomsetManager to easily cleanup all rom-files with these cryptic chars. But runs only on windows.

I’m the developer of MAME Set Rebuilder. The application DOESN’T CHANGE ROM HASH, a file has its hash and no application in the world can change the hash of a file (without change the file itself)!!!

What you see is a change of the ARCHIVE HASH and IT IS NORMAL because each time an archive is created the header is different. The same thing happens with Clrmamepro and other rebuilders.

If the dat that Lakka provides uses ARCHIVE hash instead of ROM (inside archive) hash it is a logical problem from who doesn’t understand nothing about M.A.M.E. and hash algorithms.

I’m also the developer of M.A.M.E. SDL Plus (a full speed M.A.M.E. emulator also on Raspberry Pi v1), MAME Roms Extractor (an application that creates home machines roms from a M.A.M.E. set for a not-M.A.M.E. emulators) and other applications of M.A.M.E. world. I know what I say

For linux folks, I used the below to remove clones from my FB Neo Arcade-Only non-merged set. The dat file used is https://github.com/libretro/FBNeo/tree/master/dats/ . I specifically used the FinalBurn Neo (ClrMame Pro XML, Arcade only).dat one

#!/usr/bin/bash
find *.zip ./fbneo -printf "%f\n" >temp.out
sed 's/.zip//g' temp.out >games.out
while IFS= read -r game
do
	if [[ $(grep "game name=\"$game\"" fbneo.dat | grep -c 'cloneof="') -gt 0 ]]; then
		mv "./fbneo/$game.zip" ./fbneo-clones
	fi
done <games.out
rm -f *.out

Quick and simple way to achieve what I want which is just remove clones…you can certainly manually copy back clones that you want to keep or write another script to do this for you.

As i keep repeating, be careful with that, in both emulators there are non-working parent romsets with working clones.

thanks for the heads up. As the script is for purely removing clones, so everyone can use it as-is. Is there’s a specific list of games that covers your mentioned case? will try to improve the script

Non-working romsets have <driver status="preliminary"/>, working romsets have <driver status="good"/>, so i suppose you could check if a parent with the former has a clone with the later.

There is no fixed list, because non-working romsets can become working ones at any moment.