> Naturally I plan to do some tag editing to get key tags consistent,
> following which I'll have LMS rescan my library, hopefully without
> having to drop all tables beforehand which would necessitate
> reimportation of artist images etc. which has already been done. If I
> simply updated the relevant file tags and issued a rescan would
> persistent metadata survive or be lost?
What persistent data are you thinking of? LMS only collects very little
data it tries to persist, such as play count, or last played timestamp.
The connection between that database (persist.db) and the main database
is either the track's Musicbrainz ID, or the path/filename.
So... as long as you have a Musicbrainz ID, you can rename and move the
file as you want. Persistent data _should_ survive. If that's not the
case, then LMS might create a new recored for a moved (eg. different
artist or album folder) or renamed (eg. different track title in the
file name) track.
That said with a bit of SQL-Fu and eg. SQLiteStudio you should be able
to consolidate numbers after such an action. persist.db is pretty simple.
Artist images are handled by a 3rd party plugin, I assume. If you use
MAI and store them all in one folder, then yes, the artist name would be
used to find those images. But you can also drop them as eg. artist.jpg
in the artist's folder. In that case the metadata doesn't really matter.
> following which I'll have LMS rescan my library, hopefully without
> having to drop all tables beforehand which would necessitate
> reimportation of artist images etc. which has already been done. If I
> simply updated the relevant file tags and issued a rescan would
> persistent metadata survive or be lost?
What persistent data are you thinking of? LMS only collects very little
data it tries to persist, such as play count, or last played timestamp.
The connection between that database (persist.db) and the main database
is either the track's Musicbrainz ID, or the path/filename.
So... as long as you have a Musicbrainz ID, you can rename and move the
file as you want. Persistent data _should_ survive. If that's not the
case, then LMS might create a new recored for a moved (eg. different
artist or album folder) or renamed (eg. different track title in the
file name) track.
That said with a bit of SQL-Fu and eg. SQLiteStudio you should be able
to consolidate numbers after such an action. persist.db is pretty simple.
Artist images are handled by a 3rd party plugin, I assume. If you use
MAI and store them all in one folder, then yes, the artist name would be
used to find those images. But you can also drop them as eg. artist.jpg
in the artist's folder. In that case the metadata doesn't really matter.