Bug: DAP disables keyboard volume events

[JoeRip]

Bug: once DAP has been run and then closed, the "Volume +" and "Volume -" buttons on a multimedia keyboard no longer work.

Repro Steps:

1. on a clean machine (no DAP), open Window's Volume Control Panel
2. on a multimedia keyboard, hit the Volume + and Volume - buttons
3. note that the system volume slider goes up and down
4. leave control panel open
5. install DAP, which leads to DAP running
6. hit the Volume + and Volume - buttons
7. note that DAP is stealing the events, so the DAP volume control moves, but the system system volume slider in the control panel does not change (arguably, bad behavior; iTunes and WMP do not steal this event, but let it go to the system volume control)
8. close DAP
9. hit the volume buttons again

Result: in control panel, system volume slider does not change
Expected Result: Volume Buttons should resume working with system volume after DAP closes

10. reboot, try control panel again; buttons work

Spoon, looks like you're hooking these events but not letting them go when you close DAP?

[donny]

Re: Bug: DAP disables keyboard volume events

try assigning the volume up and down to some other keys (ie + & -) in the "start->dbpoweramp->configuration->keyboard control" app. then I think it won't steal the events

[JoeRip]

Re: Bug: DAP disables keyboard volume events

At this point, I don't have anything configured in the Keyboard Control. Which suggests that what is happening *now* is this:

from the DAP ChangeLog:
"Added WM_APPCOMMAND which means those Play, Stop Pause buttons on your keyboard should work (Windows NT/2000/XP only)"

I'm guessing that this code is putting a hook in place to get those window messages, and is somehow not letting go at close.

Now, if configure the keyboard controls, I'll be *adding* key-catching to the process, but I won't be removing the window message hooks.

[JoeRip]

Re: Bug: DAP disables keyboard volume events

I see that this problem has been reported before. I am seeing exactly what cparsons saw in 2002, in this thread (http://forum.dbpoweramp.com/showthread.php?t=611), which was not resolved at the time.

You guys examined if any of your processes were left running that might be commandeering the events. However, I suspect you need to look at how you're registering to get the APPCOMMAND events, and see what you should be doing to release them when you exit.

[Spoon]

Re: Bug: DAP disables keyboard volume events

It is a known bug, to br addressed when dAP is next updated.