10-19-2018, 05:40 PM
Hi Tim,
I strongly recommend not to go the way having different versions of moodeaudio (i.e. one for poular and one for classical music).
Of course most of the classical collections are organized in different ways, due to a very individual way of search structure. It all starts when tagging and ripping the music, because in that early stage one has to decide what tags one is using for searching music or even browsing through her/his collection.
Additionally it's not a good advise to "mis"use a tag for other purposes. When I started ripping with dbpoweramp I filled the tag "artist" with work-numbers (e.g. opus-numbers etc.) - a total mess. Luckily dbpoweramp allows user-defined tags, so I created one called "opus".
I´ve learned now that there is a restriction by the tags mpd is supporting - unfortunately no user-defined tags, or opus/work etc. I assume we have to live with that for now.
What I´d love to see in the near future is a version of moodeaudio where it's possible to define the tags used for creating the library individually:
One of the main advantages of Linux is that it's a library-based OS, i.e. all definitions are stored in individual ASCII-files.
Just take a look at what spoon (the guy developing dbpoweramp) is doing with his upnp-server called asset upnp. There's a certain file where all the tags used for creating the library are listed (and defined), this file is user-accessible and can be modified. Additionally one can define whether the sort-tags or the "normal" tags are to be used for sorting the entries. Wouldn´t something similar be possible for moode as well?
Keeping a long story short: Taking the restrictions of mpd into account, adding the tag "composer" in the library creation of moode is a very good starting point (thanks for doing this instantly in the 4.3 version). If it's possible to individualise the selection and the order of the list tags - even better (e.g. one searches by genre -> artist -> album, another one by genre -> composer -> album). If then one could choose how the generated list is sorted (e.g. by sort tags or by normal tags) - much better. The perfect world for classical music libraries would go beyond the restrictions of mpd, but this is not the point here.
If you see a way I can support you kindly let me know, I´ll then get in touch with you by email or whatever you prefer.
Cheers, AnnaBlume
I strongly recommend not to go the way having different versions of moodeaudio (i.e. one for poular and one for classical music).
Of course most of the classical collections are organized in different ways, due to a very individual way of search structure. It all starts when tagging and ripping the music, because in that early stage one has to decide what tags one is using for searching music or even browsing through her/his collection.
Additionally it's not a good advise to "mis"use a tag for other purposes. When I started ripping with dbpoweramp I filled the tag "artist" with work-numbers (e.g. opus-numbers etc.) - a total mess. Luckily dbpoweramp allows user-defined tags, so I created one called "opus".
I´ve learned now that there is a restriction by the tags mpd is supporting - unfortunately no user-defined tags, or opus/work etc. I assume we have to live with that for now.
What I´d love to see in the near future is a version of moodeaudio where it's possible to define the tags used for creating the library individually:
One of the main advantages of Linux is that it's a library-based OS, i.e. all definitions are stored in individual ASCII-files.
Just take a look at what spoon (the guy developing dbpoweramp) is doing with his upnp-server called asset upnp. There's a certain file where all the tags used for creating the library are listed (and defined), this file is user-accessible and can be modified. Additionally one can define whether the sort-tags or the "normal" tags are to be used for sorting the entries. Wouldn´t something similar be possible for moode as well?
Keeping a long story short: Taking the restrictions of mpd into account, adding the tag "composer" in the library creation of moode is a very good starting point (thanks for doing this instantly in the 4.3 version). If it's possible to individualise the selection and the order of the list tags - even better (e.g. one searches by genre -> artist -> album, another one by genre -> composer -> album). If then one could choose how the generated list is sorted (e.g. by sort tags or by normal tags) - much better. The perfect world for classical music libraries would go beyond the restrictions of mpd, but this is not the point here.
If you see a way I can support you kindly let me know, I´ll then get in touch with you by email or whatever you prefer.
Cheers, AnnaBlume