0000384: medialib should store and pass complete metadata to clients

Relationship Graph

Viewing Issue Simple Details
ID	Category	Severity	Reproducibility	Date Submitted	Last Update
0000384	medialib	feature	always	05-09-29 05:11	07-09-26 00:32

Reporter	koniu	View Status	public
Assigned To
Priority	normal	Resolution	open
Status	confirmed

Summary	0000384: medialib should store and pass complete metadata to clients
Description	In my struggle to make xmms2 The Ultimate Music Player(tm) I came across one annoying thing - only a limited amount of metadata (some very basic tags and backend info) is passed by the daemon to the client. Clients should have access to full metadata that is found in the carrier. If there's a DISKNUMBER or COMMENT vorbiscomment, let the client use it! Technically, to avoid potential conflicts (eg. user having "ID" tag in their oggs), those non-standard tags could be passed as a separate structure within medialib info structure. In case of Python bindings, I'd love to see it as a dictionary to allow something like: res = xmmsclient.XMMS.medialib_get_info() res.wait() info = res.value() print "COMMENT: %s" % info["metadata"]["comment"] Obviously this would imply mlib having to store all that metadata but I guess it wouldn't be such a scalability disaster, would it? In the worst case, there could be an additional config key to define metadata/tags to be stored in mlib along with those default ones. Btw, I considered this kind of limitation one of the major drawbacks of mpd.
Additional Information