On Tue, Aug 29, 2006 at 08:37:41PM +0100, Andrew Lyon wrote: > On 8/29/06, Louis-David Mitterrand <[EMAIL PROTECTED]> wrote: > > > > Indeed! The volume control acts on /dev/input/event2.
I haden't noticed up to now but the headset's volume control actually sends VolumeUp and VolumeDown events to the X server, which my window manager acts upon for sound card #1 (headset being #2). So no need for a separate daemon here, a simple reconfiguration of my wm will suffice. What I'd like to understand is why these events are visible to the X server (using xev)? My /etc/X11/xorg.conf has no particular section for the headset. > > And I discovered my keyboard volume knob also uses that interface. > > then often do.. > > you can also use lircd with dev/input driver to read these events, > although i think that support has been moved into a separate daemon > called inputlircd, at least it has on my gentoo system. Same here on debian. > i would be interested to hear if you get it working as I have similar > devices and have never looked into setting up the buttons. I'd rather try to direct the volume knob events towards X and capture them at the wm level, but they don't appear in xev. I tried making a new section in xorg.conf with /dev/input/event2 and Driver "mouse" and the events do appear but interfere with the pointer (no surprise there ;). It boggles me that headset volume events appear in xev(1) and not keyboard volume knob ones... but that is off-topic to alsa. Cheers, ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
