106 replies to this topic

[littlesat]

Manual overwrite is note done as you need to solve it at the source... please notify lyngsat that they should not remove it and put it back.... work a round it is not helpfull as it also avoids people to complaint at lyngsat... at the end it does not help really before you know the next work a round need to be added

Edited by littlesat, 18 May 2019 - 13:01.

[Huevos]

Yes, agreed but current issue in PLi is no one can scan PLS muxes.

[jpuigs]

I notified Lyngsat several days ago. Let's hope they were removed accidentally, but to me it doesn't look like it.

 

…. and have you already got a reply ??

I know Christian Lyngemark (lyngsat owner) since more than 20 years ago... he's swedish…. and in Spain when you say that "somebody does swedish" (Hacerse el Sueco), it means that he acts like if he doesn't hear you.,"play dumb",  in french it'd be "Faire la sourde oreille"

 

Jokes apart, I'd bet that these values have not been accidentally removed, they've been removed because "somebody" has told to do it.

Edited by jpuigs, 18 May 2019 - 14:17.

[Huevos]

 

It is very basic. It just reads the LCNs from the SI tables and creates a bouquet file. Enigma does the service scan.

 

Source is available on oe-alliance-plugins. I put it there today so no feedback yet. Will be in the feeds of any image that builds that git.

 

Thanks for the plugin.

I tried it, but it found nothing on French ones, and just a few tranponders on Italian ones (12543 H).

I noticed that on OpenPli satellites.xml file there is no PLS codes, just IS , that's why it just finds that tranponder that doesn't use PLS.

<transponder frequency="11509000" symbol_rate="29500000" polarization="0" fec_inner="6" system="1" modulation="2" is_id="1" />  MISSING PLS CODE
<transponder frequency="11509000" symbol_rate="29500000" polarization="0" fec_inner="6" system="1" modulation="2" is_id="4" />  MISSING PLS CODE
<transponder frequency="11509000" symbol_rate="29500000" polarization="0" fec_inner="6" system="1" modulation="2" is_id="6" />  MISSING PLS CODE
……

I inserted them, and now it works.

 

I've found 2 small problems:

-Text is too small, instead of font 18 I'd use at least 36.

-If I scan any provider, and I set "clear before scan", it deletes the other one.

 

Yes, it won't work without the PLS codes (just like any enigma scan).

 

The embeded skin is for 720 frame buffer, so if the plugin is not in the current skin that is what you will see. So text will be small on 1080 skins. I'll try to improve it.

 

If you want to clear before scan, do it on the first scan but not the second.

[Huevos]

 

I notified Lyngsat several days ago. Let's hope they were removed accidentally, but to me it doesn't look like it.

 

…. and have you already got a reply ??

I know Christian Lyngemark (lyngsat owner) since more than 20 years ago... he's swedish…. and in Spain when you say that "somebody does swedish" (Hacerse el Sueco), it means that he acts like if he doesn't hear you.,"play dumb",  in french it'd be "Faire la sourde oreille"

 

Jokes apart, I'd bet that these values have not been accidentally removed, they've been removed because "somebody" has told to do it.

 

I don't know what you mean by this. What do you mean "somebody"?

[MCelliotG]

 

Are these values be available on lyngsat.... when nope than I would consider to contact them...

This is a known issue. The PLS codes have been removed from Lyngsat. This affects 40 transponders. Without these codes PLS scans do not work. In OE-A parser a manual override has been added to insert know PLS codes.

 

I notified Lyngsat several days ago. Let's hope they were removed accidentally, but to me it doesn't look like it.

 

And the dumb question of the day is:

Is Flysat's site structure that different from Lyngsat's so the nice developers that created the parser from Lyngsat can now use Flysat instead to generate the satellites.xml file?

Because obviously there are issues with Lyngermark that are not new...

[jpuigs]

Yes, it won't work without the PLS codes (just like any enigma scan).

 

I inserted them, and now it works.

 

I've found 2 small problems:

-Text is too small, instead of font 18 I'd use at least 36.

-If I scan any provider, and I set "clear before scan", it deletes the other one.

 

The embeded skin is for 720 frame buffer, so if the plugin is not in the current skin that is what you will see. So text will be small on 1080 skins. I'll try to improve it.

 

If you want to clear before scan, do it on the first scan but not the second.

 

 

 

 

 

 

 

