Quote:
Originally Posted by tunic
<snip> When I checked the Audio File Details with TLH build 147, the conclusion was that no errors occurred. But track 4 is corrupt, and the last track has a sector boundary error. See the attached screenshot. </snip>
|
With build 147 the way TLH handles
Show audio file details has changed (see changelog that comes with TLH):
Show audio files details now "just" shows you what shntool puts out. Checking for SBEs has been completely removed (now this can be done using the new stand-alone page
Check audio files for SBEs).
That's why a) the
Fix SBEs button is missing, and b) there's no conclusion
There were sector boundary errors or
There were no sector boundary errors displayed. The conclusion you get now is
No errors occured or
There were errors. This tells you whether there were errors
processing the source files (the interpretation of the shntool output is up to the user).
In your case shntool was able to process all files (i.e. to read those file parts needed to get all the information displayed) without any error, and so you got a
There were no errors conclusion.
Maybe I should change the conclusion to
... processing the files?
Quote:
Originally Posted by tunic
<snip> I downloaded the set first as .mkw, then discovered track 4 to be corrupt so downloaded that file in .wav but it's also corrupt. I can't play the track with winamp, nor open it with Audacity. When I opened it with CD Wave editor, I was able to play the first few minutes, the rest is junk. </snip>
|
Encoded files can be tested for corruption using the
Test encoded audio files page. For
wav files there's no TLH subcomponent that can (completely) handle this. As I said it's up to you to interprete the shntool output. The length and the ratio of track 4 indicate that the file is corrupt.
Maybe I should add a function that checks for zero length and a ratio greater than 1?
Robert
No members have liked this post.