[Version 0.00.2b RC1, written by ZoFreX]
If, like me, you have a multimedia keyboard, you probably want it to work with foobar2000. I've divided this up into two parts:
Part 1: Making the "launch multimedia application" button on your keyboard launch foobar instead of Windows Media Player.
Step 1: Associate foobar with .cda files however you see fit (from foobar's preferences is an easy way to do it). That's it!
Testing: Press the "launch multimedia application" button on your keyboard. If foobar is open it should jump to the foreground, if not it should open. If it worked, jump to the "It worked!" section. If it didn't, try the troubleshooting section and if it still doesn't work, try the "It didn't work!" section.
Technical note: Yes, Windows determines what program should be launched when you press "AppKey 16" (media player button) by what opens .cda files. It took a while to figure this out! This can actually be changed so it matches .mp3 files or whatever, just change HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\AppKey\16\Association (I give no warranty whatsoever for fiddling with this, nor have I tested doing so).
Part 2: Making the media player buttons (play, stop etc) work when foobar is minimised.
Addendum A: Logitech SetPoint
Firstly, SetPoint is a horrible, poorly written program that I would strongly advise against having installed. However, you can get your media buttons working in foobar while it is minimised with a small alteration. Open up SetPoint's "players.ini" file, for me this is in C:\Program Files\Logitech\SetPoint\players.ini. At the bottom of the [players] list, add the line:
foobar2000=wac,foobar2000.exe,{DA7CD0DE-1602-45e6-89A1-C2CA151E008E}/1,xxx,xxx,xxx,xxx,xxx,xxx,xxx,0,1,foobar2000
Restart SetPoint (i.e. exit it, and then start it again), and your keys should work, if you're using foobar v0.9.4.1. The window class will need to be changed if you are not, or if you're using a different user interface module - e.g. for columnsui, the classid would be {E7076D1C-A7BF-4f39-B771-BCBE88F2A2A8}. The best long-term solution is for you to know how to find out that classid, so read on:
I used Spy++ to find the classid, but not all of you will have Visual Studio installed so I checked out some of the free options. WinID was the easiest to use:
Step 1: Download, install and run WinID http://www.dennisbabkin.com/php/download.php?what=WinID
Step 2: With foobar2000 visible on screen and WinID in the foreground, mouse over foobar's title and press shift.
Step 3: WinID will now have taken a snapshot, click the "1" in the top left corner to view your snapshot.
Step 4: Copy the class from here into the players.ini line for foobar.
Step 5: Exit and re-open SetPoint. Your multimedia keys should now work for foobar when it's minimised!
If you want the media button to launch foobar then use the SetPoint software to bind that.
It didn't work!
So you've followed the instructions, tried the troubleshooting steps, and it still doesn't work. No worries. Post:- What didn't work
- Whether the media keys work in foobar when it's focused
- Your version of Windows
- Your version of Foobar
- What keyboard you're using
- What drivers / software you have installed for your keyboard
- Anything else you think might be relevant
It worked!
Great! If you have a Windows / foobar version different to one in the "Tried & Tested" section, post so I can confirm it on that.
Tried & tested on:
Windows XP SP2
Vista build 5744 (Part 1: setting file associations from inside Foobar on non-administrator account fails hard, setting .cda assocation to foobar through Windows makes the media application launch button work fine)
foobar v0.9.4.1
Topic: Multimedia keyboards + foobar2000: A complete guide (Read 205326 times)
previous topic - next topic