Print

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

[Roman]

Finally....

I've decided to put out the first instance of the new scanner (bundled with a rebuilder update).

If you followed the project here on the forum in the past, you'd know that this is not yet a full clrmamepro replacement. It's something I had fun with by rewriting things in a way clearer and more modern code style. If you want to know more about the benefits, you will find information in the readme file. There is no profiler yet (that's the next thing to do) but you are already able to switch between a handful of setups (e.g. a -listxml and -listsoftware profile) which actually should be enough for a MAME user. Regarding the UI versions, they are preliminary. Things might change a little or a lot. The goal of these releases is to get robust cores. I highly recommend to have a peak at the readme file and of course the usage (especially turning on fix options) is your very own risk.

If you're enjoying this little project as much as I do, feel free to support me

[Roman]

Well, if you want to play around with the tools outside of the MAME world (i.e. load other datfiles which clone the XML layout from MAME (e.g. dir2dat created ones and others floating around), you can use

https://mamedev.emulab.it/clrmamepro/binaries/scanner0011_rebuilder0081.zip

This allows you to load more datfiles than the typical MAME ones

[ntt3]

Thank you!!!
I haven't scanned files since I've started using the rebuilder, time to have a check

[mslug4ever]

Great news! Thank you Roman for your work.
I'll try the new scanner and new rebuilder version.

[RusselCrowe]

Hi Roman,

Thanks for the nice tools you are developing and take care about. I really appreciated it.

Here is my first impression from the new scanner.
Is it possible that the results of scanning with clrmame and scanner could be different regarding missing or unneded objects?
I firstly scanned with clrmame pro from listxml 0.266 with no faults, than I tested the scanner with the same setting (split) and here I gor a lot of unneded files. I then set to fixed and scanned again. Afterwards in scanner all was clean. Now as expected I got a lot of missing (but fixable) errors in clrmame.
BR, Russel

[Roman]

Hi,

the answer is: it depends :-)

There are some main differences in the merge modes:

- standalone (new) versus not or unmerged (old): The new standalone mode is more accurate in my opinion since it includes all dependency files (parent/bios/devices) into the set. The old mode only takes over the parent ones (and with some tricks the  bios)

- full merged mode: the full merge mode acts like cmpro's full merge mode with "full merge mode -> hash collision name" enabled. The naming there is a bit misleading. It simply means that all clone sets inside a packed parent set are stored in subfolders.

- split: this should be fully identical to cmpro


Regarding scan results there can be slight differences:

- the tree is finally sorted alphabetically be machine description, cmpro is by setname which leads to some weird output order
- some results might slighly differ since the new scanner is simply different and the categorization of a wrong named machine or a wrong placed machine or an uneeded machine differs a bit. But after fixing, the resulting sets should be fine.


I assume you're using full merged sets and don't use the "keep clones in subfolders" mode in cmpro.....Personally I think it's a bit clearer to store the clones in subfolders (however that only really works when you keep the archives zipped/7zipped).


I'm wrong with my assumption about the full merge mode, please let me know an example of a set which is differently handled.

[RusselCrowe]

Hi Roman,

unfortunately I use split sets and both scanner were set to that.
An example would be 10-Yard Fight '85 but there are a lot of more.

[Roman]

Check your profiler->options->Parse ROM (and DISK) 'merge' tags.

Both should be enabled (which is the default) and I think you got them disabled which would lead to various additional (hash identical) needed files .

This is also mentioned here: https://www.emulab.it/forum/index.php?topic=9767.0

[RusselCrowe]

Thanks,
Parse Rom was disabled. I set it to on as well and scanning now again.
I am not really sure why it was unset, since I use clrmame for ages and never switch profiler options anyhow.

Thanks in advanced, I think I will use the new scanner in future for mame -listxml and clrmame for other purpose

[Roman]

4.015 (2014-08-19)
....
    misc: parse rom merge tags enabled by default (on clean install)

Over-a-decade-users may have that ;-)

[nullz3]

Greetings Roman,

