View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000051 | MMW v4 | Other | public | 2003-02-07 04:20 | 2009-02-20 04:19 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Fixed in Version | 3.1 | ||||
| Summary | 0000051: Errors interrupt Caching/Normalization/Conversion/Synchronization Operations | ||||
| Description | Currently, when the user performs a variety of operations, if an error occurs partway through the operation, the operation is halted until the user interacts with the system in some manner. This results in situations such as: -User tries to do Volume Analysis overnight but finds that the operation halted after 500 tracks. -User tried to synch/auto-convert to iPod before going to the office, but finds that operation halted as he grabs the iPod. -etc. What should happen in these cases is that the user should be presented with an error message _at the end of the operation_ so that the problem in question does not interrupt the operation. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1198 | ||||
| parent of | 0000244 | closed | jiri | Return rip error messages once after CD has ripped |
| parent of | 0005060 | closed | Ludek | Error log form: [Save as Playlist] button should save regular MM playlist (not M3U as currently does) |
| related to | 0003562 | closed | Ludek | When automatically updating podcasts there should not be any error dialogs presented. |
| related to | 0004412 | closed | Ludek | Fixed failed rips should generate a single error message after rip operation |
| related to | 0003763 | closed | Ludek | Background volume analysis triggers errors for inaccessible tracks / CDs |
| related to | 0005585 | closed | Ludek | Podcast episode downloads may be incomplete (due to network interruption) |
| related to | 0005884 | closed | Ludek | Scanning errors should be logged |
| related to | 0006219 | closed | Ludek | Synchronization errors should be logged |
| related to | 0007774 | assigned | rusty | DLNA errors should be shown in log form |
|
|
Note: in testing normalization previously, all I did was select several tracks and verify that it works. Now I'm trying to normalize my entire collection, however, I'm finding it quite difficult to do so, because of: a) errors due to tracks that are unavailable b) errors due to decoding tracks The effect is that I can't just select my entire collection and expect SDB to normalize it overnight. It significantly hampers this functionality. I was thinking of 2 possible solutions: 1) Hack: don't provide error messages about individual songs--just indicate at the end of normalization that 'Volume Levels have been analyzed, however, several Tracks were inaccessible or could not be decoded, and consequently could not be analyzed. Sort your Tracks by the 'Leveling' column to see which ones haven't been analyzed. [Ok] 2) Hack2: Similar to above, but add a 'Unanalyzed Volume' node to 'Files to Edit', and change the last sentence in the above error message to 'Select the 'Unanalyzed Volume' node within 'Files to Edit' to view unanalyzed tracks. 3) Full fix: report unanalyzed tracks in a popup at the end. e.g. 'The following tracks could not be analyzed because they were inaccessible and/or could not be decoded: xx, yy, ....' Raising priority to high. |
|
|
Note: the same problem applies to file conversion (e.g. cannot decode xx.mp3 occurs after 40 of 140 tracks). |
|
|
Note: a possible means of solving this problem in a manner that doesn't require a log is to just indicate 'failed' in the normalization field. That way the user knows that the attempt was made, but it was unsuccessful. (a track that has 'fail'ed normalization should not be considered as having been analyzed for the purposes of the '[x] Analyze Volume only for Tracks with unknown leveling adjustment' option. i.e. if the user attempts to manually re-analyze these tracks, they should be considered as having unknown values and should be re-analyzed. |
|
|
Another user told me of a related problem--aside from the annoyance of being interrupted with errors, thereby preventing unattended operations for many functions, there's also a problem of lack of feedback when a problem does occur. e.g. if a CD is ripped in WMP, the user can easily see the status of the rip for any of the individual operations, and if one of the tracks isn't successfully ripped, an error is indicated for_that_track. Similarly, with MediaMonkey the user should be told which tracks have ripped successfully and which failed, or which tracks synched successfully and which failed, or which tracks leveled properly and which failed, etc... |
|
|
Since the implementation of similar issue in 0004412 seems to make sense, we should try to use the same for the issues described here. The actions for which it should be implemented are: 1. Calculaction of leveling coefficients. 2. Synchronization (particularly related to auto-conversions). 3. Copying to VCD (probably not that important). 4. Conversion (probably not that important either, users usually don't convert that many tracks. That said, it still might be useful) 5. Downloading of Podcasts (it happenned to me, that download of some 50 episodes was queued, but after just few of them, there occurred an error and the process was stopped until I clicked OK. Btw, also the error message should be better formatted in this case, what I got was something like 'Winet error 0012345'. Instead there should be something like 'Error while downloading "podcast - episode"' plus some error description, e.g. 'timeout', etc.). |
|
|
6. Volume leveling (if a track e.g. CDA audio track cannot be leveled) - 6) is already fixed in build 1190. See 0003763 for more details. |
|
|
Implemented issues 1,2,4,5,6. i.e. All except 3 (Copying to VCD) Rusty, review the wording, please. Added in build 1191. |
|
|
There was a problem analyzing volume the following Track(s): --> There was a problem analyzing volume for the following: For other error messages, please give me a list of all the strings so that i can more quickly get feedback to you on them. Thx. |
|
|
'There was a problem ripping the following Track(s):' 'There was a problem levelling volume the following Track(s):' 'There was a problem analyzing volume the following Track(s):' 'There was a problem converting the following Track(s):' 'There was a problem downloading the following file(s):' In all cases there is the default 10 seconds in which is shown the first error with indication 'Remaining time: 10 seconds' as was specified in 0004412. |
|
|
a) analyzing volume grammar correction -->There was a problem analyzing volume for the following Track(s): b) 'There was a problem levelling volume the following Track(s):' --> 'There was a problem levelling volume for the following Track(s):' c) 'There was a problem converting the following Track(s):' --> 'There was a problem converting the following file(s):' d) the 'Remaining time:' warning can be changed to: --> 'Operation will continue in:' OR 'Warning will disappear in:' (choose which is more appropriate--I don't recall if the implementation actually pauses the operation, or if it's just an indicator re. how long the dialog is shown). Note: Besides a couple of grammar corrections, I'm switching to the use of file(s) in some cases (instead of Track(s)) because the function may apply to video in the future. |
|
|
Fixed 1198. |
|
|
verified 1223 |
