Jump to content


Photo

SignalFinder


  • Please log in to reply
10 replies to this topic

#1 EnoSat

  • Senior Member
  • 183 posts

+4
Neutral

Posted 9 July 2022 - 18:57

I saw some interesting additions in SignalFinder.
Would it be possible to add them to the SDG?
 
 
Read TID,NID,POS
Attached File  screenshot_20220709194420.jpg   80.73KB   7 downloads
 
Show SDT
Attached File  screenshot_20220709194438.jpg   56.44KB   7 downloads


Re: SignalFinder #2 Huevos

  • PLi® Contributor
  • 4,247 posts

+158
Excellent

Posted 15 July 2022 - 10:41

That's my mod. OpenPLi were never interested in the implementation.

Re: SignalFinder #3 WanWizard

  • PLi® Core member
  • 68,598 posts

+1,739
Excellent

Posted 15 July 2022 - 14:08

Never seen it before myself, can't imagine what the objections would have been?


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: SignalFinder #4 Huevos

  • PLi® Contributor
  • 4,247 posts

+158
Excellent

Posted 15 July 2022 - 19:16

1) Littlesat didn't like that it is not built in to the C++ code.

2) Littlesat didn't like that it polls.

3) Littlesat didn't like that it uses AutoBouquetsMaker's dvbreader.so file.

4) Maybe other things, I can't remember.

 

The class just drops in without touching the base SatFinder class.

 

https://github.com/O...in.py#L594-L926

 

And if the reader is not available it just drops back to the base class.

		if dvbreader_available:
			session.openWithCallback(boundFunction(SatfinderCallback, close), SatfinderExtra)
		else:
			session.openWithCallback(boundFunction(SatfinderCallback, close), Satfinder)

Oh, and obviously needs the widgets in the skin.

 

The original version used something similar to AutoDiseqc.py, but was just too slow and clunky with continual spinners every time it changed frequency and inaccurate results.

 

Was just a personal project to fill my needs.



Re: SignalFinder #5 WanWizard

  • PLi® Core member
  • 68,598 posts

+1,739
Excellent

Posted 15 July 2022 - 20:33

I think 1 is related to 3, and I guess he had a point there, you don't want Enigma to have a dependency on ABM, 99% of OpenPLi users don't use that.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: SignalFinder #6 littlesat

  • PLi® Core member
  • 56,272 posts

+691
Excellent

Posted 15 July 2022 - 20:53

Indeed the feature is Nice… but the implementation is not that optimal. It was long time ago I did evaluate it. All code that can check a transponder is already available in enigma2… when eg you scan.

There are more implementation I did comented as I world prefer to have it implemented in a better structured method.

Autobouquets maker lakes from to sides. The way it scanners and the way it fills the bouquets…. But the devs made it with what they could do with their knowledge and I do not have the time to show how it can be Made better to demonstratie it.

It should be startend to find a way to use the Scanning code we have in enigma2 and/or add/adapt the ‘api’ instead of using an additional binary… so I prefer To have the functionality that we have in the so file moven to the standaard enigma2 binary code.


Edited by littlesat, 15 July 2022 - 21:01.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: SignalFinder #7 Huevos

  • PLi® Contributor
  • 4,247 posts

+158
Excellent

Posted 16 July 2022 - 14:08

@Littlesat, The ONID/TSID code is available in AutoDiseqc.py but it just does not work properly for repeated retunes.

 

I'm not aware of any code in the binary that reads the orbital position from the transport stream.

 

All this mod does is use the *.so file, nothing to do with ABM bouquets. Just reads from the transport stream.

 

Converting that code to the enigma2 binary? What is the point? OpenPLi uses other *.so files for things not built in to the binary, e.g. bitrate. I think that needing everything built in to the binary is a philosophy that is not based on good logic. In the case of Fastscan and CableScan it is obvious that it is clearly wrong.

 

Anyway, the reader is built in to OpenViX. For OpenPLi, not so simple.


Edited by Huevos, 16 July 2022 - 14:11.


Re: SignalFinder #8 littlesat

  • PLi® Core member
  • 56,272 posts

+691
Excellent

Posted 16 July 2022 - 15:39

Bitrate is a plugin… but unless this I also think this can be integrated. And you point indeed to the autodiseqc part… why not adapt it?
The code was made in a way the developers of it could do at that moment, but it was never implemented in a structured/proper or better say optimal way. I tried to get it to a better direction but never succeed with it…

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: SignalFinder #9 WanWizard

  • PLi® Core member
  • 68,598 posts

+1,739
Excellent

Posted 16 July 2022 - 15:49

The problem is not the binary in itself, the problem is that enigma will need a depdency on ABM to get access to that binary, which means ABM will have to be present in every OpenPLi image. Which we don't want.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: SignalFinder #10 Huevos

  • PLi® Contributor
  • 4,247 posts

+158
Excellent

Posted 16 July 2022 - 18:01

That file is so useful I made it a standalone package a few years ago.

https://github.com/Huevos/dvbreader/



Re: SignalFinder #11 littlesat

  • PLi® Core member
  • 56,272 posts

+691
Excellent

Posted 17 July 2022 - 08:24

Just to give you the real pain I have with this.

 

At the moment abm was created I was not in it because I prefered to get fastscan extended and preferably also cablescan integrated so there is one kind of scan tool.

 

aActually Cablescan and fastscan demonstrates how you should do it, including filling the userbouquets and lamedb without manipulating the files and reload them with extra parsers etc.

but the code needs to made for a big part in cpp… and the developers of abm did made it in python because as far I understood could not create it easily in cpp… except for the small cpp code that was still mandatory…

 

As long nobody has time or energy to make it properly it will never be implemented better. So we have to live with it as it is.

 

there is no need to defend the so method is good or wrong. It is more about time and energy someone needs and can spend into it to do it really right.

 

for me it has low priority on ‘my personal scrum board’… at this moment I do not have the time and energy to do it due to circumstances.


Edited by littlesat, 17 July 2022 - 08:33.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W



0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users