You are correct... latest release Ubuntu 7.10 comes with PA 0.9.6. I'll look into getting the latest version of PA. My goal was to use PA as a replacement for esound server... I'd like to be able to record/mix different sound sources (midi, analog, sound from files (mp3, wav, ogg, etc)) and be able to create different file formats, including sound delivered in flash (I'm not a fan of flash as it consumes alot of cpu time, but it is in demand). I played with jackd for a while and was impressed with it's technical capabilities, but unfortunately, I haven't found a way to play flash sound through jackd... that is, flash in firefox. I found a how-to in the Ubuntu forum that seemed to patch together a solution the involved PA: http://ubuntu-utah.ubuntuforums.org/showthread.php?t=548178 and have run into configuration/version issues since. Question: PA, esound, jackd, etc.. are all called sound servers, implying that you can replace one with another... like apache vs iis.... is the main difference that they use different client/server communication protocols? So, the competition among the sound servers is really over the communication protocol... and it looks like sound performance/features is affected by the communication protocol. Tanu Kaskinen wrote: > On Thu, Jan 31, 2008 at 08:52:32PM -0500, Richard Geddes wrote: > >> The PA daemon is not starting and PA Manager is say "connection refused" >> . Not sure what to make of it, but your suggestions are welcome. >> > > "Connection refused" is the message you get when trying to > use a pulse client program without having the daemon > running. > > >> Here's some output from /var/log/messages: >> >> >>> pulseaudio[7278]: main.c: Module load failed. >>> pulseaudio[7278]: main.c: failed to initialize daemon. >>> pulseaudio[7288]: pid.c: daemon already running. >>> pulseaudio[7288]: main.c: pa_pid_file_create() failed. >>> pulseaudio[7291]: pid.c: daemon already running. >>> pulseaudio[7291]: main.c: pa_pid_file_create() failed. >>> pulseaudio[7285]: module-alsa-sink.c: Failed to set hardware >>> parameters: Operation not permitted >>> pulseaudio[7285]: module.c: Failed to load module "module-alsa-sink" >>> (argument: "sink_name=delta_out device=hw:0 channels=10 >>> channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7"): >>> initialization failed. >>> pulseaudio[7285]: main.c: Module load failed. >>> pulseaudio[7285]: main.c: failed to initialize daemon. >>> pulseaudio[7294]: module-alsa-sink.c: Failed to set hardware >>> parameters: Operation not permitted >>> pulseaudio[7294]: module.c: Failed to load module "module-alsa-sink" >>> (argument: "sink_name=delta_out device=hw:0 channels=10 >>> channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7"): >>> initialization failed. >>> pulseaudio[7294]: main.c: Module load failed. >>> pulseaudio[7294]: main.c: failed to initialize daemon. >>> > > The "Failed to set hardware parameters: Operation not > permitted" is an encrypted message, and means that > pulseaudio couldn't open the device for 16-bit samples, > because the device only supports 32-bit samples. You seem to > have an older version of pulseaudio. Since 0.9.8 pulseaudio > has supported 32-bit samples, so you'll have to upgrade to > at least that version. > > An unrelated note: you seem to have made the decision to run > pulseaudio as a system-wide daemon. That is not generally > recommended way to run pulseaudio, it's only for the cases > when the per-user way just doesn't cut it. This isn't a > fatal mistake (if it's mistake at all, I don't know what > kind of setup you actually have/need), and you don't > necessarily need to fix it. Some information on this matter: > http://www.pulseaudio.org/wiki/SystemWideInstance > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20080201/bd390ad2/attachment.htm>
