Trader's Little Helper

[dorrcoq]

Go to tlh.easytree.org and you can get version 2.7.0 which really should work without issue.

[amber438]

Same error message with that version. wondering if it's because I installed my torrent program first?

[pernod]

I have the same problem since about a year, nothing to do with the new version though. I have to manually restore integration every time I start my PC, first time I get an error message like you do, the second time it works but sometimes I need to re-do it again a few hours later because it doesn't work anymore when I right click on a file. It's nothing major but still a nuisance. It has worked without these issues for years, I guess it has to do with administrator priviledges but re-installing TLH as administrator doesn't solve the problem either. Very strange all this.

[pernod]

Well, since about a week, without any rhyme or reason (that I know of) integration seems to have been restored without me having to manually restore it every time. Knock on wood!

[Five]

a week and a half away from the 15th anniversary of tlh

earliest archive page showcasing v0.9.1 Build 48
https://web.archive.org/web/20050321104905/http://thor.prohosting.com/roh0205/

thanks Robert

[tzuriel]

Just wanted to say thank you for TLH. It's an invaluable tool.:):cool:

Not sure what we did before this!

[GRC]

Just wanted to say thank you for TLH. It's an invaluable tool.:):cool:

I concur. I use it regularly.

Thanks, thanks, thanks

[teanertiner]

I have an interesting question. I have been using TLH for many years, mostly to validate flac files with the fingerprint files. Recently, my FTP client transferred a bunch of torrents from my seedbox and I found them to be corrupted. So I started testing the torrent file against the downloaded files. Some validate perfectly, others have errors with files missing or pieces not matching like this http://imgur.com/a/x6o6bKK. Some of this can be traced to characterset differences. But the finger prints still verify the files are complete and the audio files test OK. Can someone explain this? Thank you.

[tunic]

Judging from the image (http://imgur.com/a/x6o6bKK) that you posted originally (which you can't embed because the link doesn't have a file extension), I believe you're suffering from the 99% problem as explained on this Wiki page (http://wiki.dimeadozen.org/index.php/99percent_problem) from Dime. The torrent verification is looking for an image file, you might have deleted it.
Or, the filename of that particular file has characters that are not recommended to use in file names, the double quotation marks ( " " ). You could for instance try to change the filename, and in e.g. Notepad edit the torrent and checksum file(s) accordingly. I'm actually not sure if this works for the torrent file, never tried but it does work for the md5 checksum file. You could also completely remove that line for the image file.
The .ffp checksum file reported no problems, because it only checks the flac files.

[teanertiner]

The double quotes are the problem with the missing file, and I have tested the renaming of the file. I guess what I wonder about is that the last flac file says "4/5 matching pieces" but that file tests OK when testing and checking the ffp file (which also supposedly has missing pieces). So, my thought it that when generating the torrent file, the data to be torrented is not split on file boundaries and therefore a "piece" could contain multiple files or parts of multiple files and the inability to find the file with the bad name throws an error for the pieces contained in the other files as well, even though those files are really OK.

Does that make sense?

If that is the case, correcting the filename and the torrent file as you suggested should correct the entire issue. I will try to test that.

Thanks for the help.

[Five]

:confused:

okay, how about try extracting wav from flac, then take that wav and generate st5. also generate st5 from flac. if the checksums match and there are no errors the wav audio is exact.

[John Webster 1]

My computer crashed and lost everything including TLH which I had for few years with no problems. Bit worried about downloading stuff at moment. Can someone provide a link or confirm which TLH to download. Thanks

[Seth01]

Dude. First post in this thread says:



I've decided to make my prog public. You can download it here:

http://thor.prohosting.com/roh0205

http://tlh.easytree.org/


Robert

[Unidecker]

i just uninstalled and re installed the latest version thanks rohann and no virus no junk no problems :) works like its supposed to.


thanks R

[Unidecker]

ok now i have encoded and decoded two seperate flac and wav sets/shows and both went perfect as planned ...

once again roann thank you for your hard work.

you're app has no virus and or issues...
-Uni

[doctorzap]

weird issue

can not use this announce url

Announce URL: https://www.zappateers.com/announce/f4f65bfd9f6082125f16fd821e3521e1

is it suppose to be

Announce URL: http://www.zappateers.com/announce/f4f65bfd9f6082125f16fd821e3521e1

is anyone else have this issue

[1bgsky]

