Hello Frank, > The history and reason behind this design decision is that, back > when this work was first done (I believe Vista timeframe) > empirically we found that the names returned by drivers for speakers > were very odd and unfriendly. The problem is not only in endpoint names. Windows works with speaker-type nodes a different way than with line-type ones. For example, channel configuration button in audio properties applet is enabled only for speaker-type nodes. In addition, there are some differences in stream processing, channel mapping etc. So if a driver can provide its own name for the output node, it cannot do it without losing some device functions and decreasing compatibility. Regards, Eugene ****************** 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/