[pulseaudio-tickets] [PulseAudio] #875: [patch] Add module for jack sense evdev input devices
#875: [patch] Add module for jack sense evdev input devices -+-- Reporter: joeshaw | Owner: lennart Type: enhancement | Status: new Milestone: | Component: core Keywords: | -+-- Sound modules in the Linux kernel have the ability to create input devices for sound card jacks through the snd_jack API. (See sound/core/jack.c) These devices are exported as evdev devices which notify (and can be queried about) a few different switches. I'm attaching a new PA module which maps one of those devices to a source and/or sink. Whenever the jack sense changes, a property is set on the source/sink. Clients can watch for notifications and take action (such as muting, changing the default source/sink, migrating streams to that source/sink) when the property changes. -- Ticket URL: http://pulseaudio.org/ticket/875 PulseAudio http://pulseaudio.org/ The PulseAudio Sound Server ___ pulseaudio-tickets mailing list pulseaudio-tickets@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets
Re: [pulseaudio-tickets] [PulseAudio] #875: [patch] Add module for jack sense evdev input devices
#875: [patch] Add module for jack sense evdev input devices --+- Reporter: joeshaw | Owner: lennart Type: enhancement | Status: new Milestone: | Component: core Resolution: |Keywords: --+- Comment(by coling): Thank you very much for this. I just wish you'd discussed the implementation with us before starting development. Jack Sensing support is not something that should be handled as a module, but rather something built in to the alsa-sink/source itself. Ultimately Jack Sensing should result in a change of sink/source port e.g. changing from built in Speakers to Headphones port in the case. Clients should not need to do any watching of sink properties etc. however they may wish to take some action, however they will be made aware of this due to the port changes anyway. The main complications with regard to Jack Sensing comes from when users have specifically overridden the port manually - who do we want to take notice of, the user choice or the automatic information? I'd err on the side of the latter, but there are still some complications (e.g. some hardware has three ports - Speakers, Headphones and something else I can't remember off the top of my head, so it's not a simple binary choice. But certainly the ports system is the correct place to hook up jack sensing. I'd love it if you would come and discuss this with us on the IRC channel or via the devel list. -- Ticket URL: http://pulseaudio.org/ticket/875#comment:1 PulseAudio http://pulseaudio.org/ The PulseAudio Sound Server ___ pulseaudio-tickets mailing list pulseaudio-tickets@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets
Re: [pulseaudio-tickets] [PulseAudio] #875: [patch] Add module for jack sense evdev input devices
#875: [patch] Add module for jack sense evdev input devices --+- Reporter: joeshaw | Owner: lennart Type: enhancement | Status: new Milestone: | Component: core Resolution: |Keywords: --+- Comment(by joeshaw): Is there a concept of a null port? We would need the null port to be selected until another jack was sensed, because our clients make determinations about which sound card to use based on whether the jacks on one of them is used at all. -- Ticket URL: http://pulseaudio.org/ticket/875#comment:2 PulseAudio http://pulseaudio.org/ The PulseAudio Sound Server ___ pulseaudio-tickets mailing list pulseaudio-tickets@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets
