#275 Log Checksum Verifier for other Operating Systems

[Anonymous]

Originally created by: xispy2
Originally owned by: tmkkmac

There is the Rip log checksum plugin (https://code.google.com/p/xld/issues/detail?id=29), which works great on a Mac. But it's necessary to run XLD with the plugin installed to validate logs generated by it.

So the idea is very simple: Provide stand-alone binaries for other operating systems to verify the checksums of XLD logs. A very simple command line tool would be sufficient, which checks one or more log files and gives a simple output: Good / Bad.

Something similar exists for logs generated by Exact Audio Copy, CheckLog.exe, which is only available for Windows, unfortunately. Personally, I'm mostly interested in a binary for Windows, but I assume there'd be an interest for all major operating systems.

Thanks for your consideration.

[Anonymous]

Originally posted by: tmkkmac

Here is a standalone log checker for Win32 (works under CLI). It should run on *nix systems using wine.
Note: SSE2 is required.

[Anonymous]

Originally posted by: tmkkmac

(No comment was entered for this change.)

Owner: tmkkmac
Status: Started

[Anonymous]

Originally posted by: xispy2

Thank you!

[Anonymous]

Originally posted by: tmkkmac

Please report if it works properly.

[Anonymous]

Originally posted by: xispy2

With initial testing I had some issues with character encodings: The log file must be in ANSI, everything else will result in a "Malformed". With special characters in the log's path name, the tool doesn't read the file at all.

But generally it seems to work as intended, which is great. Thank you so much for doing this, I'm sure there'll be other people appreciating this tool as well. I'll report back with more extensive results.

Since Wine is often a bit troublesome to use, is there any chance you could also provide a generic Linux binary?

[Anonymous]

Originally posted by: tmkkmac

>The log file must be in ANSI
That's strange. The log files from XLD are encoded with UTF-8, and changing encoding should result in "Malformed" result. The checker reads the file as binary, so the file encoding shouldn't be a problem.

>With special characters in the log's path name
This is a known issue. My compiler toolchain is mingw, and it doesn't support unicode entry point (wmain).

>Wine is often a bit troublesome to use
As far as I've tested the checker works with wine without problem.

[Anonymous]

Originally posted by: tmkkmac

Here is a new version fixing path name issue.

[Anonymous]

Originally posted by: xispy2

Awesome, thanks for your quick response. I'll test and let you know, if I find any more issues.

[Bill]

Thanks for providing this as it's been helpful over the years. This particular log shows to be fine when checked with XLD's log checker on macOS, but fails when using this Windows log checker. I don't see any obvious causes for this and would appreciate any thoughts.

[log removed]

[tmkk]

Logchecker on Mac says it is malformed.

[Bill]

I'm not sure why we would have inconsistent results, but I'm showing the log to be good on Mac. Okay well, your response and quick reply is appreciated. Best regards.

[tmkk]

Maybe you are still using old buggy XLD logchecker plugin? Please use the latest version (XLDLogChecker-20181110.zip).

[Bill]

Updated the log checker and the log is correctly showing malformed now. I had last updated it when the app went 64 bit, but it appears there was another update shortly thereafter that I missed. This is something I should have double checked. Apologies for bothering you with this, and thanks again for your time.