[roann]

Originally Posted by Speedy71471

Greetings all -

Love TLH... replaces a lot of things I was doing in CMD files.

One thing I did observe... the "test" feature doesn't really work with Shorten files. TLH will report that a corrupt SHN file will decode properly even though it actually had a corrupt block and aborts (you can see the message using command-line shntool).

Dunno if anyone noticed (I know most folks use FLAC these days but I have about 600GBs of SHNs... :wacko:

SS

Shorten.exe doesn't have any verify option. So I simulated it with "decode to NUL device and see if there's an error message". In other words: TLH decodes the shn file via shorten.exe but no decoded data will be written to your harddisk. Only error messages of shorten.exe will appear in the log window. If TLH reports that a corrupt shn file will decode properly there wasn't any error reported by shorten.exe during decoding.

Robert