Posts: 2,838
Joined: Dec 2006
Reputation:
2
This all appears so complicated to me. When "overwrite tag" is disabled, there is clearly a bug as spelled out in the opening post and supported by screen shots. There is a clear use case of people not wantint to enable "overwrite tag" with the simplest being that they have spent a lot of time tagging and now no longer want to scrape additional information.
Any idea why this is clear cannot be resolved and what it is hard to get consensus that this is even a bug?
Server: Asus Sabertooth Z77 | Intel Core i5 3.4 GHz | 16 GB DDR3 | 128 GB SSD, 82 TB (9 x 6 TB, 7 x 4 TB)
HTPC 1: Raspberry Pi 2 | HTPC 2: Raspberry Pi 2 | HTPC 3: Raspberry Pi
Posts: 2,838
Joined: Dec 2006
Reputation:
2
Thanks, fully under stood what you are saying and makes sense. Let me share my thoughts.
1) As a first step, I would suggest just to remove scanning the MBID. "Basic" users just want to see the perfomers for a slong to be listed as credited on the release, including qualfifiers such as "featured". A "basic" user will not mind having the artists listed separately when searching the artist view. This is the as feature-rich as ITunes and basically all other music clients are, so this should be the basic feature of Kodi as well. Everything beyond is "just" icing on the cake. So ideally, the first step would be just reach this status by solving the "bug" caused by the "MBID" (in other words, disable scanning the MBID until a solution is found).
2) For the advcanced users (like myself), we are also excited to have the full advanced features that you are describing above. They want the artist displayed as credited on the release, but be able to see the individual artists in artist view. For these users, MBZ/Picard have introduced a new tag "artists" and also provides the "MBID". Using the "MBID" still requires to download additional information, which is against the logic of Kodi being able to just use "local information". That's where the need to support the "artists" tag (and potentially albumartists tag) comes from. It appears to be the only way to only use local information to reach the desired advanced functionality. This feature in any case should be "optional". I will be using it, but the majority of users will be happy just to have the "Itunes-functionality" described in (1).
What do you think?
Server: Asus Sabertooth Z77 | Intel Core i5 3.4 GHz | 16 GB DDR3 | 128 GB SSD, 82 TB (9 x 6 TB, 7 x 4 TB)
HTPC 1: Raspberry Pi 2 | HTPC 2: Raspberry Pi 2 | HTPC 3: Raspberry Pi
Posts: 6
Joined: Dec 2013
Reputation:
0
Same here......... Please fix it!
Posts: 248
Joined: Dec 2012
Reputation:
7
Rouzax
Senior Member
Posts: 248
Nope, nothing new on the ticket.
Posts: 5,485
Joined: Jul 2012
Reputation:
385
It works, though this is a special case where albumartist=Various Artists. In this example there is a single Artist tag and two MB Artist IDs. The scraper used the MBIDs to retrieve data from MB (ResolveIDToUrl). With "override tags" off, Kodi entered the song artist in MyMusic db as "artist / artist" (entered twice with separator). Two artists were added, "artist" with the first MBID, and the same "artist" with the second MBID.
Note that if you remove the MBArtistIDs from the tags, the scraper instead parses the artist tag (CreateArtistSearchUrl). Using that, plus "override tags" on, you get pretty close to the right results (except no artist entry for the Feat. artist Years & Years).
scott s.
.
Posts: 2,838
Joined: Dec 2006
Reputation:
2
Any progress? Anything I can do?
Server: Asus Sabertooth Z77 | Intel Core i5 3.4 GHz | 16 GB DDR3 | 128 GB SSD, 82 TB (9 x 6 TB, 7 x 4 TB)
HTPC 1: Raspberry Pi 2 | HTPC 2: Raspberry Pi 2 | HTPC 3: Raspberry Pi
