2015-03-03 19:08:31,529 - WARNING Error submitting played track to Last.fm: trackNumber is not a valid integer: None
or
2015-03-04 16:08:25,794 - WARNING Error submitting playing track to Last.fm: There was an internal error. Please retry your request.
Although, AFAICS (using MusicBrainz) all the tracks do have track numbers…
here is another intersting fact:
If you reproduce 2) and you then rename the album tags so that the many albums are displayed in a different order (i.e change the name of an album so that it is later or earlier alphabetically, which changes its rank in the list) then the albums that are displayed empy will still be the ones after the first one and not the one that you changed. This to me indicates that the problem does not relate to the actual albums, but to how they are displayed. For some reason you can see the same album normally, in the case that it is first in the list. However, the very same album will be displayed as empty if you artificially bump it down to second or third place…
Thanks, glad to hear that! Regarding the other issues (duplicate artists with/without albumartist tags, and the scrobbler error), I was not able to reproduce them so far, but I’ll keep trying…
the list of artist itself (in the .db-file) has the double entries. But it appears that every time that an artist is doubled it has one version with uri and name, and another with uri, name and, MB-id. So, I going to assume that when you tag files with MusicBrainzPicard, those albums that get an id from their database will be listed as different artist than those that don’t by sqlite-extension. This could also explain the scrrobler problem, perhaps it works using these MB-id’s. I don’t know if they are necesary though, because when the tag is missing and PiMusicBox cannot then display the album art, (using the same files) Rhythmbox, however, can. And AFAIK it uses last.fm also.
OK, that explains it to me. Actually, this is “by design”: Artists with the same name, but different MBIDs are considered separate entities. Names are not unique, and that’s why Musicbrainz assigns every individual artist/band its own ID. Mopidy-Local-SQLite therefore uses the MBID if available to identify an individual artist.
Now, “None” or NULL counts as a separate MBID of its own, which is not ideal, but I haven’t figured out how to deal with that otherwise, yet. The handling of multiple artists with the same name is also a little confusing, since only the name is returned, so you can’t tell which is which. So there’s room for improvement and I’m open to suggestions, but I generally consider this a “feature” and not a bug
