Re: direct access to sound device not possible

In the past months, audacity, has worked ok (version 1.1). After the 
upgrade with apt-get, it wont work anymore (version 1.2) .
Searching with Google, I found that I need Jack to connect Alsa to the 
audio application ( http://www.djcj.org/LAU/jack/ ), but the problem has 
continued.
I verified when Audacity starts that appears a daemon as "CheckHardware 
--sound /usr/bin/audacity".
Yesterday, I want to install Mustajuuri (similar to audacity), and I 
needed to install some libraries such as audiofile, snd; and after some 
probes, and reinstalling some sound packages (audiofile, snd, speex), 
audacity now works ok, but with a few changes in the control center- 
multimedia (disabling full duplex).
http://www.tml.hut.fi/~tilmonen/mustajuuri/
I dont know why appears as input and output only /dev/dsp  in the 
Audacity settings, and not appears other devices when all Alsa native 
devices are under /proc/asound. The device /dev/dsp is the Open Sound 
device emulation for alsa.

Thanks,
                Juan

Eduard Avetisyan wrote:

>hi!
>
>check if you're running artsd or esd in the meantime. xmms is
>smart enough to use these sound daemons without demanding direct
>access to the sound device. BTW, may happen that Audacity has a
>similar option/plugin, you may want to check it...
>
>Cheers
>        Eduard
>
>--- Juan Erbes <[email protected]> wrote:
>  
>
>>Hi!
>>When I open some audio applications such as Audacity or
>>env24control, I 
>>got the error "direct access to sound device not possible".
>>I have SuSE 8.2, and the spund card is a SBLive Platinum with
>>livedrive, 
>>and, of course with Alsa drivers.
>>With other applications such as Xmms, I have no problem.
>>
>>Thanks,
>>               Juan
>>    
>>
>
>
>__________________________________
>Do you Yahoo!?
>The New Yahoo! Shopping - with improved product search
>http://shopping.yahoo.com
>
>
>  
>