ScanSetup.pyo buggy in the terrestrial scan

[alexwilmac]

One of the last updates introduced a bug in the ScanSetup.pyo under /usr/lib/enigma2/python/Screens/.
It affects ONLY terrestrial scan, not SAT.

The bug consists of two facts:
1) A prescan is performed like (if I remember well, in vuplus OE3 images). This makes useless possible optimized terrestrial.xml files.
2) What counts most: after the prescan you get always an error.

I used a ScanSetup.pyo from previous releases and both bugs were solved.

Regards.
ViX-5.4-ManualScan-Complete-1.jpg
ViX-5.4-ManualScan-Complete-2.jpg

[Huevos]

Thanks for reporting.

[Huevos]

Which receiver are you using?

[nunigaia]

Which receiver are you using?

@Huevos

As @alexwilmac is a friend that I know from long date ( member of Vuplus-communityu board ) he owns a Solo4K, but the issue is recursive at all Vuplus STB´s.

The last commit that it works, but i am not sure 100% ... is this one --> https://github.com/OpenViX/enigma2/c...7ea5388d8d2a44

So, the bug was introduced by this one --> https://github.com/OpenViX/enigma2/c...388d8d2a44from 21/Nov/2020

Thanks

Note: Probably not for all tuners ( brands and models )

MTSIF and Vuplus Turbo Tuner ... first Model has this issue.

[abu baniaz]

Can you post a screenshot of the scan settings you are using please?

>>This makes useless possible optimized terrestrial.xml files.
I presume you are saying you are using your own xml file, please attach it to the post.

[alexwilmac]

At the moment I have had the chance of testing only Solo4K but I've got reports concerning at least also Duo4K from some friends of mine.
As soon as possible I'll try Duo2 and Zero4K.

[alexwilmac]

Just added Duo2 to my tries: again, no problem under ViX 5.4.001 (and OBH 4.4.001) and identical errors and behaviour under 5.4.008 (and OBH 4.4.008).
I'm going to test Zero4K, hopefully within the day.
Also got the same report about a Duo.

[abu baniaz]

Just saying there is a problem is not helpful. Please post a screenshot of the scan settings you are using.

Are you using your own xml file?

[Huevos]

I've fixed it. Will commit soon.

[nunigaia]

I've fixed it. Will commit soon.

Thanks @Huevos

[alexwilmac]

NO, of course not.

[alexwilmac]

Many thanks, Huevos!
I had, meanwhile, the chance of testing also another VU+, the Zero4K, and with a different terrestrial tuner. But you came to the right conclusion even without this other try.

[Matrix10]

I've fixed it. Will commit soon.

I don’t understand one function though.
Can you say something more.

What is the function of this scan ? (shoot)
To resume normal and complete scanning again.

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

Thanks

Shoot is from open Pli but the same is in all other images

shot1P.jpg

[abu baniaz]

The latest commit by Huevos fixes issue for me on ViX. PLI did not have a problem.

Details of what the binary file from Vu+ does are a bit of a mystery. The initial commit to make it work is here ( link to comment last night): https://github.com/OpenPLi/enigma2/c...mment-48273772

Dimitrij will probably add an option for that vu+ scan so people decide whether to use it or not. I won't be using it.

[alexwilmac]

I knew this function (whom I name "prescan") in BH and I saw only there, among the images I've really been using. It has never been under many OE-A images (I'm surprised it's used by PLi, unless it is used only now because of this new .pyo; but I don't know PLI at all).
It was not possible, if I remember well, to avoid it but under BH (and I suppose VTi) but, at least, in those images it is a useful function because it does a quick search for used transponders and then it performs the scan only for the ones it found actually used.
I remember that, at the time, I appreciated it because it seemed that the added time for this initial search was more than compensated by a much quicker scan but now, not only I'm no longer using BH or other vuplus-based images, but I simply learnt how to optimize my terrestrial.xml file to scan only the active transponder in my city.

I want to underline again, in case it was not clear enough, the bug (as you can see) was not due to it but it affects also default terrestrial.xml scanning.
I mentioned this prescan only because it didn't happen before in OE-A images I use and because it was annoying and, above all, because I suspected it was connected to the following, much more serious bug, which ended in the error about the tuner configuration.
Obviously, the main problem was the error after the prescan, not the prescan in itself but, it was not a surprise that, after replacing the .pyo file as you suggested, both issues were gone.
Thank you again, Matrix!