View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002215 | MMW v4 | Conversion/Leveling | public | 2005-12-05 03:49 | 2005-12-06 06:02 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0002215: DRM-related conversion errors result in support calls/refund requests | ||||
| Description | When users convert DRM-protected tracks to other formats (either manually or using the synchronization auto-conversion facilities) and the conversion fails, they receive a message along the lines of 'Cannot decode file xxxx'. The net effect is that they think that MM is buggy and doesn't perform as advertised (this week alone I've received 3 e-mails on the subject). Consequently, I think we need to add a string along the lines of 'Cannot convert file(s) due to DRM restrictions: xxxx.wma, yyyyy.wma... [OK]' Setting as 'Immediate' because we need to get the string in. | ||||
| Additional Information | Originally raised in 0001355 (item 5) | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 921 | ||||
|
|
Fixed in build 921. - Due to plug-in structure it's currently problematic to show a debug message corresponding exactly to the error occured. For that reason I'd propose a message: 'File %s cannot be decoded. It is possibly due to DRM restrictions.' Let me know if you want to change the wording. |
|
|
Verified 921. |
