>> where the buffer is auto-silenced that they need to write samples into the >> specific position. Reset is nice, but you cannot tell the count of frames >> to be skipped without filling. > >However I think that auto-silence is not the best thing we've designed. > >We're using an interrupt handler to do what a rt-like user space process >should do. > >We'd have many things that might be solvable (like saturation in dmix by >example) in this way, but we've (rightly) choosen not to do it to >respect the general principle "never do in kernel space what is doable >in user space". > >Sometimes I think that auto silence is an unfortunate exception and I'd >prefer we'd try to move in the opposite direction.
i think that its similar to the discussion we had 2 weeks ago about callbacks abramo. alsa-lib could provide functions to do auto-silence, but the question remains: where and when are they called? the kernel provides a clearly defined point of control where this can happen if the user has asked for it and its needed. trying to do it in user space is clearly a nicer idea, but its hard to see where it should happen, or how to make sure it does happen if it has been requested. ------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
