24 May
2013
24 May
'13
2:51 a.m.
Len Ovens writes:
Ah, indeed. Thanks!
Janina
The recommended way of using PA is by session. This
allows more options
and I think is more secure. To run system wide, PA has to be started at
boot time. Normally, PA is set up to auto find and grab ports, but the
config files in /etc/pulse have some commented out lines that might give
some ideas on only connecting PA to one audio IF.
I would first look at the online docs available for PA about running it
system wide. Then put on your sysadmin hat and play. There are some man
pages included as well that may help. You are going into places beyond
what I have tried to do. You are likely to find more help on the pulse
audio mailing list than here though.
Yes, good advice, and makes sense the PA list would know more about how
to circumscribe it.
Ah, yes.
Thanks for pointing these out. Looks like pacmd is the one for
sourcing profiles. But, where do these come from? There must be a set
somewhere? Or, is the profile what one creates with pavucontrol?
look in /usr/share/pulseaudio/ and subdirectories.
--
Len Ovens
www.OvenWerks.net
--
Janina Sajka, Phone: +1.443.300.2200
sip:janina@asterisk.rednote.net
Email: janina(a)rednote.net
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/