Re: sound question

2003-11-13 Thread Cordula's Web
> > > > play: /dev/dsp: Device busy
> > > Perhaps esd is running and grabbing the sound device?
> > 80418  ??  Ss 2:56.38 esd -terminate -nobeeps -as 2 -spawnfd 
> > so if I kill -9 the esd process, icq will start emitting sounds ?
> unfortunately no, it will just "mute" my xmms session

1. Who started esd? 'root' or a non-root user? (ps axu)
2. Try fiddling with esd's flags? (man esd)

I don't have a solution, but it's obvious that esd is
opening /dev/dsp, and some programs like xmms or other
sound apps communicate directly with esd, e.g. with
a unix socket. If your app uses /dev/dsp directly, it
will fail, because esd has locked it for itself.

When I run mpg123, esd runs with the following params:

$ ps ax | grep esd
  15939  ??  Rs 0:03.23 esd -terminate -nobeeps -as 2 -spawnfd 5

It also opens this unix socket:

$ sockstat | grep esd
cpghost  mpg123   159414 stream esd[15939]:10
cpghost  esd  159396 stream (none)
cpghost  esd  159397 stream /tmp/.esd/socket
cpghost  esd  15939   10 stream /tmp/.esd/socket

You could check the permissions of /tmp/.esd/socket

Perhaps your sound app doesn't know how to use esd
(you'll have to kill esd for this), or it knows, but
can't, for some obscure reason.

Of course, this is just a wild guess.

-- 
Cordula's Web. http://www.cordula.ws/

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: sound question

2003-11-13 Thread Petre Bandac
unfortunately no, it will just "mute" my xmms session

any other solutions ?

petre

On Thursday 13 November 2003 21:11 Anno Domini, Petre Bandac wrote using one 
of his keyboards:
> [EMAIL PROTECTED] ps -ax | grep esd
> ~
> 80418  ??  Ss 2:56.38 esd -terminate -nobeeps -as 2 -spawnfd 5
> 84843  p5  S+ 0:00.01 egrep esd
>
>
> so if I kill -9 the esd process, icq will start emitting sounds ?
>
> petre
>
>
> On Thursday 13 November 2003 21:04 Anno Domini, Cordula's Web wrote using
> one
>
> of his keyboards:
> > > play: /dev/dsp: Device busy
> >
> > Perhaps esd is running and grabbing the sound device?
> >
> > I have a similar problem with mpg123. Calling mpg123
> > multiple times (e.g. in a loop with a shell script)
> > until it works is an acceptable work-around for me:
> >
> > #!/bin/sh
> > until (mpg123 "$1")
> > do
> > sleep 1;
> > done
> >
> > Of course, a solution would be better than a work-arond :)

-- 
Login: petreName: Petre Bandac
Directory: /home/petre  Shell: /usr/local/bin/zsh
On since Tue Nov 11 14:37 (EET) on ttyv0, idle 11:26 (messages off)
No Mail.
No Plan.

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: sound question

2003-11-13 Thread Petre Bandac
[EMAIL PROTECTED] ps -ax | grep esd
~
80418  ??  Ss 2:56.38 esd -terminate -nobeeps -as 2 -spawnfd 5
84843  p5  S+ 0:00.01 egrep esd


so if I kill -9 the esd process, icq will start emitting sounds ?

petre


On Thursday 13 November 2003 21:04 Anno Domini, Cordula's Web wrote using one 
of his keyboards:
> > play: /dev/dsp: Device busy
>
> Perhaps esd is running and grabbing the sound device?
>
> I have a similar problem with mpg123. Calling mpg123
> multiple times (e.g. in a loop with a shell script)
> until it works is an acceptable work-around for me:
>
> #!/bin/sh
> until (mpg123 "$1")
> do
> sleep 1;
> done
>
> Of course, a solution would be better than a work-arond :)

-- 
Login: petreName: Petre Bandac
Directory: /home/petre  Shell: /usr/local/bin/zsh
On since Tue Nov 11 14:37 (EET) on ttyv0, idle 11:21 (messages off)
No Mail.
No Plan.

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: sound question

2003-11-13 Thread Cordula's Web
> play: /dev/dsp: Device busy

Perhaps esd is running and grabbing the sound device?

I have a similar problem with mpg123. Calling mpg123
multiple times (e.g. in a loop with a shell script)
until it works is an acceptable work-around for me:

#!/bin/sh
until (mpg123 "$1")
do
sleep 1;
done

Of course, a solution would be better than a work-arond :)

-- 
Cordula's Web. http://www.cordula.ws/

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"