Reply to thread

Message

<blockquote data-quote="bigj" data-source="post: 32154" data-attributes="member: 10940">Yes to both these - I reapplied just to be sure - but it's still the same.I'd be ok with the timeshift-always-on workaround, but unfortunately, even with this workaround I still have a problem:The compro captured stream has drop outs (video/audio discontinuities) whenever the Leadtek is active. Interestingly the converse isn't true, the Leadtek works regardless of whatever the compro is doing. The compro works fine if the leadtek is not active. I tried running the compro in solo-mode and running the&nbsp; leadtek winfast DTV software to activate it outside of MP. Running like this, the compro is fine - implying there is no fundamental HW level conflict. Also, since the leadtek works ok if the compro is in use, there is no fundamental problem with MP (I tried switching the card1,card2 order to confirm this too). Rather, the problem lies when using the compro+leadtek with directshow/bda... Now my question (to myself) is - is this the compro's drivers not playing nice or the leadteks drivers not playing nice! Mmm or is the dshow runtime at fault, but always/only affecting the compro due to some internal card enumeration ordering...Fun and games...BigJ.</blockquote>

[QUOTE="bigj, post: 32154, member: 10940"] Yes to both these - I reapplied just to be sure - but it's still the same. I'd be ok with the timeshift-always-on workaround, but unfortunately, even with this workaround I still have a problem: The compro captured stream has drop outs (video/audio discontinuities) whenever the Leadtek is active. Interestingly the converse isn't true, the Leadtek works regardless of whatever the compro is doing. The compro works fine if the leadtek is not active. I tried running the compro in solo-mode and running the leadtek winfast DTV software to activate it outside of MP. Running like this, the compro is fine - implying there is no fundamental HW level conflict. Also, since the leadtek works ok if the compro is in use, there is no fundamental problem with MP (I tried switching the card1,card2 order to confirm this too). Rather, the problem lies when using the compro+leadtek with directshow/bda... Now my question (to myself) is - is this the compro's drivers not playing nice or the leadteks drivers not playing nice! Mmm or is the dshow runtime at fault, but always/only affecting the compro due to some internal card enumeration ordering... Fun and games... BigJ. [/QUOTE]

Verification