Re: [Audacity-devel] Locking of /dev/dsp?

[Dominic M. <do...@mi...>]

Audacity uses PortAudio, which "scans" all possibly devices (like
/dev/dsp, /dev/dsp1, etc.) before picking one.  It tries to open
each one and if it succeeds, it closes it.  If that's all it takes
to lock up artsd, then unfortunately there isn't currently a way
to disable this behavior, sorry.

- Dominic

Jef Oliver wrote:
> Hey Everyone,
> 
>      It seems that every time I open Audacity, all access to my soundserver 
> (ie arts) is blocked.  After I close Audacity, the access is still blocked, I 
> have to issue "killall -HUP artsd" to get my soundserver running again.  Let 
> me give some details here.
> 
> Linux Kernel 2.4.20 (i486)
> KDE 3.1.1a
> Arts configured to run on /dev/dsp1
> Audacity configured to run on /dev/dsp
> 
> Now, whenever I use a program configured to use OSS or ESD, I configure them 
> to use /dev/dsp and leave Arts running on /dev/dsp1.  This configuration 
> works great.  The device locking only seems to happen when I open Audacity.
> 
> Does Audacity require direct access to the entire soundcard?  If not, any 
> ideas on what might be causing this device locking?
> 
> Thanks for any help.
> Jef
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Audacity-devel mailing list
> Aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel