Multimedia keyboards + foobar2000: A complete guide, If like me you have a multimedia keyboard, you probably want it to wor Options

[ChronoSphere]

This method is mentioned in the first post (Addendum A). You need to edit the window class to match the one that Columns UI uses (instructions in the first post).

No, look carefully: (first line, Addendum A; second - mine)
foobar2000=wac,foobar2000.exe,{DA7CD0DE-1602-45e6-89A1-C2CA151E008E}/1,xxx,xxx,xxx,xxx,xxx,xxx,xxx,0,1,foobar2000
foobar2000=cmd,foobar2000.exe,{DA7CD0DE-1602-45e6-89A1-C2CA151E008E}/1,xxx,xxx,40009,40044,40010,40051,40011,0,1,foobar2000

I tried changing the class to the ColumnsUI one, doesn't work, all keys stop working. Maybe ColumnsUI uses different cmd IDs <.<

[PedroQ]

For those using Columns UI:

CODE

[Players]
foobar2000=wac,foobar2000.exe,
{E7076D1C-A7BF-4f39-B771-BCBE88F2A2A8},xxx,xxx,xxx,xxx,xxx,xxx,xxx,0,1,foobar2000

HTH

[alphameric]

Interesting SetPoint hacking

this is exactly what i needed.
the typical classid method outlined elsewhere does not work for Panels UI.
For your method, all i had to do was set the media buttons to silent, then boot up setpoint.
After that foobar recognized my media keys and i could set them globally

[knocker]

Interesting SetPoint hacking

I've been using a Logitech keyboard with multimedia keys successfully for a while now, by not having SetPoint installed, but recently got myself a Logitech mouse too. Now I need to have SetPoint running, and it grabs hold of control of the keyboard too, ruining all the multimedia keys which used to work just fine.

