View Issue Details

IDProjectCategoryView StatusLast Update
0013444MMW 5Generalpublic2022-09-14 14:39
Reporterrusty Assigned To 
PriorityurgentSeveritytweakReproducibilityalways
Status assignedResolutionopen 
Target Version5.2 
Summary0013444: Facilitate leveled playback so that it occurs automatically
DescriptionA couple of changes should be made re. automatic volume analysis so that it occurs pretty much automatically with little user intervention:

1) As proposed in 0013411, automatic volume analysis should be enabled by default for audio files, but the performance setting should be modified so that only a single CPU is used (low priority) in the background so that it doesn't interfere with the UI.

2) As proposed in #13440, automatic volume leveling settings should appear in the Library options (immediately above 'Remove unused attributes...') so that users can see it via the startup wizard. I'm not sure if it's possible, but it could make sense for the setting to be duplicated in 'Volume Settings'. On the other hand, if it's enabled by default as proposed at 1) perhaps this isn't really required.
TagsNo tags attached.
Fixed in build

Relationships

related to 0013411 feedbackrusty Replay Gain: Add option to Calculate Replay Gain on RIP 
related to 0017779 closedLudek Unanalyzed volume node tweaks / improved approach to Album Volume 
related to 0017754 closedmichal Hide "Analyze Waveform" menu item / Automatic waveform generation often fails 

Activities

peke

2016-08-03 23:01

developer   ~0045310

1a) Volume analyze can be easily performed during Track playback if Track doesn't already contain it.

jiri

2016-08-04 13:38

administrator   ~0045313

Last edited: 2016-10-24 14:51

Decreasing priority in order to be resolved after the first MM5 pre-release.

rusty

2021-05-19 18:12

administrator   ~0063288

I think that 1) should be implemented only after 0017779 is fixed (i.e. automated volume leveling should work properly for albums from the beginning).

jiri

2021-05-20 07:49

administrator   ~0063313

I agree with 2), but I'm not that sure 1) should be done. I'd rather leave it as opt-in, since I suppose that many users wouldn't like MM to automatically go through all their collections, update tags, etc.

Deferring for 5.1.