View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000097 | MMW v4 | Conversion/Leveling | public | 2003-02-13 16:08 | 2007-01-26 23:31 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | feature | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Summary | 0000097: Library Automation: Analyze Volume automatically | ||||
| Description | Per a discussion in bug #77, automated Normalization was thought to be a useful feature as it would negate the need for the user to manually look for unnormalized songs and normalize them. There are two possible approaches: 1) During playback, this feature would simply check if a song had a normalization co-efficient, and would calculate one. 2) When CPU utilization is low, MM would simply analyze volume for unanalyzed tracks in the background (low priority thread). Also discussed, was the fact that this would be a nice feature for the Gold version, as it fits nicely with all the automation features of the File Monitor. Fron a configuration perspective this could just be added to the 'Volume Leveling' panel in the 'Volume Analysis' box (or the 'General' box defined in bug 0001132): [x] Automatically analyze volume of unanalyzed Tracks Note: for both of these approaches, errors in volume analysis should not be reported via the UI, but rather should appear within the Leveling adjustment field as an error (e.g. just show '!'. | ||||
| Additional Information | Related to #510 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Updated this feature description based on how the Volume leveling functionality has evolved. |
|
|
Technical details: - If the feature is enabled, MM checks if there are any unleveled tracks (i.e. leveling <100dB) tracks on a) MM startup b) After new tracks are added to DB (e.g. on the end of Tracks scanning thread, Conversion thread, etc.) - The scanning is started as an Idle priority thread. - Never are all unleveled tracks read in memory, always only one album is retrieved from DB and scanned (so that not much memory is occupied and also so that whole album leveling coefficients can be calculated) - In case decoding of track fails and so leveling can't be calculated, not error message is shown, an invalid positive value (+999999dB ?) is be written to DB so that MM UI can show '!' in leveling fields and so indicate that track wasn't successfully leveled. This is not only for this auto-leveling feature, but should work when leveling is calculated in any way. - User can terminate the function either in Options by unchecking the checkbox, or when 0002583 is implemented in status bar. |
|
|
solved |