I changed to Windows 10 last week and got error messages that certain files weren't there when they certainly were.

I then dl'd the latest version of tlh but I still get error messages. So far one saying the file is corrupted :( Is thiis a known issue?

[pstern]

I've had a problem lately with the 'Delete source files' box. I have it checked, and after encoding or decoding a window pops up asking 'Are you sure you want to delete the source files?' When I click yes I get a message in red: 'file cannot be deleted (access is denied).'

[roann]

I've had a problem lately with the 'Delete source files' box. I have it checked, and after encoding or decoding a window pops up asking 'Are you sure you want to delete the source files?' When I click yes I get a message in red: 'file cannot be deleted (access is denied).'
Without further information, the following possible reasons come to mind:

#1 The folder ownership has changed.
#2 You do not have the appropriate permissions (read-only attribute; User Account Control).
#3 The file is encrypted.
#4 The file is corrupted.
#5 The user profile is corrupted.

Likely because of #2 TLH cannot delete the source files.

[pstern]

Without further information, the following possible reasons come to mind:

#1 The folder ownership has changed.
#2 You do not have the appropriate permissions (read-only attribute; User Account Control).
#3 The file is encrypted.
#4 The file is corrupted.
#5 The user profile is corrupted.

Likely because of #2 TLH cannot delete the source files.

#2 indeed. I knew it was something that I hadn't considered and that it would be obvious once I posted the issue. Thanks for your help!

[gmbseoxx]

Trader's Little Helper Alternative – Plenty of alternatives app to Trader's Little Helper that available to download out there.

[oshular]

Hello everyone. I'm having an odd issue with TLH 2.8.4. I have several TB of flac files with ffp and st5 that I created in past months/years. When I try to verify them now I get error in red 'format of file 'filename' is not supported.' I can create a new ffp file with those same flac files, but if I try to verify the new ffp file I get that same error. Also, if I try to create a new st5 file I get that same error. Everything was working fine until just recently. I did try uninstalling and reinstalling but still same thing. Very strange. Any help would be greatly appreciated. Thank you

[roann]

Hello everyone. I'm having an odd issue with TLH 2.8.4. I have several TB of flac files with ffp and st5 that I created in past months/years. When I try to verify them now I get error in red 'format of file 'filename' is not supported.' I can create a new ffp file with those same flac files, but if I try to verify the new ffp file I get that same error. Also, if I try to create a new st5 file I get that same error. Everything was working fine until just recently. I did try uninstalling and reinstalling but still same thing. Very strange. Any help would be greatly appreciated. Thank you
:hmm: I just checked verifying ffp and st5 files on an old Win 10 system - no problems at all...

Does "format of file ... is not supported" refer to the checksum file (TLH cannot open/read the checksum file) or to audio files listed within the checksum file (TLH can open/read the checksum file but fails to open/read audio files listed within)?

[oshular]

:Does "format of file ... is not supported" refer to the checksum file (TLH cannot open/read the checksum file) or to audio files listed within the checksum file (TLH can open/read the checksum file but fails to open/read audio files listed within)?

Hi Roann,
Thanks for responding. I'm getting that same message for each flac file in the st5. I tested some more and actually this is only happening with the 24 bit flac files. The st5 for my 16 bit 44.1 kHz flac files are verifying okay and allowing me to create new st5 files. But for all my 24 bit flac files, regardless of sample rate, I get that message when trying to verify previously created ffp and st5 as well as when trying to create new st5. I can create new ffp but then can't verify it.

[roann]

For a lot of tasks TLH uses free third party command-line tools.

When creating/verifying ffp checksum files flac.exe is used. flac.exe is able to handle 24-bit files, so no problems here.

When creating/verifying st5 checksum files shntool.exe is used. shntool.exe in turn calls flac.exe for decoding the audio data. Though shntool.exe is able to handle 24-bit WAV files it is not able to handle lossless encoded 24-bit files. In other words: shntool.exe is not able to handle st5 checksums of 24-bit audio files if an external decoder is involved. That's why TLH gives you the "format of file ... is not supported" error message.

Note: FLAC fingerprint and st5 checksum of a FLAC file are always identical because both are simply the md5 checksum of the raw WAVE data of the audio file. So there's no need to create st5 checksums for FLAC files.

[gmbseoxx]

When I was attempting to update to a newer version of the program Traders Little Helper it was flagged by Malwarebytes as being Generic.

[roann]

