On 2008/11/09 23:53, encoded <[EMAIL PROTECTED]> wrote: > It is unfortunate that Rattlesnake needs it's own database, but I > highly doubt that a patch would get accepted into MPD to track such > data.
Hi Eric, why don't you ask me? ;-) Having some sort of modifiable "sticker database" for song files could be a good idea, which could store all sorts of additional and volatile information about songs. This is hard to get right. But it is possible. If you have an idea how to implement it, let's talk about your design. And of course, let's talk about code. Something different came to my mind lately when I reviewed your shout/mp3 code - we should move the encoder API out of the output/ directory, into src/encoder, and make it a regular MPD core infrastructure, just like outputs and decoders. Other future MPD extensions might find that useful, too. If you have some time, please give it a try. Max ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Musicpd-dev-team mailing list Musicpd-dev-team@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
