Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

1

clrmame Discussion / [REBUILDER] multiple INPUT sources

« on: 04 October 2023, 15:48 »

Heya Roman!

Is it possible to declare 1 or more paths to the -i switch?

I'm getting this error and in documentation there's no mention on how many INPUT paths should be used:

Code: [Select]

--input: At Most 1 required but received 2
Run with --help for more information.

-i, --input: The rebuilder input folder. This folder is checked for matching data. This option is mandatory and the folder has to exist.

I was thinking something like this:

Code: [Select]

rebuilder -i "d:\roms\oldmame" "g:\backups\mames", or this if you prefer:

Code: [Select]

rebuilder -i f:\games\fixme -i s:\data\games\mame01 -i s:\data\romsets\arcade

2

clrmame Discussion / why some sample are unnedded?

« on: 26 August 2023, 20:03 »

cmp will always delete unneeded samples (which consist of whole machines) and then - running a 2nd NEW SCAN instance - will complain those previously unneeded sets are now missing.

Copying the parent sample into its clone sample will again then lead to unneeded.

Code: [Select]

$ cp samples/moepro90.zip samples/nes_jf29.zip
Example: nes_jf29 VS moepro90 http://adb.arcadeitalia.net/?mame=nes_jf29

Code: [Select]

NES Cart Bandai BT-554 PCB [folder: nes_bandai_pt554 - sampleparent: ftaerobi - size: 0]
missing device: NES Cart Bandai BT-554 PCB
missing sample: 00
missing sample: 01
missing sample: 02
missing sample: 03
missing sample: 04
missing sample: 05
missing sample: 06
missing sample: 07

NES Cart Jaleco JF-13 PCB [folder: nes_jf13 - sampleparent: moepro - size: 0]
missing device: NES Cart Jaleco JF-13 PCB
missing sample: 00
missing sample: 01
missing sample: 02
missing sample: 03
missing sample: 04
missing sample: 05
missing sample: 06
missing sample: 07
missing sample: 08
missing sample: 09
missing sample: 10
missing sample: 11
missing sample: 12
missing sample: 13
missing sample: 14
missing sample: 15

NES Cart Jaleco JF-19 + ADPCM (Moero!! Pro Yakyuu 88) PCB [folder: nes_jf19_pcm - sampleparent: moepro88 - size: 0]
missing device: NES Cart Jaleco JF-19 + ADPCM (Moero!! Pro Yakyuu 88) PCB
missing sample: 00
missing sample: 01
missing sample: 02
missing sample: 03
missing sample: 04
missing sample: 05
missing sample: 06
missing sample: 07
missing sample: 08
missing sample: 09
missing sample: 10
missing sample: 11
missing sample: 12
missing sample: 13
missing sample: 14
missing sample: 15
missing sample: 16
missing sample: 17
missing sample: 18
missing sample: 19

NES Cart Jaleco JF-23 (Shin Moero Pro Yakyuu) PCB [folder: nes_jf23 - sampleparent: smoepro - size: 0]
missing device: NES Cart Jaleco JF-23 (Shin Moero Pro Yakyuu) PCB
missing sample: 00
missing sample: 01
missing sample: 02
missing sample: 03
missing sample: 04
missing sample: 05
missing sample: 06
missing sample: 07
missing sample: 08
missing sample: 09
missing sample: 10
missing sample: 11
missing sample: 12
missing sample: 13
missing sample: 14
missing sample: 15
missing sample: 16
missing sample: 17
missing sample: 18
missing sample: 19

NES Cart Jaleco JF-24 (Terao no Dosukoi Oozumou) PCB [folder: nes_jf24 - sampleparent: terao - size: 0]
missing device: NES Cart Jaleco JF-24 (Terao no Dosukoi Oozumou) PCB
missing sample: 00
missing sample: 01
missing sample: 02
missing sample: 03
missing sample: 04
missing sample: 05

