salvage corrupt mp3

For the most part, it's a PCM (.wav) file.
There is nothing in there that indicates it's
mp3; the ID3 block doesn't make it mp3. At
0x400 you have what sort of looks like the
start of a riff file but it's messed up. The
data is PCM, or could be, so get something like
sox, and a binary file editor, and a few tutorials
on PCM and .wav files, and have at it. You should
be able to hear if the data is also messed up with
just a little bit of work.

What you COULD do is find a PCM player that
plays raw PCM, and just feed it some of the file.
Not many apps will play 4.7 GB files (seems odd
unless you were recording directly to a DVD), so
cut out a few MB and play that. The initial part
of the file will play as noise but if the rest is
good, it will sound normal. From the looks it's
44100 Hz, 16-bit, 2 channel, intel-byte order
(low byte high byte). The start of each sample
is aligned okay if you want to start play at the
beginning.

--
40th Floor - Software @ http://40th.com/
phantasm.40th.com - The finest sound in the world

On Jul 6, 7:00 am, Gardner <[email protected]> wrote:
> Hello Everybody,
>   I recently attempted to record a 12 hour DJ set with Sound Forge.
> While exporting to mp3 sound forge crashed leaving an mp3 on the
> desktop that was 4.7GB in size. The mp3 is not recognized by WMP,
> Winamp, VLC, MPlayer, and Audacity thinks it can parse it but it just
> infinitely increments the time to complete.
>
> I opened the file up in a hex editor and it has an ID3 tag and
> something that looks like a header. Unfortunately I am not familiar
> enough with the binary mp3 format or header to determine if everything
> looks good.
>
> My hope is that some hardcore audiophile or a talented programmer will
> be able to immediately see if there is a major issue:https://spunts.com/beginning-of-corrupt.mp3
>
> All of the DJs would like copies of the sets and it was a really
> wicked party. Any insight would be greatly appreciated.
>
> Regards,
>   Gardner

I have had sound file that would not play or xfer on my WIN XP machine
from my Zoom H2.
I then connected to WIN ME, ran CHKDSK and file got corrected.

Maybe I could do this on WIN XP, gotta find the CHKDSK program.

--
See new Amero corrency at
http://Amero.PhotosNYC.com

In article <e03aecd5-ff24-4d29-9859-475b125cfb91@
59g2000hsb.googlegroups.com>, [email protected] says...
> Maybe I could do this on WIN XP, gotta find the CHKDSK program.
>
>

I run chkdsk on my windows xp by entering "chkdsk", the drive letter and
any additional parameters in the start>run command box. You can also
run it from a window similar to a DOS window by entering "cmd" in the
start>run box then the appropriate chkdsk command with parameters as
listed below. Remember to enter "exit" to get out of the command
window, and of course press the enter key to start your commands.

The information below was copied from the help file displayed after
entering the search term "chkdsk" in the Help and Support Center found
on the XP start menu.

----------------------------------------


The chkdsk command requires the file Autochk.exe. If it cannot find it
in the startup directory (\%systemroot%\System32, by default), it will
attempt to locate it on the Windows Installation CD. If you have a
multiboot computer, be sure you are issuing this command from the drive
containing Windows.

chkdsk [drive:] [/p] [/r]

Parameters

none

Used without parameters, chkdsk displays the status of the disk in the
current drive.

drive:

Specifies the drive that you want chkdsk to check.

/p

Performs an exhaustive check even if the drive is not marked for chkdsk
to run. This parameter does not make any changes to the drive.

/r

Locates bad sectors and recovers readable information. Implies /p.


--
I. Care
Address fake until the SPAM goes away ;-}

Gardner <[email protected]> put forth the notion in...news:ab14227e-01fb-
[email protected]:

> Hello Everybody,
> I recently attempted to record a 12 hour DJ set with Sound Forge.
> While exporting to mp3 sound forge crashed leaving an mp3 on the
> desktop that was 4.7GB in size. The mp3 is not recognized by WMP,
> Winamp, VLC, MPlayer, and Audacity thinks it can parse it but it just
> infinitely increments the time to complete.
>
> I opened the file up in a hex editor and it has an ID3 tag and
> something that looks like a header. Unfortunately I am not familiar
> enough with the binary mp3 format or header to determine if everything
> looks good.
>
> My hope is that some hardcore audiophile or a talented programmer will
> be able to immediately see if there is a major issue:
> https://spunts.com/beginning-of-corrupt.mp3
>
> All of the DJs would like copies of the sets and it was a really
> wicked party. Any insight would be greatly appreciated.
>
> Regards,
> Gardner

I use Vegas Pro, and it has a mechanism for recovering a file in case
there's a crash. Does Sound Forge not have that? You didn't say what
version you're running.

If it's there, it's most likely in the designated temp-work location
specified under your setup options or something like that.


david

"Gardner" <[email protected]> wrote in message
news:ab14227e-01fb-42a2-b4df-4dde5911ceac@25g2000hsx.googlegroups.com...
> Hello Everybody,
> I recently attempted to record a 12 hour DJ set with Sound Forge.
> While exporting to mp3 sound forge crashed leaving an mp3 on the
> desktop that was 4.7GB in size. The mp3 is not recognized ...

...
> Regards,
> Gardner

I am not familiar with Sound Forge.

Sound Forge was recording this session somewhere in some format. If it was a
temporary file it would not have deleted it until shutdown. It did not
shutdown, it crashed. Do you have a massive temporary file somewhere?

If such an event occurs the one thing not to do is to re-open the original
app that just crashed, because it is possible that the first thing it is
going to do is overwrite its old temporary file with a new empty one. This
behaviour varies from program to program. Some of the "better worser" ones
know they fail and are prepared to recover. If you do not know that you have
one of those programs the first thing to do to save vital data is copy and
rename the temporary file.

On Sun, 6 Jul 2008 04:00:46 -0700 (PDT), Gardner <[email protected]>
wrote:

>Hello Everybody,
> I recently attempted to record a 12 hour DJ set with Sound Forge.
>While exporting to mp3 sound forge crashed leaving an mp3 on the
>desktop that was 4.7GB in size. The mp3 is not recognized by WMP,
>Winamp, VLC, MPlayer, and Audacity thinks it can parse it but it just
>infinitely increments the time to complete.
>
>I opened the file up in a hex editor and it has an ID3 tag and
>something that looks like a header. Unfortunately I am not familiar
>enough with the binary mp3 format or header to determine if everything
>looks good.
>
>My hope is that some hardcore audiophile or a talented programmer will
>be able to immediately see if there is a major issue:
>https://spunts.com/beginning-of-corrupt.mp3
>
>All of the DJs would like copies of the sets and it was a really
>wicked party. Any insight would be greatly appreciated.

It looks like a header and then PCM data (about 0.01 seconds worth
of header and 0.02 seconds worth of "audio" - at least it's a
reasonably flat straight line with a little noise in it). As a first
approximation you could copy it (to protect and keep the original) and
rename it to a .wav file and see if you can play that. If not, open it
as "raw PCM", 16-bit stereo 44kHz and see if that is playable. That's
how I opened the file in Cool Edit 2000 (okay, so I've got really old
software).

>
>Regards,
> Gardner