Reply to thread

Message

<blockquote data-quote="CyberSimian" data-source="post: 1141260" data-attributes="member: 141969">When I was using WMC with my (at that time) newly-acquired TBS6284 cards, I had a problem with the start-up of one tuner causing a momentary interruption on other tuners that were already active (the interruption was visible both on live TV and recorded TV).&nbsp; The situation was very complex, because it depended on which tuner started first, which tuner started second, and which card they were on; some combinations worked correctly, others combinations caused the momentary interruption. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown&nbsp; &nbsp; :(" loading="lazy" data-shortname=":(" />Part of the difficulty in identifying a faulty tuner or faulty tuner-card is identifying which PCI-Express slot corresponds to which set of tuners.&nbsp; Although the &quot;device id string&quot; uniquely identifies which tuners reside on which card, it does not obviously identify which card resides in which slot.&nbsp; The only way that I found to identify the slot was to remove one card, reboot, and then write down the device-id string shown in Windows &quot;Device Manager&quot; for the remaining card.&nbsp; All very cumbersome. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown&nbsp; &nbsp; :(" loading="lazy" data-shortname=":(" />Ideally, MP should identify the PCI slot or PCI-Express slot containing the card on which each tuner is located. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />&nbsp; (Assuming that that is even possible, of course. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" />)Finally, I am pleased to report that the momentary interruption that occurred when tuners started on WMC does not seem to occur with MP.&nbsp; I guess that there is some difference in the tuner management such that MP does not provoke this error. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite24" alt="(y)" title="Thumbs Up&nbsp; &nbsp; (y)" loading="lazy" data-shortname="(y)" /> -- from CyberSimian in the UK</blockquote>

[QUOTE="CyberSimian, post: 1141260, member: 141969"] When I was using WMC with my (at that time) newly-acquired TBS6284 cards, I had a problem with the start-up of one tuner causing a momentary interruption on other tuners that were already active (the interruption was visible both on live TV and recorded TV). The situation was very complex, because it depended on which tuner started first, which tuner started second, and which card they were on; some combinations worked correctly, others combinations caused the momentary interruption. :( Part of the difficulty in identifying a faulty tuner or faulty tuner-card is identifying which PCI-Express slot corresponds to which set of tuners. Although the "device id string" uniquely identifies which tuners reside on which card, it does not obviously identify which card resides in which slot. The only way that I found to identify the slot was to remove one card, reboot, and then write down the device-id string shown in Windows "Device Manager" for the remaining card. All very cumbersome. :( Ideally, MP should identify the PCI slot or PCI-Express slot containing the card on which each tuner is located. :) (Assuming that that is even possible, of course. :D) Finally, I am pleased to report that the momentary interruption that occurred when tuners started on WMC does not seem to occur with MP. I guess that there is some difference in the tuner management such that MP does not provoke this error. (y) -- from CyberSimian in the UK [/QUOTE]

Verification