OK, and just to clarify things so I don't keep pecking away at the details.
I'm designing a zone based music navigation system that is similar to other devices I use (my Phatnoise Phatbox, in particular). This is going to be an interface between MC and Russound RNet products (yes, I know about the CAV6.6 project - not what I really want).
I want to be able to switch between major modes (Artist, Artist/Album, Genre, Playlist). I want to be able to quickly scan within these modes. This will include first-letter alphabetical scanning (A, B, C, etc.) as well as skipping by artist, artist/album, genre, playlist. This is going to be my primary interface to my collection of 10,000+ audio files, so solid navigation is critical.
Just as an added kicker, I'm going to try to add voice navigation (text-to-speech feedback messages), but that's just gravy.
I've got the basics - I can play, skip individual songs, display messages, etc. However, the playlist navigation features exposed by the API seem to be, sorry to say, rudimentary. Given the navigation capabilities of the base software, there appears to be a lot of functionality that isn't exposed yet.
The major issues right now are the inability to figure out which playlist/scheme the zone is currently using, and the need to navigate through the playlists on a strict file-by-file basis.
Please note, this is just constructive criticism - obviously the API is a work in progress. I'm just hoping that there is some more progress to expose the capabilities of the base system, cause otherwise I'm stuck rewriting a lot of what it already does. That would turn MC into not much more than a music database with multiple zone playback (from my app's perspective). At that point, I could almost do just as well with multiple instances of WinAmp.
Also, please be aware that I never touched MC until last weekend, and might be missing a LOT about it - I'm very aware of my own ignorance. But that also means I have no "brand loyalty" and am generally going to call it as I see it.