Am Tuesday 28 September 2010 schrieb Max Kellermann:
> It could also be integrated into MPD itself, e.g. with stickers. I
> implemented stickers last year after it had been requested over and
> over.
Not by me ;-)
(i don't think stickers have "such" high value over the tags present
anyway...)
On the other hand, covers are a rather "natural" feature of every MP GUI and
used by most or even all present MPD GUI clients.
Since client side solutions does not only double lots of codes (and remain
inferior, since that specific cover source you'd like to use is not
"autosupported" by your preferred client) but also lead to database
fragmentation and lock-ins, ie. you generated a pretty nice cover accomplished
database but if you're on (or switch to) another box/mobile/webclient/better
OS that's (maybe) all gone - not to mention that a local cover database raises
problems for "low on storage" clients ("mpc stats" -> Albums: 977 -> 238MB
@250kb each, and it's not halfwise complete so far ;-)
Therefore i'd prefer a server side solution - it shouldn't be "too hard"
either, since the cover fetching stuff just begs for scripting support.
-> have a "coverscripts" directory and let ppl. use perl or bash scripts or
whatever to fetch cover urls (stdout) from WP, Amazon etc., pass them to the
client and have it ask for acceptance... "or so" ;-)
Cheers,
Thomas
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Musicpd-dev-team mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
