From: Pete Black <pete@claudia.daemon.sh>
To: alsa-devel@lists.sourceforge.net
Subject: ALSA 'share' device, or 'software multi-open'
Date: Mon, 30 Sep 2002 12:46:11 +1200 [thread overview]
Message-ID: <3D979ED3.3050205@claudia.daemon.sh> (raw)
Hi there,
I am interested in knowing what ALSA's current support is for a
'software multi-open' driver/plugin, that can take the output of several
streams, mix them together in realtime and play them out to the soundcard.
From browing the list archives, I come across several references to a
'share' plugin, but also several references to the fact that the author
of the plugin is the only one who has ever actually used it.
I am aware of esd/arts/JACK etc., but none of these projects do what I
would like to have - a simple, lowish-latency, application-transparent
method of sharing a sound card.
I have also seen posts on the same alsa-devel mailing list to the effect
that mixing several audio streams in software is easy, and an
application-level problem hence the lack of implementation in ALSA
itself. I think that idea is ludicrous, and this type of sharing is
absolutely necessary, especially when using Linux to make music with the
variety of software synths that are now available.
Specifically, I have a CMI8738 card, and I want to be able to run seq24
(MIDI sequencer),and a couple of separate software synths at the same time.
I understand that drivers such as the SBLive and trident support
multi-open, passing the streams to the hardware for mixing, but why does
there seem to be no way to do the same thing with software?
ESD doesn't seem to put any appreciable load on the system, and network
transparency is not really a requirement, at least for me.
Does ALSAs architecture make doing this in software at the driver/plugin
level difficult, or is it just that nobody wants this capability?
And, should it be that this functionality is simply not implemented,
what would be the best way to approach building in this capability - the
plugin API, an extended, card-specific driver, or what?
Thanks
-Pete
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next reply other threads:[~2002-09-30 0:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-30 0:46 Pete Black [this message]
[not found] <20020930020414.90EFD6876@claudia.daemon.sh>
2002-09-30 3:54 ` ALSA 'share' device, or 'software multi-open' Pete Black
2002-09-30 4:43 ` Patrick Shirkey
-- strict thread matches above, loose matches on Subject: below --
2002-09-30 13:08 Patrick Shirkey
[not found] <20020930123444.5C7846875@claudia.daemon.sh>
2002-09-30 22:11 ` Pete Black
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=3D979ED3.3050205@claudia.daemon.sh \
--to=pete@claudia.daemon.sh \
--cc=alsa-devel@lists.sourceforge.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.