View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002072 | MMW v4 | Burning / Disc Handling | public | 2005-10-12 19:41 | 2007-04-12 08:43 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | feature | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Fixed in Version | 3.0 | ||||
| Summary | 0002072: Data Disc Burning: Verify Data functionality (fails for auto-conversion) | ||||
| Description | Because of the number of incorrectly burned CD/DVDs, it would be useful to have the possibility for MM to verify that the data burned to a CD accurately matches the source. Such functionality is already present in applications such as Nero. Proposed implementation: Action: __Burn__^ should just add several new options. Currently it has Burn, Test, Test & Burn. To this we should add: a) Burn & Verify data b) Test, Burn & Verify Data. Data should be verified on a per CD/DVD basis. If verification of the CD/DVD fails, then the user should be presented with: 'The data on the disc failed verification, which means that one or more tracks may not play correctly. Re-burn this disc? [Yes] [No]' For successful burns, no new functionality is required. | ||||
| Additional Information | Originally raised by Peke at 0002064 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1028 | ||||
|
|
Due to the number of support complaints about bad burns, and requests for this feature, I'm raising this to urgent. |
|
|
I added possibility of re-burn failed disc in build 962, because this is very useful in case of multiple burning when one of the burnt discs fails. In the other hand I don't believe that verify data functionality is such critical issue, I have never seen successfuly burned disc which doesn't match the original data, but true is that I am not sure. We can create image file to the HD beforehand and do a bit by bit comparison with data written to the disc, but this will take a time and HD space. Do it on the fly could be better, but there might be some implementation and technical problems. |
|
|
The true is that the best solution (and also the most easy) will be to check track by track from list of burned tracks by stream comparison immediately after successful burning. We can do it simply on-the-fly by reading streams of source path (on HDD) and destination path (on CD/DVD). |
|
|
Verify Data functionality has been implemented. Once burning is finished, the verification progress bar appears equipped by track paths and performing of byte by byte comparison is starting. If any track doesn't match the source or doesn't exist, the relevant report is showed up to user with prompt to Re-Burn disc. Cause we have not implemented any such functionality for audio burning I chose [x] Verify data on disc after burning checkbox to enable it. (similar like in Nero). |
|
|
Disc verification always fails when tracks on the destination have been auto-converted. Tested on 1023. |
|
|
Strange think, I can reproduce it "only" in 50% of cases and it shows me message that just burnt mp3 file on the CD does not exists although it exists. It looks like MM does not an access to the CD, but I do not know why the Auto-conversion affects this. |
|
|
I've re-tested it again and it does not seem to be a problem of auto-conversion at all. I've successfuly verified many tracks that had been auto-converted beforehand. And I also got the error for a track that had not been auto-converted. It depends only on successfuly refreshing of volume disc label. If the CD volume content is successfuly refreshed (mostly in case of a blank CD) then there is no problem with verification, but if the volume is not updated right then there is the verification problem. Nevertheless I see only one solution to ensure updating of the volume. To eject and close the drive before verification process. |
|
|
I have added the solution "To eject and to close the CD drive before verification process" in case that disc content is not updated after burning (i.e. MM does not have any access to the new file on the CD). Added in build 1028. |
