I see the changes stick now after restarting E2 or rebooting. I love the Combined description as well.
Multituner: First commits - but they need a lot of improvements
Re: Multituner: First commits - but they need a lot of improvements #261
Re: Multituner: First commits - but they need a lot of improvements #262
Re: Multituner: First commits - but they need a lot of improvements #264
Re: Multituner: First commits - but they need a lot of improvements #265
Posted 25 March 2019 - 20:51
Default mode single is indeed an option but in the Netherlands a dual lnb (19.2 + 23.5) is most standard... So should we do this change to single... the we also can consider quad. AutoDiseqc finds the most used satellites and when we have one, two, three or four sats they are always found...
Equal to has added value... and is different from connected to.
Edited by littlesat, 25 March 2019 - 20:58.
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 #266
Re: Multituner: First commits - but they need a lot of improvements #267
Re: Multituner: First commits - but they need a lot of improvements #268
Re: Multituner: First commits - but they need a lot of improvements #269
Re: Multituner: First commits - but they need a lot of improvements #270
Posted 25 March 2019 - 23:55
Then you mean when you select equal to you should not have scr available? Or still allow somehow to select the scr ‘channel/frequency separately? Maybe we should no get that far?
At this moment I have no idea how to ‘hide’ the equal to in this situation...
Fbc musn’t Have Jess/unicable... they may have
Edited by littlesat, 25 March 2019 - 23:57.
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 #271
Re: Multituner: First commits - but they need a lot of improvements #272
Posted 26 March 2019 - 07:49
What can be done is only add the option equal to only when there are tuners available without Jess/unicable. Might be not that difficult.
Edited by littlesat, 26 March 2019 - 07:53.
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 #273
Posted 28 March 2019 - 22:32
Traceback (most recent call last): File "/usr/lib/enigma2/python/Components/ActionMap.py", line 49, in action File "/usr/lib/enigma2/python/Screens/Satconfig.py", line 764, in okbuttonClick AttributeError: 'NoneType' object has no attribute 'slot'
Attached Files
Re: Multituner: First commits - but they need a lot of improvements #274
Posted 28 March 2019 - 23:59
But how did you het there in the first place without having tuners insertted?
I suggest this is in the NIM selection screen where you do not see any tuners and then click ok... suggest sanity check should solve the gsod. Or even more better do not show the tuner list af all when there are no tuners... so add something in menu.xml or so with conditional or so that arrange the option is not shown... when there are no tuners there is no need to select one and config one...
Edited by littlesat, 29 March 2019 - 00:09.
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 #275
Re: Multituner: First commits - but they need a lot of improvements #276
Posted 29 March 2019 - 05:37
When sundtek reports as tuner that should not be an issue
Edited by littlesat, 29 March 2019 - 05:38.
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 #277
Posted 29 March 2019 - 05:39
I made a small video as well from current state.
dm920 Enigma version 2019-03-29 (develop)
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 #278
Re: Multituner: First commits - but they need a lot of improvements #279
Posted 29 March 2019 - 08:44
Someone's tuner went faulty and going in tuner configuration resulted in a crash. I checked and could reproduce it. -> sorry I do not understand
When sundtek reports as tuner that should not be an issue
@Littlesat, what he is saying is if you are in the NimSelection screen and there are no Nims to select, and you press OK to select a Nim, that will result in a BSoD. So there needs to be a sanity test to prevent that. No idea if that is related to the "HotSwitch" code. I doubt it.
Re: Multituner: First commits - but they need a lot of improvements #280
Posted 29 March 2019 - 10:45
https://github.com/t...ped_q=hasTuners
i simply removed the whole menu entries using SystemInfo["hasTuners"]
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users