158 replies to this topic

[Huevos]

Almost every satellite receiver allows the user to choose between FTA and encrypted channels when doing a scan. And also to display an encryption flag in the channel list.

 

Is there any reason why this hasn't been implemented in Enigma2? And is it possible?

[littlesat]

I would recommend you could ask those who initially did design E2

 

What added value does it have. Only to indicate it in a channel list. When you actually zap to a channel you'll see this information. And during a scan the actual status of a channel is used (some channels are sometimes free and some channels do have an ECM while they are free)...

 

Of course it can be added. We need to add a flag in lamedb, add a flag to each channel in the software and arrang that in channel list an indicator might be given (another indicator)... and we need to add to store this flag during scanning of channels...

 

The big question is will this really be added value????

[blzr]

you can choose to scan only fta services, in manual scan

Attached Files

•  manual_scan.jpg   60.67KB   73 downloads

[zeros]

I see here an opportunity to sort out the free unencrypted channels. May find some interesting free channel, which would otherwise be overlooked but I'm not sure, is it worth the hassle Adding this flag?

[zeros]

Please delete my double posts- I posted at the same time, and since it is adopted, then I tried several times..

[Huevos]

you can choose to scan only fta services, in manual scan

Yes, sorry, got confused.

[Huevos]

The big question is will this really be added value????

You can say that about most things that are added to the image, but as a collective they make the image what it is today.

[Huevos]

you can choose to scan only fta services, in manual scan

So what about the background scan? Say I set up my manual scan to only grab FTA services. Then I'm viewing those services. Does the background scan just add the encrypted services off the same transponder that I told manual scan not to include?

[blzr]

well, not sure, but I would be highly surprised if option selected for one particular manual scan had an affect on general background scan process on a given transponder/satelite(s);

how I understand it, it's usefull for creating any FTA bouquets, eg. you choose to scan only free services on 13E, then you just rename resulting 'Last scanned' to 'FTA 13' or cherry-pick interesting FTA services and add it to some bouquet, etc...

[Huevos]

Littlesat the added value is you can see the encrypted channels at a glance before zapping, rather than zapping through each and every channel to find this out.

[Rob van der Does]

Littlesat the added value is you can see the encrypted channels at a glance before zapping, rather than zapping through each and every channel to find this out.

That's exactly why I would love such a feature.

Even though knowing that it'll never be perfect, as some services toggle between FTA & encrypted.

[littlesat]

Without any 100% guarantee that at that moment that channel is indeed encrypted or not.... It can only indicate the status of that channel before....
But mostly indeed it might be true...
And it is another icon you might see configurable in the channel list.

I do not want to be negative or pessimistic about such things... I will only try to give all arguments also negative ones.

Openpli is open software. A good patch is of course welcome.
To make this work it also requires some changes is cpp. This will not only be python related changes. In addition you need also find a way to store it in lamedb so it might also gave issues with settings editors.

[Huevos]

Without any 100% guarantee that at that moment that channel is indeed encrypted or not.... It can only indicate the status of that channel before....

You could say that about anything. For example way bother having a channel list at all because some channels may have closed down and gone and the channel list doesn't reflect this. It's obvious we can't know the true state of a channel until we try to tune it, but that doesn't mean that "at-a-glance" information is not useful. For me this is a real pain because if I switch to a channel and the screen remains blank it is not immediately obvious if this is due to no signal or encryption. Only after several seconds if/when the error message appears does it become obvious if it is due to lack of signal.

 

To make this work it also requires some changes is cpp.

That's why I posted, as I have zero knowledge in that area.

 

In addition you need also find a way to store it in lamedb so it might also gave issues with settings editors.

Same with AAC audio pid caching, which is not yet recognized by most settings editors, but that was added recently and no one complained then. And anyway as long as that individual channel is not edited with the settings editor the settings will remain. Also even if the settings editor did remove the flag, a background scan should reinstate it next time the transponder is accessed.

[littlesat]

I understand you would like this feature.... Indeed you need to patch also around in cpp in more places to make this correctly. And indeed the caching from acc and settings editors is a pain...

When someone needs this feature hopefully someone is willing to make it and possibly help you...

As most users are working with standaard settings we need first to find a way how to put it in labedb and settings editors...

I suggest the complete effort is huge... This is not a simple patch... And just for yet another added icon feature in the channel list...

And that is why I was doubting the real added value.. But it might indeed be a missing feature compared to non e2, provider owned boxes.

When you really make this a good feature you also update the flags as,
1, free
2, coded but unknown if it can be encoded,
3, coded last time I zapped the channel it did open...
4, coded the last time I zaped the channel did not open....

But note this is a huge patch...

Edited by littlesat, 28 March 2014 - 11:47.

[Dimitrij]

My opinion is that this patch is needed.
Primarily for enigma2 open software/openPli progress.

Edited by Dima73, 28 March 2014 - 19:01.

[Dimitrij]

My opinion is that this patch is needed.
Primarily for enigma2 open software/openPli progress.

Sorri.My terrible english

 

My opinion is that this patch needed.
Primarily for enigma2 open software/openPli progress.

[Huevos]

Mine too, and it has been asked for several times in the past.

[Rob van der Does]

And it looks like DBE has already anticipated that change:

 DBE-Encrypted.jpg   201.73KB   71 downloads

[littlesat]

Then in lamedb there should already be a way to get the information a channel in encrypted yes or no... If so then this could be a relative simple patch... In servicelist.cpp you need to add an option to add the specific icon and an algorythm ro detect the encryption status.

Edited by littlesat, 29 March 2014 - 07:36.

[littlesat]

As far I can see there exist a way in lamedb to detect a channel has encryption or not (it has ECM streams the last time you zapped to it)

 

5226:00eb0000:0c99:0003:25:0
Canvas HD
p:M7 Group,c:000204,c:010068,c:020024,c:030204,c:050001,C:1819,C:1818,C:1817,C:0500,C:0100

When there are no front numbers, so the lenght is 4 after a C line... you have a caid.

 

I hope this information is helpfull for Huevos... and in addition I hope when we makes a patch for it he also offers a patch for OpenPLi directly
 

Edited by littlesat, 29 March 2014 - 08:30.