In case any one was curious, I converted Takashi's "Writing an ALSA
Driver" document to DocBook/SGML. It's available for download here:
http://www.kevindumpscore.com/download/writing-an-alsa-driver.sgml
=
-- kwconder at yahoo dot com
__
Do you
> > on the other hand, having more documentation is almost always a
> > good thing. now, where are the volunteers?
>
> Lot's of possible flames here but the main thing is that the
> people who do understand the alsa-driver well enough are either
> too busy to find the time or have justifiable re
Abramo Bagnara <[EMAIL PROTECTED]> wrote:
>Documentation has not been written for lack of funding and lack of
>volunteers.
Well, I've come foward a few times as a documentation volunteer and
have been frustrated at every turn. The first time I volunteered, the
ALSA team suddenly switched from the
> Michal Kochanowicz wrote:
> I'm trying to setup mixer using ALSA but I find it painull due
> to lack of documentation. Yes, there is so-called API
> documentation but in fact it's worthless. It contains little
> more than function names and argument types.
Merely saying something is worthle
On Mon, 29 Apr 2002, Bearcat M. Sandor wrote:
> I have the following in mind:
> Creating my own music DSP modes
>
> Are there any books that cover programming in these areas?
http://shoko.calarts.edu/~glmrboy/musicdsp/dspbooks.html
-- Kevin Conder, [EMA
y section then?
> The following document represents it current state. I
> would like to ask for feedback even though it is very incomplete.
What is the license for this documentation and its examples?
-- Kevin Conder, [EMAIL PROTECTED]
___
Al
http://www.alsa-project.org/alsa-doc/alsa-lib/confhooks.html#confhooks
http://www.alsa-project.org/alsa/library-source/doc/asoundrc.txt
-- Kevin Conder, [EMAIL PROTECTED]
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourcefo
doesn't like my attachment then let
me know off of the list. We can make alternate arrangements...
-- Kevin Conder, [EMAIL PROTECTED]
spelling_patches.tar.gz
Description: Binary data
d "sustenuto" is misspelled as "sostenuto".
Please note that "pornamento" and "portnamento" occur in constants
(in asoundef.h, IIRC). Correcting them could possibly have an adverse
effect on existing code. What should we do?
I
> > > Kai Vehmanen wrote on Thu, 07 Mar 2002 05:41:34 -0800:
> > >
> > > Why is ALSA the better alternative?
> > > Have I missed some important points?
> >
> > Kevin Conder wrote:
> >
> > OSS has one crucial advantage over ALSA:
s issue. Have I missed some important points?
OSS has one crucial advantage over ALSA: documentation!
Perhaps one day ALSA will have something like the Programmer's Guide to
OSS. Check it out at http://www.opensound.com/pguide/
-- Kevin Conder, [EMAIL PROTECTED]
On Fri, 15 Feb 2002, Andy Wingo wrote:
> On Fri, 15 Feb 2002, Kevin Conder wrote:
>
> >
> > Finally, if you're going to turn everything over to the Wikki
> > kiddies then count me out! I believe in quality over quantity.
> >
>
> having written m
out! I believe in quality over quantity.
-- Kevin Conder, [EMAIL PROTECTED]
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
On Tue, 12 Feb 2002, Kai Vehmanen wrote:
> On Tue, 12 Feb 2002, Kevin Conder wrote:
> > The
> > last time I checked, the ALSA developers were adding doxygen comments to
> > the source code.
>
> The best part of javadoc is that it adds very little overhead.
I was wondering about the status of ALSA's API documentation. The
last time I checked, the ALSA developers were adding doxygen comments to
the source code. Was that project completed?
-- Kevin Conder, [EMAIL PROTECTED]
___
Alsa-
site about GTK+ 2.0:
http://www.gtk.org/api/
> Without news, it's hard to tell a dead site [like this] from
> a live one.
Ok, it looks like the site is being maintained. I apologize if
anyone was offended. It was just hard to tell from the front page. I'll go
back to
ad
site [like this] from a live one.
BTW, to read GTK 2.0 documentation, try this site instead:
http://developer.gnome.org/doc/API/
> www.gimp.org looks good to me.
Me too, scroll down to the bottom. ;-)
-- Kevin Con
n? Your personal preference?
Different audiences (developers, vendors, users, etc.) have different
criteria for importance. It would be hard for others to make sense of your
order. Why not just sort things alphabetically?
-- Kevin Conder, [EMAIL PROTECTED]
__
ed dnoise:
http://mitpress2.mit.edu/e-books/csound/fpage/getCs/getCs.html
-- Kevin Conder, [EMAIL PROTECTED]
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
On Wed, 14 Nov 2001, Dan Hollis wrote:
> On Wed, 14 Nov 2001, Andy Wingo wrote:
> > Mark Rages put up a wiki that might be useful for you. I believe it's
> > linked to from www.linuxdj.org/audio/lad/.
>
> linuxdj.org doesn't exist...
Here's the URL for the Wiki page:
http://mlug.missour
I converted "Writing an ALSA Client" to DocBook/XML as a
proof-of-concept. This was one Wiki page so it doesn't show all of the
possibilities of DocBook. But imagine a larger document with a full Table
of Contents and also an Index. Imagine being able to print hundreds of
pages from a sin
On Mon, 15 Oct 2001, Jaroslav Kysela wrote:
>
> > I think in ORA's "In a Nutshell" series might be trademarked. How
> > about an ALSA Programmer's Guide that is similar to the OSS Programmer's
> > Guide? Check out the OSS Programmer's Guide at
> > http://www.opensound.com/pguide/
>
> I'm goi
On Mon, 15 Oct 2001, [iso-8859-1] Jörn Nettingsmeier wrote:
> the wiki allows many people to add bits and pieces every once in a
> while, so that the work will be shared and people can just add their
> $.02 without taking all the responsibility and administrivia of
> writing a complete, stand-alo
On Sun, 14 Oct 2001, Mark Rages wrote:
>
> On Sun, 14 Oct 2001, Kevin Conder wrote:
>
> > Can you look at it off-line (besides grabbing everything with
> > wget)? Can you print it out (besides one page at a time)? Can you search
> > it (besides using google on
On Sat, 13 Oct 2001, Mark Rages wrote:
> Previously I proposed using a Wiki for documentation,
Can you look at it off-line (besides grabbing everything with
wget)? Can you print it out (besides one page at a time)? Can you search
it (besides using google on-line)?
> Would this be an ef
What is meant by the PCM Interface? To me, it means Pulse Code
Modulation. But I've been playing too much with Casio keyboards.
-- kevin at kevindumpscore dot com
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/list
On Sat, 29 Sep 2001, Petter [iso-8859-1] Sundlöf wrote:
> We've set up a channel on OPN (irc.openprojects.net), called #ALSA.
> Developers are welcome, as are users. People keep dropping in with
> questions.
>
> We think it's a good means of support
What a joke! Everytime I go in, there
On Tue, 18 Sep 2001, Curtis Veit wrote:
> I have been watching the 0.9 betas mature.
> It looks to me as though it may not be much longer
> until a final release. This made me wonder if anyone is
> bring the documentation up to date. I'd be interested
> helping on this
So would I. I
28 matches
Mail list logo
