I have had two tracks become apparently corrupted since installing 2.00b3

The tracks have just turned to white noise, and have to be reloaded.

Has anyone else had anything like this happen?

This has been discussed several times: the tracks are not actually corrupted, but prototype normalizer (and compressor?) that got into release by mistake sometimes incorectly determines tune's peak volume and overamplifies it into clipping. Reloading the tune erases its dynamic metadata, removing the effect.

To verify that, you can do one of two things: one is to retrieve the (supposedly corrupted) tune from the player and upload it again. It should sound OK (which means that the file itself was not corrupted). Another is to erase all dynamic metadata (see here and here).

That said, I did notice 2.0b3 decoder complain about bad file format of tunes that previously played OK, or insert a short blip of noise at the end (or perhaps beginning) of some tunes.

Chances are the track is undamaged. The other things in the other reply will work, too, but the easiest thing is to downgrade to 1.03, make sure the track is undamaged, and wait for the next beta release.

I had thought of the normaliser bug, but the track just degenerates to a sort of static hiss, so I thought it might be something different.

I'll try the developer image later this evening and nuke the settings to see if that helps.

The downgrade will be my last resort, I don't think I could live without 2.0 now I've seen it

Thanks