--- In softrock40@..., Robert McGwier <rwmcgwier@c...>
wrote:
Because we will need to continue
to use PortAudio to support things like VAC that do not know WDM-
KS,
or WDM period for that matter, we have chosen to take this
generous
offer and to fix the broken, non functional WDM-KS module in
PortAudio
as pay back to that project. Eric is hard at work on this (and
too many
other) issues.
After we completely understand WDM-KS and PortAudio works, then
it will
be much easier to implement our own version of VAC, which will be
based
upon MSVAD in the Windows DDK. I really liked Covington's
approach to
make it file like but since the callback works so well, we might
do
that instead.
Stay tuned
Bob
Hi Bob,
From what I gathered from posts made by the author of VAC to various
newsgroups in the past when he was developing the driver it appears
that VAC is the old NT Style type of driver.
The last progress I made on vSound was to implement a callback
mechanism to user mode using a user mode created event object. The
handle to the object is passed down to the driver via IOCTL and the
driver dereferences it into kernel space. When data is available
the driver signals the event that the user mode app is waiting on.
With this you now have a callback-like interface to the driver
similar to PortAudio. The obvious nice part of basing a virtual
audio driver on WDM is being able to use it with Ks.
73 de Phil N8VB
