View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002561 | MMW v4 | Burning / Disc Handling | public | 2006-07-21 04:56 | 2006-08-04 15:12 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | closed | Resolution | duplicate | ||
| Summary | 0002561: Nero ImageDrive causes CD Playback/Burning problems with MediaMonkey | ||||
| Description | When Nero ImageDrive is enabled, MediaMonkey behaves 'strangely': 1.DVD Burner locks up 2.MediaMonkey is very slow to view/play tracks on the CD 3.MediaMonkey doesn't close properly (akrip dll doesn't 'let go') I don't know if this is an ImageDrive problem or a MediaMonkey problem, or a hardware problem. I'm attaching one log in which MM appears to freeze because it is 'stuck' while reading tracks from the CD. Setting as 'immediate' in case this is relevant to the burning issues with the current release, though we can push it since there's a workaround. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
I've installed Nero 6.6 which include Nero Image Drive. I have enabled Nero Image Drive and burning in 2.5.4 seems to work all right. |
|
|
Assigning to Rusty to upload the missing debug log and possibly test on another machine or find some more steps to reproduce. |
|
|
Sorry about that--I've posted the debug log. |
|
|
I haven't seen _any_ problem with Nero Image Drive, all burning seems to work ok. |
|
|
Perhaps my assessment of the root of the problem was incorrect. Do you see anything on the debug log that would explain why MM appears to be unresponsive while it is trying to read the tracks from the CD? |
|
|
The log doesn't show anything useful. I numbered the issues: 1. Could be the problem some users reported with hpcde 1.98 (burning wizards shows only after several minutes)? 2. It it audio or data CD, any differences? I suppose it's ImageDrive emulated CD, right? 3. What exactly happens, any log of this? |
|
|
It seems that this issue was actually a duplicate of 2553. |
