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. -- Len Ovens www.OvenWerks.net _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
