From: "Ivica Bukvic" <ico@fuse.net>
To: 'Paul Davis' <pbd@op.net>
Cc: alsa-devel@alsa-project.org
Subject: RE: What is the current status of the alsa sound server (signal polling)?
Date: Fri, 19 Apr 2002 18:15:59 -0400 [thread overview]
Message-ID: <000101c1e7ef$c91178d0$ac1f830a@ico> (raw)
In-Reply-To: <200204191659.g3JGxPT15571@post2.fast.net>
Hmmm, but it seems that on their website docs they mention that you can
use oss-sink and other audio routing in order to provide audio routing,
so I was wondering if I could use that for my purposes...
Ico
> -----Original Message-----
> From: Paul Davis [mailto:pbd@op.net]
> Sent: Friday, April 19, 2002 1:02 PM
> To: Ivica Bukvic
> Cc: alsa-devel@alsa-project.org; alsa-user@alsa-project.org
> Subject: Re: [Alsa-devel] What is the current status of the alsa sound
> server (signal polling)?
>
> I meant to add:
>
> >Also, what is the current status of gstreamer in this department and
>
> gstreamer has nothing to do with this. gstreamer is an internal
> architecture/framework for a single application and has nothing to do
> with sharing audio interfaces or audio data with other processes.
>
> --p
next parent reply other threads:[~2002-04-19 22:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200204191659.g3JGxPT15571@post2.fast.net>
2002-04-19 22:15 ` Ivica Bukvic [this message]
2002-04-20 1:00 ` What is the current status of the alsa sound server (signal polling)? Andy Wingo
[not found] <20020419165659.NXSI388.mta01.fuse.net@newmx1.fast.net>
2002-04-19 22:14 ` Ivica Bukvic
[not found] <20020419165711.C6B2C47B24@audio13.medien.uni-weimar.de>
2002-04-19 22:05 ` joy ping
[not found] <000101c1e766$39a37a60$ac1f830a@ico>
2002-04-19 14:03 ` joy ping
2002-04-19 15:52 ` Ivica Bukvic
2002-04-19 16:40 ` joy ping
2002-04-19 16:59 ` Paul Davis
2002-04-19 17:00 ` Paul Davis
2002-04-19 17:01 ` Paul Davis
2002-04-19 5:51 Ivica Bukvic
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='000101c1e7ef$c91178d0$ac1f830a@ico' \
--to=ico@fuse.net \
--cc=alsa-devel@alsa-project.org \
--cc=pbd@op.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.