ScanSetup.pyo buggy in the terrestrial scan

[Huevos]

Well it’s just a time extension and not a shortening of the scan ?
Or I don't understand something there ?

The binary checks each transponder is active and any PLP.

The check is pretty quick compared to the timeout scanning an inactive frequency.

Personally, I have never found enigma's built-in terrestrial scanning satisfactory, which is why I wrote the TerrestrialScan plugin. It is in the feeds under SystemPlugins.

[Matrix10]

search for used transponders and then it performs the scan only for the ones it found actually used

I don't see it
Why then does it scan all frequencies and not just one activ in my test/prescan.
So prescan is a pure waste of time,without function.

[Huevos]

It builds a list of transponders that the binary says are "OK".

https://github.com/OpenViX/enigma2/b...nSetup.py#L437

[Matrix10]

It builds a list of transponders that the binary says are "OK".

https://github.com/OpenViX/enigma2/b...nSetup.py#L437

Unfortunately I still don't see the benefits of prescan,
A greater benefit would be for prescan to test the transponder signal
and if there is no signal then there is no wasting time on scans.
That doesn't work for me and besides prescan I have a full scan again.
But well with the exit it is possible to interrupt prescan and make only full scan.

[Huevos]

I don't understand your post.

It scans the transponders of your configured region and returns the good ones.

[Matrix10]

I don't understand your post.

It scans the transponders of your configured region and returns the good ones.

"It scans the transponders of your configured region and returns the good ones."
And then it goes on , to completely scan all the transponders.
Active and inactive.
Bad ones and good ones.
It is to be expected that it scans only active transponders and shortens the scan time.
This way the total scan is only longer.
We have a prescan + complete scan.
Or I don't understand what kind of function prescan is then ?

Tested with Ultimo 4K / T2 tuner

[Huevos]

Is this "wrong" behaviour happening in PLi?

[Matrix10]

Is this "wrong" behaviour happening in PLi?

If I'm not mistaken in all the images is the same
and also in those based on VU + coding.
(BH image tested)

[Huevos]

Ok, the initial commit came from PLi in November. I have submitted a fix there.

https://github.com/OpenPLi/enigma2/p...155e3a473d505f

Let's wait and see if that is accepted before deciding what to do next.

[Matrix10]

Ok, the initial commit came from PLi in November. I have submitted a fix there.

https://github.com/OpenPLi/enigma2/p...155e3a473d505f

Let's wait and see if that is accepted before deciding what to do next.

Thank you for your work.