Jump to content


Photo

Multituner: First commits - but they need a lot of improvements


  • Please log in to reply
318 replies to this topic

Re: Multituner: First commits - but they need a lot of improvements #241 Huevos

  • PLi® Contributor
  • 4,706 posts

+167
Excellent

Posted 23 March 2019 - 17:22

The purpose of that clause was just to test that if the tuner config was "advanced" thathat there was at least one orbital slot configured.



Re: Multituner: First commits - but they need a lot of improvements #242 littlesat

  • PLi® Core member
  • 57,255 posts

+702
Excellent

Posted 23 March 2019 - 17:30

Shoot... only at first reboot... on VU when you select a DVB-T/C tuner

ADD Peer h7=h7.local:8001
ADD Peer h7=h7.local:8001
REMOVE Peer h7
REMOVE Peer h7
Traceback (most recent call last):
  File "/usr/lib/enigma2/python/Components/ActionMap.py", line 49, in action
    res = self.actions[action]()
  File "/usr/lib/enigma2/python/Screens/Satconfig.py", line 768, in okbuttonClick
    self.session.openWithCallback(boundFunction(self.NimSetupCB, self["nimlist"].getIndex()), self.resultclass, nim.slot)
  File "/usr/lib/enigma2/python/mytest.py", line 289, in openWithCallback
    dlg = self.open(screen, *arguments, **kwargs)
  File "/usr/lib/enigma2/python/mytest.py", line 299, in open
    dlg = self.current_dialog = self.instantiateDialog(screen, *arguments, **kwargs)
  File "/usr/lib/enigma2/python/mytest.py", line 242, in instantiateDialog
    return self.doInstantiateDialog(screen, arguments, kwargs, self.desktop)
  File "/usr/lib/enigma2/python/mytest.py", line 259, in doInstantiateDialog
    dlg = screen(self, *arguments, **kwargs)
  File "/usr/lib/enigma2/python/Screens/Satconfig.py", line 607, in __init__
    self.createSetup()
  File "/usr/lib/enigma2/python/Screens/Satconfig.py", line 282, in createSetup
    terrestrialcountrycode = nimmanager.getTerrestrialCountrycode(self.slotid)
  File "/usr/lib/enigma2/python/Components/NimManager.py", line 740, in getTerrestrialCountrycode
    return self.terrestrialsList and self.terrestrialsList[config.Nims[nim].terrestrial.index][2] or None
  File "/usr/lib/enigma2/python/Components/config.py", line 1676, in __getattr__
    raise AttributeError(name)
AttributeError: terrestrial

Edited by littlesat, 23 March 2019 - 17:32.

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


Re: Multituner: First commits - but they need a lot of improvements #243 Huevos

  • PLi® Contributor
  • 4,706 posts

+167
Excellent

Posted 23 March 2019 - 17:42

You know on Vu only one tuner type is listed at once even though the tuner is hybrid. So multitype only contains the active type. Or something like that. Only accurate info for Vu hybrid comes from the /proc, not delsys.


Edited by Huevos, 23 March 2019 - 17:44.


Re: Multituner: First commits - but they need a lot of improvements #244 zeros

  • PLi® Contributor
  • 1,635 posts

+61
Good

Posted 23 March 2019 - 17:57

I'm touch the thorough test in tomorrow, you’ve done a great job!

DM920UHD DVB-S2X TRIPLE tuner + Triple M.S tuner DVB-S2X, DVB-T2/T, QboxHD, QboxHD Mini, Icecrypt T2300HD,
Qviart Lunix3 4K, Raspberry Pi 4 Model B 4GB & 8GB

Vertex 4K60 4:4:4 600MHz


Re: Multituner: First commits - but they need a lot of improvements #245 littlesat

  • PLi® Core member
  • 57,255 posts

+702
Excellent

Posted 23 March 2019 - 18:15


Shoot... only at first reboot... on VU when you select a DVB-T/C tuner

 

