I want to burn a CD with MediaMonkey right now, when I realize, the "CD label" edit control clears itself each second. Means, I start to enter a label for the CD, when it is automatically cleared one or two second(s) later.
What I did:
1. Select a bunch of songs
2. Click on "Send to->CD/DVD/BD (burn)"
3. Walk through the wizard, till the last page.
It doesn't matter, whether a song is playing or not.
Giving up here and using Nero again.
1383: CD-burning - can't edit label [#7932]
Moderator: Gurus
Re: 1383: CD-burning - can't edit label
I can't reproduce on 1384.
Download MediaMonkey ♪ License ♪ Knowledge Base ♪ MediaMonkey for Windows 2024 Help ♪ MediaMonkey for Android Help
Lowlander (MediaMonkey user since 2003)
Lowlander (MediaMonkey user since 2003)
Re: 1383: CD-burning - can't edit label
The problem still exists in Build 1384. It is 100% reproducable here.
I disable all scripts (renamed script folders) as I claimed one of them to trigger something in the background, but this did not solve the problem.
Therefore I started good old DebugView with the hope to find something. At least I got the following idea of what could cause the issue.
If no media is in drive, DebugView adds follwing entries to its log each second:
With an empty CD in drive the following entries are added each second:
At the same time, those entries are added to the log of debugview, the entered CD label disapears. Seems there is a background task active, wich intents to automatically update drive information and accidently clears the CD label edit control, too.
But why are the disk information queried each second? Is this intended? I think it would be enough to update disk information, if a CD/DVD/BD is mounted or ejected. Due to DriveChanged: entering I tend to say, there is some callback called too often?
I am not sure, whether it is helpful or not, but left next to the "< Back" button, there seems to be a progress bar. The text says: "Burning: 58.3MB (available 703.1MB / 703.1MB)" The progress bar shows about 5% of progress I estimate. The confusing is, I did not yet press "Burn!"
I disable all scripts (renamed script folders) as I claimed one of them to trigger something in the background, but this did not solve the problem.
Therefore I started good old DebugView with the hope to find something. At least I got the following idea of what could cause the issue.
If no media is in drive, DebugView adds follwing entries to its log each second:
Code: Select all
[3076] DriveChanged: entering
[3076] hpCDEBurn: Device refreshed
[3076] DriveChanged: UpdateDeviceMedia finished
[3076] hpCDEBurn: Device refreshed
[3076] hpCDEBurn: We are using the default list
[3076] hpCDEBurn: AddSpeed proc. - speed: 2770, multiplier: 1385.000000
[3076] DriveChanged: GetDeviceSpeeds finished
[3076] DriveChanged: Drive Info updated
[3076] Added speed to box: 4.0 x
[3076] DriveChanged: Disc info and speeds updated
Code: Select all
[3076] DriveChanged: entering
[3076] hpCDEBurn: Device refreshed
[3076] DriveChanged: UpdateDeviceMedia finished
[3076] hpCDEBurn: Device refreshed
[3076] hpCDEBurn: We are using a list of speed given by device
[3076] hpCDEBurn: AddSpeed proc. - speed: 5645, multiplier: 176.400000
[3076] hpCDEBurn: AddSpeed proc. - speed: 2822, multiplier: 176.400000
[3076] hpCDEBurn: AddSpeed proc. - speed: 7056, multiplier: 176.400000
[3076] DriveChanged: Status bar updating finished
[3076] Added speed to box: 40.0 x
[3076] Added speed to box: 24.0 x
[3076] Added speed to box: 8.0 x
But why are the disk information queried each second? Is this intended? I think it would be enough to update disk information, if a CD/DVD/BD is mounted or ejected. Due to DriveChanged: entering I tend to say, there is some callback called too often?
I am not sure, whether it is helpful or not, but left next to the "< Back" button, there seems to be a progress bar. The text says: "Burning: 58.3MB (available 703.1MB / 703.1MB)" The progress bar shows about 5% of progress I estimate. The confusing is, I did not yet press "Burn!"
Re: 1383: CD-burning - can't edit label [#7932]
Confirm! label no longer cleared in built 1385.