New
#1
Volume controls on K800 Keyboard do not work with Headphones
Morning,
Bit of a weird one here...within the last week - I installed a fresh copy of Win 7 x64 SP1 on a new office workstation. I am using the Logitech K800 keyboard and J.River Media Center for media playback.
NOTE: I am using the Gigabyte EP45-UD3R motherboard and it's onboard Realtek Azalia HD audio chip. I am NOT using the Realtek drivers (more on that in a moment) - I am using the built in Windows 7 HD Audio drivers.
Long story short - I discovered some conflicts with the internals of the motherboard where the front panel headphone jack of my case (Antec P182) would exhibit static in the phones if moving the mouse on screen. Traced that to some weird issue with the USB ports so I had to install a separate front panel insert into the case and attached JUST the audio cable so I could get static free headphone listening.
Now the issue. When using J.River Media Center (and WASAPI Event Style from within Media Center) and I select "speakers" under it's Device Output area - I am able to use the Mute, Volume Up and Volume Down hot keys on the K800 to control the audio level that comes from the speakers.
But - if I change the Device Output to Headphones - using the exact same audio device - suddenly the three audio buttons (upper right of the keyboard by the Calculator button) suddenly do not work.
Couple things - I cannot recall in any previous build whether or not these button were working or not OR if I just decided to try them for the first time with headphones. I don't use headphones often with this machine but when I did in the past...volume seemed fine...just can't remember if I ever attempted to control it via keyboard :)
Also - when wrangling with that static issue in the headphone jack...I did install the actual Realtek drivers for 10 minutes to see if it would make a difference. It did not. Knowing the history of the Realtek crap and how one can never uninstall it correctly - I am wondering if I now have a conflict with old drivers, old registry entries or something else that might be contributing to this issue.
Would love to hear if anyone has seen anything like this - especially involving a Logitech keyboard.
Cheers,
VP