Also solved... Only happens with DVB-T tuner... it seems only C was pre-defined.... simple logic fix...

 

https://github.com/O...a2bceb55df634f5

 

This was 'deep diving'... especially as you could only trigger it at a first reboot....


Edited by littlesat, 23 March 2019 - 18:22.

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


Re: Multituner: First commits - but they need a lot of improvements #246 Huevos

  • PLi® Contributor
  • 4,706 posts

+167
Excellent

Posted 23 March 2019 - 18:45

Yes, confirmed here.

 

Testing again now.



Re: Multituner: First commits - but they need a lot of improvements #247 littlesat

  • PLi® Core member
  • 57,255 posts

+702
Excellent

Posted 23 March 2019 - 18:49

Thanks....
I hope this nightmare is finished...;)...

Edited by littlesat, 23 March 2019 - 18:51.

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


Re: Multituner: First commits - but they need a lot of improvements #248 Tech

  • Forum Moderator
    PLi® Core member
  • 14,932 posts

+487
Excellent

Posted 23 March 2019 - 20:35

I also heard the h9combo is okay too.


Aan de rand van de afgrond is een stap voorwaarts niet altijd vooruitgang....

On the edge of the abyss, a step forward is not always progress....

Hardware: 2x Daily used Vu+ Ultimo 4K - Vu+ Duo 4K SE and a lot more.... - VisioSat BiBigsat - Jultec Unicable Multiswitch 4 positions: 19.2/23.5/28.2 East - Diseqc motorized flatdish antenna

Software : HomeBuild OpenPLi Develop and Scarthgap builds, local cards driven by OsCam

Press the Geplaatste afbeelding button on the buttom right of this message ;)

Have you tried our wiki yet? Many answers can be found in our OpenPLi wiki


Re: Multituner: First commits - but they need a lot of improvements #249 littlesat

  • PLi® Core member
  • 57,255 posts

+702
Excellent

Posted 23 March 2019 - 20:55

Thanks!

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


Re: Multituner: First commits - but they need a lot of improvements #250 MCelliotG

  • Senior Member
  • 443 posts

+35
Good

Posted 23 March 2019 - 21:11

So, moving now to cosmetics, is that dreadful "hotswitchable" term here to stay?

Στάλθηκε από το Redmi Note 5 Pro μου χρησιμοποιώντας Tapatalk

Re: Multituner: First commits - but they need a lot of improvements #251 littlesat

  • PLi® Core member
  • 57,255 posts

+702
Excellent

Posted 23 March 2019 - 21:22

The name on the ui what the user sees is changed to combined... in the software code it is still hotswitchable (can be changed later)

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


Re: Multituner: First commits - but they need a lot of improvements #252 2Easy

  • Member
  • 7 posts

+1
Neutral

Posted 24 March 2019 - 17:16

Thanks, it helps  :)



Re: Multituner: First commits - but they need a lot of improvements #253 zeros

  • PLi® Contributor
  • 1,635 posts

+61
Good

Posted 24 March 2019 - 19:38

It's all good, but there's so lot of things changed, so I can’t tell about everything. Generally, I think it's okay. I add some screens from my dm, No GSOD. I have a fullscan, what didn't finish somehow, but Scan was done only for activated tuners (what is good).
Also came the tuners to reconfigure after online update (no problems for me, just for info).

Attached Files


DM920UHD DVB-S2X TRIPLE tuner + Triple M.S tuner DVB-S2X, DVB-T2/T, QboxHD, QboxHD Mini, Icecrypt T2300HD,
Qviart Lunix3 4K, Raspberry Pi 4 Model B 4GB & 8GB

Vertex 4K60 4:4:4 600MHz


Re: Multituner: First commits - but they need a lot of improvements #254 littlesat

  • PLi® Core member
  • 57,255 posts

+702
Excellent

Posted 25 March 2019 - 02:51

There is some work in progress regarding the old config to new config ‘transfer’ when you update/flash... that does not work properly yet...

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


