v19 Scanning bug
#1
I had a tagging (APE) error.  I had a single ARTIST artist1 but for MUSICBRAINZ_ARTISTID I had 2 mbids in the format "mbid1, mbid2" and there was also an ARTISTSORT in the format "artist1sort; artist2sort".  After scanning I got an artist with strArtist set to the mbid2, strMusicbrainzArtistID set to mbid2, and strSortName set to artist2sort.  So it added the second artist's sortname and mbid, but also used the mbid as the (missing) artist name.

scott s.
.
maintainer of skin  Aeon MQ5 mods for post-Gotham Kodi releases:
Matrix see: Aeon MQ5 Mod Martix release thread
Leia see: Aeon MQ5 Mod Leia release thread
Reply
#2
Not sure I would call that a bug @scott967 , more Kodi doing its best to handle a tagging error gracefully. With mbid showing as artist name at least it was obvious to you there was some problem.
Reply
#3
(2020-09-30, 10:08)DaveBlake Wrote: Not sure I would call that a bug @scott967 , more Kodi doing its best to handle a tagging error gracefully. With mbid showing as artist name at least it was obvious to you there was some problem.

I take your point, as it was fairly easy to see there was a database issue, though
I'm not sure how a typical user would trouble shoot that.  I guess if "prefer online information" was selected it would retrieve the artist name?

My personal problem was the script I run for pulling MusicBrainz data gets the sortname, but I don't usually review that after it gets entered into the tags.

scott s.
.
maintainer of skin  Aeon MQ5 mods for post-Gotham Kodi releases:
Matrix see: Aeon MQ5 Mod Martix release thread
Leia see: Aeon MQ5 Mod Leia release thread
Reply



Logout Mark Read Team Forum Stats Members Help
Scanning bug0
This forum uses Lukasz Tkacz MyBB addons.