Audacity Forum

I'm not sure why it matters, but I used this one:
http://www.chmaas.handshake.de/delphi/f ... /xvi32.htm
It's free for Windows machines.

But any freeware HEX editor should do the trick.

If they're all "13"s, then there's no music structure either. Wouldn't that be like giving the church a clear coat with Gym Finish®?

Since 13 is considered "unlucky" (whatever that means), I'd prefer to think it would be more like applying heavy wax to all the stairs.

I'd bet that would make the services more exciting.

After all, you can't make an omelette without killing a few people.

Turns out OS-X supports od and hexdump.

I get lines of "03" 243 thousand times. Not 13.

03 is ETX, End Of Text. 13 in hex is, what, DC3, Device Control? Am I trying to over analyze a completely destroyed file?

Koz

I have been transferring the mp3s between two Windows XP PCs that use NTFS using a usb stick which has FATS. I don't know if this is what is causing the problem. But the mp3s are fine on the PC where they were created.

I have also tried using copy instead of drag 'n' drop onto the stick, only moving one at a time, shutting down Audacity before moving the files, but nothing seems to work. But it may well be that it is the usb stick that is the problem.

It's pretty safe that this isn't a slightly damaged file from having traveled through a USB Stick. Two different people on two different computers have taken the file apart at the byte structure level and confirmed that it's just not a sound file. Never was. There is something magic in the music creation process that is very broken.

I don't remember if I addressed this or not, but if this is all happening on a PC, what is the status of the virus protection? Could somebody else be inside your computer with you "helping you out?" When was the last time you scanned the machine thoroughly?

Koz

The PC I'm using with Audacity to create the mp3s is not connected to the internet. I virus-scanned it anyway and nothing came up. The mp3s are fine on that PC. I now add the bitrate as a column in the folder where I save them, and if it says '128' I know I'm ok.

When I copied them onto the usb stick the bitrate showed zero. I have now successfully transferred them using another usb stick.

<<<I have now successfully transferred them using another usb stick.>>>

Then you win, but it's still extraordinarily hard to believe a bad USB stick created that kind of damage.

Koz