How about managing the entire Empeg database as an XML/XSL web-site?

Each track can have whatever the XML file describes it as: name of audio file, length, author, name of original CD or web site, prefered visual, prefered EQ setting, prefered volume. But more importantly, for different generes there are different fields of interest: group, composer, lead players, chorus, orchestra, name of classical piece and name of movement inside the piece, place of track in the playlist (info I miss about the classical pieces), name of album.

Attaching the right XSL to each XML file (giving the name of the XSL file as part of the data in the XML file) will allow the user to actually control which of all this info will be displayed and how (scrolling, flushing at beginning of track etc...).

Going even further, when MkII arives with Ethernet, it might be possible to edit the fields over HTTP.

(I admit not to know XML/XSL too deeply, but I hope what I describe here makes sense).


Unit 119, 6Gb, Blue