Many Albums ending up in [untagged] group

[feeling_zenjp]

Problem Description
I recently tried migrating from Asset to MinimServer and of the 700 or so albums on my NAS, MinimServer dumped about 100 of them into [untagged]. Previously, these all showed up in Asset under the correct Artist and Album.

Background
Knowing the MinimServer is a stickler for standards and consistency, I had a look at a couple albums from the same artist where one album appears in my control point, and the other appears with all the tracks dumped in [untagged]. Looking at the ID3 tags and paying attention to case, both the album that appear correctly and the one that does not contain "Album", "Artist", "Title", and "Track".

I tried deleting the tags and re-applying the tags manually via dbpoweramp but this had no effect.

Finally, to aid in troubelshooting, I cleared the MinimServer log, set it to trace level and set the scan directory to just the artist directory on the NAS containing the two albums for our sample comparison. Although there is a lot of verbose output, I do not specifically see any actual error messages or messages pertaining to missing tags.

Provided Logs
The trace level log of the rescan of just the two albums is attached. For Reference, the album that does appear in the library is "Phantom Limb". The album that does not is, "The Pines".

[simoncn]

From the log you attached, I see these files are WAV files. There are two ways to add tags to WAV files: ID3v2 and LIST/INFO. MinimServer supports ID3v2 but not LIST/INFO. Is it possible that the file whose tags cannot be read is using LIST/INFO tags instead of ID3v2?

If this is the reason for the problem, you should be able to convert LIST/INFO tags to ID3v2 tags using a tagging program such as dBpoweramp or Mp3tag.

Another possibility is that the files are tagged with ID3v1. This is not supported by MinimServer because it is an obsolete format that was superseded by ID3v2 over 20 years ago. You can convert ID3v1 to ID3v2 using a tagging program.

Unfortunately the trace log that you provided doesn't show tag data for the files being scanned because the tag data is being read from the MinimServer cache. To produce a trace log that shows scanning information, set the startupScan property to full and then do a rescan. This will produce a larger log file, so please zip this file before posting it to the forum.

[feeling_zenjp]

Thanks for the response.

My collection comprises of about 600 ripped CDs all with the metadata supplied using dbpoweramp ID3 batch converter. The rest are download purchases. In the case of the example provided, both the albums are download purchases. However, the ID3 tags were again supplied by dbpoweramp.

So in this case, the problem singles one out but not the other and the tags are both supplied by the same tool.

As requested, I set the StartupScan property to "full" and rescanned the library on trace level, using just the artist directory to reduce noise so the attached file contains a scan for one album that works and one album that remains classified as "untagged" after dumping and reloading the control point cache directly from Minimserver.

[simoncn]

Unfortunately this log shows the same as the previous log, with no tag information because the cache is being used when scanning the files.

I think a simpler way for me to understand what is causing this problem would be for you to upload to my FTP server one file from the album that works and one file from the album that doesn't work. Please don't upload more than one file from each album because the storage quota on my FTP server is limited.

I would like to send you a PM with details of how to upload these files but it appears you have disabled forum PMs. Please send me a PM with information about how I can contact you.

[feeling_zenjp]

I've now enabled PM.

FWIW, today I uninstalled MinimumServer and then deleted the "AppData\Roaming\MinimServer" directory that had the *.mcache files in it and reinstalled. The idea being that this should absolutely force a rebuild of the cache now that the tags were recreated again in dbpoweramp. However, the result was unchanged.

I can provide you as single sample file on request.

[simoncn]

Thanks for uploading these files. The file with the problem has tags in LIST/INFO format. The file without the problem has tags in both LIST/INFO and ID3v2 formats. You should be able to use dBpoweramp to add ID3v2 tags to the files that don't have them.

[feeling_zenjp]

Thanks for your help!

So what I've discovered is that if there are LIST/INFO only tags, dbpoweramp's ID3 tag editor and the batch conversion tool will continue updating LIST/INFO even if the option to overwrite existing tags is selected. In order to get it to add ID3, I had to use it to delete all metadata first, and then run the ID3 batch converter again and it seems to have added the same metadata but in the correct format.