I just synchronized with JEmplode and all my files are gone! All i did was import one song and then clicked sync. Now there is nothing. It also says no free space which doesn't make any sense. Please hep!!

Nevermind, I just synched with Emplode and it fixed it somewhat. Im never using Jemplode again.

Hi.

Never heard of such a problem with jemplode, in fact, I know of more unfixed bugs in emplode than in jemplode, and many people on this board are using jemplode regularly.
What exactly did you do in jemplode? Was there anything special about the file you added? Like special characters in the id3 tags, or special (i.e. images or lyrics) id3v2 tags?

cu,
sven

Even more importantly, did you use the latest JAR file for Jemplode? Perhaps you were running an old version that had a bug?

All I did was add a song, i.e. dj quik - trouble. Then I did a sync and it started going crazy. Previously I had added 5 songs from radiohead that weren't tagged yet. After I synced, all my playlists were gone and when i searched for a song a found it , it would restart the player and sat rebuilding database. After I synched it with emplode for some reason it found my playlists and worked fine. I don't understand. Must be one of those days.

Sounds like an error occured during the JEmplode sync, and the databases had not been rebuilt. This got fixed on your next sync using Emplode.

Rerunning JEmplode-sync might have cured it as well. Or not.

For the record, it's conceivable that the same error might have happened with Emplode. For instance, maybe the player is having disk trouble, or it had that known Beta-11 bug where it didn't reboot after a synch, and the database got temporarily messed up.

This might not be necessarily Jemplode's fault, but the first thing is to check what version of Jemplode he's running (my initial question was never answered).

My b Tony, I was using the latest version of Jemplode from the site. It is.. 2.0.11-36. Do you think my HD is screwed at all?

Don't know. Could have been anything, including something silly like an odd ID3 tag on a file that confused Jemplode's tagging engine. In any case, you've already discovered that Jemplode didn't really delete all your files, you just needed to rebuild the database.