All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Swanson <mark@WebServiceSolutions.com>
To: alsa-devel@lists.sourceforge.net
Subject: smix plugin available?
Date: Mon, 25 Nov 2002 20:16:47 -0500	[thread overview]
Message-ID: <200211252016.47211.mark@WebServiceSolutions.com> (raw)

Hello,

A gentleman by the name of Abramo Bagnara recently stated he may have some 
code that would kick-start the development of the smix plugin. I think this 
is a very useful and increasingly important component. Abramo stated he had 
no problem releasing it, but I could not find where or if he did so.

If Abramo - or anyone - could point me in the right direction I would 
appreciate it.

The reasons I'm looking for this is to solve the following problems with 
soundcards that do not have a hardware mixer:

When using Gnome/KDE (esd/arts) no programs can access the sound device unless 
they are written to use arts/esd/jack/etc...

It is not logical for every program to write support for esd, artsd, jack, 
alsa, etc. Programs should write to ALSA and let ALSA do software mixing if 
required. Windows provided this since DirectX (3?). Solaris provides this too 
(esd apparently doesn't block on Solaris).

I believe that the majority of sound cards in use (on Linux) do not have 
hardware mixing, and that this is already a large problem that will continue 
to get larger.

One of the big reasons this is affecting me is that Java sound will not work 
unless you have a hardware mixer. My understanding is that the Sun folks seem 
to think that it is wrong to have to implement many different ways to create 
sound when the sound library (ALSA) should do it for them - the way it works 
in Windows/Solaris. I completely agree with them.

Cheers.

-- 
Schedule your world with ScheduleWorld.com
http://www.ScheduleWorld.com/



-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T 
handheld. Power & Color in a compact size! 
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en

             reply	other threads:[~2002-11-26  1:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-26  1:16 Mark Swanson [this message]
2002-11-26  3:19 ` smix plugin available? Paul Davis
2002-11-26  3:54   ` Mark Swanson
2002-11-26  4:13     ` Paul Davis
2002-11-26  8:13       ` Frans Ketelaars
2002-11-26 12:33         ` Mark Swanson
2002-11-26 19:32   ` Florian Bomers
2002-11-26 23:11     ` Paul Davis
2002-11-27  0:54       ` Florian Bomers
2002-11-27  1:06       ` James Courtier-Dutton
2002-11-27  9:29         ` Jaroslav Kysela
2002-11-27 11:36           ` tomasz motylewski
2002-11-27 13:21             ` James Courtier-Dutton
2002-11-27 13:53             ` Paul Davis
2002-11-27 14:24             ` Jaroslav Kysela
2002-11-27 13:07           ` Avoiding xruns... was " James Courtier-Dutton
2002-11-27 13:55             ` Paul Davis
2002-11-27 13:42           ` Paul Davis
2002-11-27 15:21             ` Kai Vehmanen
2002-11-27 16:26             ` Jaroslav Kysela
2002-11-27 13:45           ` Paul Davis
2002-11-27 14:39             ` Jaroslav Kysela
     [not found] <20021127135012.7B5A559D353@kerberos.suse.cz>
2002-11-27 14:43 ` Jaroslav Kysela
2002-11-27 15:04   ` Paul Davis
     [not found] <200211271350.OAA22613@mail.bodensee.com>
2002-11-27 15:47 ` tomasz motylewski
2002-11-28 13:50   ` Paul Davis

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=200211252016.47211.mark@WebServiceSolutions.com \
    --to=mark@webservicesolutions.com \
    --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.