[mythtv-users] Digital Devices Duoflex with Octopus CI

[Hika van den Hoven]

Hoi Mike,

Wednesday, July 27, 2016, 4:08:12 PM, you wrote:

> On 27/07/16 14:39, Hika van den Hoven wrote:
>> Hoi Discussion,
>>
>>  Earlier this week I received my new DD duoflex C2/T2 with a Octopus
>>  single CI+. I got it setup without to much difficulty, although proper
>>  documentation is a bit lacking. I had to gather it from all over the
>>  net.
>>  http://www.digital-devices.eu/shop/de/linux-treiber
>>  https://www.linuxtv.org/wiki/index.php/Digital_Devices_DuoFlex_C%26T
>>  and some others. I used the dddvb driver as in the first link.
>>  The kernel driver is not supporting all DD devices and you need
>>  a separate driver that seems to work OK AND a not so good documented
>>  option needs to be added on loading the ddbridge module:
>>  adapter_alloc=3, although dd mentions fmode=3.  From what I have
>>  found it has to do with unicable, any way without it both tuner and
>>  the CI get their own /dev/dvb/adapter* directory and besides them
>>  not being able to communicate with each other, making the CI+
>>  unusable, MythTV gets unstable. It has the following possible
>>  settings:
>>  0: adapter0, adapter1 and adapter2
>>  1: adapter0 with both frontends, adapter1 with CI+
>>  2: adapter0 with both frontends, adapter2 with CI+
>>  3: single adapter0 directory with both frontends and CI+
>>  Any other integer gives option 2, no option gives 0.
>>  Both frontends have a frontend,demux, dvr and net node
>>  The CI+ has a ca0 and a ci0 node.
>>
>>  You should be able to switch the frontends between Cable and
>>  Terrestrial mode, but I have not found how, but as they at present
>>  are in Cable modus as I need them, that is no urgent problem.
>>
>>  If you leave it at that they work good and all channels are found,
>>  however not with the CI+ although it seems to have to work almost
>>  transparent and I found some vague mentioning that some got it
>>  working with one tuner under MythTV and a little less vague with
>>  TVheadend.
>>
>>  It should work by redirecting the output from one of the tuners to
>>  the CI+ port and it should be transparent. (In windows you can use
>>  the CI+ with both tuners, but not under Linux) In my case through:
>>
>>  echo "00 02" > /sys/class/ddbridge/ddbridge0/redirect
>>  echo "01 02" > /sys/class/ddbridge/ddbridge0/redirect
>>
>>  before Mythbackend is started for either the first or the second
>>  tuner as described in the second link.
>>  I guess I have to disable multirec for that tuner.
>>
>>  If I do this that tuner becomes completely blind. I can not find any
>>  channels anymore, (but I can through the other) and I can not get any
>>  output. The CAM is OK as it works in my TV. If I try to watch liveTV
>>  through that tuner I get a black screen and I see no errors in the
>>  log. At one time the backend even kind of froze. I could not stop it
>>  even with kill and when I rebooted the machine it hung.
>>
>>  Anybody any thoughts?
>>
> A minor thought. You could put the CI port in an "Input Group" with a tuner, which means that both
> are considered part of the same input and would not be used
> simultaneously - like some of the cards 
> which have both digital and analog tuners. I'm not sure you can do this and use /both/ tuners
> though, but either alone should work like that.

Interesting thought, but MythTV only sees the two frontends?

> I don't think you'd be able to use multirec with a CI card but
> without knowledge of the specific 
> hardware I couldn't say. The bare tuners, yes, you should be able to assuming the multiplexes
> conform to some reasonable standard.



Tot mails,
  Hika                            mailto:hikavdh at gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens