linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: ookhoi@humilis.net
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>, eugene.teo@eugeneteo.net
Subject: Re: 2.6 sound drivers?
Date: Thu, 17 Jul 2003 13:32:57 +0200	[thread overview]
Message-ID: <s5hfzl5z8uu.wl@alsa2.suse.de> (raw)
In-Reply-To: <20030717111958.GB30717@favonius>

At Thu, 17 Jul 2003 13:19:58 +0200,
Ookhoi wrote:
> 
> Takashi Iwai wrote (ao):
> > At Thu, 17 Jul 2003 16:57:04 +0800,
> > Eugene Teo wrote:
> > > One thing I noticed abt this ALSA driver is that if I am playing
> > > say, xmms at the moment, any additional sound output will be delayed
> > > until I stop xmms. Is there any workaround? 
> > > 
> > > Using Intel(r) AC'97 Audio Controller - Sigmatel 9723 Codec
> > 
> > the intel chip supports only one stream for playback, so the
> > succeeding open is blocked since ALSA opens the device in the blocking
> > mode as default.  and it's so for OSS-emulation, too.
> > 
> > for the oss-emulation, you can change this behavior via the module
> > option nonblock_open of snd-pcm-oss module.  please check
> > Documentation/sound/alsa/OSS-Emulation.txt.
> 
> Wouldn't esd (the enlightment sound daemon) take care of this in
> userspace? I can have sound out of xmms, firebird, mpg321 and mplayer at
> the same time with esd.

of course, it does.
not only esd but arts can.

also, ALSA provides dmix plugin, which does the similar mixing but
without server process in very low latency.  unfortunately, using dmix
plugin for OSS apps is tricky.


Takashi

  parent reply	other threads:[~2003-07-17 11:18 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-16 22:58 2.6 sound drivers? Robert L. Harris
2003-07-16 23:10 ` Rudo Thomas
2003-07-16 23:29   ` Robert L. Harris
2003-07-16 23:46     ` Rudo Thomas
2003-07-16 23:10 ` Mike Fedyk
2003-07-16 23:30   ` Robert L. Harris
2003-07-16 23:39     ` Mike Fedyk
2003-07-16 23:46     ` David Ford
2003-07-17  0:08       ` Robert L. Harris
2003-07-17  1:07         ` Wes Janzen
2003-07-17  1:42         ` James H. Cloos Jr.
2003-07-17  7:26     ` Martin Schlemmer
2003-07-17  8:57       ` Eugene Teo
2003-07-17  9:22         ` Takashi Iwai
2003-07-17 11:19           ` Ookhoi
2003-07-17 11:31             ` Ed Sweetman
2003-07-17 12:10               ` Alan Cox
2003-07-17 13:11                 ` Ookhoi
2003-07-17 11:32             ` Takashi Iwai [this message]
2003-07-16 23:37 ` Jeff Garzik
2003-07-16 19:25   ` Max Valdez
2003-07-17  1:05     ` Jeff Garzik
2003-07-17  2:18       ` Norberto BENSA
2003-07-17 13:13         ` Ian Hastie
2003-07-17 13:25           ` Takashi Iwai
2003-07-17 13:19         ` Terje Kvernes
2003-07-17 16:08           ` Norberto BENSA
2003-07-17 11:22             ` Max Valdez
2003-07-17 16:54             ` Takashi Iwai
2003-07-17 18:43               ` Norberto BENSA
2003-07-17 19:44               ` Ian Hastie
2003-07-18  9:45                 ` Takashi Iwai
2003-07-17 18:46             ` dacin
2003-07-17 19:12               ` MONOLITHIC sound (was Re: 2.6 sound drivers?) Douglas J Hunley
2003-07-17 20:09                 ` dacin
2003-07-16 23:39   ` 2.6 sound drivers? Robert L. Harris
2003-07-16 23:57     ` Matt Reppert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5hfzl5z8uu.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=eugene.teo@eugeneteo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ookhoi@humilis.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).