Hi Bitt,

Basically it comes down to this. I already have copies of all the MP3s locally - they're what jEmplode pushes to the empeg for each song. What I want is to simply take the state of a player - all its songs, playlists, and wendy filters - and save it to a file. Then I'd like to be able to apply that set of data to a new empeg, or to my same empeg after upgrading it.

Another way to think about it. Let's say you start with a fresh empty empeg. You start jEmplode and begin dragging a whole bunch of files into it, and you define a bunch of filters. At that point, jEmplode has all the data and the empeg has nothing (yet). I just want to be able to save that state out of jEmplode, so if I were to sync to another empeg (or my freshly upgraded empeg), I don't have to tell it all of the same things again. Transferring all the fids back to the PC only to transfer them back to the empeg is doing twice the work that's needed, since I already have everything locally. Plus, I don't know if copying the fids will copy things like wendy filters too.

It's like exporting your browser bookmarks before you upgrade your operating system so you can reload them. I just want to restore the state of what jEmplode wants to push back onto the empeg.

If jEmplode had an import/export capability, that would be perfect! I'd export the list of crap that's on my old unit, upgrade it, run jEmplode and connect to the new unit, load that file, and hit Synchronize.

- Chris