Salvaging Garbage Audio

Not sure if anyone can help, but figured it was worth a try.
 
So, I recorded my portion of a podcast this morning using Sonar X2 Studio and an M-Audio Fast Track Pro interface. Was in a rush, so once I saw meters moving, I figured I was fine. Unfortunately, I think what happened is the default 16-bit, 44.1K recording setting in Sonar didn't match the default 24-bit 48K setting of the interface and I ended up with garbled audio that's only 11 minutes long instead of what should have been about 27 1/2 minutes.
 
Is there any way to fix this? FYI, I've tried to use a few utilities I found on the web--R8Brain for sample rate and bit rate conversion and Header Investigator for tweaking the file header info on what the settings should be, and nothing seems to help. I'm desperate to get this fixed because otherwise the whole podcast is shot.
 
Any thoughts or suggestions would be appreciated.
 
Bob O'Donnell

The audio is garbled in Sonar itself. I first noticed it when I imported into Logic Pro on a Mac where I normally record this podcast and do the editing. So I went back to Sonar thinking I had exported incorrectly or something like that, but unfortunately, the original track in Sonar sounded exactly the same.

It's a combination of distortion, running too fast (note that the recording was supposed to be about 27 1/2 minutes but the files shows it at 11) and digital noise. If there was a way to post an attachment, I could upload the first ten seconds and you could hear what I mean.
 
Bob
 

It would be quicker to re-record than try and undo the glitch.

Yes, it's former EM Editor...hi Bob!
 
You can post an example on hightail.com and give the download link here, the link is good for 7 days if you use the freebie version. But I suggest you upload a piece of the original file, not an MP3, just in case someone can figure out how to fix it.
 

Well, looks like I haven't posted enough in order to put up a URL (as I discovered when the link to my new company website didn't work). BTW, the company is TECHnalysis Research and you just put those two words together and add a dot com to get to the site.
 
As for the Hightail URL, not sure how I'm going to post that...got any ideas?

Ah, got it...thanks. Still trying to get Hightail app loaded, but will post link shortly.

The first thing I would do is update the drivers and firmware of your interface (if applicable) in order to try and prevent it from happening again

Thank you for the sample. The file downloaded as a 32-bit float/44.1Khz (contrary to the OP), yet is noticeably "asymmetrical" and has severe clipping (after the 3.5s mark). I opened this with Adobe Audition, and Audition was having a very difficult time processing this wave file (i.e. it was hanging to even play it), which makes me wonder if the file was corrupted in some way (it is very unclear on "how" though).
 
In the interest of time, it may be best to redo this, as well as do a brief run prior to the actual recording to make sure. I will often set up a track, record a bit as a test, then simply delete that test audio and record on the same track so that I know the setup is good. Based on the clipping in this file, I think it would be very difficult to recover it (if even possible). I have seen the asymmetrical post once before (from Beepster, I believe?) but totally forget the "root cause" of that.

I really appreciate you both checking out the file, thank you very much.
The outcome is, unfortunately, as I feared.
 
The weird thing is I did a clean install of Sonar X2a and the latest Fast Track Pro drivers on another notebook that I had recently wiped and put a clean install of Windows 7 on and using the default settings for everything, I ended up with the same type of garbled audio issue on that machine when I did a short recording test. In futzing around with things on the machine I originally had recorded this file on (which runs Windows 8.1) I did get things to work properly, so now I have to figure out what I did again.
Thanks again for the help and Craig, would be great to reconnect in more detail.
 
Bob O'Donnell