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.

41

clrmame Discussion / Re: Unwanted file being created

« on: 06 September 2025, 18:02 »

maybe s7.7z
rom name="s5.7k" size="32768" crc="de5cd249" sha1="e3752b88b539e1057a35619ffbad01720ab60d7d" region="fgtiles" offset="8000"
from
machine name="saurop" sourcefile="tecfri/sauro.cpp" cloneof="sauro" romof="sauro"
which is 32k in size and of course not a 7z zile (archive).

no idea why it was placed in your rompath though....so maybe it could be worth looking at your saurop (or sauro or its clones) archive (depending on the used merge mode) and check if it somehow wants to move the file due to wrong naming or whatever....and may get confused due to the 7z file extension...

42

clrmame Discussion / clrmame 0.5 released

« on: 06 September 2025, 17:54 »

clrmame 0.5 released

https://mamedev.emulab.it/clrmamepro/binaries/clrmame_v05.zip
https://mamedev.emulab.it/clrmamepro/binaries/readme.html

UI:

misc: recoded resize/move/drag controls handling, allowing resizeable combo boxes etc (resets your current positions once, though)
misc: moving options/modifiers in rebuilder/scanner to tabs, reducing used vertical space
misc: aligned scanner/rebuilder look
misc: scanner, chd version check options are now visible in the chd tab
fixed: don't remember window placement on first close without changing tabs
added: rebuilder, tree output for rebuilt files (context menu available, too)

Core:

misc: tweaked the determination of best fitting rompath a bit for users which split chds/roms
misc: updated to spdlog 1.15.3
fixed: scanner, updateMissingInformation phase isn't thread safe and could lead to crash
fixed: resolved potential reallocation/dangling pointer issues

43

clrmame Discussion / Re: Is there a clrmame roadmap?

« on: 02 September 2025, 18:04 »

The current release notes for upcoming 0.5:


UI:
- fixed: don't remember window placement on first close without changing tabs
- misc:  moving options/modifiers in rebuilder/scanner to tabs, reducing used vertical space
- misc:  recoded resize/move/drag controls handling, allowing resizeable combo boxes etc (resets your current positions once, though)
- misc:  aligned scanner/rebuilder look
- misc:  scanner, chd version check options are now visible in the chd tab (before only in settings.xml)
- added: rebuilder, tree output for rebuilt files (context menu available, too)

Core:
- misc:  tweaked the determination of best fitting rompath a bit for users which split chds/roms
- misc:  updated to spdlog 1.15.3
- fixed: scanner, updateMissingInformation phase isn't thread safe and could lead to crash
- fixed: resolved potential reallocation/dangling pointer issues



after that....:

- profiler (already started but not yet visible to the user, needs to get finalized)


long time roadmap.....well, I've got several things on my wish/to do list like: batcher, dir2dat, delta chds, etc....

44

clrmame Discussion / Re: mac crossover problem

« on: 02 September 2025, 18:02 »

If it's thread related, it might be fixed in 0.5 already since there were some potential reallocation/dangling pointer issues....so maybe you can do some retesting later...

45

clrmame Discussion / Re: Setting so "Fix Issues" doesn't create new partial sets?

« on: 01 September 2025, 19:44 »

If you want to limit the machines you're working with, "filters" are the thing to look for.
The filter options offer all kind of selections, e.g. filter by regular expression, filter by xpath expression (very powerful), filter by a file list and last but not least (scanner only though) available machines.

However all filters also enable all dependencies (e.g. devices, bios files, parent sets in case of a clone when using split merged sets etc) automatically. I personally think this makes sense since your (limited number of) sets should still be useable in the emulator.....and the emulator needs the dependency sets....

So you're looking for the "available:" filter. Simply enter "available:" (without the quotes but with the colon) in the filter combo box. This will check your rom/sample paths first for available machine sets and focuses on them (and their dependencies). Surely there is a downside of this filter: If a new MAME version uses new names for your sets, they aren't detected anymore....

46

clrmame Discussion / Re: mac crossover problem

« on: 01 September 2025, 15:28 »

Well, 0.5 is around the corner which fixes some thread safety issues here and there....which could cause crashes...but rarely (however who knows when it is running in a crossover environment). But such errors would be more random.

Your information about the rezipped archives is interesting, however, the file flags inside an archive should not play a role at all since a normal scan only reads the file header structures inside the zip. But maybe the archives had general structural issues. This doesn't mean that the stored data is corrupt. In most cases you can unzip them perfectly fine. It means that zip related structures (local file headers, central directoy entries) are not ok. Rezipping fixes such things. Corrupt structures might have an impact on the used zip libraries. So it would be interesting to see such archives, maybe you can repeat your crash problem with 'some' and send me some examples.

47

clrmame Discussion / wip

« on: 29 August 2025, 17:13 »

So....ok...finished working on the resizable controls.....and still not really in the mood to finalize the profiler, so I took a look at the wishlist and added some rebuilder output (see attached screenshot). It lists rebuilt (standard coloring) and existing (blue) roms/chds and indicates if the machine is fully available (checked circle) or incomplete machines (half filled circle).

Don't know if it's really needed but since I've already aligned the layout of the rebuilder to match the scanner layout, I though adding this request is some nice add on...

so....coming closer to a new release...still without the profiler though.

48

clrmame Discussion / Re: So quiet in here...

« on: 06 August 2025, 07:34 »

Well nothing special you'd say. People who know how to program dialogs would say (besides "god damn use some more modern gui tool") : Resizing of controls, hey there is an option for it...well yes...unless you add something like a horizontal/vertical divider which you grab and move that one....so I took a little time to make some generic routine which also handles that....more or less for fun.....Still have to get rid of some annoying things like combo box focus and list control loosing its border...*sigh*.....
But yeah...it's still fun

Update, ok fixed the border and combobox focus/text selection thingie....

49

clrmame Discussion / Re: clrmame vs clrmame pro - VASTLY different results

« on: 06 August 2025, 07:30 »

There is only one major difference between clrmame and clrmamepro (in its default settings) which is highlighted in the documentation. If you're using full merge mode, clrmame puts clone files not plain into the parent archive but into subfolders in the archive. So you got a (let's focus on zip) archive folder like:
parent.zip
- parentrom1.bin
- parentrom2.bin
clone1/clone1rom1.bin
clone1/clone1rom2.bin
clone2/clone2rom1.bin
and so on.

By the way: clrmamepro can also do that by triggering one option (hash collision mode).

In full merge mode there are no archives for clonesets, furthermore the clone files are now part of the parent and so they appear there if they are missing. clrmamepro scanned differently (and actually pretty slow) and put out the results still split by parent and clone.

If you now say "but I first have to look at the missing roms in detail to see if I need to grab a clone set somewhere to complete my full merged set", no, there is a context menu option which lists -in case of a missing file- the belonging clone set on top level, so need to expand the view....but that's just a sidenote

"clrmame pro shows I'm missing those 8 plus 26 more (which is accurate)." , please give a concrete example. Maybe you didn't use clrmamepro's profiler->parse rom/disk merge tags in the past and you talk about dupes. clrmame fully uses the merge attributes of the xml output now and so there won't be any requirement to keep dupes.

50

clrmame Discussion / So quiet in here...

« on: 05 August 2025, 17:22 »

well well well.....it's summer time...holiday time....so what do you expect?
I was on holiday and had no time to do more work on the profiler, however, I've added a bit UI stuff here.....take a look here https://mamedev.emulab.it/clrmamepro/binaries/resize.mp4
It's still work in progress though.....

51

clrmame Discussion / Re: romsets missing after rebuild even though CLRMame reports 0 roms missing

« on: 02 August 2025, 21:51 »

sorry for the delay but I only found a little time now to look at it.
Using an official MAME (and assuming you use standalone and zip), the rebuilder rebuilds bbh in standalone mode correctly. All of its roms belong to its parent "iteagle" so you end up with a with zipfile named bbh which includes a folder named  iteagle which include something around 16 roms and in addition you got a "bbh" subfolder outside of the archive which includes the bbh_v1.00.14.chd.

If you don't have anything like that you either a) have a different data basis (as mentioned, I used the official MAME.exe) or b) your rebuilder source does not include the chd or the iteagle roms or c) you forgot to enable the recursive flag so that the rebuilder runs through subfolders.

52

clrmame Discussion / Re: clrmame 0.4 cannot rebuild non-merged/standalone set from split

« on: 31 July 2025, 06:28 »

Then most likely your datfile does not have any parent clone relationships specified. Take a look at it and check if you see cloneof/romof/merge attributes. If you‘re not sure you can also attach it here

53

clrmame Discussion / Re: romsets missing after rebuild even though CLRMame reports 0 roms missing

« on: 24 July 2025, 07:05 »

The xml also includes empty sets which don‘t have any files at all. You can show them in the scanner context menu.
Regarding nodump files, they don‘t exist and if you had dummy placeholders for them in the past, such fake files won‘t be rebuilt.
I dont have access to mame‘s xml output at the moment so I cant check your bbh example to see what files the xml lists for it.

By the way, the new clrmame does not have ‚non merged‘ mode. It has a ‚standalone‘ mode….which makes me think if you talk about the new clrmame or the old clrmamepro.

54

clrmame Discussion / Re: What if...

« on: 17 June 2025, 06:58 »

Actually I just played around with it a bit and if I do some threading here and some other logging there, I can make it twice as fast for adding the zip compared to yesterday....

Well what is different compared to the old cmpro...most of it is design, cleaner coding and not forget pugixml which does a marvelous job when parsing xmls......

55

clrmame Discussion / What if...

« on: 16 June 2025, 17:43 »

....you take a "TOSEC - DAT Pack - Complete (4743) (TOSEC-v2025-03-13)" zip file containing 4743 datfiles and drop them in the old clrmamepro profiler?
Well, ok, a select dialog opens rather quickly, you select all 4743 dats and add them to cmpro....so..what happens? On a decent PC it takes about ~5 minutes until the dats are added to the profiler....so..keep that in mind for now... As you might know, for the new clrmame, I'm currently working on the profiler. Unfortunately I had not that much time lately but I want to give you an update what happened.

So maybe start with some common core/ui news:
UI:
- fixed: don't remember window placement on first close without changing tabs
Core:
- misc:  tweaked the determination of best fitting rompath a bit for users which split chds/roms
- misc:  updated to spdlog 1.15.3
- fixed: scanner, updateMissingInformation phase isn't thread safe and could lead to crash
- fixed: resolved potential reallocation/dangling pointer issues


Nothing really big, but fixing one thread safe bug and resolving possible reallocation issues improves stability.

Now back to the profiler...it looks a bit like the old one, on the left side you will have a folder structure, on the right the belonging files for the selected folder. You can add profiles (either by context menu or by drag'n drop), you can move folders around my drag'n drop, you can of course add and delete folders via context menu.

The main handling of files and folders, is mostly done but there are a couple of things which need to get implemented, the actual color coding/different icons, some more columns on the right, more progress dialog handling etc....maybe I find some more time in the next days...

now back to that "what if" thing from the beginning. Here is a video which shows what happens if you drag'n drop the mentioned zipfile in the new profiler. The video grabbing isn't perfectly grabbing the drag'n drop operation which happens within the first seconds of the video but you can see how long it takes to fully parse (!) (did I mention that old clrmamepro only reads in the datfile header) 4743 datfiles, select the tosec folder to show the files in there, move the tosec-pix folder insinde the tosec-iso folder (that will do the same on your harddisk then) and restart clrmameui to see how long in takes after an import...

https://mamedev.emulab.it/clrmamepro/binaries/profiler.mp4

Actually, I think I can make it faster.....but time till tell

Keep in mind, it's just a start for a profiler, what you really need when working with 4k datfiles is a good rompath assignment management and batch runs.......again...time will tell...

56

clrmame Discussion / Re: clrmame 0.4 released

« on: 11 June 2025, 13:10 »

Filterming "mechanical" ones....well...is the mechanical flag inside the xml ok for you? Then it's easy, e.g. with an xpath based filter (talking of new clrmame now). In old cmpro you are able to use select sets with %M=1 to select mechanical ones (or %M=0 to select non mechanical ones).
If you're not happy with MAME internal mechanical flag, well, then you need to go by name or sourcefile as you do.......this can also be done in new clrmame via xpath filters...

The profiler in cmpro supports all kind of datfiles....anything which is MAME -listxml/-listsoftware based (or nointro, romcenter, etc...etc...), so, yeah, you can simply drag'n drop your xml file in it....or use "add datfile". And yes, the upcoming profiler for clrmameUi will support anything -listxml/-listsoftware like, too

57

clrmame Discussion / Re: clrmame 0.4 released

« on: 11 June 2025, 05:55 »

Hmm....well...when the profiler is done, the settings will be stored differently (each dat/xml file will have its own settings, similar to cmpro). Surely you will be able to use your own dat/xml/mame.exe exports with the profiler....and actually the xml/exe box inside the rebuilder/scanner will be obsolete then. I will think about if there can be some kind of fast 'switch profile' option inside the rebuilder/scanner....but don't count on it.

Addpaths won't be touched. The only thing I think about is that the dialogs can be made a little bit smaller vertically when I e.g. use some tabs for the Modifiers and Options groups. Then the full dialog should also fit on smaller resolutions.

Regarding fixes, yes, there are a couple of things which I may release soon but currently I work on the profiler...and it still will take a while. I keep you updated

58

clrmame Discussion / Re: clrmame 0.4 released

« on: 10 June 2025, 05:50 »

Well ok, easy answer: The window in its minimal height is too big for a 1920x1080 resolution with 150% scaling.
Generally the window will get smaller in a future release when the profiler is done, then you don't need the upper xml/exe input box anymore.

I can also think of a scrollable area for the controls....I will have a look

Till then, I guess you need to live with it or use 125% scaling....

59

clrmame Discussion / Re: clrmame 0.4 released

« on: 09 June 2025, 21:08 »

I've tried a 4k resolution with 150% scaling and an auto-hiding taskbar.....no problems......so..maybe a screenshot would help since I don't really understand what the problem is :-)

60

clrmame Discussion / Re: clrmame 0.4 released

« on: 09 June 2025, 19:09 »

The window can be resized but yes, there is a vertical and horizontal limit which you won't get under. Simply because you won't see all controls then. You can make it as big as you want. I haven't see any reason to enable the maximize button yet...maybe I will.
I don't understand the point with the hiding taskbar. I don't see any issues here with that option enabled.