View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004747 | MMW v4 | Burning / Disc Handling | public | 2008-06-03 15:51 | 2008-06-05 13:20 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.0 | ||||
| Fixed in Version | 3.0 | ||||
| Summary | 0004747: Burn with autoconversion fails without giving useful error message | ||||
| Description | Partway through the list of tracks, I get an error indicating that 'there was a problem with auto-conversion.' After much investigation, it turns out that the playlists that were being burned had a single DRMed track and that it could not be converted due to the DRM. This was needlessly frustrating though because: 1) There should be an error message indicating that a track couldn't be converted due to drm. 2) At the moment that the error message appears, the status bar should show which track is exhibiting the problem, but instead it shows either the track before or after. I'm posting a log to the server. Note that the DRMed track was Dr. Seuss Green Eggs and Ham.m4b. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1183 | ||||
|
|
Rusty, unfortunately I cannot reproduce and I don't see a reason for a regression in this area. Could you test whether it is related to a particular track? Which convert settings you use? From the log I see that the last track that had been converted was the "Come on lets Jump", but it could failed on another track. I have uploaded "MM.exe" file where I added some debug messages so that I could find out which track failed. Could you please re-generate the log by using the MM.exe attached on our FTP? |
|
|
I've clarified the bug's description. The problem was caused by a DRMed track and the fact that there's no feedback about what the problem is. |
|
|
Based on discussion with Jiri - in order to done it consistently with device synchronization: The convert error will not be reported for the DRM track, but just the original (not converted) file will be used and burnt. (same as in the case of device sync.) Fixed in build 1182. |
|
|
Based on further discussion with Jiri, only track which format is set as supported should be burnt so that this would be consistent with device sync behaviour. i.e. M4P is not set as supported by default therefore should be eliminated from list of tracks to burn. Fixed in build 1183. |
|
|
Tested build 1183, and M4B tracks are still burned even when there are explicitly not supported (i.e. MP3 is the only type of filetype that is configured as supported in the Burn auto-conversion dialog). |
|
|
Rusty, M4B are burned, but once they are auto-converted and the conversion fails (like for M4P) then they are not burned if they are not supported. But if they are converted successfuly or if the auto-conversion is disabled then they are burnt. This is intedned, isn't it? |
|
|
Verified 1183. When I initially tested this, I'd uninstalled MM beforehand and forgot that the auto-conversion feature was inactive. It's working fine. |
