[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Busy sound device
From:       Matthias =?iso-8859-1?q?H=F6lzer-Kl=FCpfel?= <mhk () caldera ! de>
Date:       2000-12-07 12:11:38
[Download RAW message or body]

On Donnerstag,  7. Dezember 2000 11:31, Thorsten Westheider wrote:
> Hi,
>
> I noticed that my sound based (non-KDE2) applications block
> indefinitely when attempting to access the audio device.
> Killing artsd immediately solves the problem, those
> applications play and record sound quite nicely then.
> I don't think it's supposed to be this way, is it?
> Same problem occurs with a H.323 GUI client I'm working on;
> this one employs the OpenH323 library, which, in turn uses
> "legacy" audio support (/dev/audio, /dev/dsp etc.) and also
> blocks with artsd running.
> So I said to myself, why not try to add sound server aka aRts
> support to get rid of the problem once and for all.
> Got a copy of the very fine book "KDE 2.0 Development"
> (congratulations to all contributors), gave the example_add
> a try and...failed:
>
>   Synth_PLAY: audio subsystem init failed
>   ASError = device /dev/dsp can't be opened (Device or resource busy)
>
> Well, that's exactly why I wanted to switch to aRts in
> the first place, to get rid of busy audio devices.
> Where did I miss the point?

Just run your non-KDE apps like this:

artsdsp application

This will make it talkd to artsd instead of opening /dev/dsp directly.


Bye,
Matthias.

 
>> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]