View Post [edit]
Poster: | mnuanes | Date: | Feb 1, 2003 11:53am |
Forum: | etree | Subject: | Re: can anyone help?? RRFB 03-1-10 |
Reply [edit]
Poster: | nomad | Date: | Feb 1, 2003 2:34pm |
Forum: | etree | Subject: | Re: can anyone help?? RRFB 03-1-10 |
Reply [edit]
Poster: | Rich | Date: | Feb 3, 2003 12:29am |
Forum: | etree | Subject: | Re: can anyone help?? RRFB 03-1-10 |
It is a corrupt file.
I copied a response for this problem from Mark Goldey:
The file is corrupt.
http://research.umbc.edu/~hamilton/shnfaq.html
If the file plays OK in WinAmp, you may be able to generate .wavs from it by setting the output (under Preferences) to the Nullsoft .wav generator, which will create a .wav file. You'll want to listen carefully to be sure that the .wav has no flaws, though.
Reply [edit]
Poster: | Michael Moran | Date: | Feb 3, 2003 8:52am |
Forum: | etree | Subject: | Re: can anyone help?? RRFB 03-1-10 |
Reply [edit]
Poster: | Michael Moran | Date: | Feb 2, 2003 6:40am |
Forum: | etree | Subject: | Re: can anyone help?? RRFB 03-1-10 |
Reply [edit]
Poster: | sunphish | Date: | Feb 2, 2003 1:32am |
Forum: | etree | Subject: | Re: can anyone help?? RRFB 03-1-10 |
Reply [edit]
Poster: | Diana Hamilton | Date: | Feb 4, 2003 4:36am |
Forum: | etree | Subject: | Re: can anyone help?? RRFB 03-1-10 |
Also, from the misc reports here, I'm not clear on this: Is it *every* track of the 1/10/2003 d/l that's giving MD5 = OK on md5 check post-download, yet failing to decompress for *everyone*? Thanks for any details! I see there have only been positive reviews (2), that's part of what's puzzling me.
BTW given the nonstandard-looking prep on the fileset, it's possible there was some confusion or error at the seed>shn prep stage...
Reply [edit]
Poster: | Diana Hamilton | Date: | Feb 4, 2003 6:08am |
Forum: | etree | Subject: | Re: RRFB 03-1-10- remedy |
b38a8e23aa6653d5083bb7a63eb00b18 *TrackD102.shn
which matches the one onsite (presumably uploaded with the shns). Indeed there is a "no magic number error on decompression attempt.
Conclusion: Situation serious at the seeder's end (he is presumably generating md5s on incorrectly compressed shns).
Followup needed from users: Please post reports here of any other shn sets where this identical thing is happening (ie, shns pass md5s, yet don't decompress properly). If it is multiples from the same person, it will help to present a better package of info to him to address fixes from his end. Thanks!