Kodi 18 - Music Library Development Roadmap - One Man's Plan

  Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Post Reply
tkgafs Offline
Senior Member
Posts: 115
Joined: May 2008
Reputation: 2
Post: #16
(2017-05-19 10:33)DaveBlake Wrote:  
(2017-05-15 10:38)tkgafs Wrote:  Dave, is the discussion here http://forum.kodi.tv/showthread.php?tid=305853 covering a way to get a playlist to display the artwork for a currently playing track via a switch or the like, likely to get included in your deliberations?
I'm still hoping someone else will pick this up, so it is lurking between "todo" and "this I don't have resources for". I won't tidy-up these posts until I decide which, but it will get on the list one way or other.

Dave thank you your efforts are appreciated
find quote
HeresJohnny Offline
Fan
Posts: 324
Joined: Mar 2011
Reputation: 2
Location: Germany
Post: #17
Thanks again for taking the mantle on this, Dave!

I have a bit of spare time now to test stuff as I also have detailed tagging for classical music.
However, I'd like to come forward with a request of my own as well, which would entail a change in KODI.

My usecase:
I come from foobar2000 which so far has been the gold standard of tagging for me. I have tagged some albums with musicbrainz, but not all.
foobar2000 uses the semi-colon ';' as delimiter for fields that accept multiple values.

My problem in KODI:
The advancedsetting-parameters <itemseparator> and <artistseparators> seem to be partly reduntant and conflicting.

Explanation:
KODI recognizes the foobar2000 delimiter as a comma ','. Consequently, I have defined

Code:
    <itemseparator>, </itemseparator>    <!--  separator used for multiple artists/genres in tags. Note, this is *comma* *space*  -->

This works fine for genres, which are appropriately split. I doesn't work that well for artists called "Earth, Wind & Fire" or "Crosby, Stills, Nash & Young". In the first example, KODI creates two artists, in the second example three artists. All of them have the complete discography for the correct group assigend, though.

This doesn't change if the musicbrainz ID are present, as <itemseparator> seems to take priority.

Now, my proposal would be to exempt artists from being treated through <itemseparator> and be exclusively treated through <artistsseparator>. This current treatment seems to be redundant. The latter filter allows me to define

Code:
    <artistseparators>
        <separator> and </separator>
        <separator> And </separator>
        <separator> feat. </separator>
        <separator> Feat. </separator>
        <separator> with </separator>
        <separator>; </separator>
        <separator> ft. </separator>
        <separator> Ft. </separator>
    </artistseparators>

and all should be well (as long as I change all group names that have 'and' to '&', like 'Martha and the Muffins' => 'Martha & the Muffins... no big deal and doesn't hurt scraping).
(This post was last modified: Yesterday 15:20 by HeresJohnny.)
find quote
Post Reply