cd wave said cannot open RIFF chuck, file is not a valid wave file. so does that mean i have a f'd header that will have to be manually edited? i think a friend of mine has cool edit, so maybe i can get the file to him to try. and i can still try chkdsk i guess, tho i tried that on the file that i copied to the HD, and nothing appeared wrong.
I will continue on the RIFF header edit scenario. What you have to do is make the first 44 bytes of this file match that of a good file recorded using the same settings.
Download Ultra-Edit from
www.ultraedit.com . Open up your file with it and it should switch to the hex view because it will detect it as being a binary file. Now open a good file. Set the Window so that you can compare the files in the same window. (From the menu this is Window->Tile Horizontal or Window->Tile Vertical )
Make sure that the first 44 bytes of both files match exactly. Ultra-Edit will allow you to change values by positioning the cursor on the bytes you wish to change. Save the RIFF corrected file.
Now redo the audiohack procedure and you should get two files. The first file will have the RIFF header counter and data chunk counter corrected based upon the file size.
If you get a file that can be opened in an audio editor but it contains white noise, then the actual offset to the data is incorrect. With many software pacakges the riff header should take up 44 bytes, but this is not always the case if the fmt chunk is larger or there is a pad chunk inserted into your file by some process.
In that case, you would need to import the file as raw and specify the start of the pcm data. Ultraedit can help you determine the start of the data chunk. I use Samplitude 7 for raw data import because it has a way to specify a starting offset to the samples. With 24-bit data one of six offsets would be correct. I would try separate attempts with 45, 46, 47, 48, 49, or 50.
Audiohack also has an option to strip the RIFF header from the file, but it has to be able to determine where the data chunk starts. For your file this can't be determined. However, I guess I need an option so that the user can specify a certain number of bytes to strip from the beginning of the file. That way it could be subsequently imported to any software package that has the raw import capability.
Gordon