All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>,
	Jaroslav Kysela <perex@suse.cz>
Subject: Re: TODO-1.1
Date: Mon, 07 Mar 2005 16:27:34 +0100	[thread overview]
Message-ID: <s5hd5ubwk61.wl@alsa2.suse.de> (raw)
In-Reply-To: <1109970174.6710.25.camel@mindpipe>

At Fri, 04 Mar 2005 16:02:54 -0500,
Lee Revell wrote:
> 
> I just noticed the TODO-1.1 file in ALSA CVS, and it seems like a lot of
> it is done.
> 
> >   - [ti] software volume control on alsa-lib (for c-media chips)
> > 
> 
> This one is done...

Yep.

> > Emu10k1:
> > ========
> >   - [ti] mixer redesign - Peter's patch for audigy looks better,
> >        a bit clean up is needed.
> 
> Would anyone care to elaborate on this one?  Personally I don't think a
> mixer redesign is needed.  Applying Mikael's patch would put the SBLive
> and Audigy mixer in a good state.  Splitting the view to "Playback" and
> "Capture" made the emu10k1 mixer a lot more comprehensible.  Finally,
> the multichannel patch lets JACK users bypass the mixer completely.

Agreed.  The current state is in a good shape.

> >   - ld10k1 development?
> 
> I propose this be added to alsa-tools.  Although Peter will not be
> maintaining it anymore, others have volunteered, and it's quite useful.

OK, if Peter has no objections, I'll merge it into alsa-tools.
(But not today - I'm just back from a trip in USA and currently too
 busy to catch up all pending mails and bug reports ;)

> >   - [ti] ALSA-native sfxload
> 
> Is there any reason asfxload can't be added to alsa-tools too?

I wanted to clean up the code.  It's based on the OSS framework.
But I'll have little time for improving this anyway, so it's fine to
merge it to alsa-tools tree at first, so that any other person can
take care of that, too.


Takashi


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

      reply	other threads:[~2005-03-07 15:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04 21:02 TODO-1.1 Lee Revell
2005-03-07 15:27 ` Takashi Iwai [this message]

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=s5hd5ubwk61.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=perex@suse.cz \
    --cc=rlrevell@joe-job.com \
    /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.