View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003367 | MMW v4 | Burning / Disc Handling | public | 2007-08-07 23:57 | 2007-08-24 18:42 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.0 | ||||
| Fixed in Version | 3.0 | ||||
| Summary | 0003367: Error trying to burn CD on some systems | ||||
| Description | As reported at: http://www.mediamonkey.com/forum/viewtopic.php?t=19394 Some users consistently get an error trying to burn a CD. This appears to be an hpcde problem, however, before forwarding it to them, please review the new logs posted to the ftp server to make certain that the issue isn't within MM. Setting as 'immediate' because if it is an HPCDE problem, I want to forward this to them right away, along with any feedback you may have for them. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1059 | ||||
|
|
From the debug logs: The user burnt an audio CD with [x] On the fly audio burning the problem came at 58 % of burning process with error code 199680 after an unsuccesfull writing (!pDevice->WriteLockBuffer(...)) The hpcde should know what this error code (199680) means. Note: the user (Danny) wrote: Using Sony CD-RW CRX220E1, 52/24/52 2.4 Ghz P4, XP Pro 1 GB Ram Note2: We could send him a hpcde sample app (attached on our FTP) so that we can be sure that it is not our problem. In case the sample app works he could also try to burn an audio CD by using MM without [x] On the fly audio burning. Note3: The freezing of audio burning (with On-The-Fly buffer) was fixed in A7 (so that Danny needn't to reboot computer after such unsuccesfull burning), but this not solve the writing problem. |
|
|
User confirmed that disabling 'on the fly' burning solves the problem. He's unable to test with the test app, as it yields the following error: “This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.” Can you rebuild the test app? |
|
|
Primo's feedback: Hi Russell The error code means Generic Write Error. There are a lot of reasons for this including hardware and software. One thing that you may want to try is to supply 26 or 32 blocks of data to WriteUnlockBuffer instead of 40. We will also check for a possible bug in PrimoBurner internal buffer handling. Do you get this error on other devices as well? We need to know whether it is related to particular device or it is pure software problem. Thank you PrimoBurner SDK Support http://www.primoburner.com |
|
|
According to Primo I changed the burning code so that writing is performed per 32 blocks instead of 40 blocks that could solve this problem. Also the Jiri's changes which he done for 0002930 could fix this problem, because this problem seems to be related to audio burning with using on-the-fly buffering. Needs to be tested! Fixed in build 1059. |
|
|
Verified that no regressions were introduced. |
