Hi, Matt, Oh, ok, I'll follow your advice. I was worried about the InstallSubDevice() equivalent in AVStream. As for the multiple (wave) devices, I guess I'll have to make two instances of the same filter. Does that sound right to you? Thank you for your time. _____ From: wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Matt Gonzalez Sent: Sunday, August 14, 2005 10:43 PM To: wdmaudiodev@xxxxxxxxxxxxx Subject: [wdmaudiodev] Re: Wave Devices using AVStream driver I suggest you go ahead and try adding KSCATEGORY_AUDIO to the Categories list in your filter descriptor. That was all I had to do. Make sure the reference string in the AddInterface entry in your INF matches the ReferenceGuid in your KSFILTER_DESCRIPTOR. Matt Sam Tertzakian wrote: Hi, Right now, I am only listing KS_CATEGORY_CAPTURE and KS_CATEGORY_RENDER. I expect that I should list KSCATEGORY_AUDIO as I do for my WavePCI drivers. But, in the WavePCI drivers, I use "InstallSubDevice( ...., "Wave", .... );" to link the name in the INF to my kernel mode device. But, in AVStream I don't see the equivalent function InstallSubDevice(). -----Original Message----- From: wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Matt Gonzalez Sent: Sunday, August 14, 2005 9:13 PM To: wdmaudiodev@xxxxxxxxxxxxx Subject: [wdmaudiodev] Re: Wave Devices using AVStream driver What categories are you listing for your filter? Matt Sam Tertzakian wrote: I have an AVStream driver that captures/renders audio. To do so, I use GraphEdt and the device is listed under "WDM Streaming Devices". Now, I need to make it also appear under "Audio Capture" devices. Can I do this with AVStream? If so, how? With WavePCI we use PortCls functions to expose the wave device. I want to do the same thing using an AVStream driver. I want to be able to use the device using the Wave API. I think it is possible since, as far as I know, the USBAudio.sys is an AVStream driver and it exposes Wave devices. Thank you ****************** 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.com/ ****************** 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.com/ ****************** 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.com/ ****************** 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.com/