i didn't thoroughly read what he was trying to do, but for reference, jEmplode stores a tag attribute at the top level only that tells the system that the playlist is a soup playlist (soup="search:refs=0", for instance). When you sync with jEmplode, it looks at the soup definition and looks for anything that is 1) missing from the def and adds it and 2) shouldn't be there (doesn't match anymore) and removes it. So if you put other things into the soups that weren't there before, they should be automatically removed by jEmplode. However, you sort of can copy subsections of the soups to other places (with the caveat that when that section becomes completely empty <i.e. you remove all the artists with a given name>, it will be discarded by the soup and not kept up to date -- so if you added a new artist with that name after clearing all the others out, it would make a new playlist for the artist).

ms