AlsaProject - User contributions [en]

Matrix:Vendor-Cyrix

2007-08-14T21:13:14Z

Ash: New page: ==Soundcard List for Cyrix== {| class="MatrixTable" ! Product ! Chipset(s) ! Driver & Docs ! Tags, Notes |- | {| class="MatrixTableInner" | CS5530 (VSA1) |- |} | {| class="MatrixTable...

==Soundcard List for Cyrix==

{| class="MatrixTable"
! Product
! Chipset(s)
! Driver & Docs
! Tags, Notes
|-
|
{| class="MatrixTableInner"
| CS5530 (VSA1)
|-
|}
|
{| class="MatrixTableInner"
| CS5530 (VSA1)
|}
| [[Matrix:Module-cs5530|Details]]
| [[Matrix:Tag-PCI|[PCI]]]
|-
|
{| class="MatrixTableInner"
| CS5530 (VSA2)
|-
|}
|
{| class="MatrixTableInner"
| CS5530 (VSA2)
|}
|
| [[Matrix:Tag-PCI|[PCI]]]
|-
|}
{{Matrix:VendorEnd}}

Documentation

2007-08-11T15:12:56Z

Ash: /* System Maintainers Info */

{| align="right"
| __TOC__
|}

== User Info ==

*[[ALSA User Info]]
*[http://www.agnula.info/documentation/dp_tutorials/alsa_jack_ladspa/ Overview of ALSA]
*Hardware Recommendations
*[http://lau.linuxaudio.org/ Linux Audio Users Guide]

== System Maintainers Info ==

*[[System Maintainers documentation]]

*[[Matrix:Main|Sound Card Matrix & INSTALL documentation]]
*[http://alsa.opensrc.org/ The Unofficial ALSA Wiki]
*The latest [http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/alsa/alsa-driver/INSTALL INSTALL] file
*kerndriv Updating ALSA Kernel drivers
*olddocs Older documents
*[http://www.alsa-project.org/alsa-doc/doc-php/asoundrc.php?company=Generic&card=Generic&chip=Generic&module=Generic .asoundrc]
*Kernel Module overview(snd, virmidi, etc..)

== Tools ==

*alsactl
*amixer, alsamixer
*aplay/arecord
*aconnect, aseqnet
*envy24control
*hdsploader, hdspmixer
*vxloader

== Developer Info ==

*[[ALSA Library API]]
*[[ALSA Driver Documentation]]
*[[Tutorials and Presentations]]
*[[ALSA 0.9.x Developer documentation]]
*[http://hg-mirror.alsa-project.org/ HG (Mercurial) Repositories]
*[[ALSA contributors]]

== Hardware Manufacturers ==

*[[ALSA Soundcard Vendor Information|Getting support for your hardware.]]

Download

2007-08-11T14:59:10Z

Ash: /* Remove dead link */

{| align="right"
| __TOC__
|}
==Latest Software Source Releases==
{| border="1" cellspacing="0" cellpadding="5"
! Package
! Stable Release
(2007-06-11)
! Development Release
! Description
|-
| [ftp://ftp.alsa-project.org/pub/driver/ Driver ({{ALSA download package|module=driver}})]
| {{ALSA download file|module=driver|release=stable|short=true}}
| {{ALSA download file|module=driver|release=development|short=true}}
| Kernel drivers
|-
| [ftp://ftp.alsa-project.org/pub/firmware/ Firmware {{ALSA download package|module=firmware}})]
| {{ALSA download file|module=firmware|release=stable|short=true}}
| {{ALSA download file|module=firmware|release=development|short=true}}
| Firmware for cards that require it
|-
| [ftp://ftp.alsa-project.org/pub/lib/ Library ({{ALSA download package|module=lib}})]
| {{ALSA download file|module=lib|release=stable|short=true}}
| {{ALSA download file|module=lib|release=development|short=true}}
| Userspace library
|-
| [ftp://ftp.alsa-project.org/pub/plugins/ Plugins ({{ALSA download package|module=plugins}})]
| {{ALSA download file|module=lib|release=stable|short=true}}
| {{ALSA download file|module=lib|release=development|short=true}}
| Additional library plugins Eg.jack, pulse, maemo ...
|-
| [ftp://ftp.alsa-project.org/pub/utils/ Utilities ({{ALSA download package|module=utils}})]
| {{ALSA download file|module=utils|release=stable|short=true}}
| {{ALSA download file|module=utils|release=development|short=true}}
| Utilities aplay,arecord,amixer etc
|-
| [ftp://ftp.alsa-project.org/pub/tools/ Tools ({{ALSA download package|module=tools}})]
| {{ALSA download file|module=tools|release=stable|short=true}}
| {{ALSA download file|module=tools|release=development|short=true}}
| Tools
|-
| [ftp://ftp.alsa-project.org/pub/pyalsa/ PyALSA ({{ALSA download package|module=python}})]
| {{ALSA download file|module=python|release=stable|short=true}}
| {{ALSA download file|module=python|release=development|short=true}}
| Python bindings for ALSA lib
|-
| [ftp://ftp.alsa-project.org/pub/oss/ OSS compat lib ({{ALSA download package|module=oss}})]
| {{ALSA download file|module=oss|release=stable|short=true}}
| {{ALSA download file|module=oss|release=development|short=true}}
| OSS compatibility library
|-
|}

See [[ChangeLogs]] to find out what has changed since the previous release.

==<tt>.bz2</tt> extension handling==

The <tt>.bz2</tt> extension belongs to the bzip2 compression utility which replaces gzip. You may unpack the <tt>.tar.bz2</tt> files directly using one of the following commands:
''using the newer version of tar:''
<nowiki>tar xjf </nowiki>''<file>''

'''or''', ''using the older version of tar:''
<nowiki>tar xIf </nowiki>''<file>''

'''or''', ''with all versions of tar:''
<nowiki>bunzip2 -c </nowiki>''<file>''<nowiki> | tar xf -</nowiki>

==FTP Access==

'''Primary Site'''
*[ftp://ftp.alsa-project.org:/pub ftp.alsa-project.org:/pub]
'''US Mirrors'''
*[ftp://ftp.silug.org:/pub/alsa ftp.silug.org:/pub/alsa]
'''Europe Mirrors'''
*[ftp://ftp.task.gda.pl:/pub/linux/misc/alsa ftp.task.gda.pl:/pub/linux/misc/alsa]
*[ftp://gd.tuwien.ac.at:/opsys/linux/alsa gd.tuwien.ac.at:/opsys/linux/alsa]
*[ftp://ftp.iasi.roedu.net:/pub/mirrors/ftp.alsa-project.org ftp.iasi.roedu.net:/pub/mirrors/ftp.alsa-project.org]

==FTP via HTTP (web) access==

'''Europe Sites'''
*[http://dl.ambiweb.de/mirrors/ftp.alsa-project.org http://dl.ambiweb.de/mirrors/ftp.alsa-project.org]
*[http://alsa.mirror.fr http://alsa.mirror.fr]
*[http://gd.tuwien.ac.at/opsys/linux/alsa http://gd.tuwien.ac.at/opsys/linux/alsa]
*[http://alsa.cybermirror.org http://alsa.cybermirror.org]

==Developers: HG access==

*[http://hg-mirror.alsa-project.org/ HG Repository]

==(Unofficial) Daily Snapshot Tarballs==

The tarballs of the latest HG version with ready-for-build configure script are available at:
*[ftp://ftp.suse.com/pub/projects/alsa/snapshot/ Daily Snapshot]

==Tracker System==

*[https://bugtrack.alsa-project.org/alsa-bug Bugs]

==ALSA HG (Mercurial) SCM repositories==

HG (Mercurial) SCM can be found at http://www.selenic.com/mercurial.

The ALSA sources can be obtained using:
<nowiki>hg clone http://hg-mirror.alsa-project.org/alsa-driver alsa-driver</nowiki>
A full list of ALSA repositories can be found at the [http://hg-mirror.alsa-project.org/ HG Repository].

As an alternative to HG you may also try via rsync access:
<nowiki>rsync -avz --delete rsync://alsa.alsa-project.org/hg </nowiki>''your_directory''

To get the latest code, but without the .hg repository (encouraged if you are not using HG):
<nowiki>rsync -avz --delete --exclude=.hg* rsync://alsa.alsa-project.org/hg </nowiki>''your_directory''

==Rsync==

{| border=1
|+ ''ALSA rsync access''
|URL
|rsync://alsa.alsa-project.org/ftp
|-
|Access
|read-only
|-
|Description
|read-only access to the whole FTP tree
|}

Download

2007-08-11T14:53:04Z

Ash: /* Remove dead links */

{| align="right"
| __TOC__
|}
==Latest Software Source Releases==
{| border="1" cellspacing="0" cellpadding="5"
! Package
! Stable Release
(2007-06-11)
! Development Release
! Description
|-
| [ftp://ftp.alsa-project.org/pub/driver/ Driver ({{ALSA download package|module=driver}})]
| {{ALSA download file|module=driver|release=stable|short=true}}
| {{ALSA download file|module=driver|release=development|short=true}}
| Kernel drivers
|-
| [ftp://ftp.alsa-project.org/pub/firmware/ Firmware {{ALSA download package|module=firmware}})]
| {{ALSA download file|module=firmware|release=stable|short=true}}
| {{ALSA download file|module=firmware|release=development|short=true}}
| Firmware for cards that require it
|-
| [ftp://ftp.alsa-project.org/pub/lib/ Library ({{ALSA download package|module=lib}})]
| {{ALSA download file|module=lib|release=stable|short=true}}
| {{ALSA download file|module=lib|release=development|short=true}}
| Userspace library
|-
| [ftp://ftp.alsa-project.org/pub/plugins/ Plugins ({{ALSA download package|module=plugins}})]
| {{ALSA download file|module=lib|release=stable|short=true}}
| {{ALSA download file|module=lib|release=development|short=true}}
| Additional library plugins Eg.jack, pulse, maemo ...
|-
| [ftp://ftp.alsa-project.org/pub/utils/ Utilities ({{ALSA download package|module=utils}})]
| {{ALSA download file|module=utils|release=stable|short=true}}
| {{ALSA download file|module=utils|release=development|short=true}}
| Utilities aplay,arecord,amixer etc
|-
| [ftp://ftp.alsa-project.org/pub/tools/ Tools ({{ALSA download package|module=tools}})]
| {{ALSA download file|module=tools|release=stable|short=true}}
| {{ALSA download file|module=tools|release=development|short=true}}
| Tools
|-
| [ftp://ftp.alsa-project.org/pub/pyalsa/ PyALSA ({{ALSA download package|module=python}})]
| {{ALSA download file|module=python|release=stable|short=true}}
| {{ALSA download file|module=python|release=development|short=true}}
| Python bindings for ALSA lib
|-
| [ftp://ftp.alsa-project.org/pub/oss/ OSS compat lib ({{ALSA download package|module=oss}})]
| {{ALSA download file|module=oss|release=stable|short=true}}
| {{ALSA download file|module=oss|release=development|short=true}}
| OSS compatibility library
|-
|}

See [[ChangeLogs]] to find out what has changed since the previous release.

==<tt>.bz2</tt> extension handling==

The <tt>.bz2</tt> extension belongs to the bzip2 compression utility which replaces gzip. You may unpack the <tt>.tar.bz2</tt> files directly using one of the following commands:
''using the newer version of tar:''
<nowiki>tar xjf </nowiki>''<file>''

'''or''', ''using the older version of tar:''
<nowiki>tar xIf </nowiki>''<file>''

'''or''', ''with all versions of tar:''
<nowiki>bunzip2 -c </nowiki>''<file>''<nowiki> | tar xf -</nowiki>

==FTP Access==

'''Primary Site'''
*[ftp://ftp.alsa-project.org:/pub ftp.alsa-project.org:/pub]
'''US Mirrors'''
*[ftp://ftp.silug.org:/pub/alsa ftp.silug.org:/pub/alsa]
'''Europe Mirrors'''
*[ftp://ftp.task.gda.pl:/pub/linux/misc/alsa ftp.task.gda.pl:/pub/linux/misc/alsa]
*[ftp://gd.tuwien.ac.at:/opsys/linux/alsa gd.tuwien.ac.at:/opsys/linux/alsa]
*[ftp://ftp.iasi.roedu.net:/pub/mirrors/ftp.alsa-project.org ftp.iasi.roedu.net:/pub/mirrors/ftp.alsa-project.org]

==FTP via HTTP (web) access==

'''Primary Site'''
*[http://www.alsa-project.org/alsa/ftp http://www.alsa-project.org/alsa/ftp]
'''Europe Sites'''
*[http://dl.ambiweb.de/mirrors/ftp.alsa-project.org http://dl.ambiweb.de/mirrors/ftp.alsa-project.org]
*[http://alsa.mirror.fr http://alsa.mirror.fr]
*[http://gd.tuwien.ac.at/opsys/linux/alsa http://gd.tuwien.ac.at/opsys/linux/alsa]
*[http://alsa.cybermirror.org http://alsa.cybermirror.org]

==Developers: HG access==

*[http://hg-mirror.alsa-project.org/ HG Repository]

==(Unofficial) Daily Snapshot Tarballs==

The tarballs of the latest HG version with ready-for-build configure script are available at:
*[ftp://ftp.suse.com/pub/projects/alsa/snapshot/ Daily Snapshot]

==Tracker System==

*[https://bugtrack.alsa-project.org/alsa-bug Bugs]

==ALSA HG (Mercurial) SCM repositories==

HG (Mercurial) SCM can be found at http://www.selenic.com/mercurial.

The ALSA sources can be obtained using:
<nowiki>hg clone http://hg-mirror.alsa-project.org/alsa-driver alsa-driver</nowiki>
A full list of ALSA repositories can be found at the [http://hg-mirror.alsa-project.org/ HG Repository].

As an alternative to HG you may also try via rsync access:
<nowiki>rsync -avz --delete rsync://alsa.alsa-project.org/hg </nowiki>''your_directory''

To get the latest code, but without the .hg repository (encouraged if you are not using HG):
<nowiki>rsync -avz --delete --exclude=.hg* rsync://alsa.alsa-project.org/hg </nowiki>''your_directory''

==Rsync==

{| border=1
|+ ''ALSA rsync access''
|URL
|rsync://alsa.alsa-project.org/ftp
|-
|Access
|read-only
|-
|Description
|read-only access to the whole FTP tree
|}

ALSA Soundcard Vendor Information

2007-08-11T14:32:21Z

Ash: /* Remove some dead links */

{| align="right"
| __TOC__
|}

== Author: The ALSA Development Team ==

maintained by Christopher David (cdavid at ketl.com)<br>
additions by Patrick Shirkey (pshirkey at boosthardware.com)

last updated: April 12, 2002

== Abstract ==

This document outlines information that soundcard vendors need in
order to be compatible with ALSA and Linux at large. It is targeted
mainly for companies that design and sell soundcard hardware. It may
also be useful to new ALSA developers who desire a background about
information they get from a given soundcard vendor.

== Background ==

ALSA stands for Advanced Linux Sound Architecture.
Its main goal is just what its title says, to create an advanced sound architecture for Linux.
ALSA is committed to being released under the [http://www.gnu.org/copyleft/gpl.html Gnu GPL].
The scope of the project extends from the low level soundcard drivers, all the way up to a high level sequencer.
This document is mainly concerned with what is needed to develop the low level soundcard drivers.

ALSA is the sound driver subsystem of the mainstream Linux kernel. ALSA is fully compatible with OSS/Lite Mixer and PCM
interfaces. ALSA offers better native interfaces that new applications can use.

== What we need to write good drivers ==

ALSA developers need several things to write good drivers. We need:

*good documentation
*necessary firmware
*a way to get additional information if needed
*example source code is helpful

Good documentation is needed before ALSA developers can write good
drivers. Basically, we need to know everything that anyone else
writing a driver would need to know. Most of the information we need
should be in the data sheets of each chip. We also need to have a
memory map of all the chips, and any additional registers that may not
be included in other data sheets.

It is important that the firmware for a given soundcard is made
available to us. By firmware, we mean code that would be downloaded to
a piece of hardware that is necessary for it to function. i.e. code
running on some DSP chip that is located on the soundcard. This would
not be code that runs on the host system. (Host system is the one
running Linux.) It is important that there are no distribution
restrictions on the firmware. We must be able to freely distribute the
firmware code as part of ALSA. We would like the source code for
firmware. It is not required that it is given to us, but we are
definitely willing to accept it.

We also may need some additional information about how the sound
card works. This varies a lot from card to card. For example, if a
programmable PLL needs to be programmed to a certain frequency before
the card will function, we need to know this. If your company can
appoint a contact person for additional information, that would be
great! Generally, we do not have very many questions. We are used to
developing drivers on our own. We will not be taking up much of that
person's time.

We would also like any example source code that could be given to
us. Obviously this is not as important as the other issues. But
example source code can often be helpful, especially for parts that
are poorly documented.

== Our view of NDAs ==

Unfortunately, ALSA developers generally do not want to sign
non-disclosure agreements, or NDAs. It is possible that a few ALSA
developers could individually sign these types of agreements, but that
would have to be worked out on an individual developer basis. It has
happened in the past. We do not recommend the use of NDAs at all,
because one way or another, they restrict our development effort. It
should be possible to give ALSA developers the information they need
without requiring an NDA. Many companies regularly do this.

Our big problem is with NDAs that restrict the release of our
source code. Since ALSA is released under the Gnu GPL, all of our
source code is made publicly available. Agreeing to an NDA that
requires binary-only distribution of our code conflicts with the Gnu
GPL. Thus we cannot agree at all to NDAs that restrict the release of
our source code. Besides, binary only versions of kernel drivers just
does not work very well in Linux.

Another type of NDA would restrict soundcard documentation to a
small group of people. This type of NDA is at least feasible, but it
still restricts our development effort. The problem is that only those
persons covered under the NDA may be capable of fixing bugs and
providing new features for that card. Often, people from all over the
world send patches to our code. We want all these people to have
access to the documentation. It hurts our project when some people, who
are very capable of sending patches, will not be able to write them in
the first because of lack of documentation.

== Why soundcard documentation should be public ==

There are several reasons why your company would want to give us the
information we request. The most important reason is that it will help
your company sell more cards! Many times Linux users ask us which
cards we support. We tell them, and they go buy these
cards. Obviously, the only cards we can support are those we can get
good documentation for.

Also, by making your soundcard documentation public, you really
have contributed something to the Linux development effort. That
should give you a good, warm, fuzzy feeling inside.

There other reasons too. First, other operating systems will have
an easier time supporting your hardware. Second, many developers will
be able to double check our driver, making it very robust. In the end,
this makes your hardware look good. Also, people interested in doing
custom things with your hardware will be able to, giving you another
venue for sales.

With the user base of Linux growing so rapidly, can your company
really afford not to support ALSA and make your soundcard
documentation public? We are not asking for your corporate secrets
here. We are not asking for the Verilog source code for each chip in
your product. We are not asking for schematics, gerber plots, or
anything like that. We just need basic information that enables us to
write a good sound driver.

== Views on Binary Only drivers ==

ALSA does not stop anybody from releasing binary-only drivers. But
ALSA does not support nor encourage these drivers either. The stance
that ALSA takes on binary-only sound card drivers is similar to
Linus's stance on binary-only drivers in the kernel. There is an
[http://lwn.net/1999/0211/kernel.phtml article in the Linux Weekly News]
about this. There are additional requirements that ALSA places on
binary only drivers beyond Linus's view.

Linus Torvalds, leader of the Linux development effort, has stated
that because binary-only drivers depend so heavily on a given kernel
version, and therefore are so prone to "breaking" when kernel
development proceeds, as it is bound to do, he does not intend to
support nor encourage the use of binary-only loadable drivers.

If Linux developers were to try to maintain compatibility with a given
binary-only driver, it would severely limit the avenues of
development open to Linux. Our goal in Linux development is to
achieve the highest performance, the best stability (in terms of bug
free code), and the most advanced technology possible.

We simply cannot be made subject to the limitations that would be
placed on us by having to maintain compatibility with a third party
binary-only loadable module.

We, the ALSA development team, working as a subset of Linux kernel
developers, agree with Linus Torvalds' reasoning. And this is the very
crux of why we ask you for documentation on your hardware. We truly
want to purchase and use your hardware in our Linux based systems, but
we simply cannot use binary-only drivers; it's just too cumbersome and
frustrating for all involved. Drivers that could be distributed as
source code would eliminate all of those problems.

There is nothing to stop any company from developing a binary only
driver that works with ALSA. But there are several issues and
requirements we want to make clear to anybody attempting to do this.

*Binary-only drivers will not be distributed as part of ALSA, even when ALSA becomes part of the mainstream kernel. That means any company releasing binary only drivers will have to find alternative distribution mechanisms. They cannot rely directly on ALSA for this. The main implication of this is ALSA will work "out of the box" with all sound cards, except for unsupported cards.

*Users of binary only dirvers must be instructed not use ALSA for technical support whatsoever! These users must be notified with the following notice.
"These drivers are not part of the official ALSA distribution. ALSA will
never support these drivers. DO NOT attempt to contact ALSA for support."

*The end user MUST always confirm this notice by downloading, or unpacking the drivers. There must also be some contact listed that is available for technical support. ALSA resources must not be listed anywhere as avenues for support.

*Binary-only drivers cannot be based on any ALSA source code. They must be written from scratch. Binary-only drivers that contain ALSA code are infringing on copyright laws.

*The developer assumes full responsibility for ensuring the driver works accross new versions of ALSA, different kernels, and different platforms. If we change ALSA, and a binary-only driver cease to work because of it, we will not do anything to fix it.

All our drivers are distributed in source form. The single source
file works with all kernel versions, all platforms, and all ALSA
versions. There is only one source for us to maintain and
support. (Elegant, isn't it?) We really like it that way. Drivers
distributed in binary form may require multiple builds, even though
the source does not need to change. Obviously different binaries are
needed for different platforms. In addition, it is possible that
different binaries are even needed for the same platform depending on
the kernel version, or ALSA version.

This may not be as bad as it seems. Once ALSA reaches version 1.0,
the same binary may work across multiple kernel and ALSA releases. But
we are not making any promises. Again, all of these problems go away
when the driver source is released under GPL to the public.

We do understand that sometimes companies feel compelled to hide
their hardware implementations by not releasing the driver source.
The general Linux user base most likely prefers that any driver is
available for a given piece of hardware rather than no driver. So
please do not let ALSA's stance on binary only drivers deter your
company from releasing one. Since ALSA is open source and is
documented, everything you need to write binary only drivers is
available. We are not out to stop you, but we can not make any
promises that your binary driver will work across all future releases
of ALSA.

== Summary ==

ALSA wants to support your soundcard hardware. We have something
really good here that we think should run on all sound cards. It is a
well thought out, open sound architecture that is capable of
supporting the needs of musicians, audiophiles, game players, home and
business users alike. It has easy-to-use APIs. It provides a level of
modularity and flexibility never seen before in a sound
architecture. There are many great minds collaborating on ALSA, and
even though it is currently in the very early stages, so far the
results are outstanding. As a soundcard manufacturer, ask yourself one
question. Do I want to be part of something great?

Thanks, <br>
The ALSA development team

== Related links ==

*[http://www.precisioninsight.com/alspaper.html Managing Graphics Hardware Vendor Relationships in the Linux Developer Community]
*[http://www.news.com/News/Item/0,4,30027,00.html Linux shipments up 212 percent]
*[http://www.heise.de/newsticker/data/odi-13.01.99-000/ Microsoft sieht Linux pro Jahr um 960 Prozent wachsen]
*[[ALSA Blacklist]] Cards for which necessary information is not available to enable driver development
*[http://www.gnu.org/copyleft/gpl.html Gnu General Public License]
*[http://lwn.net/1999/0211/kernel.phtml Linux Weekly News article concerning recent binary-only drivers in Linux]
*[http://www.kroah.com/log/linux/free_drivers.html Greg Kroah-Hartman offers free driver development]

Applications

2007-08-11T14:26:55Z

Ash: /* Fixed a small typo */

{| align="right"
| __TOC__
|}

==Introduction==
The ALSA driver is fully compatible with OSS/Lite Mixer and PCM interfaces, so probably all OSS (Open Sound System) applications which use these interfaces should work. The ALSA driver offers better native interfaces, and many applications now offer native support.
If your Application is not mentioned, please edit this page and add it.

==Applications==

===Compatible===

All OSS applications should work with ALSA through the OSS emulation layer.

===Native (0.9.0)===
{| width="100%"
! style="background:#BBBBBB;" align="center" | '''Name'''
! style="background:#BBBBBB;" align="center" | '''Description'''
|-
|[http://www.iua.upf.es/~mdeboer/projects/aconnectgui/ aconnectgui]
|aconnectgui is a FLTK based frontend for aconnect
|-
|[http://www.iua.upf.es/~mdeboer/projects/alsamixergui/ AlsaMixerGui]
|fltk based alsamixer frontend
|-
|[http://pkl.net/~node/alsa-patch-bay.html ALSA Patch Bay]
|A graphical patch bay app for the ALSA sequencer API. Supports FLTK 1.1 and GTKmm 2.
|-
|[http://www.alsaplayer.org AlsaPlayer]
|MP3/WAV/MOD/others Real-Time player
|-
|[http://savannah.nongnu.org/download/alsa-xmms/ alsa-xmms]
|ALSA plugin for XMMS. Integrated in next XMMS release(after 03/23/03).
|-
|[http://perso.wanadoo.es/plcl/ametro/ametro-en.html ametro]
|ALSA MIDI Metronome. This program is a little, simple MIDI Metronome using the ALSA sequencer, made in Kylix.
|-
|[http://amsynthe.sourceforge.net amSynth]
|a real-time, polyphonic, Analogue Modelling SYNTHesizer
|-
|[http://ardour.sourceforge.net Ardour]
|Multitrack Digital Audio for Linux
|-
|[http://members.tripod.de/iwai/alsa.html ASeqView]
|ALSA sequencer event viewer
|-
|[http://www.slabexchange.org/index.cgi?DOWNLOAD Bristol Synthesiser]
|Bristol Synthesiser emulation package
|-
|[http://ccrma-www.stanford.edu/software/clm/ CLM]
|Common Lisp Music is a music synthesis and signal processing package
|-
|[http://web.tiscali.it/mupuxeddu/csound/index.html Unofficial Csound for Linux]
|Csound is a software synthesis package in the tradition of so-called music-N languages
|-
|[http://www.wakkanet.fi/~kaiv/ecamegapedal/ ecamegapedal]
|graphical a realtime audio processor
|-
|[http://www.wakkanet.fi/~kaiv/ecasound/ ecasound]
|harddisk recording, audio processing etc..
|-
|[http://www.wakkanet.fi/ecawave/ ecawave]
|graphical sound file editor
|-
|[http://ftp.gnome.org/pub/GNOME/stable/sources/esound/ Esound 0.2.25]
|The Enlightened Sound Daemon mixes several audio streams for playback by a single audio device
|-
|[http://www.maysl.at/ fische]
|Fische provides standalone sound visualisation under linux using the ALSA and SDL libraries
|-
|[http://www1.tcnet.ne.jp/fmurata/linux/down/ gamix]
|Another GTK ALSA mixer
|-
|[http://gephex.org gephex]
|GePhex is a modular video effect framework. We support a wide range of input devices like soundcards, joysticks, webcams and midi-devices.
|-
|[http://genpo.sourceforge.net/ GENPO]
|The GENeral Purpose Organ - emulates many pipe, theatre and reed organs.
|-
|[http://glame.sourceforge.net GLAME]
|Gnu/Linux Audio Mechanics sound editor and filter network GUI
|-
|[http://www.paw.co.za/projects/gnome-alsamixer/ GNOME ALSA Mixer]
|An audio mixer for GNOME which supports ALSA 0.9.x.
|-
|[http://www.gstreamer.net/ Gstreamer]
|a development framework for creating applications like media players, video editors, streaming media broadcasters
|-
|[http://www.hanappe.org/iiwusynth.html iiwusynth]
|IIWU Synth is a software, real-time synthesizer
|-
|[http://jackit.sourceforge.net JACK]
|Jack Audio Connection Kit
|-
|[http://www.jazzware.com JAZZ++]
|A full size midi sequencer
|-
|[http://www.ircam.fr/jmax jMax]
|A visual programming environment for interactive real-time music and multimedia
|-
|[http://www.suse.de/~mana/kalsatools.html Kalsatools]
|Kalsatools: AlsaModularSynth, Kaconnect, and KWaveView
|-
|[http://www.parabola.demon.co.uk/melys/ Melys]
|Melys Midi sequencer
|-
|[http://www.iki.fi/ik/mpegspdif.html Mpegspdif]
|Utility that can be used in sending MPEG-audio through S/PDIF interface to some external decoder that supports IEC 61937 for MPEG
|-
|[http://www.mplayerhq.hu/homepage/ Mplayer]
|Movie Player for Linux
|-
|[http://muse.seh.de/ MusE]
|MusE is a MIDI/Audio sequencer with recording and editing capabilities
|-
|[http://osw.sourceforge.net Open Sound World]
|OSW is an open-source environment for real-time music-event and signal processing. A graphical-patching environment and a command-line "server" mode are available for Linux/ALSA.
|-
|[http://www.pure-data.org/ Pd]
|Pd is a real-time software system for live musical and multimedia performances
|-
|[http://www.core-sound.com/pdaudio-alsa-20031001.tar.gz PDAudio Recorder (Linux)]
|PDAudio Recorder (Linux) is an application intended to be run on HP iPAQ PDAs running the Linux/Familiar distribution. See Core Sound's web site for more information: http://www.core-sound.com
|-
|[http://www.parabola.demon.co.uk/alsa/pmidi.html pmidi]
|pmidi is a program to play midi files through the ALSA sequencer
|-
|[http://www.nongnu.org/protux/ Protux]
|A practical and powerful audio tool using the power of keyboard+mouse combination (without clicks) to speed up the process of audio production.
|-
|[http://www.kwintv.org qtvision]
|KDE application to watch TV on the desktop.
|-
|[http://www.all-day-breakfast.com/rosegarden/ Rosegarden]
|Integrated MIDI sequencer and musical notation editor
|-
|[http://www.libsdl.org/ SDL]
|Simple DirectMedia Layer is a cross-platform multimedia library
|-
|[http://www.filter24.org/seq24/ Seq24]
|Seq24 is a real-time midi sequencer for live techno performance.
|-
|[http://www.cs.berkeley.edu/~lazzaro/sa/sfman/index.html sfront]
|A translator that converts MP4-SA files into efficient C programs that generate audio
|-
|[http://simsam.sourceforge.net simsam]
|simsam plays MIDI-triggered samples via ALSA or JACK
|-
|[http://ccrma-www.stanford.edu/software/snd/ Snd]
|Snd is a sound editor
|-
|[http://ccrma-www.stanford.edu/software/snd/sndlib SndLib]
|SndLib is a library of sound-related functions
|-
|[http://www.soundtracker.org SoundTracker]
|music tracker for X / GTK+
|-
|[http://squeak.org/ Squeak]
|Squeak is an open, highly-portable Smalltalk-80 implementation whose virtual machine is written entirely in Smalltalk.
|-
|[http://www.iua.upf.es/~mdeboer/projects/tapiir/ tapiir]
|a software multi-tap-delay, real-time sound processing application
|-
|[http://tcvp.sourceforge.net TCVP]
|An all-purpose multimedia framework.
|-
|[http://terminatorX.cx terminatorX]
|terminatorX is a realtime audio synthesizer that allows you to "scratch" on digitally sampled audio data (*.wav, *.au, *.ogg, *.mp3, etc.) the way hiphop-DJs scratch on vinyl records.
|-
|[http://www.goice.co.jp/member/mo/timidity/ TiMidity++]
|MIDI to WAVE converter/player
|-
|[http://www.vislab.usyd.edu.au/staff/chris/tk707/ TK-707]
|A midi drum/rhythm sequencer based on Roland TR-x0x machines
|-
|[http://members.tripod.de/iwai/alsa.html Virtual Keyboard]
|Virtual Keyboard with the ALSA sequencer support
|-
|[http://cs.alfred.edu/~lansdoct/linux/xamixer2 XAMIXER2]
|GTK ALSA mixer
|-
|[http://xine.sourceforge.net/ xine]
|xine is a free, gpl-licensed video player for unix-like systems
|-
|[http://xlv.sourceforge.net XLV]
|Another light and fast development framework to build media players, converters, ...
|-
|[http://www.amb.org/xmcd Xmcd]
|Xmcd is the premier CD player/ripper program suite for UNIX and Linux platforms. For real-time CDDA playback, xmcd supports many architectures including native ALSA.
|-
|[http://zynaddsubfx.sourceforge.net/ ZynAddSubFX]
|ZynAddSubFX is a powerful realtime, multi-timbral software synthesizer.
|}

===Native (-0.5.0)===

{| width="100%"
! style="background:#BBBBBB;" align="center" | '''Name'''
! style="background:#BBBBBB;" align="center" | '''Description'''
|+'''*** NB 0.5 drivers and older are considered deprecated and are no longer supported by ALSA Developers ***'''
|-
|[http://www.foxproject.org/projects/infopages/mixer.html fOX Mixer]
|Windows 95 style mixer
|-
|[http://www.mygale.org/~miodrag/mikmod/ MikMod]
|module player (IT, XM, S3M, MTM, 669, STM, ULT, FAR, MED, MOD)
|-
|[http://www-ti.informatik.uni-tuebingen.de/~hippm/mpg123.html mpg123]
|player for MPEG-1 layer I, II, III files
|-
|[ftp://ftp.alsa-project.org/pub/apps/mbone/rat RAT]
|Robust Audio Tool (mbone conferencing tool)
|-
|[http://cs.alfred.edu/~lansdoct/linux/xamixer XAMIXER]
|GTK ALSA mixer
|-
|[http://bohemians.org/~iznogood/wmmixer-alsa/ WMMixer]
|WMMixer for AfterStep & WindowMaker
|-
|[http://www.ne.jp/asahi/i/yamahata/widi/index.html WIDI]
|MIDI player by Isaku Yamahata
|-
|[http://server.bohemians.org/~iznogood/ x11amp plugin]
|ALSA output plugin for x11amp
|-
|[http://server.bohemians.org/~iznogood/ xmms plugin]
|ALSA output plugin for xmms
|-
|[http://www.goice.co.jp/member/mo/timidity/ TiMidity++]
|MIDI to WAVE converter/player
|-
|[http://www.freeamp.org FreeAMP]
|Free Audio Music Player
|-
|[http://myy.helia.fi/~anttiner/kmikmod.html KMikMod]
|A mikmod version for the KDE desktop
|-
|[http://xmp.helllabs.org/ XMP]
|xmp is a free module player for UNIX
|-
|[http://fox.mit.edu/xsw/yiff/ YIFF]
|Sound server for games and applications
|}

Mailing-lists

2007-08-10T22:38:21Z

Ash: /* Archives on other hosts */

{| align="right"
| __TOC__
|}

== Big Warning ==

We have continuous problems with e-mail spammers. The ALSA server does not accept an e-mail from open relays. We are using the three databases to determine, if your relay is open or if your relay does not follow our policy. Please, do not complain directly to any ALSA administrator. Your messages will be silently ignored. Complete information is available:

* http://www.mail-abuse.org/rbl/ (spam hosts)
* http://www.mail-abuse.org/dul/ (dialup hosts)
* http://www.mail-abuse.org/rss/ (open relays)

== alsa-announce at alsa-project.org ==

The mailing list for ALSA related announcements of new releases and ALSA software. ''[open, moderated]''

[http://lists.sourceforge.net/lists/listinfo/alsa-announce Subscribe to alsa-announce here].

*[http://www.mail-archive.com/alsa-announce%40lists.sourceforge.net alsa-announce archive at mail-archive.com]
*[http://www.geocrawler.com/redir-sf.php?list=alsa-announce alsa-announce archive at geocrawler]

''To unsubscribe from the old alsa-announce mailing list, send an e-mail to < alsa-announce-request-old at alsa-project.org > with the body 'unsubscribe <email_address>'.''

== alsa-devel at alsa-project.org ==

The mailing list for ALSA developers. ''[open, unmoderated for subscribers, moderated for others]''

If you would like to work on the driver, library or an ALSA application [http://mailman.alsa-project.org/mailman/listinfo/alsa-devel subscribe to alsa-devel here].

*[http://mailman.alsa-project.org/pipermail/alsa-devel/ alsa-devel archive at mailman.alsa-project.org]
*[http://news.gmane.org/gmane.linux.alsa.devel alsa-devel archive at gmane.org]
*[http://www.mail-archive.com/alsa-devel%40lists.sourceforge.net alsa-devel archive at mail-archive.com]
*[http://www.geocrawler.com/lists/3/SourceForge/12349/0/ alsa-devel archive at geocrawler]
*[http://www.geocrawler.com/redir-sf.php?list=alsa-devel old alsa-devel archive at geocrawler]

== alsa-user at lists.sourceforge.net ==

The mailing list for ALSA users. ''[open, unmoderated for subscribers, moderated for others]''

If you need a help with the installation of ALSA packages etc [http://lists.sourceforge.net/lists/listinfo/alsa-user subscribe to alsa-user here].

*[http://news.gmane.org/gmane.linux.alsa.user alsa-user archive at gmane.org]
*[http://www.mail-archive.com/alsa-user%40lists.sourceforge.net alsa-user archive at mail-archive.com]
*[http://www.geocrawler.com/lists/3/SourceForge/12350/0/ alsa-user archive at geocrawler]
*[http://www.geocrawler.com/redir-sf.php?list=alsa-user old alsa-user archive at geocrawler]

''To unsubscribe from the old alsa-user mailing list, send an e-mail to < alsa-user-request-old at alsa-project.org > with the body 'unsubscribe <email_address>'.''

== alsa-cvslog at alsa-project.org ==

The mailing list for anyone. ''[open, receive only]''

If you want to receive the CVS commit information [http://lists.sourceforge.net/lists/listinfo/alsa-cvslog subscribe to alsa-cvslog here].

*[http://www.mail-archive.com/alsa-cvslog%40lists.sourceforge.net alsa-cvslog archive at mail-archive.com]

== alsa-conf at alsa-project.org ==

The mailing list for ALSAconf team members. ''[closed, unmoderated]''

If you want work on the configuration library and application, send message to Jaroslav Kysela < perex at suse.cz >.

*[http://www.alsa-project.org/archive/alsa-conf alsa-conf archives]

== alsa-doc at alsa-project.org ==

The mailing list for ALSA programmer's documentation team members. ''[closed, unmoderated]''

If you have any question about the ALSA programmer's documentation a suggestion to improve the programmer's documents, please, post an e-mail to the alsa-devel mailing list instead. If you want work on ALSA programmer's documentation, send message to Jaroslav Kysela < perex at suse.cz >.

*[http://www.alsa-project.org/archive/alsa-doc alsa-doc archives]

== Archives on other hosts ==

*[http://news.gmane.org/gmane.linux.alsa.user Archive for mailing list for ALSA users at gmane.org]
*[http://news.gmane.org/gmane.linux.alsa.devel/ Archive for mailing list for ALSA developers at gmane.org]

ALSA Blacklist

2007-08-10T21:49:46Z

Ash:

We are looking for programming information for the hardware listed below. Please, if you have any information, mail this information to [[Mailing-lists|alsa-devel mailing list]]. Thank you.

* SAA7785 (Thunderbird) - used in the Philips 'Edge' range. This chip is used in the PSC702/703/704/705/706 cards.

Please, look into [[ALSA Soundcard Vendor Information]] too.

Matrix:Vendor-Avance Logic

2007-05-06T01:47:15Z

Ash: /* Soundcard List for [http://www.avance.com Avance Logic] */

{{Matrix:VendorBegin}}

==Soundcard List for [http://www.avance.com Avance Logic]==

{| class="MatrixTable"
! Product
! Chipset(s)
! Driver & Docs
! Tags, Notes
|-
|
{| class="MatrixTableInner"
| ALS007
|-
|}
|
{| class="MatrixTableInner"
|}
| [[Matrix:Module-dt019x|Details]]
| [[Matrix:Tag-ISA|[ISA]]]
|-
|
{| class="MatrixTableInner"
| ALS100
|-
| ALS110
|-
| ALS120
|-
|}
|
{| class="MatrixTableInner"
|}
| [[Matrix:Module-als100|Details]]
| [[Matrix:Tag-ISA|[ISA]]]
|-
|
{| class="MatrixTableInner"
| ALS200
|-
|}
|
{| class="MatrixTableInner"
|}
|
| [[Matrix:Tag-Unknown|[Unknown]]] [[Matrix:Tag-ISA|[ISA]]]
|-
|
{| class="MatrixTableInner"
| ALS300
|-
|}
|
{| class="MatrixTableInner"
| ALS300
|}
| [[Matrix:Module-als300|Details]]
| [[Matrix:Tag-PCI|[PCI]]][[Matrix:Tag-48kHz|[48kHz]]]
|-
|
{| class="MatrixTableInner"
| ALS300+
|-
|}
|
{| class="MatrixTableInner"
| ALS300+
|}
| [[Matrix:Module-als300|Details]]
| [[Matrix:Tag-PCI|[PCI]]][[Matrix:Tag-48kHz|[48kHz]]]
|-
|
{| class="MatrixTableInner"
| ALS4000
|-
|}
|
{| class="MatrixTableInner"
| ALS4000
|-
|}
| [[Matrix:Module-als4000|Details]]
| [[Matrix:Tag-PCI|[PCI]]]
|}
{{Matrix:VendorEnd}}