Fixed in build 5.1.0.2802+ Please retest when it gets available for public.

Hi,
Better late then ever. It should be fixed as soon as MM 5.1 gets out to public.

If you feel anything to add feel free and I'll relay into bug.

Glad I could help then.

TBH, I have been a gold member since 2008 and I was using MM for some years before that, so it has taken me nearly 20 years to report it. I noticed and was mildly irritated by the effect probably 6-7 years ago, but it has taken me until now to really try to get to the bottom of it. So maybe others have picked it up and been just as lazy as me.

Hi,
100% true, strange is that no one noticed before you for past 20 Years

Added as https://www.ventismedia.com/mantis/view.php?id=19928

Yeah. Classic corner case.

Hi,
Sample track is pure silence

GOOD CATCH!

OK. Let's do something about the swamp.

I've uploaded the debug log and some screenshots and a file that reliably causes the issue.

Ticket #5710

--miw

You can attach it to a Support Ticket: https://www.mediamonkey.com/support

I'm up to my ass in other alligators at the moment. Maybe next week I'll be able to drain the swamp.

In the meantime I have restored a file from backup that reliably causes the problem. I can submit that?

--miw

Hi,
It would be great if you can capture that in debug log and supply compressed in support ticket.along with one +64db Volume adjustment.

See viewtopic.php?f=30&t=86643

Yep. That works too.

So far, all of the albums I have found in the class "Get repeatedly re-analysed but do not trigger a file sync" have been .flac files. I think there might be some that are not .flac, but that is certainly the great majority.

I have investigated 2 of the albums in the class "Get Repeatedly re-analysed and *do* trigger a file sync, and both albums had a track in them that was silence. This seems to cause an error in the background scan. If you do a force volume analyse, then the track has a volume adjustment of +64dB and also will not play in Mediamonkey. I deleted those tracks from the database. Problem solved as far as I am concerned. People who like to listen to whole albums may not like this solution.

You could try Tools > Edit tags > Update tags on those files and see if the volume values get written to the files.

Hmm. I have looked into the class of albums "Get repeatedly re-analysed but don't trigger a file sync (i.e. are not changed according to the OS.) I looked at the album, and it had volume data. But then I re-scanned the directory and the values disappeared - i.e. the values seem to have been written to the database but not the tag. Since I monitor all files on startup, no doubt that detects no volume data in the tags and triggers a volume analysis, which once again fixes the database but not the tags. Rinse and repeat.

I forced volume analysis on about half the albums and verified that tags were written. Caused a massive file sync operation.

I will watch to see if the number of files that gets re-analysed halves next time and post back here.

So, they have both Track Volume and Album Volume values know, but get re-analyzed. Do all files on the Album (right click Find more from same > Album) have these values calculated?

Yes - they do have album volume information visible in the details tab or "properties".