NES Cart Jaleco JF-29 (Moe Pro! '90) PCB [folder: nes_jf29 - sampleparent: moepro90 - size: 0]
missing device: NES Cart Jaleco JF-29 (Moe Pro! '90) PCB
missing sample: 00
missing sample: 01
missing sample: 02
missing sample: 03
missing sample: 04
missing sample: 05
missing sample: 06
missing sample: 07
missing sample: 08
missing sample: 09
missing sample: 10
missing sample: 11
missing sample: 12
missing sample: 13
missing sample: 14
missing sample: 15
missing sample: 16
missing sample: 17
missing sample: 18
missing sample: 19

NES Cart Jaleco JF-33 (Moe Pro! Saikyou-hen) PCB [folder: nes_jf33 - sampleparent: mpsaikyo - size: 0]
missing device: NES Cart Jaleco JF-33 (Moe Pro! Saikyou-hen) PCB
missing sample: 00
missing sample: 01
missing sample: 02
missing sample: 03
missing sample: 04
missing sample: 05
missing sample: 06
missing sample: 07
missing sample: 08
missing sample: 09
missing sample: 10
missing sample: 11
missing sample: 12
missing sample: 13
missing sample: 14
missing sample: 15
missing sample: 16
missing sample: 17
missing sample: 18
missing sample: 19
Another example:

Code: [Select]

<machine name="nes_bandai_pt554" sourcefile="src/devices/bus/nes/pt554.cpp" isdevice="yes" runnable="no" sampleof="ftaerobi">
<description>NES Cart Bandai BT-554 PCB</description>
<device_ref name="speaker"/>
<device_ref name="samples"/>
<sample name="00"/>
<sample name="01"/>
<sample name="02"/>
<sample name="03"/>
<sample name="04"/>
<sample name="05"/>
<sample name="06"/>
<sample name="07"/>
<chip type="audio" tag=":addon" name="Speaker"/>
<chip type="audio" tag=":samples" name="Samples"/>
<sound channels="1"/>
</machine>

3

clrmame Discussion / Re: -listxml VS hash/*.xml

« on: 22 April 2023, 20:20 »

Ask the devs 😁

Nice one Roman!

4

clrmame Discussion / Re: rebuilder 0.05 released

« on: 22 April 2023, 20:09 »

doing parallel calculate threads….

Yup, I meant exactly this: bring computational (CPU) operations into parallel execution. 

5

clrmame Discussion / Re: -listxml VS hash/*.xml

« on: 22 April 2023, 20:05 »

Actually I don't know the reason why -listsoftware does not include all software lists of the hash folder

Or, may I add: why M. A. M. E. devs chose this "doubled" approach? I mean, -listsoftware seems to me somewhat redundant since there're also XMLs inside hash/ folder... 

6

clrmame Discussion / Re: -listxml VS hash/*.xml

« on: 22 April 2023, 05:46 »

-listsoftware does not include all software lists from mame's hashfolder and secondly, it's a real pain to set this mode up correctly. You'd need unique distinct rompaths for each software list and scanning takes long, more memory usage etc..etc...

Gotcha! 

7

clrmame Discussion / Re: rebuilder 0.05 released

« on: 21 April 2023, 21:00 »

- parallelization? You don't want to have multiple threads treating your hd/ssd like crazy...ever tried to copy various bunch of files from one hd to another in multiple copy operations...it will crawl

But a first small test was already pretty positive which gave a extra ~25% speed boost when sha1 input scanning was enabled....

That's the way!!

Thanks Roman 

8

clrmame Discussion / -listxml VS hash/*.xml

« on: 21 April 2023, 20:51 »

Hey Roman, just tried importing -listsoft into cmp and found out it's loading by itself all (all? Maybe... ?) Software Lists in one shot.

Soooooo... I'm asking you: what's the point of loading all different SOFT xmls from the hash/ folder of MAME? 

Sure there's something I'm missing, but I do not understand what... ... 

9

clrmame Discussion / Re: mame merged sets not scanning correctly?

« on: 13 April 2023, 18:34 »

@Pandor: not on PC ATM, but IIRC starting from the same -listxml and using merged sets you'll end up with same results on both CMP and RV.
Only thing you need to change in CMP is the Hash Collision methodology (as Roman already told you) and you'll have same Scan results. 

Anyway,
may I suggest you mixing the modes for your romset?
I find myself really pleased with roms UNMERGED (including BIOS) and chd sets merged.
Be aware I'm meaning chd sets, not chd.

10

clrmame Discussion / Re: Rebuilder 0.04 released

« on: 04 April 2023, 08:50 »

Thank You Roman for this very handy and lightweight commandline utility! 
Oh, I really love the -m standalone switch!!!

Some suggestions:

• parallelization
• creation of complete sets only
• cache
• and last, but no least... Linux executable! 

## Future Plans / Source Availability

In this state of the project it is closed source, mainly due to the use of the
full version licence of ZipArchive.

There are definetly plans for the future to get open source. Currently there are
discussions about some licences (e.g. free version of ZipArchive is currently
GPL)

What about http://www.zlib.net/ or https://github.com/ctabin/libzippp ?

11

clrmame Discussion / Re: [SOLVED] Separate paths CHD VS nonCHD?

« on: 03 September 2022, 12:38 »

So... Just ad addendum: I ended up using two different xml (both generated - better, exported - with ALT+E while running MAME inside its Main Screen).
Example (CHD only)


CHD only XML = merge, sets (gamechdname.zip and gamechdname/game.chd) are inside path/to/mame/set/chd
rom only XML =  unmerge, sets (blahblah.zip) are inside path/to/mame/set/rom

12

clrmame Discussion / Re: Slow MAME SNAP.ZIP scan and rebuild with 4.046b

« on: 03 September 2022, 12:16 »

What do you expect when you run WINE ;-) Surely it's slower. clrmampro is a native windows program, no support for weird emulation bugs sorry ;-)

You're right.
To be fair, some clrmamepro/WINE combos runs as fast as in Windows.
This wouldn't be an issue if every clrmamepro release had always been slower on every WINE version! 

P. S.: hey Roman, have you ever wondered releasing clrmamepro' sources to the public? 

13

clrmame Discussion / Re: Slow MAME SNAP.ZIP scan and rebuild with 4.046b

« on: 03 September 2022, 11:24 »

WINE on its own is of course already a problem....

Yup! 


it's slower everywhere.
On standard sets (rom+chd+sample) when Rebuilding / Scanning.
Also even when when selecting the radio button in "You Prefer" (both Rebuilder and Scanner):

• On Windows it changes the selection (almost) immediately.
• On WINE it takes several sesconds.

I'll give a shot with previous WINE version(s).

Roman, do you provide some place where I can download all the old releases of clrmamepro?

14

clrmame Discussion / Re: Slow MAME SNAP.ZIP scan and rebuild with 4.046b

« on: 03 September 2022, 06:58 »

How should I know what happened ;-)

There were no changes from 4.045 to 4.046b which were anyhow speed related. And since noone else reported such a slow down, it must be something on your end.....could be anything...from a busy hd (due to other threads accessing it, incl. virusscanners), to bad network drivers when it's a net drive, etc...etc.

Or maybe you've enabled things like sha1 checking or other time consuming options.

So...."What happened" is nothing I can give an answer to.

"Here it runs fine and fast"

Dont'k know how to debug, but in WINE latest clrmamepro runs slow also.
(Yeah, could be something "wrong" on WINE side)
I'm using it on Windows, at the moment.

15

clrmame Discussion / Re: Clarification with Merged sets, roms, CHDs and their relationships

« on: 03 September 2022, 06:55 »

Thanks! 

16

clrmame Discussion / Clarification with Merged sets, roms, CHDs and their relationships

« on: 01 September 2022, 20:24 »

OK... First of all, let's define a legend:

SET	ROMset	ROM	CHD
Some Name	mame/somena.zip	mame/somena.zip/chip01	mame/somena/harddisk.chd
	(or mame/somena/)	(or mame/somena/chip01)

Hey Roman, I'd like to understand more about the settings for merged sets.


PROFILER > OPTIONS > MISC PROFILER OPTIONS

• Parsing Options
  
• Parse ROM 'merge' Tags
     Why someone would not to parse the merge attribute (as declared inside M. A. M. E.'s XML) of a clone's rom name?
     I mean, if I want my sets to be merged I need to tell clrmamepro to parse the merge attribute, right?
  
• Parse DISK 'merge' Tags
     As above... I want my sets to be merged, so both roms and CHDs should be merged accordingly to what's declared inside M. A. M. E.'s XML.
  


• Hash Collision_{(is this enabled only when Hash Collision Name is selected in Full Merge Mode?)}
  
• Single File
     This will put only roms with same sha1sum inside its clone's subdirectory, right?
  
• Single Clone
     This will put ALL roms of each clone with same sha1sum inside the relative clone's subdirectory, right?
  
• All Clones in Relationship
     ?
  

SETTINGS

• Full Merge Mode
  
• Normal Mode
     ?
  
• Hash Collision Name
     "You use the hash collision naming convention fo all clone files, no matter if a hash collision happened or not."
     ? ... Please could you elaborate on this in simple terms
  

Looking at this excerpt as a reference, could you help me by reporting a concrete example?

Code: [Select]

<machine name="hotd4a" sourcefile="sega/lindbergh.cpp" cloneof="hotd4" romof="hotd4">
<description>The House of the Dead 4 (Export) (Rev A)</description>
<year>2005</year>
<manufacturer>Sega</manufacturer>
<biosset name="bios0" description="6.0.0010 alternate version"/>
<biosset name="bios1" description="6.0.0009"/>
<biosset name="bios2" description="6.0.0010"/>
<rom name="6.0.0010a.bin" merge="6.0.0010a.bin" bios="bios0" size="1048576" crc="10dd9b76" sha1="1fdf1f921bc395846a7c3180fbdbc4ca287a9670" region="pci:1f.0" offset="0"/>
<rom name="6.0.0009.bin" merge="6.0.0009.bin" bios="bios1" size="1048576" crc="5ffdfbf8" sha1="605bc4967b749b4e6d13fc2ebb845ba956a259a7" region="pci:1f.0" offset="0"/>
<rom name="6.0.0010.bin" merge="6.0.0010.bin" bios="bios2" size="1048576" crc="ea2bf888" sha1="c9c5b6f0d4f4f36620939b15dd2f128a74347e37" region="pci:1f.0" offset="0"/>
<rom name="fpr-24370b.ic6" merge="fpr-24370b.ic6" size="4194304" crc="c3b021a4" sha1="1b6938a50fe0e4ae813864649eb103838c399ac0" region="pci:1e.0:03.0" offset="0"/>
<rom name="vid_bios.u504" merge="vid_bios.u504" size="65536" crc="f78d14d7" sha1="f129787e487984edd23bf344f2e9500c85052275" region="pci:01.0:00.0" offset="0"/>
<rom name="317-0427-com.bin" merge="317-0427-com.bin" size="8192" crc="ef4a120c" sha1="fcc0386fa708af9e010e40e1d259a6bd95e8b9e2" region=":pic" offset="0"/>
<disk name="mda-c0004a_revb_lindyellow_v2.4.20_mvl31a_boot_2.01" merge="mda-c0004a_revb_lindyellow_v2.4.20_mvl31a_boot_2.01" sha1="e13da5f827df852e742b594729ee3f933b387410" region="cf" index="0" writable="no"/>
<disk name="dvp-0003a" sha1="46544e28735f55418dd78bd19446093874438264" region="dvd" index="0" writable="no"/>
[...]
## tuncated output ##
[...]
</machine>


If I understood correctly the merge mode, I should end up with this:

Parent romset

Code: [Select]

mame/hotd4.zip:
317-0427-com.bin
Parent CHD

Code: [Select]

mame/hotd4/:
dvp-0003b.chd
Clone CHD

Code: [Select]

mame/hotd4a/:
dvp-0003a.chd
BIOS romset

Code: [Select]

mame/lindbios.zip:
6.0.0009.bin
6.0.0010.bin
6.0.0010a.bin
fpr-24370b.ic6
vid_bios.u504
BIOS CHD

Code: [Select]

mame/lindbios/:
mda-c0004a_revb_lindyellow_v2.4.20_mvl31a_boot_2.01.chd

Thank you Roman!

17

clrmame Discussion / Re: [PROFILER] CANNOT manually add M. A. M. E.'s XML (-listxml)

« on: 24 August 2022, 20:02 »

So you need to run it with utf8 encoding in powershell:

mame.exe -listxml | out-file mame.xml -encoding utf8

Thank you Roman!  SOLVED. 

18

clrmame Discussion / Re: [PROFILER] CANNOT manually add M. A. M. E.'s XML (-listxml)

« on: 21 August 2022, 19:03 »

The file has been generated using the official mame.exe (https://www.mamedev.org/release.php).
Maybe some bug using it inside PowerShell?
I'll try with Command Prompt as soon as I can.

19

clrmame Discussion / [SOLVED] Profiler: CANNOT manually add M. A. M. E.'s XML (-listxml)

« on: 21 August 2022, 14:45 »

Adding M. A. M. E.'s XML (-listxml) via "Profiler > Add DatFile..." is NOT recognized by clrmame: the DatFile is not detected, although the corresponding "mame.dat" file is generated (alongside "mame.xml").

mame.xml:

Code: [Select]

mame.exe -listxml > mame.xml
It only works with the official MAME 0.nnn full driver information in XML format (downloaded from https://www.mamedev.org/release.php ).



One interesting thing is the two XML files differs in size:

Code: [Select]

## MAME 0.246 full driver information in XML format ##
mame0246.xml
size = 271978244 bytes
SHA-1 = F53FE5CDCB5207F586CCD34070367E0FB87FA51C

## mame.exe -listxml > mame.xml ##
mame.xml
size = 543956490 bytes
SHA-1 = F9D6669071371A357627A64CB3A1273BE0BE3C4D

20

clrmame Discussion / Re: ClrMame Tutorial

« on: 19 May 2022, 20:07 »

What I do now is maintain the full split set and then create a non-merged set with just the games I use on my cabinet.  I haven’t found a way to do a full non-merged set, but I have figured out how to get the BIOS and device files to get copied into the set separately.

I just PMed you.