Bug 90828

Version:            (using KDE Devel)
Installed from:    Compiled sources
OS:                Linux

User-defined meta information
Most casual music listeners don't have a lot of demands when it comes to information about what they are listening to. Most of the time, the name of the track, lead artist, and album name is all that is required. But there are those of us out there that really care a lot about all the details. We love to get obsessive over all these little tidbits of information, such as the names of each musician in the group, who originally wrote the tune, exactly when and where the recording was made (the FULL date, not just the year), make & model of the instruments used in the recording, whether or not this is an original recording or a “digitally remastered” re-issue, which record label released the recording, etc.

The ultimate Amarok would give us “power users” a way to store all of this valuable information about the music on a per-track basis. The per-track basis is especially important because a lot of these details change from track to track on the same album. It is common for a lot of jazz recordings to feature completely different side-men on each track of the same album. It is also common to see different recording dates for each track, not to mention some of the tracks being recorded at a live show, while others are recorded in a studio.

Because each of us have different levels of obsessiveness when it comes to storing this additional information, and because a lot of this info is not always available, the ultimate Amarok would need a flexible, but organized way for the collector to store as much info as they would like. Possibly in a structure similar to a hash table (think Windows Registry). The Ogg-Vorbis format seems to allow an arbitrary amount of this kind of information to be stored inside the file: http://www.xiph.org/ogg/vorbis/doc/v-comment.html

I'm thinking of giving the user a settings panel to define their own fields for tagging the file. This way I would be able to define a tag such as "Recording Label" and be able to search by that tag when creating playlists.

All of this meta-info should also be searchable. This would allow me to specify extremely powerful searches on my collection, such as “show me every tune where Elvin Jones is on drums”, or “how many tracks do I have of Wynton Marsalis playing a song written by Thelonious Monk?”.  The sky is the limit here, and would make for some very interesting playlists! This search functionality could even be extended to provide for regular expression matching for the ultimate in power searches! Just imagine being able to filter out all of the music that you have in your collection, but are not particularly fond of  (random play everything in my collection where artists does NOT equal “Yanni”).

While a simple, arbitrary hash table with user-defined keys would go a long way, I could imagine the need for a three dimensional array type of structure when it comes to listing who is playing what, such as Instrument - > Piano -> Chick Corea, or possibly adding a fourth dimension for model of instrument as well. Being able to easily define  these multidimensional relationships as well as search by them is where the real power is unlocked.