There is a bug in VLC 1.1.0 QT4 interface that causes processed hotkey events to forwarded. So if volume up key from keyboard is pressed, VLC raises the volume, but it also sends same hotkey event forward and because of this Windows Mixer also raises volume.
Same applies to mute, so both VLC and Windows Mixers are muted. Right way would be that VLC eats all hotkey events it has processed and forwards only those, that it doesn't process.
Tested under Win32.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
0
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items
0
Link issues together to show that they're related.
Learn more.
Please, don't mark Priority Highest unless ticket is about critical security issue. That kind of ME ME ME ME ME attitude will easily put you to ignore list.
It's obviously not a super-critical issue, but it does cause problems every time we use VLC. Even if it only affects notebook users, thats hundreds of thousands of incidents every day where we try to adjust our volume, remember that it's broken, re-adjust VLC's volume back to something sensible, minimize VLC, adjust system volume, and maximize VLC again.
This is not a minor or low-priority issue.
More Detail:
When I try to adjust my (Dell 1720) laptop's system volume (I do this through the built-in volume buttons on my laptop) as I need to every time I watch anything, VLC "steals" the event and adjusts it's own internal "volume", which is undesired in almost all use cases. There is no option in any of the advanced settings of VLC to fix this. It used to work fine.
The worst case is if you mute inside VLC, both VLC and system mutes.
Then change to another player/browser and unmute. System unmutes.
Switch back to VLC. No sound !!! Press unmute. Still no sound !!!
Yes, you got it. Each time mute button is pressed, either system or VLC is muted.
Only way to get sound is to look at the tiny mute icon in VLC and see when it's no
longer muted. Then get out of VLC and unmute outside.
The annoying thing with volume is that VLC changes volume much faster than system
so by using volume up and down you always end up with VLC volume 200% and system
volume much to low. I don't know what happens to sound quality but I suspect it
will be affected by using 200%.
There should be an option to switch the use of hotkeys for Media Keyboard volume and mute buttons. Either only in VLC or only send it on to the system.
I'm very happy with VLC but this is so annoying I'm starting to use other players instead.
The problem is valid for all W32 systems using media keyboard buttons.
For me that is my HTPC, my stationary gaming PC, my notebook and my work laptop.
I second that this should be high priority & the fix released ASAP.
Like LTB mentioned, worst case is when the VLC mute & system mute are in alternating states, where the end result is no sound whatsoever from VLC. People who don't realize what's going on with the alternating mute states would think VLC is broken.
So it's a serious UI problem that affects a large percentage of users & pertains to a very common VLC function (mute). Do you call that normal priority?
To clarify the "right way" mentioned in the bug report, I think the fix should be for VLC not to process keyboard volume & mute events at all. The well-established standard is for keyboard audio controls to affect system-wide & not program-specific settings. When I hit the keyboard mute key, it's because I'm getting a call & I want everything muted, not just VLC.
I can confirm the problem, and like stated before it is not just annoying for notebook users. Any multimedia keyboard, or gaming keyboard for that matter (including my G110) results the same problems. About the priority:
The problem itself is not a security issue, nor does it crash computers. However I think users annoyance should be seriously taken into consideration. If many users get too annoyed so they will stop using this great piece of software, I don't think that will help improve it.
The problem doesn't bother me that much, for I choose to use version 1.0.5, the latest release in which this problem does not occur.