Audit log report

[bodbod]

Hi,

As an interesting feature, I believe having an audit log report giving you the following details would be useful :

- game summary (per collection : missing, extras (not recognized))
- artwork summary (per collection as well, details of the mising ones and not recognized items)

it's maybe in the next release knowing you guys but better to mention it !

retrofe.exe -auditG / -auditA

Thanks !

[The SPY]

Did this feature ever get implemented, This is something I'd really find handy right now

[Pieter Hulshoff]

Sorry, but no. Not yet.

[The SPY]

ok, all good, know you're hard at work.  Just wondering how to get the actual rom name displayed on a layout. but I can't see a this as a text parameter in the documentation. I know the system must know what it is, as it passes it as a parameter to the launcher etc. but can't find what "tag" I should be using to get it to display.  This would help me with some manual debugging, rather than having to go back to the log file every change etc

[Pieter Hulshoff]

There's no tag to display the rom name in a layout at the moment. You can display the title, which equals the rom name unless it's overwritten by the meta xml description information tag. I could add it if you feel it's really helpful; shouldn't be too much work.

[The SPY]

OK, so that's where that information is coming from. I'm just trying to tidy up my roms and sometimes I'm finding that it's really hard to actually tell the name of the rom that its going to open. At the moment if I'm unsure I open the rom then quit retroFE and the check the log file, which is a very slow process, if I could display the actual rom name the process would be much quicker, but I would only need to do this occasionally.  So not worth your time to update the code to add this feature

So that now brings me to my next question, When and how is the Meta.db created ? it doesn't appear to have been updated in my build since I did the original install. So it's not reading in any changes that I make to the xml files in the meta folder ?  Do I have to force an update somehow ?

[Pieter Hulshoff]

It should auto update whenever your RetroFE executable or an xml file is updated. It does that check based on file time stamps. You can always force a rebuild by deleting the meta.db file of course.

[The SPY]

when I delete the file and reopen , RetroFE won't launch to past the opening movie. I get this error in the the log file
[2020-05-16 17:09:06] [ERROR] [Metadata] Unable to create Metadata table. Error: database is locked
[2020-05-16 17:09:06] [ERROR] [RetroFE] Could not initialize meta database
[2020-05-16 17:09:06] [INFO] [Layout] Initialized
[2020-05-16 17:09:12] [INFO] [SDL] DeInitializing
[2020-05-16 17:09:13] [INFO] [RetroFE] Exiting

It creates a new meta.db file but it is zero bytes in size ?

[Pieter Hulshoff]

Sounds to me like you have an error in your meta xml files, causing RetroFE to fail creating the meta.db file. Can you upload the entire log.txt file?

[The SPY]

here is my log file. Could this be a linux permissions issues ? I see it has an number of import errors in the log file

[Pieter Hulshoff]

This doesn’t show the xml import. Can you delete the meta.db file again, run RetroFE again, and send me that log.txt file?

[The SPY]

ok, deleted meta.db and log file, so a nice fresh log file. but I don't think it's even trying to load the xml files. It errors out saying the db is locked

[Pieter Hulshoff]

Ok, that is odd... Can you move the meta xml files temporarily, delete the meta.db, and see if that allows you to start it again? If that works, add the xml files in a few at a time to find the culprit. If it doesn’t work, perhaps I’ll need to take a closer look at your entire setup.

[The SPY]

I tried that, still no luck still has the error DB locked, But I have moved the app from being on my NAS to being on the local HD and mapped the "data" folders only to the NAS and it now works as expected and the meta.db file can be deleted and it rebuilds its self from the XML files etc on startup.

So it's some weird permissions issue with having the meta.db file on the NAS rather than the local drive. It's odd that RetroFE can create the file and write to the log file correctly on the NAS, but it can't open the for write access the Meta.db file

[hiorik]

So it's some weird permissions issue with having the meta.db file on the NAS rather than the local drive. It's odd that RetroFE can create the file and write to the log file correctly on the NAS, but it can't open the for write access the Meta.db file

For me, that has more to do with permissions within the NAS than a bug in RetroFE.