When I was attempting to update to a newer version of the program Traders Little Helper it was flagged by Malwarebytes as being Generic.
This was and is a pain in the ass - see this (http://www.thetradersden.org/forums/showpost.php?p=2659394&postcount=975) old post.

If you don't trust me you're free to use one of those...
Trader's Little Helper Alternative – Plenty of alternatives app to Trader's Little Helper that available to download out there.

[Bobbin TB]

For a lot of tasks TLH uses free third party command-line tools.

When creating/verifying ffp checksum files flac.exe is used. flac.exe is able to handle 24-bit files, so no problems here.

When creating/verifying st5 checksum files shntool.exe is used. shntool.exe in turn calls flac.exe for decoding the audio data. Though shntool.exe is able to handle 24-bit WAV files it is not able to handle lossless encoded 24-bit files. In other words: shntool.exe is not able to handle st5 checksums of 24-bit audio files if an external decoder is involved. That's why TLH gives you the "format of file ... is not supported" error message.

Note: FLAC fingerprint and st5 checksum of a FLAC file are always identical because both are simply the md5 checksum of the raw WAVE data of the audio file. So there's no need to create st5 checksums for FLAC files.

I have this issue with ffp and st5 files. Not sure what to do about it, short of manually comparing checksums.

[roann]

For a lot of tasks TLH uses free third party command-line tools.

When creating/verifying ffp checksum files flac.exe is used. flac.exe is able to handle 24-bit files, so no problems here.

When creating/verifying st5 checksum files shntool.exe is used. shntool.exe in turn calls flac.exe for decoding the audio data. Though shntool.exe is able to handle 24-bit WAV files it is not able to handle lossless encoded 24-bit files. In other words: shntool.exe is not able to handle st5 checksums of 24-bit audio files if an external decoder is involved. That's why TLH gives you the "format of file ... is not supported" error message.

Note: FLAC fingerprint and st5 checksum of a FLAC file are always identical because both are simply the md5 checksum of the raw WAVE data of the audio file. So there's no need to create st5 checksums for FLAC files.

I have this issue with ffp and st5 files. Not sure what to do about it, short of manually comparing checksums.

Without any further information I only can tell what you've quoted.

It would help to do some testing on my side if you could upload a ffp file, a st5 file, and an audio file as .zip/.rar/.7z archive to a free file hoster of you choice. Just PM (or email) me the download link.

[Bobbin TB]

Without any further information I only can tell what you've quoted.

It would help to do some testing on my side if you could upload a ffp file, a st5 file, and an audio file as .zip/.rar/.7z archive to a free file hoster of you choice. Just PM (or email) me the download link.

Here's one:
https://archive.org/details/sp2007-06-24.mk4.flac24

That year in the collection has a lot of shows with this problem because the band played a lot of shows at the Orange Peel, doing a short sort of residency, and one person taped a lot of them in 24bit.

I tried updating flac.exe but it didn't help.

[roann]

Here's one:
https://archive.org/details/sp2007-06-24.mk4.flac24

Thanks very much. Downloaded the files and tested a bit... The reason for the issue seems to be third party app flac.exe.

The last official release of a FLAC Windows binary is v1.3.2. There never was an official Windows binary of the latest v1.3.3 release, but there are unofficial binaries available (at RareWares (https://www.rarewares.org/index.php), for example). The latest TLH release (v2.8.4 build 185) comes with unofficial FLAC v1.3.3 binaries, the previous TLH release (v2.8.3 build 182) comes with the official FLAC 1.3.2 binaries.

To make a long story short: with the v1.3.2 binaries there are no issues when verifying/creating checksum files. I don't know why the v1.3.3 ones don't work - my knowledge of the C programming language is too poor to really understand the FLAC and shntool source code. If someone knows what's going on or can help please PM me.

So, as a workaround just copy the v1.3.2 releases of flac.exe and metaflac.exe (download (https://ftp.osuosl.org/pub/xiph/releases/flac/flac-1.3.2-win.zip)) to the subfolder CmdlineApps of the TLH installation folder.

Robert

[Bobbin TB]

Thanks very much. Downloaded the files and tested a bit... The reason for the issue seems to be third party app flac.exe.

The last official release of a FLAC Windows binary is v1.3.2. There never was an official Windows binary of the latest v1.3.3 release, but there are unofficial binaries available (at RareWares (https://www.rarewares.org/index.php), for example). The latest TLH release (v2.8.4 build 185) comes with unofficial FLAC v1.3.3 binaries, the previous TLH release (v2.8.3 build 182) comes with the official FLAC 1.3.2 binaries.

To make a long story short: with the v1.3.2 binaries there are no issues when verifying/creating checksum files. I don't know why the v1.3.3 ones don't work - my knowledge of the C programming language is too poor to really understand the FLAC and shntool source code. If someone knows what's going on or can help please PM me.

So, as a workaround just copy the v1.3.2 releases of flac.exe and metaflac.exe (download (https://ftp.osuosl.org/pub/xiph/releases/flac/flac-1.3.2-win.zip)) to the subfolder CmdlineApps of the TLH installation folder.

Robert

Awesome, thanks for the help. I just assumed it used 1.3.2 since that was the latest Windows one. Didn't think to check. Things seem to be working ok now. C is a little old school and beyond my capability. I didn't see an issue in github but I'll check again and submit one if there isn't. Thanks again.

[TTDaddy]

Howdy

I use TLH daily and love it. I'm trying to create checksums of a folder full of Beatle stuff, and I get a message that any file titled "Ob-La-Di, Ob-La-Da" "does not exist". Everything else is recognized, but every time THAT name comes up the program skips it. Can anyone enlighten me as to why? Thanks in advance!

[tunic]

Howdy

I use TLH daily and love it. I'm trying to create checksums of a folder full of Beatle stuff, and I get a message that any file titled "Ob-La-Di, Ob-La-Da" "does not exist". Everything else is recognized, but every time THAT name comes up the program skips it. Can anyone enlighten me as to why? Thanks in advance!

Is it just one file, or are there more files named as such?
Did you try renaming the file? I just tried to rename a flac file to Ob-La-Di, Ob-La-Da.flac and it didn't fail to create the md5 checksums, but perhaps your operating system has issues with some characters e.g. a comma in the filename. (I'm on Windows 11)
However I assume it's more likely that the file is corrupt. What happens when you test the file, e.g. run the option "Test Encoded Files" or "Show Audio file details"?

Can you copy/paste the Process Log?

[roann]

Howdy

I use TLH daily and love it. I'm trying to create checksums of a folder full of Beatle stuff, and I get a message that any file titled "Ob-La-Di, Ob-La-Da" "does not exist". Everything else is recognized, but every time THAT name comes up the program skips it. Can anyone enlighten me as to why? Thanks in advance!

Is it just one file, or are there more files named as such?
Did you try renaming the file? I just tried to rename a flac file to Ob-La-Di, Ob-La-Da.flac and it didn't fail to create the md5 checksums, but perhaps your operating system has issues with some characters e.g. a comma in the filename. (I'm on Windows 11)
However I assume it's more likely that the file is corrupt. What happens when you test the file, e.g. run the option "Test Encoded Files" or "Show Audio file details"?

Can you copy/paste the Process Log?

Second the questions...

Whenever TLH has to process a file it first checks (via a Windows function) whether or not the file exists. The file contents can be any crap the OS just checks its internal list of file names for the path given. So I don't think file corruption is the reason - and, because of the initial check for file existence, running other tasks on the file will fail too.

As tunic I guess this is a problem with the filename that may have some Unicode characters in it (TLH is not able to handle such characters). As suggested, copy a file, rename it and try again to create the checksum.

[mstaggerlee]

Hello everyone. I'm having an odd issue with TLH 2.8.4. I have several TB of flac files with ffp and st5 that I created in past months/years. When I try to verify them now I get error in red 'format of file 'filename' is not supported.' I can create a new ffp file with those same flac files, but if I try to verify the new ffp file I get that same error. Also, if I try to create a new st5 file I get that same error. Everything was working fine until just recently. I did try uninstalling and reinstalling but still same thing. Very strange. Any help would be greatly appreciated. Thank you
I had the same problem. Sometimes the latest is NOT the greatest - new versions of code introduce new bugs.

TLH 2.7.0.172 does not suffer from this issue, 24-bit flac files work as expected in every case. I suspect the newest version of flac.exe is responsible.

[roann]

Hello everyone. I'm having an odd issue with TLH 2.8.4. I have several TB of flac files with ffp and st5 that I created in past months/years. When I try to verify them now I get error in red 'format of file 'filename' is not supported.' I can create a new ffp file with those same flac files, but if I try to verify the new ffp file I get that same error. Also, if I try to create a new st5 file I get that same error. Everything was working fine until just recently. I did try uninstalling and reinstalling but still same thing. Very strange. Any help would be greatly appreciated. Thank you
I had the same problem. Sometimes the latest is NOT the greatest - new versions of code introduce new bugs.

TLH 2.7.0.172 does not suffer from this issue, 24-bit flac files work as expected in every case. I suspect the newest version of flac.exe is responsible.

There's indeed an issue with the latest flac.exe - details and workaround see this post (http://www.thetradersden.org/forums/showpost.php?p=3061836&postcount=1031).

[wharfratjoe]

The below fix also addresses the issue in this thread.

I to have the latest version of TLH: 2.8.4 (Build 185) and suffered from the same issue with 24bit files. TLH also had issues verifying 16/48 ffp's.

I also have FlacFrontend installed on my windows 10 laptop. If you do not have it, you can download/install it from here - http://flacfrontend.sourceforge.net/

1. Renamed flac.exe in traders little helper to flac.tlh located in C:\Program Files (x86)\Trader's Little Helper\CmdlineApps
2. Copied flac.exe from flac frontend (C:\Program Files (x86)\FLAC Frontend\tools)
3. Open TLH and test your 24bit and 16/48 ffp's and they should have no issues verifying now
4. From a command prompt you can also check both versions of flac in the traders little helper directory if renamed that according to step 1 above.

TLH version:
C:\Program Files (x86)\Trader's Little Helper\CmdlineApps>flac.tlh -v
flac 1.3.3

flac frontend version:
C:\Program Files (x86)\Trader's Little Helper\CmdlineApps>flac.exe -v
flac 1.3.0

[roann]

The below fix also addresses the issue in this thread.

I to have the latest version of TLH: 2.8.4 (Build 185) and suffered from the same issue with 24bit files. TLH also had issues verifying 16/48 ffp's.

I also have FlacFrontend installed on my windows 10 laptop. If you do not have it, you can download/install it from here - http://flacfrontend.sourceforge.net/

1. Renamed flac.exe in traders little helper to flac.tlh located in C:\Program Files (x86)\Trader's Little Helper\CmdlineApps
2. Copied flac.exe from flac frontend (C:\Program Files (x86)\FLAC Frontend\tools)
3. Open TLH and test your 24bit and 16/48 ffp's and they should have no issues verifying now
4. From a command prompt you can also check both versions of flac in the traders little helper directory if renamed that according to step 1 above.

TLH version:
C:\Program Files (x86)\Trader's Little Helper\CmdlineApps>flac.tlh -v
flac 1.3.3

flac frontend version:
C:\Program Files (x86)\Trader's Little Helper\CmdlineApps>flac.exe -v
flac 1.3.0

Do _not_ use the flac.exe v1.3.0 - use v1.3.2 as described above in my post!!!

[wharfratjoe]

### Updated ###

The below fix addresses the recent issue in this thread.

I to have the latest version of TLH: 2.8.4 (Build 185) and suffered from the same issue with 24bit files. TLH also had issues verifying 16/48 ffp's.

1. Download 1.3.2 flac from https://ftp.osuosl.org/pub/xiph/releases/flac/ (https://xiph.org/flac/download.html)
2. Rename flac.exe in traders little helper to flac.tlh located in C:\Program Files (x86)\Trader's Little Helper\CmdlineApps
3. Copy the flac.exe you downloaded in step one to C:\Program Files (x86)\Trader's Little Helper\CmdlineApps
4. Open TLH and test your 24bit and 16/48 ffp's and they should have no issues verifying now
5. From a command prompt you can also check both versions of flac in the traders little helper directory if renamed that according to step 1 above.

Broken version:
C:\Program Files (x86)\Trader's Little Helper\CmdlineApps>flac.tlh -v
flac 1.3.3

Good version:
C:\Program Files (x86)\Trader's Little Helper\CmdlineApps>flac.exe -v
flac 1.3.2

[jaman57]

FYI, FLAC 1.3.4 also fails, so still stick with 1.3.2.

[TTDaddy]

Howdy

I use TLH daily and love it. I'm trying to create checksums of a folder full of Beatle stuff, and I get a message that any file titled "Ob-La-Di, Ob-La-Da" "does not exist". Everything else is recognized, but every time THAT name comes up the program skips it. Can anyone enlighten me as to why? Thanks in advance!

Hi all

It was multiple files, all with the same name(s)...and the problem was the dashes. I tried removing the comma, that didn't fix the issue. I removed the dashes and put the comma back in....voila! Problem solved. Just in case someone encounters a similar issue. Thanks!

[roann]

Howdy

I use TLH daily and love it. I'm trying to create checksums of a folder full of Beatle stuff, and I get a message that any file titled "Ob-La-Di, Ob-La-Da" "does not exist". Everything else is recognized, but every time THAT name comes up the program skips it. Can anyone enlighten me as to why? Thanks in advance!

Hi all

It was multiple files, all with the same name(s)...and the problem was the dashes. I tried removing the comma, that didn't fix the issue. I removed the dashes and put the comma back in....voila! Problem solved. Just in case someone encounters a similar issue. Thanks!
Minus sign, dash and hyphen look very similar but have different ANSI/Unicode values. TLH cannot handle Unicode characters (btw, this will change with the new TLH release): if there are Unicode characters in a filename, TLH comes up with this "does not exist" error message.

[roann]

I am currently working on a new version of TLH (v3.0.0), which will include Unicode support (as far as possible), a new feature for audio file tagging, support for the WavPack codec, a new feature for spectral analysis of audio files, and a user manual, in addition to some improvements.

Unfortunately, it turned out that programming all these features takes much more time than I expected. And then there's Murphy's Law....

So, in the hope that enough people will be found who would like to test the program, there will be some alpha and beta versions in the next months (the current 3.0.0 alpha 1 can be downloaded from the TLH homepage (http://tlh.easytree.org) now). Any comments, suggestions, requests, bug reports, questions, whatever, will be greatly appreciated!

BTW, alpha and beta versions are always installed and can be used in parallel with an already installed 2.x.x version (the already existing one is not deleted/upgraded but remains untouched).

[pglazer1]

I tried the above fixes for TLH 2.8.4 with no luck.

[TheMysticMuse]

I am currently working on a new version of TLH (v3.0.0), which will include Unicode support (as far as possible), a new feature for audio file tagging, support for the WavPack codec, a new feature for spectral analysis of audio files, and a user manual, in addition to some improvements.

Unfortunately, it turned out that programming all these features takes much more time than I expected. And then there's Murphy's Law....

So, in the hope that enough people will be found who would like to test the program, there will be some alpha and beta versions in the next months (the current 3.0.0 alpha 1 can be downloaded from the TLH homepage (http://tlh.easytree.org) now). Any comments, suggestions, requests, bug reports, questions, whatever, will be greatly appreciated!

BTW, alpha and beta versions are always installed and can be used in parallel with an already installed 2.x.x version (the already existing one is not deleted/upgraded but remains untouched).


Any plans on making it open-source and posting it to GitHub so others can contribute?

[roann]

Any plans on making it open-source and posting it to GitHub so others can contribute?
Nope.

[TheMysticMuse]

Nope.

Roger that! :thumbsup

[jerryfreak]

any possibility of a linux binary? tried running it under wine and it reported :"an OS error occurred while executing the DOS subcomponent "

im trying to test a large library of flac files and flac command line doesnt work so great

find -type f -iname '*.flac' -print0 | xargs --null flac -t -w -s

tests ok but doesnt work so well because its a huge library and its output is

filename: error

i need

/full/path/to/filename:error

(like TLH outputs)

otherwise i cant find the errors easily as many filenames are similar

[jerryfreak]

also whats the easiest way to integrate flac 1.4.3 into an existing build?

[cicada]

Hi there! My apologies if this has already been covered here. I looked for a while (sigh). I'm running "show audio file details" in len mode.
I understand how to spot those pesky SBE's
-b- in the column named "cdr"


Just ran across a 24bit flac in a set of 16bit flacs
cxx in the column named "cdr"


I would like to understand the code for various errors/ problems. I seem recall a list somewhere. It's been a long time, so I might be dreaming.
***************************************

Here's the question -
Is there a list of errors that are possible in TLH?

***************************************
A 2nd question - Here's the latest (so far unknown to me)
I found the following in a recent fileset
3--xx in the column named "problems"

Thanks and keep on keeping on!
cicada

[roann]

Hi there! My apologies if this has already been covered here. I looked for a while (sigh). I'm running "show audio file details" in len mode.
I understand how to spot those pesky SBE's
-b- in the column named "cdr"


Just ran across a 24bit flac in a set of 16bit flacs
cxx in the column named "cdr"


I would like to understand the code for various errors/ problems. I seem recall a list somewhere. It's been a long time, so I might be dreaming.
***************************************

Here's the question -
Is there a list of errors that are possible in TLH?

***************************************
A 2nd question - Here's the latest (so far unknown to me)
I found the following in a recent fileset
3--xx in the column named "problems"

Thanks and keep on keeping on!
cicada

Press the Legend button and an info window (see attached image) will open.

[cicada]

Thank you roann. I missed that after all these years. Wow!:worship::worship::worship:

[Mr. Clumpy]

If a wave form is not canonical, does that mean it is lossy or just idiosyncratic? I recorded something from a higher quality radio stream and saved it in wav, and while TLH says there are no problems and shows the format as WAV it also shows that it is not canonical.

[roann]

If a wave form is not canonical, does that mean it is lossy or just idiosyncratic? I recorded something from a higher quality radio stream and saved it in wav, and while TLH says there are no problems and shows the format as WAV it also shows that it is not canonical.

If a program (e.g. an audio editor) writes additonal information to the file header that does not correspond to the WAVE file specification, the header is called "non-canonical" (a technical description see here (https://ccrma.stanford.edu/courses/422-winter-2014/projects/WaveFormat/)). It does not mean the audio data is lossless/lossy. It just a hint that the file header is non-standard in a way.

[Mr. Clumpy]

Thanks!

[FOSFOS]

Thanks very much. Downloaded the files and tested a bit... The reason for the issue seems to be third party app flac.exe.

The last official release of a FLAC Windows binary is v1.3.2. There never was an official Windows binary of the latest v1.3.3 release, but there are unofficial binaries available (at RareWares (https://www.rarewares.org/index.php), for example). The latest TLH release (v2.8.4 build 185) comes with unofficial FLAC v1.3.3 binaries, the previous TLH release (v2.8.3 build 182) comes with the official FLAC 1.3.2 binaries.

To make a long story short: with the v1.3.2 binaries there are no issues when verifying/creating checksum files. I don't know why the v1.3.3 ones don't work - my knowledge of the C programming language is too poor to really understand the FLAC and shntool source code. If someone knows what's going on or can help please PM me.

So, as a workaround just copy the v1.3.2 releases of flac.exe and metaflac.exe (download (https://ftp.osuosl.org/pub/xiph/releases/flac/flac-1.3.2-win.zip)) to the subfolder CmdlineApps of the TLH installation folder.

Robert

Thanks for the info. Saved a lot of searching. Works perfectly
and the thing about Unicode characters :thumbsup

[Ehstahm8ed>Iz]

Thank you! Now my TLH works perfectly. Easy fix

[lpmaskman]

I tried to encode 24/48 wav files to flac which I recorded with my new Diety PR-2 recorder and the program says,: file is truncated or otherwise corrupt.
The files play fine, and can be opened with Reaper without problems, no glitches.

[roann]

I tried to encode 24/48 wav files to flac which I recorded with my new Diety PR-2 recorder and the program says,: file is truncated or otherwise corrupt.
The files play fine, and can be opened with Reaper without problems, no glitches.

Which version of TLH are you using?

[lpmaskman]

I'm using 2.8.4. Tried to update the FLAC exes too, but reverted to the original.

[roann]

I'm using 2.8.4. Tried to update the FLAC exes too, but reverted to the original.

TLH v2.8.4 (build 185) comes with FLAC v1.3.3 binaries. Please use the v1.3.2 binaries instead.

As a workaround just copy the v1.3.2 releases of flac.exe and metaflac.exe (Download (https://ftp.osuosl.org/pub/xiph/releases/flac/flac-1.3.2-win.zip)) to the subfolder CmdlineApps of the TLH installation folder. Do not use release v1.3.4 or higher.

[lpmaskman]

TLH v2.8.4 (build 185) comes with FLAC v1.3.3 binaries. Please use the v1.3.2 binaries instead.

As a workaround just copy the v1.3.2 releases of flac.exe and metaflac.exe (Download (https://ftp.osuosl.org/pub/xiph/releases/flac/flac-1.3.2-win.zip)) to the subfolder CmdlineApps of the TLH installation folder. Do not use release v1.3.4 or higher.

Does the same with downgraded exes files too. Tried both 32 and 64 bits too. Also tried to check and uncheck keep foreign metadata option.