View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0022382 | MMW 5 | Conversion/Leveling | public | 2026-10-01 16:55 | 2026-10-01 20:11 |
| Reporter | lowlander | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | sometimes |
| Status | resolved | Resolution | fixed | ||
| Platform | Windows | OS | - | OS Version | 11 |
| Product Version | 2027.0 | ||||
| Target Version | 2027.0 | Fixed in Version | 2027.0 | ||
| Summary | 0022382: Volume Analysis starts when tagging files | ||||
| Description | Randomly MediaMonkey will start volume analysis, while auto-analyze is disabled. It seems more common on larger sets of files. | ||||
| Steps To Reproduce | 1 Select ~ 500 files 2 Run setTempo --> Progress bar shows Volume Analysis (no file count shown) | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 3524 | ||||
|
|
It is by design - because of 0018003. If you have tracks with track volume, but without computed track peak value (usually after manual change of track volume in the past), the clipping prevention cannot work correctly, because it needs to have track peak value precomputed. This analysis only computes and adds this needed missing value. |
|
|
In that case the status should reflect that this is a different sort of volume analysis and also include x of y files). Users are going to want to know what MediaMonkey is doing to their files. |
|
|
OK, fixed in build 3524, used new string "Calculating missing track peak (file %d of %d)" |
