Len Ovens writes: > > On Thu, May 23, 2013 5:22 pm, Len Ovens wrote: > > On Thu, May 23, 2013 5:04 pm, Janina Sajka wrote: > >> Len Ovens writes: > >>> > >>> On Thu, May 23, 2013 10:55 am, Janina Sajka wrote: > >>> > >>> > In any case, I certainly don't want pulseaudio to have access to all > >>> my > >>> > devices, just as I don't want jack running on the audio devices I use > >>> > for Speakup and for Orca (two separate devices, unfortunately, > >>> because > >>> > of driver compatibility issues). > >>> > > >>> > In any case, this is a moderate priority project at the moment for > >>> me, > >>> > so I do spend time on it as I have time. So far I have come to > >>> believe > >>> > it would be possible to restrict pulseaudio either via its > >>> client.config > >>> > or in udev, but I haven't tried any of this yet. > >>> > >>> Really simple with the GUI. I am not sure from the command line. > >>> pavucontrol has a configuration tab with device profiles. Setting a > >>> device > >>> to off tells PA to leave it alone. It is persistent from boot to boot, > >>> so > >>> it must be stored in a file somewhere... looks like binary though. In > >>> ~/.config/pulse/ > >> > >> On a per user basis? > >> That won't quite work for me, because I also need to avoid the part > >> where pulseaudio doesn't allow sound access for a root login. > >> > >> I really want to go at this on a system-wide level, but then it's > >> possible I don't understand pa architecture, i.e. perhaps any pa is only > >> invoked user by user. > > I thought about this for a bit and I am not sure if you mean that two > users can be logged in at the same time and both listen to sound (PA would > have to run system wide) or just that only one user would login at a time > but you want the same setting for all in which case you only need to > change the system settings. > Actually, at the same time. I tend to have 23 consoles open plus the one dedicated to the graphical desktop. Sounds like overkill, but there's method to my madness, i.e. gui on tty1, mail on tty10, my work with the W3C on tty7, etc., etc. > -- I typically have 1 or 2 ttys with root login for system level things. Yes, I know sudo, but some commands actually won't work without a native root login. And, I have a user that builds rpms. All of these need screen reader support, and that works just fine over alsa, but no so well over pa--except that the Speech-Dispatcher, Espeak, plus Orca combo actively supports pa. So, my intent: Card 0 for Speakup with TTSynth and whatever incidental sound Card 1 is a digital out of 0, I don't use it. Card 2 for Orca. This one gets pa Card3 is my Sennheiser headset for SIP calls, preferably FreeSwitch, but that's horribly latent at the moment. Card4 is currently my HDSP Multiface. Needless to say, this one's for jack--once I get it working! Card5 is an old Chaintech PCI card that uses ICE1725 drivers, and has pretty good quality. I use it with mplayer, routing its output to some old JBL Ions. If I continue to have problems with the Multiface, this is my fallback until I can get something better. So, I'm OK to turn pa on/off for 2 and 5, but definitely not 0 or 4, and probably not 3. This, plus the multi logins. The UDEV rule does seem promissing. I just need to learn more about how to identify devices to UDEV. And, since Cards 2 & 3 are USB, I should arguably lock them in via UDEV, rather than counting on /etc/modprobe.d/local.conf alsa assignments to stay the same. Probably more than you needed to know about my setup! Janina > Len Ovens > www.OvenWerks.net -- Janina Sajka, Phone: +1.443.300.2200 sip:janina@xxxxxxxxxxxxxxxxxxxx Email: janina@xxxxxxxxxxx Linux Foundation Fellow Executive Chair, Accessibility Workgroup: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair, Protocols & Formats http://www.w3.org/wai/pf Indie UI http://www.w3.org/WAI/IndieUI/ _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
