[wdmaudiodev] Re: AVStream and Wave Devices
- From: "Sam Tertzakian" <sam@xxxxxxxxxxx>
- To: <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Sun, 2 Oct 2005 15:37:08 -0700
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/
Other related posts:
