Taperssection.com

Gear / Technical Help => Ask The Tapers => Topic started by: 1westkc3 on June 18, 2006, 03:31:01 AM

Title: Recording shows 0:00 length but 906MB
Post by: 1westkc3 on June 18, 2006, 03:31:01 AM
I pulled Seal with Hall & Oates last night with my Rockbox enabled H120.  I get to the car, fire up the iRiver and low the Seal set shows 0:00 length.  I get home and check and zip.  To be safe, I copy the file to my hard drive and try playing it with Foobar 2000.  It plays fine and Foobar displays length to be 1:27:39.  I try opening the file in Audacity and nothing.  So I need some help here.  I'm not at all certain how to go about salvaging this file and understanding why this may have occured.

PS - The Hall & Oates set is fine. 
Title: Re: Recording shows 0:00 length but 906MB
Post by: F.O.Bean on June 18, 2006, 03:36:52 AM
did you unzip teh zip file?
Title: Re: Recording shows 0:00 length but 906MB
Post by: 1westkc3 on June 18, 2006, 05:51:39 AM
The file is not zipped.  It is a wav file with the .wav extension.
Title: Re: Recording shows 0:00 length but 906MB
Post by: whatboutbob on June 18, 2006, 09:41:57 AM
Header will be buggered. Download and run kuba's header repair app: http://www.fi.muni.cz/~xvanek4/repair/repair.zip

This usually happens when recording does not shut down gracefully (eg when you run out of battery), because headers are written last.

How did you stop the recording?  Is it possible you only paused recording, then hooked it up to your puter?

Also, which rockbox build are you using?
Title: Re: Recording shows 0:00 length but 906MB
Post by: 1westkc3 on June 18, 2006, 10:15:47 AM
OK, so I DL'd and extracted kuba's header repair app but when I double click to run it, it flashes and nothing.  I looked for a read file for instructions but no joy.  Any ideas?
Title: Re: Recording shows 0:00 length but 906MB
Post by: whatboutbob on June 18, 2006, 10:56:15 AM
from the iriver faq:  http://taperssection.com/index.php?topic=64277.0

[540] My recorded file is xxx MB, but my audio software says it is 0:00 minutes long.  How do I fix this?

Your wav header is buggered (the little bit at the start of a wav file that stores some information about the file, including how long it is).  This can happen from a variety of causes where recording hasn't stopped gracefully (eg your battery dies mid-recording or you pause mid-recording then connect to your computer).

Use Kuba's nifty little wav header repair utility to generate a new header: http://www.fi.muni.cz/~xvanek4/repair/repair.zip (http://www.fi.muni.cz/~xvanek4/repair/repair.zip)

Once downloaded:

1) unzip the app to the same dir as your file
2) It runs from a command-line, so you'll need to get to a command prompt in windows by clicking on 'start' then 'run'.  Type 'cmd'. Click 'ok'
3) In the black window that opens, navigate to the directory your file is in.  (You change directories by typing 'cd <directory name>'). 
4) Once you're in the correct directory get the exact file size and name by typing 'dir'.
4) Now type 'Repair <filename> <filesize>'
Title: Re: Recording shows 0:00 length but 906MB
Post by: ethan on June 18, 2006, 11:30:26 AM
CDWave will fix these too. Pops up a warning about the header but will read it then you can save tracks.
Title: Re: Recording shows 0:00 length but 906MB
Post by: 1westkc3 on June 18, 2006, 12:00:34 PM
from the iriver faq:  http://taperssection.com/index.php?topic=64277.0

[540] My recorded file is xxx MB, but my audio software says it is 0:00 minutes long.  How do I fix this?

Your wav header is buggered (the little bit at the start of a wav file that stores some information about the file, including how long it is).  This can happen from a variety of causes where recording hasn't stopped gracefully (eg your battery dies mid-recording or you pause mid-recording then connect to your computer).

Use Kuba's nifty little wav header repair utility to generate a new header: http://www.fi.muni.cz/~xvanek4/repair/repair.zip (http://www.fi.muni.cz/~xvanek4/repair/repair.zip)

Once downloaded:

1) unzip the app to the same dir as your file
2) It runs from a command-line, so you'll need to get to a command prompt in windows by clicking on 'start' then 'run'.  Type 'cmd'. Click 'ok'
3) In the black window that opens, navigate to the directory your file is in.  (You change directories by typing 'cd <directory name>'). 
4) Once you're in the correct directory get the exact file size and name by typing 'dir'.
4) Now type 'Repair <filename> <filesize>'


OK, I've followed these instructions but I get an error message re. invalid parameters.  So, to clairify;
1) the file name includes spaces, do I include spaces in the repair command (Seal 6-17-06)?
2) do I include the .wav file name extension in the repair command (Seal 6-17-06.wav)?
3) do I include the "," in the file size (927,817,772)?
4) is there a space between the file name and the file size?

Sorry to be so thick and thanks for your continued support.
Title: Re: Recording shows 0:00 length but 906MB
Post by: whatboutbob on June 18, 2006, 12:51:19 PM
1) not sure. just rename it in windows explorer (right click, click 'rename') to remove the space.
2) yes.
3) no
4) yes

so assuming you rename the file to remove the space, your cmd will be: repair Seal6-17-06.wav 927817772
Title: Re: Recording shows 0:00 length but 906MB
Post by: 1westkc3 on June 18, 2006, 01:18:01 PM
Joy abounds!!!!  Thanks so much.  The repair app doesn't like spaces in the file name and identifies it as a parameter problem.  The repair worked fine and the file now reflectsb length as 87:39.  I again must express my gratitude for all your assistance and patience. 
Title: Re: Recording shows 0:00 length but 906MB
Post by: china_rider on June 18, 2006, 01:28:27 PM
FYI... for next time
repair "Seal 6-17-06.wav" 927817772 should have worked.
Title: Re: Recording shows 0:00 length but 906MB
Post by: Aaron41 on June 26, 2006, 03:38:16 PM
Seal AND Hall and Oates? Please upload that somewhere! :)

No I'm not joking. I'd be very interested in hearing both.