Hi, what happened to me today (2Beta3): Hava a playlist which I listen to since a few days. All was fine. This morning I was playing one song, went for shopping, came back, EMPEG starts up as normal but the song I was just plaing fine before now makes a crackling noise. With every bass hit it makes that crackling noise (dissortion I think you call it ??). Like the sound a complete overloaded amp does. The noise doesnt change with changing the volume on the player. It's alsways there. First I thought my install is f****, but when switching to radio all if fine. So I thought the EMPEG is broke for playing MP3. But then I switched to the next track and all was FINE. Switching back to the faulty track and the noise is back. So it looks like the this one track was somehow corrupted by the EMPEG. All other things do play absolutely normal. It's no big issue since I can just copy a good version of that track back to the EMPEG but I just wonder why that happens. I have to admit, I also have voladj kernel installed. Any suggestions what I should do ? Or just forget about it ? Or should I send the corrupted track somewhere ?

Thanks, Specki.

Greetings!

There was an experimental normalization utility that was not ready for release, but got out in this particular beta. It will be removed from the next release. If you wish to verify the MP3 file, download it (displayerserver, backup, whatever) and play the file locally.

The file was not damaged. If you downgrade your software to version 1.03, all will be well.

This is a known bug in 2.0 beta 3 and will be fixed by next release.

If you wish to verify the MP3 file, download it (displayerserver, backup, whatever) and play the file locally.

Moreover, if the file is then uploaded again (e.g. using 'replace tune' feature in emplode) it will play OK, since its dynamics metadata (peak volume etc) will be reinitialised.

Is there any way to remove that information? I would assume that it does not modify the file itself, but generates some metadata somewhere on the read/write scratch partition.

You are right. The info is on a small partition that doesn't get mounted and does not contain a conventional filesystem. See here. (The playlist Roger mentions as being nuked too is current playing order, not any of your permanent playlists. However, you do lose EQ presets you configured and such things...) Beware, however, that current 2.0b3 player does not like being started with an empty playlist. If, after nuking the dynamic metadata partition you find your player continously dying and restarting, downgrade to 1.03, start playing something, then re-apply 2.0b3.

I think it was Roger who kind of promised to document contens of the partition (in his copious spare time, I presume), so that we could nuke, and, more importantly, backup/restore, selectively.