All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Joerg Mayer <jmayer@loplof.de>
Cc: Jaroslav Kysela <perex@suse.cz>,
	Florian Schmidt <mista.tapas@gmx.net>,
	alsa-devel@lists.sourceforge.net
Subject: Re: Fw: [Bug 76413] arts does not follow ALSA API
Date: Sat, 20 Mar 2004 00:00:55 +0000	[thread overview]
Message-ID: <405B89B7.5070207@superbug.demon.co.uk> (raw)
In-Reply-To: <20040319230152.GA17001@thot.informatik.uni-kl.de>

Joerg Mayer wrote:
> On Fri, Mar 19, 2004 at 08:30:13PM +0000, James Courtier-Dutton wrote:
> 
>>The guys there just don't understand what you told them. If they took 
>>the time to actually read what you said, they could easily fix their 
>>problem.
>>
>>Summary: -
>>No bug in alsa.
> 
> 
> Summary 2:
> There seem to be quite a lot of projects that have problems to get native
> alsa support right: wine, winex, arts, xmms...
wine is only just starting to support alsa properly, due mainly to lack 
of real need to alsa support for a long time. They are starting to 
support it well now.
xmms don't support it well for obvious reasons. They charge people for 
OSS drivers, so the xmms alsa driver has to look worse!


> 
> How about a "alsa application developers meeting" once per month on IRC?
> If that meeting would be announced on the developer mailing list of
> projects that are known to use alsa, this might actually help.

Just reading the docs correctly should help.
I hang out on #alsa on freenode quite a lot, and will help if I have the 
time.

> 
> The invitation should contain something along the line:
> "If you have written code to use alsa, you should participate. Either because
> you did it right and can help others to do so too or because you didn't and
> in that case you should want to improve."
> 
>  Ciao
>        Jörg



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

  reply	other threads:[~2004-03-20  0:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-19 15:23 Fw: [Bug 76413] arts does not follow ALSA API Florian Schmidt
2004-03-19 17:02 ` James Courtier-Dutton
2004-03-19 19:05   ` Jaroslav Kysela
2004-03-19 20:30     ` James Courtier-Dutton
2004-03-19 23:01       ` Joerg Mayer
2004-03-20  0:00         ` James Courtier-Dutton [this message]
2004-03-20  0:39           ` Måns Rullgård
  -- strict thread matches above, loose matches on Subject: below --
2004-03-19 15:09 Florian Schmidt
2004-03-09 22:03 Florian Schmidt

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=405B89B7.5070207@superbug.demon.co.uk \
    --to=james@superbug.demon.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=jmayer@loplof.de \
    --cc=mista.tapas@gmx.net \
    --cc=perex@suse.cz \
    /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.