Reply to thread

Message

It did.... eventually... and only for a little while...

Tried these scenarios:

Setup 1
1x T-USB2
1x CI Module

The CI Module is configured to service the T-USB2 device in both the card properties and the WinTV CI tab.
Starting the TVService in this scenario gave an error.log straight away - 'Unable to start graph'. Changing channels to first a scrambled one and then to a FTA channel (called 'Nederland 1'), both resulted in the same error.

See: Setup1.log.zip

Setup 2
1x T-USB2
1x CI Module

The CI Module is set in the WinTV CI tab to service another device than the hooked-up T-USB2. In the card properties window, it still is checked it has a CAM available.
Restarted the TVService and tuned into a scrambled channel. For obvious reasons this didn't work and a clear error message was displayed (Channel is scrambled). FTA tuning was no problem

See: setup2.log.zip

But....
Playing with the settings and fiddling around a bit with checkboxes and restarting the TVService every now and then, it suddenly started working!?!?!?!?! I could now watch scrambled channels with the T-USB2 + CI Module

The odd thing is: it's not reproduceable. Continuing to fiddle with the settings didn't breakup the ability to use the CI module with the T-USB2. Unless the code in the patched library is self-learning and recoding itself on the fly, I got no explanation.

However, I then stopped the TVService, disconnected the T-USB2, hooked up the T-Stick and restarted the TVService and all hell broke loose on the error.log file. It quickly grew to > 4MB.
And in no way it was possible to make the thing work again (while it did before) and changing prefs and props in the TVServer Configuration didn't help a bit; error.log kept growing rapidly and it wouldn't ever work

See: setup3.log.zip

Then I hooked up the T-USB2 again, paired it back to the CI Module: same result as Setup 1... unable to start graph for scrambled and FTA channels.

Tried the settings from Setup 2 again: FTA channels are received okay, scrambled channels produce a neat 'Unable to tune - Channel is scrambled'

Trying to fiddle again with the settings, but the CI support for the T-USB2 never came back (log files identical to the ones for Setup 1)
Continue to fiddle with settings for the T-Stick also never gave back the CI support for it..
See: Setup4.log.zip

And the strangest thing is that even with the original DLL, it is not possible anymore to get the T-Stick to function properly with the CI module anymore either...
See: Setup5.log.zip

<blockquote data-quote="jigsjdg" data-source="post: 309905" data-attributes="member: 66927">It did.... eventually... and only for a little while...Tried these scenarios:Setup 11x T-USB21x CI ModuleThe CI Module is configured to service the T-USB2 device in both the card properties and the WinTV CI tab.Starting the TVService in this scenario gave an error.log straight away - 'Unable to start graph'. Changing channels to first a scrambled one and then to a FTA channel (called 'Nederland 1'), both resulted in the same error.See: Setup1.log.zipSetup 21x T-USB21x CI ModuleThe CI Module is set in the WinTV CI tab to service another device than the hooked-up T-USB2. In the card properties window, it still is checked it has a CAM available.Restarted the TVService and tuned into a scrambled channel. For obvious reasons this didn't work and a clear error message was displayed (Channel is scrambled). FTA tuning was no problemSee: setup2.log.zipBut....Playing with the settings and fiddling around a bit with checkboxes and restarting the TVService every now and then, it suddenly started working!?!?!?!?! I could now watch scrambled channels with the T-USB2 + CI ModuleThe odd thing is: it's not reproduceable. Continuing to fiddle with the settings didn't breakup the ability to use the CI module with the T-USB2. Unless the code in the patched library is self-learning and recoding itself on the fly, I got no explanation.However, I then stopped the TVService, disconnected the T-USB2, hooked up the T-Stick and restarted the TVService and all hell broke loose on the error.log file. It quickly grew to &gt; 4MB.And in no way it was possible to make the thing work again (while it did before) and changing prefs and props in the TVServer Configuration didn't help a bit; error.log kept growing rapidly and it wouldn't ever workSee: setup3.log.zipThen I hooked up the T-USB2 again, paired it back to the CI Module: same result as Setup 1... unable to start graph for scrambled and FTA channels. Tried the settings from Setup 2 again: FTA channels are received okay, scrambled channels produce a neat 'Unable to tune - Channel is scrambled'Trying to fiddle again with the settings, but the CI support for the T-USB2 never came back (log files identical to the ones for Setup 1)Continue to fiddle with settings for the T-Stick also never gave back the CI support for it..See: Setup4.log.zipAnd the strangest thing is that even with the original DLL, it is not possible anymore to get the T-Stick to function properly with the CI module anymore either...See: Setup5.log.zip</blockquote>

[QUOTE="jigsjdg, post: 309905, member: 66927"] It did.... eventually... and only for a little while... Tried these scenarios: [B]Setup 1[/B] 1x T-USB2 1x CI Module The CI Module is configured to service the T-USB2 device in both the card properties and the WinTV CI tab. Starting the TVService in this scenario gave an error.log straight away - 'Unable to start graph'. Changing channels to first a scrambled one and then to a FTA channel (called 'Nederland 1'), both resulted in the same error. [I]See: Setup1.log.zip[/I] [B]Setup 2[/B] 1x T-USB2 1x CI Module The CI Module is set in the WinTV CI tab to service another device than the hooked-up T-USB2. In the card properties window, it still is checked it has a CAM available. Restarted the TVService and tuned into a scrambled channel. For obvious reasons this didn't work and a clear error message was displayed (Channel is scrambled). FTA tuning was no problem [I]See: setup2.log.zip[/I] But.... Playing with the settings and fiddling around a bit with checkboxes and restarting the TVService every now and then, it suddenly started working!?!?!?!?! I could now watch scrambled channels with the T-USB2 + CI Module The odd thing is: it's not reproduceable. Continuing to fiddle with the settings didn't breakup the ability to use the CI module with the T-USB2. Unless the code in the patched library is self-learning and recoding itself on the fly, I got no explanation. However, I then stopped the TVService, disconnected the T-USB2, hooked up the T-Stick and restarted the TVService and all hell broke loose on the error.log file. It quickly grew to > 4MB. And in no way it was possible to make the thing work again (while it did before) and changing prefs and props in the TVServer Configuration didn't help a bit; error.log kept growing rapidly and it wouldn't ever work [I]See: setup3.log.zip[/I] Then I hooked up the T-USB2 again, paired it back to the CI Module: same result as Setup 1... unable to start graph for scrambled and FTA channels. Tried the settings from Setup 2 again: FTA channels are received okay, scrambled channels produce a neat 'Unable to tune - Channel is scrambled' Trying to fiddle again with the settings, but the CI support for the T-USB2 never came back (log files identical to the ones for Setup 1) Continue to fiddle with settings for the T-Stick also never gave back the CI support for it.. [I]See: Setup4.log.zip[/I] And the strangest thing is that even with the original DLL, it is not possible anymore to get the T-Stick to function properly with the CI module anymore either... [I]See: Setup5.log.zip[/I] [/QUOTE]