. In Audacity the file appears as a 1.5 sec clip and when I play it, it sounds like the entire hour long meeting in a second.
Get xvi32 (free binary editor) and open the file in it, maybe stretch the window a bit to show more data, then send us a screenshot so we can see the bytes at the beginning of the file. To get the screenshot in Windows Vista and up, look in the Start Menu for the Snipping Tool, under Accessories (and drag it to your taskbar, as it comes in quite handy). It will let you click-drag a box over what you want to copy, then give you the option to save as a PNG. Upload the PNG to ImageShack or any other image sharing service and link to it here with the "Insert Image" button (looks like shapes in a picture frame).
xvi32 couldn't open the original? Now that is weird. It doesn't care what the format is. It should open anything. Was something locking the file?What you did open does not look like MPEG audio to me. Every 288 bytes, the same structure repeats: 00 E3 48 C4 00 (rest varies).Is this what the whole file looks like?
... Yeah it looks like it does repeat...This may be the product of running the broken mp3 through the repair software, maybe not the original.
I may not have file upload privileges yet. Or, I simply can't find that option. How would I go about that on this forum?
Does WMP support MPEG 2.5? Does Foobar2000?
Okay, I was able to upload a sample file from the same time of recording.Uploaded FileThank you for taking a look.
Aha... same strange headers. I wonder if you're supposed to use a utility supplied with the pen to convert these to standard MP3 files?Some of the adverts imply that it makes 128K bitrate MP3 files, You still haven't answered the question - have you previously been able to listen to files recorded by this pen?If so, it implies that it has become defective.Update: I "fixed" the headers. VLC tries to play it, but it's pretty garbled. There are 2 possibilities:1. You're supposed to use a utility supplied with the pen to convert these to standard MP3 format. 2. The pen is broken and not correctly writing the files.
Turns out the first byte in each frame header varies. It's not always FF. So I opened it in xvi32 and replaced the sequence "__ E3 48 C4 00" with "FF E3 48 C4 00". I posted the result in [a href='index.php?showtopic=98790']the same upload thread[/a].I did not get you saying "testing, testing" ... instead, I got music ... some rap about "I'll take the girl in the front"
Still, I think your pen is broken