1 Dec
2003
1 Dec
'03
9:08 a.m.
As some of you already know I am the occasional webmaster/docs
maintainer for ALSA.
I have been planning some additions to the site to make it more
accessible but before I jump into anything that could be considered a
facelift I would like to get some opinions from y'all.
Can you tell me what things you would like to have on the website that
are not already there? What things have you noticed while using it that
are not user friendly?
I would like to add a database for some kind of card rating system.
What would you consider valuable things to rate a card against?
All opinions will be considered so don't hold back ;-]
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
Apparently upon the beginning of the barrage, the donkey broke
discipline and panicked, toppling the cart. At that point, the rockets
disconnected from the timer, leaving them strewn around the street.
Tethered to the now toppled cart, the donkey was unable to escape before
the arrival of U.S. troops.
United Press International
Rockets on donkeys hit major Baghdad sites
By P. MITCHELL PROTHERO
Published 11/21/2003 11:13 AM
1 Dec
1 Dec
9:31 a.m.
On Mon, 01 Dec 2003 22:06:50 +0900
Patrick Shirkey <pshirkey(a)boosthardware.com> wrote:
As some of you already know I am the occasional
webmaster/docs
maintainer for ALSA.
I have been planning some additions to the site to make it more
accessible but before I jump into anything that could be considered a
facelift I would like to get some opinions from y'all.
Can you tell me what things you would like to have on the website that
are not already there? What things have you noticed while using it
that are not user friendly?
I would like to add a database for some kind of card rating system.
What would you consider valuable things to rate a card against?
All opinions will be considered so don't hold back ;-]
I was astonished to see, that the website is not generated automagically
[i saw patches to the soundcard matrix, etc..]. I don't know much about
content management systems, etc, but i wonder if this wouldn't save
great hassles in the future..
Flo
--
music: http://www.soundclick.com/bands/9/florianschmidt.htm
11:44 a.m.
Florian Schmidt wrote:
I was astonished to see, that the website is not generated automagically
[i saw patches to the soundcard matrix, etc..]. I don't know much about
content management systems, etc, but i wonder if this wouldn't save
great hassles in the future..
Yes I have been thinking about it today too. The main thing is someone
has to roll up their sleeves. However I don't think it will be too much
work. I'm trying to decide if it should be a simple text based form or a
mysql database. Obviously the latter is more work but will be much
faster (if it matters).
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
Apparently upon the beginning of the barrage, the donkey broke
discipline and panicked, toppling the cart. At that point, the rockets
disconnected from the timer, leaving them strewn around the street.
Tethered to the now toppled cart, the donkey was unable to escape before
the arrival of U.S. troops.
United Press International
Rockets on donkeys hit major Baghdad sites
By P. MITCHELL PROTHERO
Published 11/21/2003 11:13 AM
12:09 p.m.
On Tue, 02 Dec 2003 00:42:56 +0900
Patrick Shirkey <pshirkey(a)boosthardware.com> wrote:
Florian Schmidt wrote:
Hmm, i thought of something simpler.. For example, each driver source
file could have a special section that contains the necessary infos for
the card matrix. Then a script to get the info from the source files and
puts it together to a html page would be enough.. This is only one
example, of course.. An sql database is probably overkill. We have
really static data here [after it's once generated]. Updates could then
be done like once a week or even daily which comes down to just running
a script that grabs the source from cvs and does its thing..
I don't know how easy this would be to create the rest of the docs but
some parts of it are already automated, like the api doc creation,
etc...
Flo
--
music: http://www.soundclick.com/bands/9/florianschmidt.htm
I was astonished to see, that the website is not generated
automagically[i saw patches to the soundcard matrix, etc..]. I don't
know much about content management systems, etc, but i wonder if
this wouldn't save great hassles in the future..
Yes I have been thinking about it today too. The main thing is someone
has to roll up their sleeves. However I don't think it will be too
much work. I'm trying to decide if it should be a simple text based
form or a mysql database. Obviously the latter is more work but will
be much faster (if it matters).
12:36 p.m.
Florian Schmidt wrote:
On Tue, 02 Dec 2003 00:42:56 +0900
Patrick Shirkey <pshirkey(a)boosthardware.com> wrote:
The main problem with this is the html tags which are used throughout
the matrix are always being updated and we don't want that info hogging
valuable space in the kernel. I am looking into a new page format now.
We have a few options so it's just deciding on the new way.
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
Apparently upon the beginning of the barrage, the donkey broke
discipline and panicked, toppling the cart. At that point, the rockets
disconnected from the timer, leaving them strewn around the street.
Tethered to the now toppled cart, the donkey was unable to escape before
the arrival of U.S. troops.
United Press International
Rockets on donkeys hit major Baghdad sites
By P. MITCHELL PROTHERO
Published 11/21/2003 11:13 AM
Florian Schmidt wrote:
Hmm, i thought of something simpler.. For example, each driver source
file could have a special section that contains the necessary infos for
the card matrix. Then a script to get the info from the source files and
puts it together to a html page would be enough.. This is only one
example, of course.. An sql database is probably overkill. We have
really static data here [after it's once generated]. Updates could then
be done like once a week or even daily which comes down to just running
a script that grabs the source from cvs and does its thing..
I don't know how easy this would be to create the rest of the docs but
some parts of it are already automated, like the api doc creation,
etc...
I was astonished to see, that the website is not generated
automagically[i saw patches to the soundcard matrix, etc..]. I don't
know much about content management systems, etc, but i wonder if
this wouldn't save great hassles in the future..
Yes I have been thinking about it today too. The main thing is someone
has to roll up their sleeves. However I don't think it will be too
much work. I'm trying to decide if it should be a simple text based
form or a mysql database. Obviously the latter is more work but will
be much faster (if it matters). 
11:47 a.m.
Patrick Shirkey wrote:
Can you tell me what things you would like to have on
the website
that are not already there? What things have you noticed while
using it that are not user friendly?
I'd like to have separate entries for USB devices, i.e., pages
independent of the driver module name.
The same would come in handy for AC'97 codecs, too.
The table is rather big. Maybe it should be split by bus type.
Having to patch the HTML source is maintainer-unfriendly. The page
just asks to be generated from some simpler source. (IMHO statically)
Regards,
Clemens
11:56 a.m.
Clemens Ladisch wrote:
Patrick Shirkey wrote:
Can you show me what you mean with ascii?
Can you tell me what things you would like to have
on the website
that are not already there? What things have you noticed while
using it that are not user friendly?
I'd like to have separate entries for USB devices, i.e., pages
independent of the driver module name.
The same would come in handy for AC'97 codecs, too.
The table is rather big. Maybe it should be split by
bus type.
Good point.
Having to patch the HTML source is
maintainer-unfriendly. The page
just asks to be generated from some simpler source. (IMHO statically)
I agree.
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
Apparently upon the beginning of the barrage, the donkey broke
discipline and panicked, toppling the cart. At that point, the rockets
disconnected from the timer, leaving them strewn around the street.
Tethered to the now toppled cart, the donkey was unable to escape before
the arrival of U.S. troops.
United Press International
Rockets on donkeys hit major Baghdad sites
By P. MITCHELL PROTHERO
Published 11/21/2003 11:13 AM
1:27 p.m.
New subject: [Alsa-user] Re: [linux-audio-user] ALSA: What is the website missing?
At Tue, 02 Dec 2003 00:54:33 +0900,
Patrick Shirkey wrote:
Clemens Ladisch wrote:
i agree with Clemens.
currently, there are plenty of USB devices enough to list as one page.
since the USB devices are independent from other soundcards, it's not
necessarily listed together.
if i understand his suggestion correctly, we can create a link from
the "generic USB" entriy in the matrix page to the USB-specific table
which show the all supported/unsupported USB devices.
in the case of ac97 codecs, the problem is a bit different than USB.
but still, it'll be nice to have another table for AC97 chips, too,
because of the following reasons:
- in many cases, people are told that the soundcard on their boards is
an AC97 chip. it's partly true, but not completely. as you know,
the real driver is different. this note should appear somewhere.
- each ac97 chip has different character and its support
(implementation on ALSA) depends, too. some supports 5.1 outputs,
some broken, some work as compatible with older chips, etc.
well, maybe the best way is to build the matrix page based on a
certain RDB. we have several keys to sort. e.g., there will be a
page sorted by the hardware maker (as it is now), a page sorted by
BUS, and one by driver, etc.
just my ~$0.02.
Takashi
Patrick Shirkey wrote:
Can you show me what you mean with ascii? Can you tell me what things you would like to have
on the website
that are not already there? What things have you noticed while
using it that are not user friendly?
I'd like to have separate entries for USB devices, i.e., pages
independent of the driver module name.
The same would come in handy for AC'97 codecs, too.
2 Dec
2 Dec
4:56 a.m.
Patrick Shirkey wrote:
Clemens Ladisch wrote:
Sorry, I wasn't very clear.
Currently, the contents of the detailed pages with installation
instructions depend on the module name (e.g., the EZ-USB info is shown
for all devices handled by snd-usb-audio), and user comments are
assigned to the module name. It would be nice to be able to have
device-specific information/comments.
Regards,
Clemens
I'd like to have separate entries for USB
devices, i.e., pages
independent of the driver module name.
Can you show me what you mean with ascii?
8:59 a.m.
Clemens Ladisch wrote:
Patrick Shirkey wrote:
OIC. This is a bit harder to implement using the current php setup as it
essentially ends up as a lot of work for me to do, and a lot of
fragmentation of the additions. But I'll try to find a way to make it
easier and saner to implement.
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
Apparently upon the beginning of the barrage, the donkey broke
discipline and panicked, toppling the cart. At that point, the rockets
disconnected from the timer, leaving them strewn around the street.
Tethered to the now toppled cart, the donkey was unable to escape before
the arrival of U.S. troops.
United Press International
Rockets on donkeys hit major Baghdad sites
By P. MITCHELL PROTHERO
Published 11/21/2003 11:13 AM
Clemens Ladisch wrote:
Sorry, I wasn't very clear.
Currently, the contents of the detailed pages with installation
instructions depend on the module name (e.g., the EZ-USB info is shown
for all devices handled by snd-usb-audio), and user comments are
assigned to the module name. It would be nice to be able to have
device-specific information/comments.
I'd like to have separate entries for USB
devices, i.e., pages
independent of the driver module name.
Can you show me what you mean with ascii? 
1 Dec
1 Dec
2:31 p.m.
On Mon, Dec 01, 2003 at 10:06:50PM +0900, Patrick Shirkey wrote:
[...]
All opinions will be considered so don't hold back ;-]
its good you are doing this Patrick - thanks...
some suggestions re the 'soundcard details' pages:
in order to counteract the misconception that alsa is complicated
perhaps the 'information overload' could be reduced somewhat.
Is it only me that considers the 'module options' to be unneeded by most
people? Consider linking to a separate page, or put it lower down the
page in the modules.conf section. They certainly shouldnt be listed
before the Introduction :-)
'quick install': is it true to say that this is irrelevant to
90% of people? As a mandrake and gentoo user, i have no intention
of ever going through the described process. Perhaps more of an
overview of installation would be beneficial, with as much distro
specific info as poss. Consider moving the compiling from tarball
instructions to a separate page.
re this paragraph:
"Native Devices
After the main multiplexer is loaded, its code requests top level sound
card module. String snd-card-%i is requested for native devices where %i
is sound card number from zero to seven. String sound-slot-%i is
requested for native devices where %i is slot number for ALSA owner this
means sound card number. The options line allows you to set various
config options before the module is loaded. String snd_id lets you set
the name of the card which is returned in the /proc/asound/cards
file..."
-the word 'multiplexer' is not self explanatory in this context. Either
explain it or drop the word.
-i think for proper english grammer it should be "*the* top level...",
"is *the* sound card number", "is *the* slot number"
-"for ALSA owner this means sound card number" I have no idea what this
means:-)
-strings should be quoted, preferably using html tags to make them stand
out,eg <code>snd-card-%i</code>.
dont know if this is useful. I have more comments if needed:-)
cheers
--
Tim Orford
3:50 p.m.
Tim Orford wrote:
dont know if this is useful. I have more comments if needed:-)
Yes very. keep it coming. ALSA is very near 1.0 release so its
worthwhile making sure all this stuff is sorted as much as possible
before then.
BTW, I just broke the matrix index page with some changes I needed to
commit. Please don't hold it against me but consider it a necessary part
of making it better for everyone. It should be fixed soon. In the
meantime you can access the install docs via the generic link for the
USB devices if you really need to.
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
Apparently upon the beginning of the barrage, the donkey broke
discipline and panicked, toppling the cart. At that point, the rockets
disconnected from the timer, leaving them strewn around the street.
Tethered to the now toppled cart, the donkey was unable to escape before
the arrival of U.S. troops.
United Press International
Rockets on donkeys hit major Baghdad sites
By P. MITCHELL PROTHERO
Published 11/21/2003 11:13 AM
2 Dec
2 Dec
1:56 p.m.
Tim Orford wrote:
On Mon, Dec 01, 2003 at 10:06:50PM +0900, Patrick
Shirkey wrote:
I'm working on these useful comments now.
Just one thing.
[...]
All opinions will be considered so don't hold back ;-]
its good you are doing this Patrick - thanks...
some suggestions re the 'soundcard details' pages:
'quick install': is it true to say that this
is irrelevant to
90% of people? As a mandrake and gentoo user, i have no intention
of ever going through the described process. Perhaps more of an
overview of installation would be beneficial, with as much distro
specific info as poss. Consider moving the compiling from tarball
instructions to a separate page.
This has been mentioned before. It would be really nice to have clear
and informative writeups for every distro. Unfortunately I run an almost
LFS system so I have very little current knowledge of the various
methods which the multitude of distros use to setup ALSA.
However I will make a very explicit note that we want users to
contribute guides or links for the howtos available and provide a space
for them.
If anyone has links now that I can add please send them. (Think: Free
advertising for your favorite distro).
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
Apparently upon the beginning of the barrage, the donkey broke
discipline and panicked, toppling the cart. At that point, the rockets
disconnected from the timer, leaving them strewn around the street.
Tethered to the now toppled cart, the donkey was unable to escape before
the arrival of U.S. troops.
United Press International
Rockets on donkeys hit major Baghdad sites
By P. MITCHELL PROTHERO
Published 11/21/2003 11:13 AM
2:18 p.m.
On Wed, Dec 03, 2003 at 02:54:35AM +0900, Patrick Shirkey wrote:
This has been mentioned before. It would be really
nice to have clear
and informative writeups for every distro. Unfortunately I run an almost
LFS system so I have very little current knowledge of the various
methods which the multitude of distros use to setup ALSA.
However I will make a very explicit note that we want users to
contribute guides or links for the howtos available and provide a space
for them.
If anyone has links now that I can add please send them. (Think: Free
advertising for your favorite distro).
gentoo:
http://www.gentoo.org/doc/en/alsa-guide.xml
mandrake:
`urpmi libalsa2 alsa-utils`
(i havnt checked this - hopefully someone else will comment)
mandrakes web-site is partly members-only so i dont trust it.</troll>
--
Tim Orford
5:52 p.m.
Patrick,
Patrick Shirkey wrote:
If anyone has links now that I can add please send
them. (Think: Free
advertising for your favorite distro).
Planet CCRMA for RedHat:
http://ccrma-www.stanford.edu/planetccrma/software/installkernelandsound.ht…
[sorry about length!]
there is also some stuff for Mandrake on the Turn-Key audio site:
http://lulu.esm.rochester.edu/kevine/turnkey/home.html
it's not responding right now, however, so I don't have the exact location.
best,
d.
7:06 p.m.
If anyone has
links now that I can add please send them. (Think: Free
advertising for your favorite distro).
Planet CCRMA for RedHat:
http://ccrma-www.stanford.edu/planetccrma/software/installkernelandsound.ht…
[sorry about length!]
3 Dec
3 Dec
12:57 a.m.
Fernando Pablo Lopez-Lezcano wrote:
Still long but a better url for the alsa configuration section:
http://www-ccrma.stanford.edu/planetccrma/software/installkernelandsound.ht…
Thanks.
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
Apparently upon the beginning of the barrage, the donkey broke
discipline and panicked, toppling the cart. At that point, the rockets
disconnected from the timer, leaving them strewn around the street.
Tethered to the now toppled cart, the donkey was unable to escape before
the arrival of U.S. troops.
United Press International
Rockets on donkeys hit major Baghdad sites
By P. MITCHELL PROTHERO
Published 11/21/2003 11:13 AM
If anyone has links now that I can add please send
them. (Think: Free
advertising for your favorite distro).
Planet CCRMA for RedHat:
http://ccrma-www.stanford.edu/planetccrma/software/installkernelandsound.ht…
[sorry about length!]
1 Dec
1 Dec
3:09 p.m.
On Mon, 01 Dec 2003 22:06:50 +0900
Patrick Shirkey <pshirkey(a)boosthardware.com> wrote:
As some of you already know I am the occasional
webmaster/docs
maintainer for ALSA.
I have been planning some additions to the site to make it more
accessible but before I jump into anything that could be considered a
facelift I would like to get some opinions from y'all.
Can you tell me what things you would like to have on the website that
are not already there? What things have you noticed while using it
that are not user friendly?
I would like to add a database for some kind of card rating system.
What would you consider valuable things to rate a card against?
All opinions will be considered so don't hold back ;-]
Besides my point about the automation of the documentation generation
process, i would like to add the following: It would probably be good to
redesign the whole documentation part of the website. And i'm a big fan
of designing my documents top down.
Thus i would like to propose a Table of Contents for a reworked
documentation part of the alsa website:
1. Introduction to ALSA
2. User documentation
2.1 Overview of ALSA from a users perspective
2.2 ALSA userspace tools
2.2.1 alsamixer/alsactl
2.2.2 aplay/arecord
2.3 .asoundrc
2.3.1 dmix, dsnoop, etc..
2.3.2 Dolby digital, 5.1 sound, etc..
3. Developer documentation
3.1 Alsa-lib api
3.2 Driver developer info
3.3 Additional info (Tutorials, etc)
4. System Maintainers documentation
4.1 How to install ALSA
4.2 Kernel Module overview (snd, virmidi, etc..)
5. Supported Souncards
5.1 Sound Card Matrix
5.2 Hardware Recommendations for certain purposes
6. Additional Sources of info
6.1 Wiki
...
Feel free to add meat, modify, or flame me to death :)
Flo
--
music: http://www.soundclick.com/bands/9/florianschmidt.htm
3:54 p.m.
Patrick Shirkey <pshirkey(a)boosthardware.com> wrote:
As some of you already know I am the occasional
webmaster/docs
maintainer for ALSA.
I have been planning some additions to the site to make it more
accessible but before I jump into anything that could be considered a
facelift I would like to get some opinions from y'all.
Can you tell me what things you would like to have on the website that
are not already there? What things have you noticed while using it
that are not user friendly?
I would like to add a database for some kind of card rating system.
...
IMO it would be very useful to have a detailed list of features
supported for each soundcard and possibly some other details that might
help in choosing the right soundcard for particular use (some info is
already there but not very organized and mostly from users (hit and
miss), I think it would be useful if developers chipped in and say which
features are supported and to what extent)
not sure how would you rate the cards - perhaps in few categories
(game/multimedia (playback), recording, midi synth, ...)
erik
3:55 p.m.
A small equivalent table would be nice.
I got a SIS mobo .. the equivalent is a intel 8x0
That was bit hard to find .
Redoing the documentation is really important.
Making easier to manage the info that's relevant.
Another datail really is what's going on with kernel 2.6
Get a bit of news about the implementation of ALSA as default
in 2.6
Even how to compile a kernel 2.6 with ALSA would be nice.
On Mon, 1 Dec 2003 20:10:03 +0100
Florian Schmidt <mista.tapas(a)gmx.net> wrote:
On Mon, 01 Dec 2003 22:06:50 +0900
Patrick Shirkey <pshirkey(a)boosthardware.com> wrote:
As some of you already know I am the occasional
webmaster/docs
maintainer for ALSA.
I have been planning some additions to the site to make it more
accessible but before I jump into anything that could be considered a
facelift I would like to get some opinions from y'all.
Can you tell me what things you would like to have on the website that
are not already there? What things have you noticed while using it
that are not user friendly?
I would like to add a database for some kind of card rating system.
What would you consider valuable things to rate a card against?
All opinions will be considered so don't hold back ;-]
Besides my point about the automation of the documentation generation
process, i would like to add the following: It would probably be good to
redesign the whole documentation part of the website. And i'm a big fan
of designing my documents top down.
Thus i would like to propose a Table of Contents for a reworked
documentation part of the alsa website:
1. Introduction to ALSA
2. User documentation
2.1 Overview of ALSA from a users perspective
2.2 ALSA userspace tools
2.2.1 alsamixer/alsactl
2.2.2 aplay/arecord
2.3 .asoundrc
2.3.1 dmix, dsnoop, etc..
2.3.2 Dolby digital, 5.1 sound, etc..
3. Developer documentation
3.1 Alsa-lib api
3.2 Driver developer info
3.3 Additional info (Tutorials, etc)
4. System Maintainers documentation
4.1 How to install ALSA
4.2 Kernel Module overview (snd, virmidi, etc..)
5. Supported Souncards
5.1 Sound Card Matrix
5.2 Hardware Recommendations for certain purposes
6. Additional Sources of info
6.1 Wiki
...
Feel free to add meat, modify, or flame me to death :)
Flo
--
music: http://www.soundclick.com/bands/9/florianschmidt.htm
4 Dec
4 Dec
6:11 a.m.
On Monday 01 December 2003 13:06, Patrick Shirkey wrote:
As some of you already know I am the occasional
webmaster/docs
maintainer for ALSA.
I have been planning some additions to the site to make it more
accessible but before I jump into anything that could be considered a
facelift I would like to get some opinions from y'all.
tbh: the only thing I've actually used the site for is soundcard info. The
idea of a facelift sounds good, this might prompt me to look at the rest of
the site. The front page is rather 'dry' and looks like it's only intended
for developers/experienced users - I'm also not keen on that pale grey-green
colour, but that's a personal thing. A more informative & extensive contents
listing here would probably encourage me to use more of the site.
Can you tell me what things you would like to have on
the website that
are not already there? What things have you noticed while using it that
are not user friendly?
I would like to add a database for some kind of card rating system.
What would you consider valuable things to rate a card against?
I don't know if 'rating' is quite the thing. But info on things like
soundfont support, whether the external MIDI port is known to work or not
would be useful info.
All opinions will be considered so don't hold back
;-]
and while we're at it:
http://www.agnula.org/documentation/dp_tutorials/alsa_jack_ladspa/
and these also may be useful:
http://www.suse.de/~mana/alsa090_howto.html
http://alsa.opensrc.org/index.php?page=AlsaGlossary
http://www.alsa-project.org/~goemon
As you've asked, I'll go look at the site a bit more deeply.
That said, It's a useful resource, thanks for even bothering :-)
cheers
tim hall
2:18 p.m.
tim hall wrote:
tbh: the only thing I've actually used the site for is soundcard info. The
idea of a facelift sounds good, this might prompt me to look at the rest of
the site. The front page is rather 'dry' and looks like it's only intended
for developers/experienced users - I'm also not keen on that pale grey-green
colour, but that's a personal thing. A more informative & extensive contents
listing here would probably encourage me to use more of the site.
I'm trying to find a way to keep the dry factor while still making it
accessible to newbies. WIP. I worry that people won't feel it is
professionally oriented if the site is too funky ;) On the other hand a
design that is clean and appealing to read is a good target.
I don't know if 'rating' is quite the thing. But info on things like
soundfont support, whether the external MIDI port is known to work or not
would be useful info.
This seems to be the general consensus. However we need to figure out a
good way to get this info. Currently we rely on the user contributions
and the wiki to do the job. If there is a better way we should find it.
and while we're at it:
http://www.agnula.org/documentation/dp_tutorials/alsa_jack_ladspa/
This is new. I have added it on my local copy.
and these also may be useful:
http://www.suse.de/~mana/alsa090_howto.html
http://alsa.opensrc.org/index.php?page=AlsaGlossary
Already included on Docs page.
This has been replaced about a year and a half ago by the current pages
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
Apparently upon the beginning of the barrage, the donkey broke
discipline and panicked, toppling the cart. At that point, the rockets
disconnected from the timer, leaving them strewn around the street.
Tethered to the now toppled cart, the donkey was unable to escape before
the arrival of U.S. troops.
United Press International
Rockets on donkeys hit major Baghdad sites
By P. MITCHELL PROTHERO
Published 11/21/2003 11:13 AM
7751
days inactive
7754
days old
linux-audio-user@lists.linuxaudio.org
21 comments
10 participants
participants (10)
-
Clemens Ladisch -
derek holzer -
Erik Steffl -
Fernando Pablo Lopez-Lezcano -
Florian Schmidt -
Patrick Shirkey -
Richard -
Takashi Iwai -
tim hall -
Tim Orford