[2822] MM Analyze Volume, scans more than selected amount

[robojock]

As Peke mentioned this happens when you have When analyzing Track volume, also analyze Album volume enabled under Tools > Options > Volume leveling. Disable the option and this won't happen.

Both MM 5.0.4.2693 and 5.1.0.2822 have that setting enabled by default. It works correctly in 5.0.4.2693 and NOT in 5.1.0.2822. and FYI that setting is for when analyzing an album with all its tracks. Not for random individual tracks as in my case located in playlist.

[Peke]

Not for random individual tracks as in my case located in playlist.

If track you select for Analyze have Album Info MM auto start analyze fo all tracks on album. Additionally if you enable Auto Analyze on unanalyzed tracks then MM starts analyze on all unanalyzed tracks.

Same goes for 5.0.4 and 5.1.

[robojock]

Not for random individual tracks as in my case located in playlist.

If track you select for Analyze have Album Info MM auto start analyze fo all tracks on album. Additionally if you enable Auto Analyze on unanalyzed tracks then MM starts analyze on all unanalyzed tracks.

Same goes for 5.0.4 and 5.1.

No I DO NOT agree with you. Since mm implemented volume analyzing in mm3 (maybe before that) if individual tracks tracks were selected it will ONLY do track analysis. If you select an album and analyze the songs then it will do tracks analysis + album. This is the Default behavior with most music apps that do volume analyzing. I am not going to install every single beta version from 5.0.4 to 5.1 just to prove a point. NEVER has mm analyzed additional songs when being selected in a playlist. Then i might as well just enable auto analyze and let mm be a resource hog while its running. It is a bug introduced in beta builds!

Volume analysis works correct in 5.0.4 as proven here
https://i.postimg.cc/brCCRXyb/Untitled-3.png
and with the same playlist volume analysis does not work here in 5.1
https://i.postimg.cc/GtZVvwh2/Untitled-2.png

[rusty]

Hi robojock,

You're right that the behavior has changed and is confusing, but the old 5.0.4 behavior was also problematic.

To explain, the old behavior was buggy because if Album gain is set to be calculated for 1 of 10 tracks on an album, then all the tracks on the album must be analyzed in order to get a correct Album Gain value (or a null Album gain value).

Without looking into the code, it appears that the fix to that issue was implemented but without the associated UI! We're looking into the best solution. Details at:
https://www.ventismedia.com/mantis/view.php?id=17779

Thanks!

-Rusty

[robojock]

Hi Rusty,

Ok i understand now, but all these years i liked how mm did the volume analysis of just selected tracks and if i wanted to analyze a whole album i would do it manually by selecting all those tracks. It is the same principle with most popular audio apps out there. I don't want to select 6000 tracks for volume analysis and to find out mm is going to scan 60000+ plus songs because of all the unanalyzed albums. How many hours/days will that take? I want to be in control of what files and how many files are analyzed.

Look at the options in foobar2000


and this is musicbee

[Rob_S]

Would it be too hard to have MM pop up a dialog if it intends to analyze anything more than the actual selection, allowing the user to opt out?

Settings choices could remain as is, the above would be a failsafe for occasions such as mentioned in the above post.

[rusty]

We could add a new dialog, but I prefer not to add extra steps unless it's really necessary/valuable for most users.

Since it seems that the current 5.0.4 behavior is well understood, maybe we should allow for that behavior unless the new option below is enabled. e.g.:

[x] Only analyze files with unknown Leveling Adjustment
[ ] Automatically analyze volume of unanalyzed files
[x] When analyzing Track volume, also analyze Album volume
. . [x] Analyze all tracks on the album

If the last option is disabled, then the question is what should happen in case the user selects a subset of the album. Possible options:
a) Generate an incorrect Album leveling value
b) Leave the Album leveling value empty
c) 5s Toast message e.g. 'Some of the selected files are subsets of an album. Include all tracks (for accuracy)? [[Yes]] [No]' (might not be possible in the short term).

Thoughts?

-Rusty

[robojock]

AFAIK most apps that i have used which use volume analysis, do by default only tracks analysis. Track analysis is useful as it makes all tracks the same volume. I do not know how they handle album volume is it blank and only calculated when the whole album is selected. Foobar has the option to scan "selection" as an album or scan album by tags. I like that approach. For me it is convenient do the scanning in little batches, where i would select what i wanted scanned.

The original problem that started this all was Unanalyzed volume node. Why not have a trigger from there to scan tracks and complete albums? Instead of the other nodes.