"In regards to managed. I was not proposing streaming bit in .net. More a bcl wrapper for config and metadata - start, stop, connect, status, change defaults, change endpoints, etc. The lower level will still handle the streaming. There has to be some
managed story for this going forward. "
I don't know how you do start/stop without streaming - start/stop is intimately associated with streaming. But there might be an opportunity for managed wrappers for some of the other parts of the audio infrastructure, who knows what might end up being
developed in the future.
androidi: One critical thing to consider - Windows tends to be developed for the noob. My quintessential example is my wife's riding instructor who is a stereotypical computer user. She ends up calling us when the sound stops working when she tries playing
back DVDs (it's an issue with the sound drivers but I can't explain that to her).
Whenever I think about sound features, I try to think about how this stuff would work for her. Whatever we do has to be discoverable and usable for someone with little technical expertise. It also needs to solve a particular customer scenario.
I like staceyw's scenario above for that reason - he's describes a clean scenario where he's trying to accomplish something that he can't implement using our current system without a great deal of difficulty AND his scenario is something that I could easily
imagine customers encountering. That scenario IS something that we might be able to address in a future version of Windows, Frank's already added it to the very long list of potential features (some of those potential features have been on the list for decades
so there obviously are no guarantees about any particular feature being implemented).