>Are you planning to standardize such features or design a >device-independent API for it? (And my manager wants to know which ALSA >release this might get implemented in...)
Just a thought on your overall issues with ALSA over the last week. The kinds of features you seem to expect from hardware didn't exist in most devices 2 years ago. Its likely that features currently considered "experimental" in hardware right now (matrix mixing springs to mind) will become more common 2 years from now. Does your manager think it wise to be writing software that is so tied into a particular model of what audio interfaces can do that it will be obsolete by the time processors run about 4 times as fast as they do now? People wrote game engines that did all this "multistream+backfill" stuff years before any cards provided hardware mixing, and they did most of it in software on CPU's that were 10-40 times slower than todays leading edge game-friendly processors. You are going to burn a lot of time trying to find common ways to access the slightly different functionality provided by *some* audio interfaces that pertains to multistreaming, and then find that you've still left a lot of users in the dark. The number of cycles you will lose by doing this in software rather than trying to abstract the h/w capability will probably be available to your users for no extra cost by the end of your work. Just my $0.01 ... --p ------------------------------------------------------- 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 _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
