152 replies to this topic

[littlesat]

As far I see this plug is a kind of 'hacky' work-a-round... it would be much better to find a real solution...

 

And this starts with a good detection of the CI is properly working and can decode a specific service and ensure that it is correctly (re)initialized when enigma2 is (re)started.

[neo]

This plugin is a "must have" when you want to combine CI(+) decoding and softcam and it is not at all in any feed?

It is possible that I have it on some boxes because I install it manually.

 

So it should be proposed in the feed. 

 

No problem with that combination here (but using the assignment plugin and an oscam filter).

 

And a plugin that overwrites my enigma2_pre_start.sh gets my veto, absolutely not done !

Edited by neo, 14 February 2023 - 12:54.

[Pr2]

This plugin is not in the nightly build feed for the ABCom Pulse 4K and this is a must have on this box when you have a CI+ module inserted.

Can you please add it into the feed?

Edited by Pr2, 28 April 2023 - 16:15.

[neo]

Then someone needs to make a bb recipe for it.

[littlesat]

Or maybe better solve the underlaying issue (with a real structured work-a-round).

e.g. when the box comes out of standby or startsup cold give the CI a reset…

Edited by littlesat, 28 April 2023 - 20:05.

[Pr2]

This is not linked with cold or hot restart the problem is zapping between CI+ and SAT (using OSCam) also sometimes when zapping from IPTV to DVB channel etc. Dimitri has done a great job with this plugin so it is a  must have for complex setup.

[WanWizard]

I would like to know what problem it exactly addresses, as I have never had or understand the need for it.

 

I know there is an issue when you have channels that can be served by both the CI and Oscam, Enigma will use both and that causes stability issues, but that can be solved worked around by blocking those channels in Oscam using a services file.

 

I've done that on my Solo 4K, and ever since the CI channelrs are as stable as a rock.

[el bandido]

I would like to know what problem it exactly addresses, as I have never had or understand the need for it.

 

The Slow zap plugin allows for splitting channels or services between two tuners. I realize that is not what it was originally designed to do, but that is what I have used it for.
 

For example, I have two ATSC usb tuners C & D connected to two different antennas. The Slow zap plugin will allow me to assign ATSC channels to each of these tuners as needed.  If I have ATSC usb tuner C using an antenna aimed West, then I can assign the channels that are viewable to the West to use tuner C and have the other ATSC channels use usb tuner D.  No other plugin that I know about allows this.

 

[neo]

So you use it to work around the limitation of having only one namespace available for ATSC / DVB-T / DVB-C ?

[el bandido]

Correct.
If enigma2 could be modified then I would no longer need the plugin. As enigma2 is now, all of the ATSC channels are viewable on one tuner and cannot be separated as needed into two or more tuners.

[Pr2]

Here is small explanation of a problem fixed with this plugin:  DVB-C is using CI+ module   DVB-S is using OScam.

Descrambling is working in DVB-C  switching to DVB-S it descramble the channel too.

 

But from DVB-S to DVB-C the first channel I zap to is not descrambled (Common interface assignment is not helpfull), I need to zap to another DVB-C to have the image and then back to the channel I want to watch (in DVB-C) so double zap is always mandatory.

 

With slow zap for CI installed and active and configure to reset play service on DVB-C and DVB-S, when zapping after a while the play service is restarted and the channel is descambled at the very first zap.

[neo]

It would intresting to know WHY this is a problem, and WHY the plugin is needed to fix (or work around) it.

 

Is it an init issue with the CI module? A timing issue with the CI module?

[littlesat]

The plugin is indeed a work-a-round as the inlaying issue is still not resolved. Unless this it is still helpfull….