2009/6/12 Lennart Poettering <lennart at poettering.net>: > It's simply started by the first app that needs it. Place "autospawn = > no" in ~/.pulse/client.conf (or /etc/pulse/client.conf). Great, that did the trick, thanks. > Shouldn't be too hard to fix for someone who cares to fix this. All > that is needed is probably some fragment in /usr/share/alsa/cards/ > that maps front:xxx in some sensible way to your card. So is that how pulse picks up it's device configuration, via the ALSA config? I'm trying to do some investigation but the config file format is a little confusing at first. I'll keep working on it anyway - I've found a few hints via the wonder of google. If pulse does use the alsa config to pick up it's devices, this thread is probably quite pertinent: http://mailman.alsa-project.org/pipermail/alsa-devel/2009-January/014029.html Thanks again, you must get through a huge pile of emails per day! Chris.
