[wdmaudiodev] Re: IAMPushSource support in AVStream
- From: "Sam Tertzakian" <sam@xxxxxxxxxxx>
- To: <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Wed, 13 Jul 2011 02:19:03 -0700
I have verified IAMPushSource is not exposed.
However, IAMGraphStreams is exposed...and MSDN documentation says that
IAMGraphStreams should be used instead.
So perhaps KsProxy is simply enforcing that people use IAMGraphStreams. It
seems to me that is the case.
Also I verified with several other vendors' behavior and exposed interfaces
appear to be the same.
It would be nice to have confirmation about this so I can explain why
IAMPushSource is not exposed, or that there is, in fact, something wrong.
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Sam Tertzakian
Sent: Monday, July 11, 2011 2:49 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: IAMPushSource support in AVStream
Hi,
It is not listed in the supported interfaces that are visible using
GraphStudio.
Also one user reported this as a bug.
However, I have not written a program to actually verify this.
I did look carefully at the documentation in MSDN and determined, perhaps
incorrectly, that there is nothing for an AVStream driver to do to expose
this interface; however, it is not clear that KsProxy will expose that.
Since the interface is not listed in the supported interfaces using
GraphStudio and since it was reported by customer...I assumed that reported
lack of support to be true. I will write a program to specifically verify
it. After I do it, will report back. I anticipate that report is reliable
based on the source, however.
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Tim Roberts
Sent: Monday, July 11, 2011 12:50 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: IAMPushSource support in AVStream
Sam Tertzakian wrote:
I have an AVStream Video/Audio capture driver. I want KsProxy to expose the
IAMPushSource interface on the audio and/or video filter. The documentation
in MSDN states that if the pin is exposed as a PIN_CATEGORY_CAPTURE and
IKsPropertySet is also exposed in the filter that the filter is considered a
"Live Source". The documentation also states that "Live Sources" should
expose IAMPushSource. But it does not appear to be the case...the interface
does not appear to be supported.
Why do you think so? How did you check this?
Is there something I need to do (such as support a specific property set) in
the AVStream driver to cause that interface to be exposed?
Ksproxy should expose that for all live capture sources.
--
Tim Roberts, timr@xxxxxxxxx
Providenza & Boekelheide, Inc.
Other related posts:
