'Twas brillig, and Daniel Mack at 03/03/11 00:58 did gyre and gimble: >> If you do decide to go the kernel route, make the actual kernel bits >> as lightweight as possible to be resilient against PA protocol changes >> and such. Hopefully the kernel bits would be write once, use with any >> version of PA for a long time to come. > > It should be completely independent from PA and just function as a > loop-trough virtual device which communicates with the userspace via a > simple protocol (for sample rate configuration etc) and exports its > audio buffers as shared memory. > > A userspace part would then be in charge to connect this interface to > PulseAudio. > > I personally have no clue about Windows development, and I would like to > keep it that way. Any volounteers with appropriate knowledge? :-) > Am I right in saying that there was an ESD type thing that did this for the winesd project? I don't know much about it, but if there is one, it's probably a good starting point.... Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mageia Contributor [http://www.mageia.org/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/]
