What is an “Album” to LMS? Albums split into two

[d6jg]

I don’t think that’s at all relevant but ask mherger
I think those errors come from some minor bug in LMS that’s nothing to do with your issue and actually has zero affect on functionality

[mherger]

Looked at this morning's scan log (it autoscans every morning) and found a series of warnings. I've copied them plus a preceding and following line of code:

[23-02-01 08:13:58.2474] Slim::Utils::Scanner::Local::updateTracks (537) Rescanning changed audio files (229)
[23-02-01 08:13:58.2520] Carp::Clan::__ANON__ (216) Warning: DBIx::Class::ResultSet::single(): Query returned more than one row. SQL that returns multiple rows is DEPRECATED for ->find and ->single at /Slim/Schema/Track.pm line 557
​

...in the FWIW dept.

This usually is caused by files which have an artist name which is identical to the "Various Artists" string used by LMS (see Settings/My Music). If you change the track's artist to the actual artist name and flag it as a compilation, the messages should go away.

[eCo]

An update. I'm running 8.3.1 now. I corrected a setting per Michael's post and the warnings have disappeared. Changing that setting forced a rescan, and all the split albums (that I could recall) disappeared. The double album-artist also disappeared. I've still got a bit of retagging ahead. If the albums continue to split, I'll let y'all know.

[eCo]

I've retagged a few dozen more albums now, and I'm seeing the same phenomena as before my above mentioned update & full rescan. The issue seems to occur when I retag an album without chaning it's name or path. It appears there's an issue updating, but not replacing, an existing album. It's not a huge deal for me because I can fix everything with a full rescan when I'm through retagging.

For the record, I'm seeing 3 separate errors:
1) split album where one version has only 1 or 2 tracks.
2) an album artist field becomes appended, not replaced by, a revised entry - like this: "[the original album artist]; [new album artist]"
3) an album becomes duplicated entirely. with all metadata appearing the same.

If someone wants to pursue the problem, just let me know. I've still got a coupla weeks or more of retagging at my current rate.

I'm not seeing warning errors in the scan log any longer, so big thanks to Michael for that!

[d6jg]

I've retagged a few dozen more albums now, and I'm seeing the same phenomena as before my above mentioned update & full rescan. The issue seems to occur when I retag an album without chaning it's name or path. It appears there's an issue updating, but not replacing, an existing album. It's not a huge deal for me because I can fix everything with a full rescan when I'm through retagging.

For the record, I'm seeing 3 separate errors:
1) split album where one version has only 1 or 2 tracks.
2) an album artist field becomes appended, not replaced by, a revised entry - like this: "[the original album artist]; [new album artist]"
3) an album becomes duplicated entirely. with all metadata appearing the same.

If someone wants to pursue the problem, just let me know. I've still got a coupla weeks or more of retagging at my current rate.

I'm not seeing warning errors in the scan log any longer, so big thanks to Michael for that!

What are you using to do the re-tagging?

[eCo]

What are you using to do the re-tagging?

Musicbrainz Picard

[d6jg]

Musicbrainz Picard

Have you tried mp3tag and set it to not alter the file date/time stamp. Doing this will stop LMS from seeing any change on a normal scan. I think that tracks will still play ok as long as the file name is unaltered but you would see no change in LMS.

Only when you do a clear & rescan would LMS rewrite its database.

[eCo]

Have you tried mp3tag and set it to not alter the file date/time stamp.

Thanks for the idea, but I'm tethered to Picard now with hours of use and personal scripts. It'll be much easier doing a final rescan than learning a new app.