I may try in tomorrow.
Multituner: First commits - but they need a lot of improvements
Re: Multituner: First commits - but they need a lot of improvements #181
Posted 16 March 2019 - 19:36
I may try in tomorrow.
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 #182
Posted 16 March 2019 - 20:10
Most probably it "caches" that info somewhere.
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916
Re: Multituner: First commits - but they need a lot of improvements #183
Posted 16 March 2019 - 20:16
1_0_1_A28_6A_212C_EEEE0000_0_0_0_20190316201616.jpg 124.4KB 1 downloads
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916
Re: Multituner: First commits - but they need a lot of improvements #184
Re: Multituner: First commits - but they need a lot of improvements #185
Posted 16 March 2019 - 21:15
Edited by zeros, 16 March 2019 - 21:16.
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 #186
Re: Multituner: First commits - but they need a lot of improvements #187
Re: Multituner: First commits - but they need a lot of improvements #188
Posted 16 March 2019 - 23:06
E.g. in ScanSetup,py you see here a list of possible multituners for the scan... it is not taken into account here what is enabled or not... isCompatible always gives DVB-S... but the ConfigModeDVBS/C/T/ATSC should be checked aswel or it should only take the mode for the not hotswitchable,
choices = [] modes = [] if n.isCompatible("DVB-S"): modes.append("DVB-S") choices.append(("DVB-S", _("Satellite"))) if n.isCompatible("DVB-T") or (n.isCompatible("DVB-S") and n.canBeCompatible("DVB-T")): modes.append("DVB-T") choices.append(("DVB-T", _("Terrestrial"))) if n.isCompatible("DVB-C") or (n.isCompatible("DVB-S") and n.canBeCompatible("DVB-C")): modes.append("DVB-C") choices.append(("DVB-C", _("Cable"))) if n.isCompatible("ATSC"): modes.append("ATSC") choices.append(("ATSC", _("ATSC"))) self.nim_type_dict[n.slot] = {"modes": modes, "selection": ConfigSelection(choices = choices)} if ttype in modes: self.nim_type_dict[n.slot]["selection"].value = ttype self.scan_nims = ConfigSelection(choices = nim_list)
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 #189
Posted 16 March 2019 - 23:11
Also satfinder we need to learn the new situation.....The message no nims avaialbe is coming from below.. This need some adaption. It reports DVB-S by default an hotswitchable... but when there is no satlist it reports no things available and also 'pokes' the configMode to nothing (why is it poking here in the config????)
suggestion...
- if n.isCompatible("DVB-S") and n.config_mode in ("advanced", "simple") and len(nimmanager.getSatListForNim(n.slot)) < 1:
+ if n.isCompatible("DVB-S") and n.config_mode in ("advanced", "simple") and (len(nimmanager.getSatListForNim(n.slot)) < 1 or nim.configModeDVBC.value or nim.configModeDVBT.value or nim.configModeATSC):
End remove these
config.Nims[n.slot].configMode.value = "nothing"
config.Nims[n.slot].configMode.save()
Or we need to consider to add "MULTI" as isCompatible (and getType)....
def SatfinderMain(session, close=None, **kwargs): nims = nimmanager.nim_slots nimList = [] for n in nims: if not any([n.isCompatible(x) for x in "DVB-S", "DVB-T", "DVB-C", "ATSC"]): continue if n.config_mode in ("loopthrough", "satposdepends", "nothing"): continue if n.isCompatible("DVB-S") and n.config_mode in ("advanced", "simple") and len(nimmanager.getSatListForNim(n.slot)) < 1: config.Nims[n.slot].configMode.value = "nothing" config.Nims[n.slot].configMode.save() continue nimList.append(n) if len(nimList) == 0: session.open(MessageBox, _("No satellite, terrestrial or cable tuner is configured. Please check your tuner setup."), MessageBox.TYPE_ERROR) else: session.openWithCallback(boundFunction(SatfinderCallback, close), Satfinder)
Edited by littlesat, 16 March 2019 - 23:23.
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 #190
Posted 17 March 2019 - 11:05
(Now I disable 'Configure DVB-T' back, but the 'DVB-T' channels are all still active)
is solved with today morning update. Just for info.
Edited by zeros, 17 March 2019 - 11:07.
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 #191
Re: Multituner: First commits - but they need a lot of improvements #192
Posted 17 March 2019 - 16:41
I have my Triple like dual tuner, it contains two Hotswitchable tuners: A and B.
When I configure let say Tuner A only ‘Configure DVB-T’, ‘and Configure DVB-S’ and ‘Configure-C’ are both switched off, then now when I descide to make
Serviche searching->Automatic scan
I have it like in added screenshots. It means it scans all my staff from only Tuner A. Despite that I have switched off DVB-S2, it scans it as well. I can rid out of that with Manual Scan. There all OK.
If you want, make so the ‘Automatic scan’ for ‘Hotswitchable’ tuners will do only for activated tuners. There Could be dual tunes as well? Just my observation.
Generally, here all very good.
I would like to hear how ims impressions on these innovation, how he feels?
Attached Files
Edited by zeros, 17 March 2019 - 16:46.
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 #193
Posted 17 March 2019 - 16:44
Edited by littlesat, 17 March 2019 - 16:45.
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 #194
Posted 17 March 2019 - 16:51
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 #195
Posted 19 March 2019 - 11:22
As long I do not experience the issue Huevos is describing it makes no sense for me to revert it... It would be helpfull to have some 'sequence' how to trigger what you experience here.
In addition for scanning there is also some progress locally here. I hope I can push some improvements next Saturday.
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 #196
Re: Multituner: First commits - but they need a lot of improvements #197
Posted 19 March 2019 - 11:27
A splitter that block the LNB voltage on one input could do it... Just connect it reversely.... So to the 'blocked' output you put DVB-T/C and to the non blocked output you put the sat LNB (stuff)... and the input is now the output to the receiver.
They have one disadvantage as they miss a low pass filter on the 'blocked' output.... Usually an LNB has the highpass filter included.
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 #198
Posted 19 March 2019 - 14:53
There is no "LNB voltage" on a C or T input.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (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: Multituner: First commits - but they need a lot of improvements #199
Re: Multituner: First commits - but they need a lot of improvements #200
Posted 19 March 2019 - 16:28
Yes the scan function is work in progress... The scan stuff still needs to 'learn' the new stuff...
Attached an untested/drafted diff... Help is always appreciated...
Attached Files
Edited by littlesat, 19 March 2019 - 16:30.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
30 user(s) are reading this topic
0 members, 30 guests, 0 anonymous users