[wdmaudiodev] Re: AVStream and Wave Devices
- From: "Sam Tertzakian" <sam@xxxxxxxxxxx>
- To: <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Tue, 4 Oct 2005 02:35:52 -0700
Here is the log I am receiving from SysAudio.sys
I am basically getting a STATUS_NOT_SUPPORTED error at the end...0xC00000BB.
It seems to be wrapping...so "sysaudio:" is the start of each line.
{394bc5e0-4669-4b52-8155-9ae47bc427f3} is my Filter GUID. DEVENUM is the bus
the device is on. It is a physical bus.
sysaudio: AudioDeviceInterfaceNotification:
(\??\DEVENUM#{00001108-0000-1000-8000-00805f9b34fb}#8&3342db83&0&000389AD03B
1_C00000000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\{394bc5e0-4669-4b52-8155-
9ae47bc427f3})
sysaudio: AddFilter:
(\??\DEVENUM#{00001108-0000-1000-8000-00805f9b34fb}#8&3342db83&0&000389AD03B
1_C00000000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\{394bc5e0-4669-4b52-8155-
9ae47bc427f3})
sysaudio: AddFilter: alias
(\??\DEVENUM#{00001108-0000-1000-8000-00805f9b34fb}#8&3342db83&0&000389AD03B
1_C00000000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\{394bc5e0-4669-4b52-8155-
9ae47bc427f3}) aulFilterType 00000001
sysaudio: AddFilter: alias
(\??\DEVENUM#{00001108-0000-1000-8000-00805f9b34fb}#8&3342db83&0&000389AD03B
1_C00000000#{dda54a40-1e4c-11d1-a050-405705c10000}\{394bc5e0-4669-4b52-8155-
9ae47bc427f3}) aulFilterType 00000002
sysaudio: AddFilter: alias
(\??\DEVENUM#{00001108-0000-1000-8000-00805f9b34fb}#8&3342db83&0&000389AD03B
1_C00000000#{65e8773e-8f56-11d0-a3b9-00a0c9223196}\{394bc5e0-4669-4b52-8155-
9ae47bc427f3}) aulFilterType 00000008
sysaudio: AddFilter: alias
(\??\DEVENUM#{00001108-0000-1000-8000-00805f9b34fb}#8&3342db83&0&000389AD03B
1_C00000000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{394bc5e0-4669-4b52-8155-
9ae47bc427f3}) aulFilterType 00000010
sysaudio: CFilterNode: e147a578
sysaudio: CFilterNodeInstance::Destroy: e10880c8
sysaudio: ~CFilterNodeInstance: e10880c8
sysaudio: UnregisterTargetDeviceChangeNotification: FNI: e10880c8
sysaudio: AddFilter: FAILED
(\??\DEVENUM#{00001108-0000-1000-8000-00805f9b34fb}#8&3342db83&0&000389AD03B
1_C00000000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\{394bc5e0-4669-4b52-8155-
9ae47bc427f3}) c00000bb
Ok, thank you in advance for any help...
-----Original Message-----
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Sam Tertzakian
Sent: Monday, October 03, 2005 1:43 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: AVStream and Wave Devices
No, it is not a SWEnum device. It is for real hardware. Ok, I'll try checked
build Sysaudio.
-----Original Message-----
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx]
Sent: Monday, October 03, 2005 10:55 AM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: AVStream and Wave Devices
There is an issue with AVStream and SWEnum that can cause this problem.
There is a conflict in the way they register device interfaces. Is this
a software enumerated driver you are writing? If so, that would be the
cause. If not, try installing the checked build of sysaudio.sys and hook
up a debugger or a utility that will let you view debug output.
Sysaudio.sys will report errors if it is unable to register a device so
it could be helpful in tracking down the cause.
-Rich
-----Original Message-----
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Sam Tertzakian
Sent: Monday, October 03, 2005 4:58 AM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: AVStream and Wave Devices
I changed the names to exactly what you have, but I still have the same
problem.
My category for each pin was already KSCATEGORY_AUDIO.
-----Original Message-----
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Stephan Kappertz
Sent: Monday, October 03, 2005 2:59 AM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: AVStream and Wave Devices
I had a similar problem when i started with the DDK AVStream sample
code.
The output pin wasn't enumerated as KSCATEGORY_AUDIO_DEVICE even though
the
KSCATEGORY_AUDIO filter did show up in KSStudio
What does your pin descriptor look like?
For me using the following Categories and names in the Pin descriptor
fixed
the problem:
Playback pin:
&KSCATEGORY_AUDIO, // Category
&KSNODETYPE_SPEAKER, // Name
Record pin:
&KSCATEGORY_AUDIO, // Category
&KSAUDFNAME_RECORDING_CONTROL, // Name
- Stephan
----- Original Message -----
From: "Sam Tertzakian" <sam@xxxxxxxxxxx>
To: <wdmaudiodev@xxxxxxxxxxxxx>
Sent: Monday, October 03, 2005 12:37 AM
Subject: [wdmaudiodev] Re: AVStream and Wave Devices
> Hi,
>
> If I explicitly break the rules is in the DDK and call
> IoRegisterDeviceInterface() using KSCATEGORY_AUDIO_DEVICE (in addition
to
> CAPTURE and RENDER), then, my device appears in KsStudio under
> KSCATEGORY_AUDIO, KSCATEGORY_AUDIO_DEVICE, KSCATEGORY_CAPTURE and
> KSCATEGORY_RENDER).
>
> But, the device does not appear under GraphEdit's "Audio Capture
Sources".
> And the device is not listed under the Control Panel in Sounds Control
> applet.
>
> I know I am not supposed to explicitly use KSCATEGORY_AUDIO_DEVICE
because
> it is reserved for SysAudio. But, it does get me a bit farther.
>
> Does anybody have any ideas?
>
>
> -----Original Message-----
> From: wdmaudiodev-bounce@xxxxxxxxxxxxx
> [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Sam Tertzakian
> Sent: Saturday, October 01, 2005 11:00 PM
> To: wdmaudiodev@xxxxxxxxxxxxx
> Subject: [wdmaudiodev] Re: AVStream and Wave Devices
>
> Hi,
>
> I forgot to mention that one of the things I tried was registering the
> classes in the driver (like the sample driver provided on the board).
But,
> the result is the same. I can always enumerate the KSCATEGORY_AUDIO
devices,
> but still it does not appear in the SYSAUDIO KSCATEGORY_AUDIO_DEVICE
> category (for "Audio Capture Devices").
>
> No matter what I do, the result is always the same.
>
> I think the key is that the SADxx registry keys are not updated
properly.
>
> I am specifically trying to expose a WaveAPI device.
>
> -----Original Message-----
> From: wdmaudiodev-bounce@xxxxxxxxxxxxx
> [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Sam Tertzakian
> Sent: Saturday, October 01, 2005 10:22 PM
> To: wdmaudiodev@xxxxxxxxxxxxx
> Subject: [wdmaudiodev] AVStream and Wave Devices
>
> Hi,
>
> I wrote a while back about exposing Wave devices using AVStream.
> I tried several ways, including setting up a topology.
> But, still, I am unable to make the device appear in the Audio Capture
> category.
>
> I set up a toplogy...thinking that might be the problem...but no it
did
not
> work.
>
> I have examined all the registry entries...they are all there except
for
the
> ones that make the "SADxx" where xx is a number entries. (SysAudio
entries).
>
> Does anybody have an INF file the can send me that I can compare mine
with?
>
>
> -----Original Message-----
> From: FreeLists Mailing List Manager [mailto:ecartis@xxxxxxxxxxxxx]
> Sent: Saturday, October 01, 2005 12:05 AM
> To: wdmaudiodev digest users
> Subject: wdmaudiodev Digest V2 #110
>
> wdmaudiodev Digest Fri, 30 Sep 2005 Volume: 02 Issue: 110
>
> In This Issue:
> [wdmaudiodev] Two identic soundcards installed
>
> ----------------------------------------------------------------------
>
> Subject: [wdmaudiodev] Two identic soundcards installed
> Date: Fri, 30 Sep 2005 16:12:19 +0200
> From: "Markus Bollinger" <bollinger@xxxxxxxxxxxx>
>
> Hello!
>
> If I have two identic Soundcards installed on my PC (e.g. "Creative
Sound
> Blaster PCI"),
> on MME the second card gets the extension "(2)" to it's friendly
device
> name.
> To select a device, MME based applications, the WaveMapper or
SoundVol32
> work correctly.
>
> But in DirectSound the "(2)" is not added.
>
> When I use WindowsMediaPlayer 10, I cannot select the second card
> When I use WinAmp 5, I can select the second card for output, but it
will
> play on the first one.
>
> Have I to consider this as application bugs, or should the driver
implement
> some workaround :
>
> I saw that with KSPROPERTY_GENERAL_COMPONENTID
> the devices can be renamed in the driver, but it seems that this does
not
> work on Windows 2000
>
> Do you know other solutions ???
>
>
> - Markus
>
> You can find Digigram at:
> Integrated Systems Asia, Suntec, Singapore, October 12-14, 2005, Booth
> number: F110
>
> ------------------------------
>
> End of wdmaudiodev Digest V2 #110
> *********************************
> ******************
>
> 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/
>
******************
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/
******************
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/
Other related posts:
