are you going to jail? why is it so hard to understand that we have laws in Europe that must be followed?
Nope
Making the channel limit for ci interface is not breakinking the law.
I am only suggesting how to handle mux based on 'Multiple service support' ( e.g. number 1..x)?
And it's not even working currently - 'Multiple service support' as 'No' doesn't do anything as system still tries to use same tuner for second encrypted channel.
I would call this as a bug.
... as there is no official use case.
Understood but
My learning from the past is different. I was working for company thinking what customer needs and not realizing what they need..
E.g. Offcial use case < customer use case and you should seek competitive advandage.
Apologies - even you didn't even read my post fully.
To make it clear without reading further my above post, I was not asking or proposing daisy chaining on my last post 
Case closed from my side.
your idea is valid and technically it works, but you would need to define a second fake sat position so that e2 is not realizing that it is the same transponder. But for daily usage this is too complicated. Most of the time you need it not for 2 recordings but for watching and recording or pip and there service relation plugin and sd alternative channel is the easier solution.
Yes on satellite you can make fake postion - not so big thing to do, but maintenance can be little mess in log run.
As you sa not perfect, but should work some way if someone needs such solution.
In case of DVB-T2 I assume you cannot have multiple terrestrial*.xml files.
In general this CI handling is not perfect, as if you autorecord something on two CI channels & same transponder you can loose both recordings.
There will be more and more CI channels in future.
I think in long run it would be good to have tuner specific recording limit for CI encrypted channels.
Alternative service doesn't work in my case as I don't have SD available for those terrestrial channels.
daisy chaining of 2 ci on same transponder is not supported. You can use service relation plugin to overcome with sd alternative channels but this is all as these modules don't offer multicrypt.
I thought it could be possible to allocate second tuner in this case and use second CI with it.
I have 7080HD and two cards and cams for one operator package. I have assigned 'HD1 ch' for CI-1 and 'HD2 ch' for CI-2 slot.
In addition I use softcam for SD channels.
Operator doesn't offer CAM for multiple service it's limited to one descramble only.
On CI settings I have defined 'Multiple service support' as 'No'
System seems to work if channels are on different transponders, but not when those on same transponder.
it would be logical that system would assign new tuner/CI for same transponder if MSS is set to 'no' ?
Is this bug, or limitation in enigma2 ?
Are there any plans to make this work ?
