[PROBLEM] Library update in progress message

[TheOldPresbyope]

How to find this damaged album?

I am not aware of a program which can scan for all possible music tracks, no matter their encoding and container (e.g., file type), verify their metadata, and report out all files which are problematic. If anyone else is, I'd like to hear about it.

I'm not a JavaScript expert but I believe the specific error you reported means either an album_artist tag or an artist tag in some file did not contain a string value.  The function .toLowerCase requires a string input, so it failed. I suppose a savvy JS coder could modify the routine to identify the file it was working from, but that person certainly isn't me.

Since you've now "cleaned" your library of extraneous files, you could try using the .mpdignore directive to narrow down the list of suspect files.

1. clear the MPD and related databases (I'm not sure what is the best way to do this.)

2. at the highest-level directory in your library collection, place a text file named .mpdignore. In it, place the text lines
 

Code:

*.dsd
*.wav

This means that MPD should scan your entire library for only .flac files. (I chose them first only because I like their tagging scheme best).

3. use the usual moOde webUI methods to update your library.

4. does this succeed in all the ways you expect? 
 - if  yes, then go to next step.
 - if not, you at least now know you have one or more FLAC files to fix. Go fix* them and then repeat.

5. repeat the above, but this time using a .mpdignore file containing

Code:

*.flac
*.wav

6. same as 3.

7. Same as 4. except now you know you have one or more .dsd files to fix.

8. Do it all again but this time with a .mpdignore file containing

Code:

*.dsd
*.flac

You can guess where this is heading. As an aside, I dislike WAV files the most because of their lack of prescriptive metadata tagging. People do all sorts of wild things to add metadata to them.

In summary, yes, this is tedious, but with a huge un-proctored collection of putative music files, you have to start somewhere.

Obviously, the same approach could be taken at a subdirectory level but not knowing your file organization (and I don't really want to!!!) I don't know what to suggest.

All this is just my 2 cents worth.

Good hunting.

Regards,
Kent

*''fix" means different things for different file types. I suppose you could turn programs like mp3tag, easytag, or kid3 loose on them but I prefer using FLAC-specific command-line tools when dealing with FLAC files, and so forth.