clrmamepro [English] > clrmame Discussion
Skipped files while rebuilding and zip compression
emulajavi:
Hi,
I have Clrmamepro 4.035 and .209 full set (merged). Only the .zips, without the chds.
I think split is better.... so pointed clrmamepro to the .209 binary and created a dat file (saying ‘no’ to software lists and then ‘ok to all’)
On the rebuilder option, selected as the source path the folder that contains all the zips of the merged roms, and as the destination path a new folder in other place.
I have two questions:
1.- On clrmamepro Settings->compression, there’s no ‘zip’ tab to select the compression level. (I think there is supposed to be a selector to select from 1 to 9) So what will the compression level that clrmamepro use when rebuilding?
2.- For example, now the rebuilding process is at 32% and says:
168244 matched
54500 created
2350 skipped
Why are there so many skipped things? I think that if I have a merged set, which is all files parent+clones on the same zip, and to convert it to split what clrmamepro does is create separate parent and clone sets, why it says it skipping things? Aren’t all the files of a merged full set useful for a split full set?
Thank you!
Roman:
1) There is no setting to change the compression level anymore (acutally for decades). clrmamepro uses 9 by default.
2) As soon as a source file does not match a hash it is counted as skipped and if it was rebuilt already. So for example if you got a file which is shared by 30 different sets (Without parent/clone relationship) it is rebuilt by the first match already 30 times ( so 'created' is increased by 30) and every time it is found again in the source it's counted as skipped. There are shared files even without parent/clone relationsships....e.g. devices or bios sets.
emulajavi:
Hi,
Thank you very much for your quick reply!
About the setting to change the compression…. last time I 'updated' my set was on MAME .149 so it's been a long time
.210 was released two days ago and while I was looking to update my .209 to .210 roms, I've seen these post:
https://forum.pleasuredome.org.uk/index.php?showtopic=35012#entry303333
Where it says that 'Due to merging differences, some sets are (currently) not reproducible using the MAME binary or -listxml output.
In order to reproduce the available full sets with any Rom Manager, it's highly recommended to use the attached datfiles.'
So what's better…. to create the .210 datfile using clrmamepro with the mame64.exe binary...or use the datfile that PD provides?
Thanks!
Roman:
The link does not work for me....so I don't know what they are writing.......What do they write? Merging differences? Source code merge or set merge? Without any details I can't comment.....
Generally, clrmamepro should be able to handle all merging problems (e.g. equally named files within a parent/clone relationship but with differnt byte data/different checksums).....
There shouldn't be a problem in using a direct MAME import.
emulajavi:
It says this:
Due to merging differences, some sets are (currently) not reproducible using the MAME binary or -listxml output.
In order to reproduce the available full sets with any Rom Manager, it's highly recommended to use the attached datfiles.
And then they post the datfiles below
I've put them in my OneDrive if you want to check them:
https://1drv.ms/f/s!Al0KjcezUqKng4wMx4a43jQ_ewayCg
Maybe this datfiles are different than generating them from mame.exe or maybe not…..
Thanks!
Navigation
[0] Message Index
[#] Next page
Go to full version