58 replies to this topic

[littlesat]

Until now I could not verify it here lnbs stay in the config... also when I programmed Jess/unicable as dummy it stays.... don’t care if I break enigma2 bards or soft via the console, restart enigma2 or restart the complete box.... and as far I know no openpli user experienced it either. I will not say the isn’t an issue, but as long I cannot verify it or have a detailed sequence to force it I cannot find the cullpit and reverting does also not help.

What config.py does vix use? Open atv’s. I hope you do not have in there what they have in line 1857 of config.py https://github.com/o...de1ad2d2f25a3bf

Edited by littlesat, 17 March 2019 - 14:59.

[Huevos]

OpenViX do not merge from OpenATV. Most of the external code comes from PLi.

 

And most of our original code gets pushed back to PLi. So lots of code in PLi (e.g. predefined transponders in ScanSetup, lots of changes in satfinder, etc, hints in satconfig, the list is endless) comes from OpenViX mainly written by me.

 

config.py is here...

https://github.com/O...nents/config.py

 

There is a possibility configfile.save() could be exposing this problem.

[littlesat]

Yep indeed... but as long I cannot trigger it and it seems you could do it at reboot/restarts and I never experienced it is is difficult to solve ...we do that save in SatConfig.py

Edited by littlesat, 17 March 2019 - 16:42.

[Huevos]

What receivers have these tuners?

[WanWizard]

The Edision OS Nino+, for example.

[littlesat]

I just fixed an issue regarding a dvb-t/c (without s) hotswitchable tuners... but that is not related to this thing I cannot verify. I also verified vix code but I cannot are yet the cullpit... or why vix might behave differently... I did not check if other code might overwrite some nim configs.

Also h7 or formuler 1 c/t tuners can do something like this...

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

[Dimitrij]

IMHO...

formuler 1/sundtek dvb-t2/dvb-c tuner at the same time it works only in one mode.

I do not have cable TV to check.

[athoik]

Tuner = frontendX = 1 delsys at a time

The term hotswitch is the ability to switch on another input on the fly using DVB API.

Nobody ever said that hotswitch is the ability to work in more than one mode at a time.

[Dimitrij]

I do not understand.

Example:

Formuler 1 dvb-t2/dvb-c tuner.

Play dvb-t service and zap to dvb-c service is it possible?

[WTE]

I do not understand.

Example:

Formuler 1 dvb-t2/dvb-c tuner.

Play dvb-t service and zap to dvb-c service is it possible?

 

Yes this is possible with the original dvb-ct2 tuner (so switch on the fly). I do not know if devices like sundtek can handle it. Your always related to the driver of the device.

Edited by WTE, 19 March 2019 - 10:45.

[Dimitrij]

OK.
Then these new features are correct.

[Huevos]

I just fixed an issue regarding a dvb-t/c (without s) hotswitchable tuners... but that is not related to this thing I cannot verify. I also verified vix code but I cannot are yet the cullpit... or why vix might behave differently... I did not check if other code might overwrite some nim configs.

Also h7 or formuler 1 c/t tuners can do something like this...

In OpenViX, if we use the current NimManager.py from OpenPLi the problem still exists. If we use OpenPLi NimManager.py from before the rogue commit all problems are solved. So whatever is provoking this problem is also in OpenPLi NimManager.py code.

Edited by Huevos, 19 March 2019 - 11:46.

[Huevos]

The Edision OS Nino+, for example.

I know the Nino+ and the Mega, but are any new receivers using this code? Or has this tuner type been abandoned by manufacturers?

[littlesat]

For us the problem does not exist in OpenPLi as simply we de not experience it. Nobody of our testers did confirm what you describe so it is kind of getting spooky.

Please give us the recipe how to provoke it!!!

 

And maybe there is 'something' else outside NimManager or SatSetup that 'triggers' it.

 

And b.t.w. it also works here with e.g. Zgemma H7...C/T tuner... As long there is no proc (VU+)...

Before that commit you can get very easily a GSOD when restoring settings with blue button.

 

So whatever is provoking this problem is also in OpenPLi NimManager.py code.

Edited by littlesat, 19 March 2019 - 13:25.

[WanWizard]

I know the Nino+ and the Mega, but are any new receivers using this code? Or has this tuner type been abandoned by manufacturers?

 

With the old code ( = from before these "hotswitchable" changes), you could configure DVB-S2, DVB-T2 and DVB-C at the same time, by switching the type, do the appropriate configuration, and than scan the type.

 

When done, you would have a tuner with S2, T2 and C config, and channels from all three in your all list, due to the scan. You can then zap from an S to a T to a C channel, and the tuner would switch accordingly,

 

So, functionally, with the old code everything worked fine for this type of tuner. The changes should only have been cosmetic ones, I have lost the plot with these changes a long time ago...

[littlesat]

I'm working on this one... The scan "stuff" does not cover this yet... In addition it gives always all the types a tuner can do in the scan setup.. also those that you did not 'connect/enable'.

 

Also the old code was wrong.. e.g. when you had sat only on the box and no DVB-C... you could not do a 'fallback' tuner on DVB-C as always everything was enabled. On tuner enabled all types enabled... In addition you always need to 'end' configuring DVB-S as otherwise the whole tuner was disabled.

 

For a diff regarding the scanning stuff (fully untested drafted code) see attachment. I hope I can finalize this on/before Saturday.

 

mmm when I put the quote on top... I do not see added text...

 

 

 

When done, you would have a tuner with S2, T2 and C config, and channels from all three in your all list, due to the scan. You can then zap from an S to a T to a C channel, and the tuner would switch accordingly,

 

Attached Files

•  diff.zip   1.63KB   6 downloads

Edited by littlesat, 19 March 2019 - 16:03.

[Dimitrij]

index a1792ac94..0ec577994 100644
--- a/lib/python/Components/NimManager.py
+++ b/lib/python/Components/NimManager.py
@@ -521,11 +521,18 @@ class NIM(object):
 				for type in types:
 					self.multi_type[str(types.index(type))] = type
 
+	def getHotswitchableTunersEnabled(self)
+			return [x for x in slot.multi_type.values() if
+				nim.configModeDVBS.value and x.startswith("DVB-S") or
+				nim.configModeDVBC.value and x.startswith("DVB-C") or
+				nim.configModeDVBT.value and x.startswith("DVB-T") or
+				nim.configModeATSC.value and x.startswith("ATSC")] if self.hotswitchable else []

def getHotswitchableTunersEnabled(self):

Edited by Dimitrij, 19 March 2019 - 18:24.

[littlesat]

Missing : ?

[zeros]

For that #29 you need dual Tuner (one Tuner that can do two at once).

For example I have such Tuner and it I can do

 

DVB-T

DVB-T

 

or

 

DVB-T

DVB-C

 

or

 

DVB-C

DVB-C

 

As I have 2x dual Tuners, then I can do it two times more. But I personally don't have DVB-C, so that I can't test.

 

Tested and it works now for me (thanks to that innovation):

DVB-T MUX1 recording

DVB-T MUX2 recording

DVB-T MUX3 recording

DVB-T MUX4 recording

And yes, in this way I can record pretty lot of channels at the same time (if needed). We actually have here 6 different MUX for DVB-T, so 2 remains..

If you have any of such tuners more, I haven't studied. Frankly, it came to me as a surprise, as I never thought like that. My first concern was that my dual tuner's second SAT wasn't working from the days of beginning. With that innovation this also all right. Just to clarify the question #29.

[Dimitrij]

Missing : ?

yes