Erik Massop edited this page Nov 4, 2017 · 1 revision

Media Tags

After a discussing about how to tag media with more information, we concluded the best way is to implement it transparent on the client side for now.

For more details and different approaches, see test discussing page.

See also Generic properties policy.

media info fields with arrays

As clients normally don't need that information, it is enough to have a local style for managing the media. Clients only have to support editing the mlib info of a track.

If a client still wants to add a shortcut for certain fields or wants to show statistics about certain fields, here's an idea for a standard interface.

field multi description examples
mood yes chillout, aggressive
style yes addition to genre, you can have a Chinese sounding pop song) chinese, medival
speed no speed in words lame, slow, normal, fast, speeding
bpm no speed in bpm 120, 90
tag yes anyithing else foo, bar

Feel free to add/change things, as this table still is evolving.

Some fields can have more as one value. unless xmms2d supports arrays as values, a semicolon separated list is used.

collections with special names

It also would be possible to have a collection with the name 'mood:aggressive' inside a tag namespace, so songs can be inside more lists and it is more easy to combine media inside special tags.

One problem with this approach is, that you would have to be able to reference a collection by name, not by its contents. So that would involve a change inside the daemon.

Clone this wiki locally
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.