Dear Tim Roberts:
After I had checked my KSNODE_DESCRIPTOR and KSTOPOLOGY_CONNECTION, I found
that there were some problems. Now, I fixed KSNODE_DESCRIPTOR and
KSTOPOLOGY_CONNECTION bugs. I can find my driver in audio capture source
filter.
Recently, I asked so many silly questions. I appreciate that you give me so
many replies, help me to solve the problem. Thanks again.
Best Regards,
Shang Jing
2016-08-17 8:02 GMT+08:00 Tim Roberts <timr@xxxxxxxxx>:
若水 wrote:
Dear Tim Roberts:
Thank you for help. My base sample is avshws code. It is a video sample,
not an audio-only sample. If I have an audio-only sample, maybe I could
find my bug easy. Could you give me an audio-only sample? Thanks.
The avshws sample is a fine start, but it only has a video pin. To turn
this into an audio sample, you'll need to change the category list to
include KSCATEGORY_AUDIO, and of course you'll have to change the datatypes
to audio types. The avssamp sample includes both a video and an audio pin,
and can give you examples of the structure's you'll need.
It shouldn't take much more than that to get you listed as a source in
DirectShow. To be recognized as a system audio device outside of
DirectShow, there are some more things you must do. You must have at least
one internal node, which means you need a KSNODE_DESCRIPTOR and a
KSTOPOLOGY_CONNECTION structure in your KSFILTER_DESCRIPTOR. These can be
very simple, but they must be present.
--
Tim Roberts, timr@xxxxxxxxx
Providenza & Boekelheide, Inc.
