[wdmaudiodev] Re: MSVAD and WDM capture
- From: "Sam Tertzakian" <sam@xxxxxxxxxxx>
- To: <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Sat, 19 Jun 2004 06:11:07 -0700
Well from what I know...the answer is you cannot change this property from
the driver in a way that affects user mode.
The driver does not really know about direct sound or the wave API. Both
those APIs (and others) are abstracted above the driver.
I am not sure why you are getting E_FAIL. I also know that I have personally
used this call to change buffer sizes in user mode successfully and that I
did not have to do anything else.
Ok, now I remember...I did not call this property with KxProxy. I called it
to set in QCap.dll. (KxProxy has small buffers but QCap has large buffers. I
needed to change from large to small.)
So, can you do me a favor? Can you try the same thing with a filter created
by QCap.dll instead of KxProxy. I bet KxProxy is rejecting your request for
some reason. If it works with QCap.dll then, at least you know your code is
correct.
-----Original Message-----
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Yura
Sent: Saturday, June 19, 2004 6:05 AM
To: Sam Tertzakian
Subject: [wdmaudiodev] Re: MSVAD and WDM capture
Hello ,Sam
Saturday, June 19, 2004, 3:05:29 PM, you wrote:
ST> Oh, sorry. You must call the function *before* you connect the pins.
ST> It is strange, but it is so.
ST> Try that...and tell me if it works.
So as I do. I call the SuggestAllocatorProperties function before connecting
pins.
Reread my post ;)
ST> -----Original Message-----
ST> From: wdmaudiodev-bounce@xxxxxxxxxxxxx
ST> [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Yura
ST> Sent: Saturday, June 19, 2004 5:09 AM
ST> To: Sam Tertzakian
ST> Subject: [wdmaudiodev] Re: MSVAD and WDM capture
ST> Hello ,Sam
ST> Tuesday, June 15, 2004, 5:40:31 AM, you wrote:
ST> Thank you so much for the answer!
ST> I tried what you suggested, but have some problems again.
ST> When I call SuggestAllocatorProperties(before the pin is connected),
ST> it returns SUCCESS. Then I connect the pin and call
ST> GetAllocatorProperties but it returns E_FAIL. When I run the graph I
ST> see that KsProxy ignored my previous
ST> SuggestAllocatorProperties call.
ST> Then I used debugger to find allocator properties in memory and to
change
ST> them. When I did this, the sound became perfect!!!(Only until I restart
the
ST> graph of course).
ST> So here is my new question. Can I change the default allocator
ST> properties that KsProxy uses from my driver? Or what else I need to do
ST> to change them from User-mode?
ST> Thanks!
--
Best regards,
Yura mailto:spirit@xxxxxxxxxx
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.de/
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.de/
Other related posts:
