Reply to thread

Message

<blockquote data-quote="tourettes" data-source="post: 654683" data-attributes="member: 10858">Yep, seems that the Xonar is driver developers have ignored the MS documentation. I'll have to check what would be the best way to handle the issue. Reclock seems to have a manual switch for that (hidden debug switch in regustry, based on the forum posts). ffdshow has a special Xonar relate setting - most likely it triggers the same channel mask override <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />I'll move those not working modes under a command line switch. Cannot promice se that it will hide all the error messages thou (since it is good to see at least the catastropic driver failures <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />).</blockquote>

[QUOTE="tourettes, post: 654683, member: 10858"] Yep, seems that the Xonar is driver developers have ignored the MS documentation. I'll have to check what would be the best way to handle the issue. Reclock seems to have a manual switch for that (hidden debug switch in regustry, based on the forum posts). ffdshow has a special Xonar relate setting - most likely it triggers the same channel mask override :) I'll move those not working modes under a command line switch. Cannot promice se that it will hide all the error messages thou (since it is good to see at least the catastropic driver failures :)). [/QUOTE]

Verification