i'm into reverse engineering a little bit, so i actually couldn't resist and took my time to figure it out how mp3s are transformed, right the next day i got my device I've got rh10 here, but i believe it's all the same for every unit out there. First of all, all the id3v1/id3v2 data is cut off, along with other stuff ( if there's any, don't really know mp3 format that much ) which is not related to the actual sound data. Then the most interesting part comes. The leftovers of a song are basically XORed with a 32-bit key which is constant for the very first song being transferred onto device, but for subsequent ones it does change and it somehow depends on the size of already transferred data. I couldn't find any obvious pattern of key changes, but most likely it could be unambiguously restored for every single song from its byte offset in the main storage file. ( cant get my hands on the device to tell exact file name now, sorry ). One could clear the situation by *cough* disassembling ss binaries, but you all know that you're breaking the law by doing that. So do i. Furthermore, i didn't want to waste my time cheers. i have to add that i did that mainly to make sure those mp3 playback drawbacks ( modified db/freq ratio ) were because of the hardware, not some sonicstage intrigues