foo_RM1800 2006-05-29 23:17:50 Heyas !So, I recently switched over from winamp to foobar2000; I also recently bought a creative labs X-Fi. On top of being a rather nice sound card, it comes with a remote control (labeled as "RM-1800"). Now, I figured I had everything I needed to make myself a nice little media center...Except for the fact that the remote only supports creative's own media player out of the box (I think... I didn't test this extensively ).After some digging around in these forums and elsewhere, it seems that the main option to use creative remotes with foobar was RM-X. Apparently that is no longer an option with foobar 0.9 though, from what I could gather.The other option that seemed to be suggested on these forums was Girder; however, since the only thing I want from my remote is to control playback in foobar, shelling out 50$ or so and installing something that would be loaded at all times wasn't exactly appealing.To make a long story short, I felt like reinventing the wheel I was curious to see how this remote works, and how foobar components are written, so I went ahead and created foo_RM1800.So, without further ado : foo_RM-1800 v0.0.1 !I have no idea if this can be of any use to anyone apart from me, but since I spent a while searching for this, I figured I might as well make it available to others I'm not sure if this'll work with anything but a Creative X-Fi and RM-1800 remote; I believe the SB Live! and Audigy cards used a similar remote but I'm not sure if the buttons map to the same scan codes. If any can test this with another creative remote, I'd be happy to know what happens !Now, I'll freely admit this is (for now) a quick hack : it only supports the play/pause, stop, next, previous, seek forward and seek back buttons. (all of which map to the foobar controls you'd expect ) I didn't really see a need for the rest of the buttons yet, and of course the volume, mute and special buttons/scrollwheels continue to work as they originally did through the X-Fi driver.Also, for now, this component assumes that the X-Fi is MIDI device number 0; that'll probably be the case for most people but if it's not, well... the remote won't work I'll work on making this cleaner when I have some free time (and if there is some interest; not much point in fidling with it if I'm the only one using it); in particular, I'd like to try my hand at implementing a configuration panel to allow the user to map buttons himself.