[wdmaudiodev] Device filter connection weirdness

  • From: Robert Bielik <robert.bielik@xxxxxxxxxx>
  • To: "wdmaudiodev@xxxxxxxxxxxxx" <wdmaudiodev@xxxxxxxxxxxxx>
  • Date: Thu, 22 Sep 2011 17:45:49 +0200

Hello all,

In Portaudio (at least a branch of it), the device filter connections/nodes are 
queried in order to find the topology filter connection pin, and
then traverse the topology filter mainly to find any input multiplexer so that 
WDM KS input devices can be enumerated analogously to WASAPI (or other 
highlevel API).

But I have a strange case where the connections and nodes are a follows:

[11:30:24.168; 5792] TRACE: PA: DumpConnectionsAndNodes: connections=2, nodes=1
[11:30:24.168; 5792] TRACE: PA:   Connection: 0 - FromNode=0,FromPin=1 -> 
[11:30:24.168; 5792] TRACE: PA:   Connection: 1 - FromNode=0,FromPin=0 -> 
[11:30:24.168; 5792] TRACE: PA:   Node: 0 - 

The node is KSNODETYPE_ADC and the connections should be to KSFILTER_NODE nodes 
on either side of the ADC node. So ideally the connections should be:

Connection: 0 - FromNode=4294967295,FromPin=1 -> ToNode=0,ToPin=1
Connection: 1 - FromNode=0,FromPin=0 -> ToNode=4294967295,ToPin=0

but as can be seen from the log above that is not the case.

This has been tested with many devices, and so far only this tester experiences a 
problem. Device in question is a "Conexant 20561 SmartAudio HD".
Smells like a driver bug to me...

Any ideas what I should do given this case ?



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


Other related posts:

  • » [wdmaudiodev] Device filter connection weirdness - Robert Bielik