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 / 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......

2

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...

3

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

4

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

5

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....

6

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 :-)

7

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.

8

clrmame Discussion / Re: clrmame 0.4 released

« on: 04 May 2025, 11:03 »

Of course zstd does not mean that you always get smaller files...nobody ever said so. It's always an average compare based on many differently sized data and different byte patterns....

9

clrmame Discussion / Re: clrmame 0.4 released

« on: 03 May 2025, 07:36 »

clrmamepro does not have zstd support.

clrmame(UI) has.
For the rebuilder, you can select your compression output method (e.g. zip (zstd). If source files don't use zstd, they will be converted, but that's a general thing, you are always able to rebuild from e.g. 7z to zip or from decompressed files to zstd etc. The only exception is when matching files already exist in the destination. They get skipped.

The scanner only needs your favourite compression method when it adds new files somewhere. For delete/rename operations, it takes what it finds (or it doesn't matter). For newly added ones it takes your prefered method which is automatically determined when you start a scan by looking at your existing files.  The method which is used most of the time is taken.

So...for zstd it would make sense to convert a collection first to zstd only with the rebuilder.

Personally I don't think in times of multi terabyte hds it's not worth spending time on recompressing archives....just to gain some space...the good thing on zstd in zipfiles however is that operations still be fast...not comparable to solid 7z archives where every add/del is expensive timewise.

10

clrmame Discussion / Re: clrmamepro unzippping some sets into separate folders

« on: 28 April 2025, 06:13 »

1st question would be: Why was it touched? Was it missing in the first place and either a rebuilder step or scanner fix missing picked it up from somewhere and added it? Or was something wrong with the file so that any kind of fix operation touched it?
If this is unknown, you can still check rebuilder->compress files needs to be ticked for rebuild operations. The scanner (fix missing for example) decides on its own which pack method to use for new files. Initially it simply counts the occurences of existing archives (or folders) in rompaths. So normally if you keep your files zipped, it will follow that.
You can move the unpacked files to a separate place and check if a normal scan unpacks the still existing archives again. Or you can move both and readd them either with the rebuilder or fixmissing/addpaths to see how they get added. In other words: Check if this is repeatable. Generally, hard to say what happened in old clrmamepro

...use the new tool instead ;-)

11

clrmame Discussion / Re: clrmame 0.4 released

« on: 21 April 2025, 13:58 »

I always wondered why people look at stats.....an empty scan results window is what you should look for ;-)

Currently stats aren't planned but surely the upcoming profiler will indicate a datfile status, too

12

clrmame Discussion / Re: clrmame 0.4 released

« on: 21 April 2025, 09:28 »

There isn't really a stats screen but the log output says a bit about the number of complete/empty/partly wrong machines

13

clrmame Discussion / clrmame 0.4 released

« on: 20 April 2025, 17:01 »

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

UI:

- scanner, fixed showing of empty and complete machines
- scanner, fixed showing of non rom/sample/disk related machine/file/folder issues

Core:

- added: read/write support for zstandard compressed zip files
- rebuilder, two zstd compression methods added, newly created/added files   will use it (existing destination files which don't get replaced won't be   updated). Source files which don't use the set compression method won't be taken into account when checking for a direct archive copy
- scanner, automatically detects if you prefer zstd or deflate compressed zips and uses the preferred setting the case that new files are added.
- with both, rebuilder/scanner you can theoretically end up with zip files which have files in it with different compression methods. Rebuilder: if you
  rebuild to existing files, scanner, if you already have a mixture of archives using different compression methods.

- added: scanner, reporting 'wrong' chd version. Current expected version is 5, warning is not shown for baddumps. Version and baddump warning can be altered in settings.xml

- misc:  changed the behaviour of devices which have romOf dependencies. When fully merging such devices they are now handled like parent/clone machines. On the one hand it makes sense since there are merge attributes indicating that such sets belong together but there are also cases where they are distinct. This is now aligned with clrmamepro, but still something which might need further discussion

- misc:  updated cli11 to 2.5.0
- misc:  updated spdlog to 1.15.2
- misc:  updated bit7z to 4.0.10

- misc:  scanner, using absolute pathnames for error reporting in path scan
- misc:  scanner, only trace-log machines with issues in fixing phase
- fixed: scanner, typo "uneeded"
- fixed: scanner: detection of empty but unneeded folders in archives
- fixed: scanner, backup of chds in software list collections can fail
- fixed: scanner, archives which match a valid rompath subfolder name (e.g. softwarelist name via pattern or automatically) are falsely iterated like a folder instead of listing them as unneeded (wrong placed)
- fixed: crash on rom definitions without a crc
- fixed: filter enrichment might miss sampleof dependencies
- fixed: doing archive backups from a folder and backup archive already exists creates a new archive instead of merging files in

14

clrmame Discussion / Re: Easter egg

« on: 16 April 2025, 12:13 »

last clue....

15

clrmame Discussion / Re: clrmame just closing

« on: 15 April 2025, 17:41 »

Thanks, problem found (missing crc in listxml output). Fixed the exception for next version, however, missing crc should be reported to MAME Devs (2 roms in tpoker2)

16

clrmame Discussion / Re: clrmame just closing

« on: 15 April 2025, 05:21 »

Ah it crashes for you during data import (shouldnt answer posts without having a coffee first). I will check it. Can you please send me the used exe file?

17

clrmame Discussion / Re: clrmame just closing

« on: 15 April 2025, 04:47 »

Sounds like the not repeatable crash when starting fixing which was reported here before. Users reported that it just closes when fixing starts and shows 0%.
Is it the same for you? Does a scan without fixing work?
If you can repeat it with a minimal set (e.g with just the files which needs fixing), can you somehow zip the whole installation and give it to me?
The  content of Backup folder might also play a role though……or threading (that can be tested by setting the threads to 1)
Users reported the problem when some versions ago two amiga sl were renamed/reorganzied.
Unfortunatey I wasnt able to repeat it yet

18

clrmame Discussion / Re: Easter egg

« on: 13 April 2025, 10:24 »

 If you know it zip your mouth…

19

clrmame Discussion / Re: Easter egg

« on: 12 April 2025, 07:50 »

ok..maybe too hard to guess.....

20

clrmame Discussion / Easter egg

« on: 11 April 2025, 18:51 »

93 (0x5D)


;-)

….coming to clrmameUI…so not an active easter egg yet