Documentation for the LMS scan process?

> Is there any documentation for the LMS scan process showing how it uses
> tags in music files and/or m3u playlists when it is building or
> rebuilding its music access menus?

Not really, no.

> The reason I ask is that I'm using the Asunder CD ripper to populate my
> LMS music library with tracks from CDs I own. Asunder evidently uses a
> crowd-sourced database to deduce the artist(s), CD and track titles.
> This works well, but it isn't consistent, e.g. the entries for most
> J.J.Cale CDs identify him as "J.J. Cale" but "Shades" uses
> "Cale, J.J". It returns tracks named "nn Artist Album track.flac" in a
> directory named "Artist Album" and puts a playlist called "Artist
> Album.flac.m3u" in the directory along with the tracks.

That's the "ARTISTSORT" tag being set to a different value.

> This messes up the lists displayed by LMS. I'd much prefer it to use
> the same scheme as I'm using to file the music.

LMS uses tags first, only if that fails it would try to guess
information from the folder and file names. You better get your tags
cleaned up.

--

Michael