Jokes apart, I'd bet that these values have not been accidentally removed, they've been removed because "somebody" has told to do it.

 

I don't know what you mean by this. What do you mean "somebody"?

 

Somebody who'd be interested people don't receive these signals. Service providers….  tv stations…..

If I knew who is, I'd tell it. 

Edited by jpuigs, 18 May 2019 - 18:23.

[Huevos]

 

 

Are these values be available on lyngsat.... when nope than I would consider to contact them...

This is a known issue. The PLS codes have been removed from Lyngsat. This affects 40 transponders. Without these codes PLS scans do not work. In OE-A parser a manual override has been added to insert know PLS codes.

 

I notified Lyngsat several days ago. Let's hope they were removed accidentally, but to me it doesn't look like it.

 

And the dumb question of the day is:

Is Flysat's site structure that different from Lyngsat's so the nice developers that created the parser from Lyngsat can now use Flysat instead to generate the satellites.xml file?

Because obviously there are issues with Lyngermark that are not new...

 

Lyngsat covers the whole arc. Flysat and King-of-sat only cover a portion.

[Pr2]

Hi,

 

I also notify Lyngsat about this but no answer.

 

Would be good to wrote a grabber for kingofsat which display them on the main page. 

 

Pr2

[Huevos]

Hi,

 

I also notify Lyngsat about this but no answer.

 

Would be good to wrote a grabber for kingofsat which display them on the main page. 

 

Pr2

Yes, nice info on there and tidy mark up, but only 75E - 63W. What about the rest of the arc?

 

As pointed out above the Lyngsat PLS info has been moved to the mux pages. So still there but would involve downloading hundreds of pages to get the full data.

[Pr2]

Page must be downloaded only if PLS is detected in the main page otherwise no need to download the sub-page.

[dhwz]

They can also encrypt the multiplexes... and decrypt it before they are relayed.

Yes of course, but why pay an encryption license when the channels are FTA?

That's, indeed, in the end, imho, the crux of the matter. They really would like to use encryption, but encryption costs money, quite a bit, so I've heard, so they now fallback to "poor men's" encryption using PLS.

Encryption makes sense though, because the feed can be received all over Europe, not just in France.

PLS is NOT an encryption at all.

[Erik Slagter]

That is why I called it a "poor men's encryption". Please read.

[Erik Slagter]

Maybe Lyngsat was "requested" to remove the PLS values (for the reason in the post above). In that case we should grab it otherwise or we could adjust the grabber script to insert them explicitly.

 

Regarding making bouquets, LCN, etc. I don't like them inside enigma, that would mean a pile of code for every provider, no thanks. So a plugin makes perfectly sense.

[bestman22]

Interested

[Huevos]

Maybe Lyngsat was "requested" to remove the PLS values (for the reason in the post above). In that case we should grab it otherwise or we could adjust the grabber script to insert them explicitly.

 

Regarding making bouquets, LCN, etc. I don't like them inside enigma, that would mean a pile of code for every provider, no thanks. So a plugin makes perfectly sense.

After exchanging a couple of emails the values have now returned... so no need to do anything.

[Huevos]

 

-Text is too small, instead of font 18 I'd use at least 36.

 

I've made the embeded skin dynamic so it scales with the screen resolution. So font is 22 in a 720 skin and 33 in a 1080 skin.

https://github.com/o...52a8df427884309

Edited by Huevos, 21 May 2019 - 02:56.

[Huevos]

 10.jpg   104.79KB   4 downloads

[littlesat]

I see the plugin does poke into /etc/enigma2 by writing files there and then do a reload settings...it also duplicates the bouquet parsers that are already in e2. It actually does the same as Abm is doing. It is better to creating/adapting the bouquets via e2.. so it actually should be a plugin... maybe some time I need to demonstrate how as it saves hundreds lines of code in this plugin, makes it more readable, faster and structured. Poking into userbouquets and bouquets and lametv is actually not done. It also introduces a ‘race’ condition...
The how is actually demonstrated in fastscan, cablescan (cpp) en somehow like ik did with hide userbouquets.

Edited by littlesat, 21 May 2019 - 06:50.

[littlesat]

When lyngsat has a reason not to give these values anymore than the only work a round is indeed put them in somehow... and hope nobody noticed it that we do not receive the same request...