jEmplode's getting close ...

All the compile errors are gone and I've successfully downloaded the database, made some modifications, and synced them back ... So the big stuff is out of the way. Things still left to do:

1) add a UI to the background sync queue (something similar to RMML)
2) add tag writing back in (either port Rio's or use TFF for now ... we'll see)
3) clean up UI weirdnesses (like missing i18n entries, etc)
4) testing testing testing

Thank you thank you thank you for all the time you put into this!

Hey Mike... Thanks for doing this! I can do so much with the soups: very excellent.

If I could make 1 request as your're wrapping up the next version. It would be nice to autosort a new soup by a specified tag. Specifically, I create a soup by ARTIST then ALBUM, and another for new music (using CTIME>"xxxxx"), then ARTIST, then ALBUM.

However, the individual songs always come up sorted by title alphabetically within the soup. I've overcome this problem by going to Emplode which now has a feature to recursively sort an entire playlist by a certain tag (i.e. tracknumber).

This way I can end up with multiple soups that have albums, each in the proper sequence.

Thanks again for all the hard work!
-Ted

#1 jEmplode request ... I worked most of the API I need for this in while I was doing Karma stuff, so hopefully it shouldn't be too much harder to finish it up in jEmplode

As a side note, one kind of cool thing that got inherited from the Karma is that soup playlists inherit tags from their children. So for instance, if you have an album soup, it will inherit the artist, year, etc of the first entry that goes into it. So all the tags will be filled out on the playlist.

ms

Nice. I'm not sure if ive sugested it outright or not, but have you thought about implementing a "single/not in album" tag? Then we could have album soup views and let out single tracks not create album entires. I suppose I could tag all my single tracks to be from some dummy album, but I don't want to. An other option would be a threshold to delete playlists in a structure if they don't contain x number of entires, but that's not as exact.

I'm looking forward to seeing the next jemplode with all the improvements.

Matthew

I might be able to do the "single" album ... Right now, I don't think soups ever mix tunes and playlists together, so I'm sure it will initially break things. The threshold one is kind of tricky, because once i delete the playlist that, say, only contained 3 (and your threshold was 4), then if you retag and cause a 4th to be created, the soup wouldn't know that there used to be 3 there, and that now the 4th causes it to qualify without a full rescan ...

Checking into a problem with uploading animations, but other than that, everything is looking really good so far. Barring the unforseen, I should have jEmplode 46 (I think it's 46 now) out by the end of the weekend.

ms