View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003038 | MMW v4 | Properties/Auto-Tools | public | 2007-05-09 11:25 | 2007-09-12 05:17 |
| Reporter | jiri | Assigned To | |||
| Priority | immediate | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.0 | ||||
| Fixed in Version | 3.0 | ||||
| Summary | 0003038: Auto-Leveling calculation improvements | ||||
| Description | 1) We should disable Auto-leveling calculation by default, because it otherwise means that simple scanning of Library causes changes in tags, which is something users complain about. 2) Before trying to calculate leveling for an album, MM should re-scan tracks of the album to make sure that it isn't already calculated and only missing in MM database. The following scenario is possible otherwise: - User has already both track and album leveling calculated for all tracks and stored in tags. - After upgrade from MM 2.5 to MM 3.0 a new DB field Album Gain is created, but it's empty, since DB wasn't rescanned yet. - Auto-Leveling Calculation things that tracks aren't calculated yet (since values aren't in DB yet) and calculates the whole collection again, even though it's already calculated. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1070 | ||||
|
|
Done. Will be in 1070. |
|
|
Seems to work fine, but I noticed one thing that I'm not sure about: For an Album with tracks: 1,2,3,4,5,6,7,8 If Album Gain analysis is disabled and the user 'Analyzes volume' for tracks: 1,2,3,4 And then Album Gain analysis is enabled and the user 'Analyzes volume' for all tracks --> All tracks are re-analyzed! --> Shouldn't MM just analyze tracks 5,6,7,8 and then calculate Album Gain for all tracks based on all 8 values that it 'knows' ? |
|
|
No, this is correct. Album Gain can't be calculated just from Track Gain (at least not exactly) and so all tracks must be recalculated. |