Re: Multituner: First commits - but they need a lot of improvements #255 Huevos

  • PLi® Contributor
  • 4,706 posts

+167
Excellent

Posted 25 March 2019 - 03:30

Tested on Vu Ultimo 4K, Zgemma H7S and OS Mega.

 

For some reason the configured satellites don't show in the NimSelction screen on the Mega. Looks like it might need more space in the skin.



Re: Multituner: First commits - but they need a lot of improvements #256 zeros

  • PLi® Contributor
  • 1,635 posts

+61
Good

Posted 25 March 2019 - 07:07

About my discovery ‘I have a fullscan, what didn't finish somehow’:
It was my fault, actually. You can try what happens when you make fullscan and if the permitted tuners there's are one of which is unlinked/not connected. So this Scan will not be finished. Try and you see. When I changed everything correctly, it did it nicely.
One thought to get over:
If You can scan such Combined Tuner and from few permitted systems (DVB-T or DVB-C or DVB-S2) will be found after scan zero services, that would give you a message after all of the Scan and then will stop the scan. I hope you understood what I mean. For example: ‘on Tuner B found 0 services’. Good, if user finds out he has something wrong or unconnected and also the search won't stop for that.
But well done imho!

DM920UHD DVB-S2X TRIPLE tuner + Triple M.S tuner DVB-S2X, DVB-T2/T, QboxHD, QboxHD Mini, Icecrypt T2300HD,
Qviart Lunix3 4K, Raspberry Pi 4 Model B 4GB & 8GB

Vertex 4K60 4:4:4 600MHz


Re: Multituner: First commits - but they need a lot of improvements #257 littlesat

  • PLi® Core member
  • 57,255 posts

+702
Excellent

Posted 25 March 2019 - 09:26

Sorry I don't understand... But is it releated to the combined tuner feature...?

 

When scanning when nothing is connected may take a long long long long long long loooooooooong time... Then the only option is 'stop' it manually to speed it up... .ofcourse you need to connect to find service ;) (only it can be considered to add an timeout for lock... but that should be already in... but than still it is slow due to the timeout).

 

In between I also solved the setting issue when you upgrade. E.g. when the tuner was multi for DVB-C, then after an upgrade and the tuner can do combined (hotswithable), then DVB-C is enabled by default -and- the old config will be purged.


Edited by littlesat, 25 March 2019 - 09:28.

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


Re: Multituner: First commits - but they need a lot of improvements #258 zeros

  • PLi® Contributor
  • 1,635 posts

+61
Good

Posted 25 March 2019 - 10:10

Yes, you got it right! I had during test that one tuner was cable was not connected, but that Tuner was enabled. As you know, I have several tuners. All scan takes a long time as we know. For me it I was sooooo long and I stopped it. First I thought something was wrong in the code but there was a one tuner that actually wasn't behind the cable. That's how it was, and it could happen to others too? But when I did, like I have my Tuners connected, I'm okay!

DM920UHD DVB-S2X TRIPLE tuner + Triple M.S tuner DVB-S2X, DVB-T2/T, QboxHD, QboxHD Mini, Icecrypt T2300HD,
Qviart Lunix3 4K, Raspberry Pi 4 Model B 4GB & 8GB

Vertex 4K60 4:4:4 600MHz


Re: Multituner: First commits - but they need a lot of improvements #259 littlesat

  • PLi® Core member
  • 57,255 posts

+702
Excellent

Posted 25 March 2019 - 10:17

Thanks for the confirmation.... few ;)

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


Re: Multituner: First commits - but they need a lot of improvements #260 littlesat

  • PLi® Core member
  • 57,255 posts

+702
Excellent

Posted 25 March 2019 - 11:16

Btw the conversion does not work for that osnino + thing there only S can be ‘restored’... as side effect of the previous ‘hack’

Edited by littlesat, 25 March 2019 - 11:17.

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



14 user(s) are reading this topic

0 members, 14 guests, 0 anonymous users