Autotagging fails for albums with fewer than 3 tracks

[TIV73]

Hi,
I'm using a custom autotagger to tag tracks, and starting with revision 2659 albums with fewer than 3 tracks are unable to be tagged. It's not that there is an exception or something, the lookup simply fails without calling any of the tagger functions.

Is there anything that changed in terms of tagging?

Update:
I had a quick look at the changes in the latest build and I think I found the culprit. searchCommon.js now says

Code: Select all

if (lst.count > 2 /* use album detection for albums with at least 3 tracks */ ) {

in line 744. If I read that correctly, any album with less than 3 tracks is now considered not to be an album and needs to go through tagging via fingerprinting. Which is bit of a problem for me, because the tagger I'm using is for https://vgmdb.net/, which doesn't allow API lookups for individual tracks (or fingerprinting), so all lookups have to go through albums.

Besides, this seems kind of an odd limitation. Just going through the newly released albums on https://vgmdb.net/ I found 4 albums with fewer than 3 tracks released in the last 3 days. What about singles with just one track?

Is there some way to configure this limitation or bypass it? Right now my tagger is unusable for 2-song albums.

[Barry4679]

Besides, this seems kind of an odd limitation. Just going through the newly released albums on https://vgmdb.net/ I found 4 albums with fewer than 3 tracks released in the last 3 days. What about singles with just one track?s.

Agreed. my MM5 database has 37 albums which naturally have 2 or less tracks. See here.

[PetrCBR]

Will make it configurable for next build.

[EDIT]

Added new tagger variable with default value of 1

Code: Select all

if (lst.count >= _this.albumTracksLimit)

[TIV73]

Amazing, appreciate it. Thanks a lot!