View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0015066 | MMW v4 | Burning / Disc Handling | public | 2018-08-30 15:27 | 2018-10-03 22:04 |
| Reporter | peke | Assigned To | |||
| Priority | high | Severity | major | Reproducibility | unable to reproduce |
| Status | feedback | Resolution | open | ||
| Target Version | 4.1.23 | ||||
| Summary | 0015066: Burning: MMW do not BURN CDs correctly | ||||
| Description | According to user MMW do not Burn CDs correctly. I'm not being able to replicate, but looks like problem is that user wants to burn CDs at lower speeds and using steps below to archive that. So burn ends in incorrect CD. | ||||
| Steps To Reproduce | 1. Select Tracks from My computer Tree node 2. Use Send to -> BURN 3. Starts burning and MMW prompts to insert a CD 4. User insert a CD and burn fail in terms incorrect Audio is burned to CD Use do that as if firstly insert a CD on speeds > 16x are available and he wants to burn CDs at lower 1x/2x speeds which he say iTunes allow. Note: Confirmed that if inserts CD prior to init burn CD Burns successfully. | ||||
| Additional Information | TEM-227-55266 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Peke , in the ticket TEM-227-55266 there is no info (except that you had a remote session with the user). So my understanding is that you cannot replicate the issue and that the user was satisfied by using a workaround to insert the CD prior to init of burn (and/or setting another burn speed), right? |
|
|
I've pushed it to 4.1.23 as based on my tests overall burning is not working correctly on Windows 10 (for me started as of build 1803). So based on my findings looks like if app is not started as Administrator and lock out exclusive access to drive it is almost impossible to be sure that CD will be burned. My tests show that at some point of burning process Windows Kernel kill access to drive and interrupts Device Burn buffer making all data to drive stop which in result make that drive (device in Device Manager) simply disappear, while it is still available in Windows explorer. Where if you try to issue any command like Eject end up in freezing whole Windows. I've tested it in number of apps and behavior is the same, only app that was more resilient was Astroburn that fail less than others but still fail. Using Windows XP/7/8.x PE boot disks do not observe such issue and burn CD/DVD/BR normally. |
|
|
@Ludek Main problem with user is that he wants to Force Burn at lower speeds even Drive do not report those speeds available and risk that CD burning fail (Mostly). Eg. I was proposing that we add INI flag to list all know CD burn Speeds (1x/2x included) and let MMW try to burn at those speeds. Only real world application I can think of is that some older hardware (Car Head Units) doi not recognize CDs burned at higher speeds. |
