All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.co.uk>
To: ALSA development <alsa-devel@alsa-project.org>
Subject: TODO list
Date: Thu, 25 May 2006 19:10:30 +0100	[thread overview]
Message-ID: <4475F316.5000908@superbug.co.uk> (raw)

Hi,

I was wondering what the current TODO list is for ALSA. The current one 
in alsa-driver hg seems somewhat out of date.
My list has the following, in no particular order:
1) Finish reverse engineering some sound cards (e.g. Creative EMU1212M)
2) Implement needed features on some already reverse engineered cards. 
e.g. The Creative Audigy PCMCIA.
3) Add dB gain architecture.
4) Improve dmix, specifically for 44.1 kHz and games like Doom3. Perhaps 
using the system clock, adjusted to match the sound card hardware clock, 
to provide accurate sample timing, at multiple different sample rates, 
irrespective of the rate the sound card runs at.
5) Perhaps use the system clock to help resample so that user space sees 
a single sample rate clock, but let alsa-lib automatically adjust for 
the different clocks of different sound cards.
6) Think of some way to simplify the mixer interface for user space 
mixers. Surely, it does not have to be so complex as it currently is?
7) Provide better OSS emulation support. E.g. redirect all access to 
/dev/dsp into user space so it can use all the features of alsa-lib 
without needing aoss. (aoss does not work if the application uses 
dynamically linked audio driver plugins.






-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642

             reply	other threads:[~2006-05-25 18:10 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-25 18:10 James Courtier-Dutton [this message]
2006-05-25 18:36 ` TODO list Lee Revell
2006-05-26 11:07 ` Takashi Iwai
2006-05-26 11:29   ` James Courtier-Dutton
2006-05-26 15:34     ` Takashi Iwai
2006-05-26 16:33       ` James Courtier-Dutton
2006-05-26 16:52         ` Takashi Iwai
2006-05-26 17:30           ` James Courtier-Dutton
2006-05-26 18:43             ` Takashi Iwai
2006-06-30 12:08             ` Johannes Berg
  -- strict thread matches above, loose matches on Subject: below --
2015-07-24  6:01 José Pekkarinen
2010-08-17 19:16 todo list varun satrawla
2010-07-14 10:01 TODO list Kulikov Vasiliy
2012-07-08 13:38 ` TODO List Benjamin BEURDOUCHE
2012-07-09  0:51 ` Keith Woodie
2015-04-03 20:40 ` TODO list Ravi Kerur
2015-04-07  7:49 ` Dan Carpenter
2015-04-09  0:36 ` Ravi Kerur
2015-04-09  8:48 ` Dan Carpenter
2015-04-09 22:57 ` Ravi Kerur
2015-04-10  5:34 ` Julia Lawall
2015-04-10 22:47 ` Ravi Kerur
2015-04-11  5:17 ` Julia Lawall
2015-04-13 22:02 ` Dan Carpenter
2015-04-13 22:42 ` Ravi Kerur
2015-04-14  6:58 ` Dan Carpenter
2009-11-21 16:30 todo list Krzysztof
2005-10-25  8:50 TODO List SMohideen
2005-10-30  9:44 ` Harald Welte
2000-04-28 11:52 Jamey Hicks
2000-04-28 12:17 ` Trevor Woolven
2000-04-29  0:27 ` David Woodhouse
2000-04-28  8:38 Trevor Woolven

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=4475F316.5000908@superbug.co.uk \
    --to=james@superbug.co.uk \
    --cc=alsa-devel@alsa-project.org \
    /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.