At Thu, 25 May 2006 19:10:30 +0100, James Courtier-Dutton wrote: > > Hi, > > I was wondering what the current TODO list is for ALSA. The current one > in alsa-driver hg seems somewhat out of date. Yep. Some documents in alsa-driver tree are obsoleted. Perhaps better to remove them. > 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. Actually, it's not dmix but rate plugin that causes more problems... > 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. A dummy kernel driver just to translate syscalls to communication with a user daemon is the only possible workaround, IMO. This idea was denied once quite ago, but I don't see any other good way right now. My additional wishes are: 8) Improve release engineering. 9) Better organized Web pages and BTS. 10) Build standard test suite and diagnosis tools. Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-devel
