View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003689 | MMW v4 | Conversion/Leveling | public | 2007-10-01 09:34 | 2007-10-14 11:50 |
| Reporter | Ludek | Assigned To | |||
| Priority | immediate | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.0 | ||||
| Fixed in Version | 3.0 | ||||
| Summary | 0003689: When auto-analyzing tracks volume there is missing [Yes to all] button when a tracks are read only. | ||||
| Description | When auto-analyzing tracks in your library and there are some tracks that are read-only a dialog apperas with suggestion to remove read-only state for the track, but this dialog appear for each such track and this is very anoying that there is missing a [Yes to all] button. The button is presented if you analyze a group of selected tracks so it should work the same way in case of auto-analyzing too. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1085 | ||||
|
|
Strange, I've just re-tested this again and the [Yes to all] button is presented. |
|
|
I probably see what's going on, but instead of fixing I wonder whether we shouldn't modify the functionality somehow. Auto-analyzing is a background operation and so it shouldn't pop-up any dialogs. It probably should either: 1. Automatically tag even read-only files. 2. Automatically ignore read-only files and save analyzed coefficients to DB only. (This one seems to be preferable, later (for 3.1?) this problem would be saved to some log, so that user would be notified about this situation somehow). Assigning Rusty to review. |
|
|
I agree with the 2nd approach, though a failed analysis should just be shown using '!' in the track or album volume leveling column. If the user sees a '!' they can then attempt to manually analyse the track(s). |
|
|
Showing '!' would mean that the analyzed value wouldn't be stored in DB, i.e. the file couldn't play leveled. I'd prefer to normally show analyzed value, the only problem is that tags won't be properly synchronized - which can user easily fix by Tag Synchronization feature. |
|
|
OK, sounds reasonable. note (related issue): in cases where MM fails to analyze a track (e.g. it can't be decoded), MM should similarly move on to the next track silently. This may already be the case...not sure... |
|
|
Fixed in build 1085. |
|
|
Verified 1088. |
