Another 3rd party player

Not a finished product yet, but after some evenings of coding I've got the following framework :

Server side :
- middleware software based on openldap server.
- multiple backends possible. Support for multiple empeg carplayers as MP3-source is functioning.
- internet streaming
- refrences to other LDAP-servers ( share music with friends/neighbours )
- Access Control based on LDAP authentication.
- Unlimited number of tunes/playlists possible

Player side :
- Hierarchical menu structure, as seen on the empeg carplayer.
- LDAP-queries can be used to generate dynamic playlists
- Uses existing font files, including all icons

As I said before, it is not functional at the moment. Everything is into place except for the actual decoding and playing of tunes.
Here's a simple schema explaining the intended behaviour :
http://fvgestel.dyndns.org/receiver/ldaprec/ldapreceiver.htm

The current 3rd party players are quite nice, but they still are very restrictive in selecting music. when using 300 playlists it's a pain to scroll through all entries to get the desired entry.

Got to go now. Will post update later

Cool. I hadn't thought of using an LDAP server for consolidating query results from multiple servers.

There's a major rework of jrec coming which will offer similar capabilities, but instead using a peer-based JXTA architecture. The merging of distributed query results is done in the RDBMS and made available to client players automagically through dynamic cursors.

--Reed

Awesome frank.. I guess I get to undo my flattening of playlist structures:)
-mark

I've captured some screendump as animated gif to drool over...
Still no decoding backend. It looks rather tricky to get a stable decoding backend. I think I'll try to extend the simple example of the libmad distr...

Send it up; let us play with it.. (..well, with the empty menus:) )
-m