I'm currently testing the scanner portion of your new software. So far i'm loving the performance and the lower CPU usage. 
Is it possible to include the feature to import set names from text files as well?  That is something I currently use with the old cmpro scanner. 

If that is not an option, I can create custom XML generated files from http://adb.arcadeitalia.net.  Problem is I can't use it with the new scanner or old cmpro for some reason.  With the new scanner I get an error saying it can't parse XML file.  With old cmpro, it doesn't show up in the profile window.

Thank you,
Nullz

[Roman]

what exactly do you mean with "import set names from text files"?

You mean you have a textfile holding set names (either line by line or somehow separated by a character?) and you want to use that as "Filter". So if your file holds "pacman" and "005" you want that the loaded datfile is limited to these two (plus their dependencies).

If that's the case, I could think about enhancing the filter (which currently does regex and xpath) maybe by entering something like "file:c:\temp\list.txt".
Or do you mean something else?

[nullz3]

what exactly do you mean with "import set names from text files"?

You mean you have a textfile holding set names (either line by line or somehow separated by a character?) and you want to use that as "Filter". So if your file holds "pacman" and "005" you want that the loaded datfile is limited to these two (plus their dependencies).

If that's the case, I could think about enhancing the filter (which currently does regex and xpath) maybe by entering something like "file:c:\temp\list.txt".
Or do you mean something else?

You explained it better than I could have   
Basically with old cmpro, I load the full MAME XML dat, then in the Set Information window, I load a text file containing set names and then tick "include BIOS, include Devices.  Here is a screen grab for visual.

[Roman]

ok, I've put it on the wishlist....should be pretty easy to add

[nullz3]

Thank you Roman!

[Bad A. Billy]

Thanks for the new code Roman!
Looking good so far!

I think I have found a bit of an oddity though. Scanned the new mameui .267 with clmpro & the new nameless scanner.
This popped up in the Greyhound Trivia games, set 7a to be exact.
Besides finding a possible extra "." in the source, it makes this happen(at least for me, maybe I'm doing something wrong):

I can have 1 scanner remove the "." to make it correct but then the other complains about not having a "." and I can go back & forth adding/removing "."s for as long as I like...
Is it something to do with the character "." itself or something else in the new scanner?

Also a couple of suggestions for the ui version:
-For the output/warning window at the bottom...you've got it sizeable but it only pulls down the top main issues window.
Can you make that lower window able to be re-sized also?
-Besides editing the settings file by hand, is there a way to delete the saved I/O paths? (Maybe I'm missing something simple?)

Thanks again for taking the time to do all this.

[Roman]

Windows does not allow (or actually auto removes) "." at the end of a filename, that's why such files get the . removed when parsing the datfile. You can have it in an archive though.
Hmm..both apps complain about the file when "." is at the end....I will check it. Correct would be without "." at the end since Windows removes it on itself.....I will do some more test on it.

Regarding your requests:

- yes, resizable logging versus resizeable scan tree (i.e. being able to resize both with a split element or something) is on my list
- yeah, for now, the combo boxes simply keep the last 5 unique entries...currently you can only clear them in the settings.xml, good point

[carbonide2]

Here's a feature from ClrMAME I'm missing in the new scanner: a list of files to ignore while scanning.
In almost every folder on my NAS there's an invisible file named ".DS_Store" (put there by macOS) and sometimes also a file called "Icon" (for custom folder icon).
This could be done on ClrMAME by adding those to the "Unneeded-Masks" list. Would you consider adding that option?

[Roman]

I put it on the wish list...maybe in a first run you'd need to add it somewhere in the settings.xml ...time will tell....

[Roman]

ok...unneededMasks are in....you can specify a regular expression to filter unneeded files/folders in rompaths and in the set's archives/folders. So to filter out ".DS_Store" on any location you could enter something like ".*\.DS_Store$"

(any char or no char before .DS_Store and the . is escaped with \ and .DS_Store is at the end of the name ($))
Surely you can create a regular expression which matches more one specific ending/whatever, e.g. by using |