I've been hacking about with SetPoint for some time, and come across the following. If you close SetPoint, then open your settings file in \Documents and Settings\username\Application Data\Logitech\SetPoint\user.xml, you should find a Device element with the DisplayName of your keyboard, and Class="KeyboardDevice". In it, there are a bunch of Button elements, with nice descriptive Names. Find the buttons you want to fix, and for each one, look inside the Trigger element for a Param element which has an attribute Silent="0". Change that to Silent="1". Once you've done that to all the media buttons you want to fix, save the file, and start SetPoint again. Those buttons with Silent="0" you can still set the behaviour for in SetPoint (which is handy for those buttons which don't have a standard behaviour), and those buttons with Silent="1" behave as if SetPoint was not running. Result!

Hope this is useful to others too,

Alex

Thats definitely useful, works perfectly! Thanks alot ~

PS: I quoted the whole post so people dont have to look for it

This post has been edited by knocker: May 3 2007, 19:30

[math]

I've been hacking about with SetPoint for some time, and come across the following. If you close SetPoint, then open your settings file in \Documents and Settings\username\Application Data\Logitech\SetPoint\user.xml, you should find a Device element with the DisplayName of your keyboard, and Class="KeyboardDevice". In it, there are a bunch of Button elements, with nice descriptive Names. Find the buttons you want to fix, and for each one, look inside the Trigger element for a Param element which has an attribute Silent="0". Change that to Silent="1". Once you've done that to all the media buttons you want to fix, save the file, and start SetPoint again. Those buttons with Silent="0" you can still set the behaviour for in SetPoint (which is handy for those buttons which don't have a standard behaviour), and those buttons with Silent="1" behave as if SetPoint was not running. Result!

This is THE method for dealing with Setpoint, don't bother with all that other complicated id stuff... this is easy and works.

[Pingue]

Has anyone got any idea how to un register such keys from WMP. I have an Acer Laptop with media keys only with the Fn button, but they still only register to WMP. at the moment, I'm just using Ctrl-Alt instead of Fn. Are there some registry values to get rid of this??? Thanks!

[sandeep108]

Nice post. But problem is there with MS Intellitype. I see no point in disabling the MM keys just to get them working when fb2k is minimised. Then in other media players they do not work. Rather leave fb2k window open and they work just fine. Of course volume is still tied to windows volume and not fb2k, but well, how much does that matter?

[MiSP]

I've been hacking about with SetPoint for some time, and come across the following. If you close SetPoint, then open your settings file in \Documents and Settings\username\Application Data\Logitech\SetPoint\user.xml, you should find a Device element with the DisplayName of your keyboard, and Class="KeyboardDevice". In it, there are a bunch of Button elements, with nice descriptive Names. Find the buttons you want to fix, and for each one, look inside the Trigger element for a Param element which has an attribute Silent="0". Change that to Silent="1". Once you've done that to all the media buttons you want to fix, save the file, and start SetPoint again. Those buttons with Silent="0" you can still set the behaviour for in SetPoint (which is handy for those buttons which don't have a standard behaviour), and those buttons with Silent="1" behave as if SetPoint was not running. Result!

This is THE method for dealing with Setpoint, don't bother with all that other complicated id stuff... this is easy and works.

I just tried this, and can confirm that it works perfectly. Note that using Logitech DiNovo Edge, the keys to be changed is Name=F5 to Name=F8 - there's no nice descripting names for "next" or "previous" or the likes unless you dig a little deeper.

[Mesingel]

Interesting SetPoint hacking

I've been using a Logitech keyboard with multimedia keys successfully for a while now, by not having SetPoint installed, but recently got myself a Logitech mouse too. Now I need to have SetPoint running, and it grabs hold of control of the keyboard too, ruining all the multimedia keys which used to work just fine.

I've been hacking about with SetPoint for some time, and come across the following. If you close SetPoint, then open your settings file in \Documents and Settings\username\Application Data\Logitech\SetPoint\user.xml, you should find a Device element with the DisplayName of your keyboard, and Class="KeyboardDevice". In it, there are a bunch of Button elements, with nice descriptive Names. Find the buttons you want to fix, and for each one, look inside the Trigger element for a Param element which has an attribute Silent="0". Change that to Silent="1". Once you've done that to all the media buttons you want to fix, save the file, and start SetPoint again. Those buttons with Silent="0" you can still set the behaviour for in SetPoint (which is handy for those buttons which don't have a standard behaviour), and those buttons with Silent="1" behave as if SetPoint was not running. Result!

Hope this is useful to others too,

Alex

YOU TOTALLY PWN !
At last, after 2 days of (intensive) browsing, I finally found someone who struck the answer, AND ACTUALLY CARED TO SHARE IT!
<3 Alex!

Oh yeah, I use a UltraX Cordless Desktop, and it worked like a charm.

This post has been edited by Mesingel: Jul 20 2007, 22:19

[trackfan504]

Interesting topic! Got everything working by reading through entire post but dang volume control.

Setpoint 4.0
Logiblech S510
XP Sp2
Foobar 9.4.3
columns ui 0.13 beta

Once I figured out to use notepad.exe to edit user.xml instead of Iexploder I for sure thought inserting "1" to volume up/down silent trigger did the trick!
When in try to configure fb keyboard shortcuts and press volume + or - nothing shows up in Key box.

Also learned it pays off to first read entire post before banging your head against the wall for little switches like /1

Any other tips to get volume button to behave?

Using e-mu 1820m pci soundcard if that makes any difference.
Cheers

[AlexVallat]

Thanks for the kind words, Mesingel!

trackfan504, the volume buttons work for me (Logitech Media Keyboard Elite), so in principle there's no reason why they shouldn't work.

Things to try:

• Is set-point still handling the volume keys - does the OSD show up?
• Do the volume buttons show in the keyboard shortcut box when SetPoint is not running?
• Do the volume keys actually change the main volume control when SetPoint is not running?
• What were the names of the volume Button elements that you changed? Mine are "Volume Up Controller" (number 786665) and "Volume Down Controller" (number 786666).
• I assume as you got the other keys working that the changes to user.xml have been recognised by SetPoint, which means you changed the right file, and SetPoint wasn't running while you did it.

Alex

[trackfan504]

trackfan504, the volume buttons work for me (Logitech Media Keyboard Elite), so in principle there's no reason why they shouldn't work.

In principle...I should have figured this out by now



Things to try:

• Is set-point still handling the volume keys - does the OSD show up? Nope, even playing
  WMP10 , no OSD
  
• Do the volume buttons show in the keyboard shortcut box when SetPoint is not running? no, either with or w/o setpoint, nuttin' in Key box.
  
• Do the volume keys actually change the main volume control when SetPoint is not running? No
  
  
• What were the names of the volume Button elements that you changed? Mine are "Volume Up Controller" (number 786665) and "Volume Down Controller" (number 786666). Same ID for S510 elements.
  
• I assume as you got the other keys working that the changes to user.xml have been recognised by SetPoint, which means you changed the right file, and SetPoint wasn't running while you did it.
  
  Yes, even without hacking xml, anything but volume control seems to be working fine.
  
  Another thing that kinda blows with Setpoint software is --> S3 standby no longer works properly....but I digress.
  
  Thanks for the feedback.
  
  

Alex
[/quote]

[AlexVallat]

• Do the volume keys actually change the main volume control when SetPoint is not running? No

That would seem to suggest that the keyboard is not actually sending volume up and volume down keypresses when those keys are pressed. Which in turn suggests that they will only work with SetPoint handling them, as they aren't normal buttons but some sort of custom hardware that only SetPoint can detect. Bad news, I'm afraid.

Getting a bit off-topic with the standby, but you might look into the device properties of the keyboard (and mouse, if SetPoint controlled) in the device manager, and unchecking "Allow this device to bring the computer out of standby" on the "Power Management" tab.

[trackfan504]

• Do the volume keys actually change the main volume control when SetPoint is not running? No

That would seem to suggest that the keyboard is not actually sending volume up and volume down keypresses when those keys are pressed. Which in turn suggests that they will only work with SetPoint handling them, as they aren't normal buttons but some sort of custom hardware that only SetPoint can detect. Bad news, I'm afraid.

As mentioned, I tried volume control either with or without running Setpoint. Since it doesn't work in either with foobar or any other media player I suspect hardware is kaput.

Getting a bit off-topic with the standby, but you might look into the device properties of the keyboard (and mouse, if SetPoint controlled) in the device manager, and unchecking "Allow this device to bring the computer out of standby" on the "Power Management" tab.

Anything researched has been tried to make S3 get along with logitech, from reg hacks to dumppo.exe, nic adapter switches, USB and contol devices enabled/disabled/installed/uninstalled. PC either gets to S1 (fans and HDDs spinning), freezes with 'preparing for standby' greeting or starts right back up. I have a lot of gear hanging off this machine, midi controllers, instruments, e-sata drives, NAS and network printer. I am prolly reaching and therefore just gave up. I suspect a few applications such as Cubase 4 or Acid Pro may mess with volume control from this keyboard. I'm chasing this one more out of interest (the inner geek) since I use Mackie's Big Knob to change levels. Thanks again!

This post has been edited by trackfan504: Jul 22 2007, 20:00

[Thanasis159]

I did what you said in Addendum A but it didn't work for me. I have Logitech EX110 wireless desktop( keyboard and mouse), I am using windows xp service pack 2 with all the latest updates, my foobar version is 0.9.4.3, the multimedia buttons work when the foobar window is focused but not when it is minimized or another window is focused. I use columns ui along with many other plugins. Any help appreciated!

[Manic]

Beautiful!! can confirm that it works perfectly with a Dell USB enhanced multimedia keyboard on Vista Business. The embedded multimedia buttons on my Toshiba Satellite Pro U200 also seem to work without any extra configs, except for the launcher, which insists on opening WMP.

To make foobar open instead of WMP youll also need to go to the Control Panel and change the default app for .cda there, as well as in foobar 2k.

[aziz]

Thank you very much brotha!

[foshelan]

Thank you buddy
It's really a great and detailed manual that I search
This gives me a lot of help

[Mangix]

i have an hp keyboard. i have the drivers and playback buttons work. but only when foobar2000 is in focus. if i try adding the playback keys as global shortcuts, foobar2000 can't add them for some reason. foo_appcommand made it work but foo_appcommand doesn't work with foobar2000 0.9.6. any ideas on how to get it to work?

[Paft]

Hello,

at default media keys work, but only when in focus. Setting the keys then setting 'global' forces to use them for foo regardless of what other app is in focus. So both ways are as useless as each other to me. No way to get it to work like, erm, normal? It is such a minor issue but one that is stopping me from using it.

[Paft]

Shortening my comment.

Global hotkey mediakeys don't work in the way "it should". When set to gobal the keys then only work for Foo and nothing else.

[novembre]

That's the point of GLOBAL hotkeys, they work even if foobar is not in focus. If you don't need this function, just disable Global Hotkey.

[Paft]

That's the point of GLOBAL hotkeys, they work even if foobar is not in focus. If you don't need this function, just disable Global Hotkey.

But then they only work when foo is in focus.

Winamp you can still control it when it isn't in focus, so long as no other app that uses mediakeys is in focus.

[cipher_nemo]

I have the same problem as the OP, even years later. I will try adding the line in SetPoint tonight and see if that helps. I'm also playing LOTRO on Windows 7 RC-1 with Foobar2000 and unfortunately, Foobar2000 is the issue here when combined with Setpoint.

I'll report if it helps me.

[cipher_nemo]

Nope, no go. I installed Visual Studio 2010 Professional any ways since I'm a software engineer who uses VS 2008 and since the 2010 was a free Beta.

I then used Microsoft Spy++ 64-bit to get the class ID of Foobar2000 version 0.9.6.8, which is: {97E27FAA-C0B3-4b8e-A693-ED7881E99FC1}

I add that foobar line to my Setpoint utility's ini file with this new class ID and still no go. In fact, I completely exited Setpoint and all Logitech G15 keyboard utilities, and this is still a no go.

On Windows 7 RC-1 with Foobar2000, I am unable to use any global keys for it when I run Lord of the Rings Online (LOTRO). I am running both as Administrator too under their executable properties.

Still broken after 3 years.