PDA

View Full Version : Decoding SHN files


Alder-fish
2007-02-13, 05:30 PM
I've got problems opening SHN files from the David Crosby 4/18/87 show using Traders Little Helper, says 'files either corrupt or truncated'. I've not had problems before decoding files of this type, and I've downloaded this twice now with the same result. Can anyone shed any light on this please? :hmm:

ohkeepa
2007-02-13, 05:31 PM
have you tried running the MD5s to see if the file is corrupt or not?

Alder-fish
2007-02-13, 05:38 PM
I've run 'verify' in TLH which says verified Ok, but checksum does not match.

ohkeepa
2007-02-13, 05:43 PM
if the checksum does not match them something is wrong with the file
is the torrent still active?

U2Lynne
2007-02-13, 06:52 PM
I've run 'verify' in TLH which says verified Ok, but checksum does not match.
This doesn't make sense to me. Isn't the verify option in TLH to verify flac files? You need to use an md5 to verify if shn files are OK. But, if the checksum doesn't match, how can the checksum verify the files as OK? :hmm:

pmonk
2007-02-13, 08:22 PM
I've got problems opening SHN files from the David Crosby 4/18/87 show using Traders Little Helper, says 'files either corrupt or truncated'. I've not had problems before decoding files of this type, and I've downloaded this twice now with the same result. Can anyone shed any light on this please? :hmm:

If you have shntool, run a len report to see what it says.

len mode output

The output of len mode may seem cryptic at first, because it
attempts to convey a lot of information in just a little bit of
space. But it is quite easy to read once you know what the col-
umns represent; and in certain columns, what each character in
the column means. Each column is explained below.

length Shows the length of the WAVE data, in m:ss.nnn (millisec-
ond) format. If the data is CD-quality, then m:ss.ff is
shown instead, where ff is a number from 00 to 74 that
best approximates the number of frames (2352-byte blocks)
remaining after m:ss. If all files are CD-quality, the
total length will be shown in m:ss.ff format; otherwise
it will be in m:ss.nnn format. NOTE: CD-quality files
are rounded to the nearest frame; all other files are
rounded to the nearest millisecond.

expanded size
Shows the total size of all WAVE chunks within the file
(header, data and any extra RIFF chunks). Essentially
this is the size that the file would be if it were con-
verted to .wav format, e.g. with shntool conv.

NOTE: Do not rely on this field for audio size! If you
simply want to know how many bytes of audio are in a
file, run it through info mode, and look at the "data
size" field in its output.

cdr Shows properties related to CD-quality files. A 'c' in
the first slot indicates that the WAVE data is not [C]D-
quality. A 'b' in the second slot indicates that the CD-
quality WAVE data is not cut on a sector [b]oundary. An
's' in the third slot indicates that the CD-quality WAVE
data is too [s]hort to be burned.

A '-' in any of these slots indicates that the particular
property is OK or normal. An 'x' in any of these slots
indicates that the particular property does not apply to
this file, or cannot be determined.

WAVE Shows properties of the WAVE data. An 'h' in the first
slot indicates that the WAVE [h]eader is not canonical.
An 'e' in the second slot indicates that the WAVE file
contains [e]xtra RIFF chunks.

A '-' in any of these slots indicates that the particular
property is OK or normal. An 'x' in any of these slots
indicates that the particular property does not apply to
this file, or cannot be determined.

problems
Shows problems detected with the WAVE header, WAVE data,
or the file itself. A '3' in the first slot indicates
that the file contains an ID[3]v2 header. An 'a' in the
second slot indicates that the audio data is not
block-[a]ligned. An 'i' in the third slot indicates that
the WAVE header is [i]nconsistent about data size and/or
file size. A 't' in the fourth slot indicates that the
WAVE file seems to be [t]runcated. A 'j' in the fifth
slot indicates that the WAVE file seems to have [j]unk
appended to it.

A '-' in any of these slots indicates that the particular
problem was not detected. An 'x' in any of these slots
indicates that the particular problem does not apply to
this file, or cannot be determined.