On Sep 3, 2009, at 9:24 PM, husk wrote:

gnd@itchybit.org ha scritto:

...

hello,

im using Ubuntu Jaunty and have problems with sound in PD 0.41.4- extended when using simultaneously Firefox and/or Audacious.

If i start PD sooner then firefox and audacious, they dont make any
sounds but sound in pd works ok. If i start PD later, firefox and
audacious work fine, but sound in PD gets stuck with: snd_pcm_open (output): Device or resource busy (in the shell) audio I/O stuck... closing audio (in pd console)

Both FF and Audacious are using the pulseaudio server. I tried to
create a /etc/asound.conf, to create a new device:

pcm.pulse { type pulse } ctl.pulse { type pulse } pcm.!default { type pulse } ctl.!default { type pulse }

and use it with pd -alsa -alsaadd pulse, but the audio output in pd
still doesnt work when running some other sound applications. When
running pd alone like this, the sound is severely garbled and after a while it
hangs the same...

Is there some normal way how to handle this ? I mean it should not
be a problem using several application at once but apparently pd has some problems with it..

Try to use command: padsp pd -oss. It worked for me. let me know husk

Do you have any more info on the 'padsp' command? If this makes Pd
work easily with pulseaudio, it seems that the Pd-extended menu item
in the Ubuntu menus could then start pd with that 'padsp pd -oss'
command.

.hc

"[W]e have invented the technology to eliminate scarcity, but we are
deliberately throwing it away to benefit those who profit from
scarcity." -John Gilmore