[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Keep non-gnome2.6 package out of the discussion please

On Tue, May 25, 2004 at 02:12:18AM +0200, Dagfinn Ilmari Manns?ker wrote:
> Sven Luther <sven.luther@wanadoo.fr> writes:
> > On Mon, May 24, 2004 at 01:34:43PM +0200, Dagfinn Ilmari Mannsåker wrote:
> >> Consider a user running KDE but who for some reason likes GStreamer
> >> for his multimedia needs. Should he be prevented from choosing Arts
> >> as the default audio sink just because the admin hasn't thought of
> >> the possibility of running GNOME apps in KDE?
> >
> > Well, if arts is running, the user (or admin) sure cannot chose to use
> > esd or oss/alsa directly, well at least not on my hardware, it would
> > result in the app silently waiting forever.
> Exactly, the user _needs_ to be able to override the global default
> setting in cases like this.

Nope, the system should know that either esd or arts is running, and
transparently set the correct device (or sink, or whatever) for all
apps, be they KDE or gnome or whatever.

What we really need is a unified way of handling sound, but then i don't
believe this is going to happen anytime soon. 

> The number of available playback channels depends on the hardware. My
> laptop has two, other soundcards may have more. ALSA can provide virtual
> channels via software mixing too, see
> <http://alsa-project.org/alsa-doc/doc-php/asoundrc.php3#softmix>.

Interesting. My eperience is that mostly if you start an app with esound
managing alsa hardware, the app hangs.

> Blocking on a busy sound device is a bug in most cases. The program
> should open the device with O_NDELAY or O_NONBLOCK and handle EBUSY
> appropriately (wait/retry, error out, warn or ignore silently, depending
> on the importance of sound playback for the overall functionality of the
> program).

Yep, most don't do so though.


Sven Luther

Reply to: