318 replies to this topic

[WanWizard]

The osmega tuner can work in one mode at a time!

So if you are record on DVB-S and you try to switch to DVB-T, you should get channel unavailable (actually channels should be red, once you start using tuner).

 

Bad example, as it is only one tuner, it is locked on DVB-S, so no zap succeeds except to a channel on the same transponder.

 

What I mean is that only if you can configure both S and T channels on that tuner, and you can zap from an S channel to a T channel without changing the tuner config, it is hotswitchable.

 

 The tuner of osmega can work in S or T or C but not in S+T or S+C or T+C.

 

Which means it is not hotswitchable. And that is all I wanted to say.

[athoik]

Can we please define what is "hotswitchable" ?

 

How I can understand that a tuner is "hotswitchable" using DVB API?

[WanWizard]

Hence my remark that I don't really like the term.

 

A "hotswitchable tuner" is a tuner that, at the same time, can have an S, C and T config (when supported), can scan S, C and T without having to change a type in the config, and allows zapping over channels of all connected/configured DVB types without any changes to the config.

 

Before all this (and in a release image), on for example the OS Nino +, you could configure S and T at the same time (I don't have C to test. set mode to S, configure it, run a sat scan, change the mode to T, configure that and run a T scan), and than zap from an S channel to a T channel to and S channel. You would have an image on all channels, and in the skin you would see the delsys change from DVB-S2 to DVB-T to DVB-S2 when you zap.

 

The traditional combi tuners that you can buy for years, like the C/T's from VU+ for example, can only be DVB-C, or DVB-T, but not both at the same time, they are set fixed in the config to the desired type. And are therefore not "hotswitchable"

 

And don't confuse them for twin tuners (which is why your recording remark was wrong), these are single tuners with a chipset that can deal with S/C and T simultaneously, but only one at the time, so they switch between S/C/T based on the tuning commands/data they receive. 

[athoik]

I think that a tuner (tuner = frontend = /dev/dvb/adapter0/frontent0 [S2/S/T2/C]) can only handle one delivery system at a time.

A dual tuner (so /dev/dvb/adapter0/frontent0 [S2/S/T2/T/C] and /dev/dvb/adapter0/frontent1 [S2/S/T2/T/C]) can handle for sure more than one delivery system at a time. First request will go on first tuner and second request will go on second tuner.


I thought that @littlesat was creating a solution to configure the available types and/or enable some of them (Something that OpenATV supports since osmini+ appeared).


If there is an S/T/C tuner able to work in S+T or S+C or T+C or S+S then most probably we have /dev/dvb/adapter0/frontent0 + /dev/dvb/adapter0/frontent1.

If there is a tuner able to work in S+T or S+C or S+S with only /dev/dvb/adapter0/frontent0, tell me how, I am all ears.

[athoik]

It would require enigma to change the delsys on every zap (on that tuner) to make that work, as there is only a single tuner available.

This is what enigma2 does already!!!

S https://github.com/O...ntend.cpp#L2009
C https://github.com/O...ntend.cpp#L2086
T https://github.com/O...ntend.cpp#L2163
ASTC https://github.com/O...ntend.cpp#L2284

Every time we are "tuning" we are specifying the DTV_DELIVERY_SYSTEM.

If we are already tuned, we are just add more PIDS to the filter.

If we are going to tune to another frequency and/or another delivery system, we are going to send the DTV_DELIVERY_SYSTEM.

[littlesat]

We are taling about one tuner frontend input that can switch on the fly between dvb c, t, s or atsc.... as far I’m informed only avl tuners can do this... all others are staddy on one type.... this is not about dual tuners that can have different modes on specific inputs.there was a lot of noise here about dmm’s tripple tuners...which is not really relevant as they have a different (closed source) API.

[athoik]

OK, let's assume that only AVL tuners can switch between their available delsys. (That's wrong, but in order to keep moving, let's assume it).


Current implementation need an improvement.

I am disabling all modes on the tuner.

 1_0_1_BB8_12C_212C_EEEE0000_0_0_0_20190315185034.jpg   236.07KB   1 downloads

Returning back to tuner list, the tuner C is now "unconfigured".

 screenshot_20190315185046.jpg   243.13KB   1 downloads

We are trying to enable tuner once more.

 screenshot_20190315185109.jpg   247.77KB   1 downloads

Returning back to tuner list, the tuner C remains "unconfigured".

 screenshot_20190315185121.jpg   243.12KB   1 downloads



In order to "active" it you need to restart e2.

 1_0_1_BB8_12C_212C_EEEE0000_0_0_0_20190315185521.jpg   242.06KB   1 downloads

After restart, the tuner is activated.


I didn't find a way to fix it. I trace it down to line "self.nimConfig.configMode.default = self.nimConfig.configMode.value = "nothing" inside Satconfig.py.

But just disabling that line doesn't fix UI. It makes it much worse.

[littlesat]

Earlier we discussed about the elsif..after you commented it out. when we have an hotswitgcable tuner that code should not be executed... so the else should be changed in elsif not hotswitchable... (pseudo code) sorry I’m travelling...

Edited by littlesat, 15 March 2019 - 19:09.

[babsy98]

with openatv all hybrid tuner working as multitype we have add the feature 2016 https://www.opena.tv...natv-image.html

 

formuler too , vu driver working too but vu revert changes back to old mode looks old vu e2 make trouble and vu ignore all reports i have send from beginning 2017 to fix the delsys issue

[littlesat]

then the proc check should be fine and we’re almost there (with cleaned up code) and the story kernel 3.3 and vu is also right...

Edited by littlesat, 15 March 2019 - 20:26.

[Beeker]

https://github.com/O...611504d64b42f1c

 

When DVB-S is disabled it still showing all sat options (since .self.nimConfig.configMode.value will be not set to 'nothing').

Isn't it better to hide sat options when DVB-S is disabled.

 

Just add one tab to the 'menu option' code to  move to code to the same 'detention block' (or whatever it's called in Python) as 'self.list.append(self.configMode)'.

Attached Files

•  hide-sat-options-menu-when-disabled.patch   9.78KB   2 downloads

[littlesat]

Beeker,

 

Thanks... now I also remembered why we needed that set config to none .... And sorry that I missed this....

 

It is merged....

Edited by littlesat, 16 March 2019 - 10:46.

[zeros]

Tested and I confirm, that this thing works now. 

But I found now new thing, what I on previous didn't saw, because I alresdy restarted my box. The thing is like so:

I put all off and restart my box. Now I enamble 'Configure DVB-T' and it's done without restart. Nice!

Now I disable 'Configure DVB-T' back, but the 'DVB-T' channels are all still active. I can swap between all of them.

Now I do restart to my box, and they're gone, like it should be at once.

No problems for me, but on some cases it may make problems? Maybe similar thing on somewhere like it was in previous? You may check it out just in case?

Otherwise, everything works for me!

I'll make another postal about Information->About->Detected NIMs

One moment.

Edited by zeros, 16 March 2019 - 16:26.

[WTE]

We are taling about one tuner frontend input that can switch on the fly between dvb c, t, s or atsc.... as far I’m informed only avl tuners can do this... all others are staddy on one type.... this is not about dual tuners that can have different modes on specific inputs.there was a lot of noise here about dmm’s tripple tuners...which is not really relevant as they have a different (closed source) API.

The multi S2CT2 (atsc) tuner has a single output (1demod) but has more tuners DVB-C/T2/ATSC and DVB-S2.

The combo CT2 tuners are as well single output (1demod) but the tuner is actually one DVB-C/T2.

 

I think hotswitchable is more refering to hotswitchable tuner as both combo CT2 and multi S2CT2 can on the fly change from dvb mode T2 to C.

 

AVL tuners can switch between Tuner DVB-CT2 and DVB-S2 which makes it so hotswitchable.

It seems the manufactures which use Silabs 2169 didn't succeed to make it like it should been but add a hack to set the tuner mode in a static input.

The strange thing what I understand with info I read is when you have the dual version SI21692 you get if I understand it well options like DVB-S2+S2 or DVB-C+DVB-S2 The SI21692 should been shown as two seperate tuners SI2169 (but this is all for unsupport dreambox) so to this can all been ignore I assume.

[zeros]

And I will add screenshots with Skins:

PLi-FullNightHD

PLi-HD

I propose with PLi-FullNightHD let it be and with PLi-HD let the part between in the Closes remove.

Attached Files

•  PLi-FullNightHD.png   671.21KB   2 downloads
•  PLi-HD.png   483.34KB   2 downloads

[littlesat]

The cosmetic presentation on a skin does not have priority now. First get it working please... it seems there is another issue eg after reboots or so unicable is not (re) stored... but something I do not fully get there the configNothing and then change it...

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

[athoik]

Now I disable 'Configure DVB-T' back, but the 'DVB-T' channels are all still active. I can swap between all of them.

We should clean the whitelist also when tuner is disabled.

--- a/lib/python/Components/NimManager.py
+++ b/lib/python/Components/NimManager.py
@@ -1549,6 +1549,7 @@ def InitNimManager(nimmgr, update_slots = []):
                                createConfig(nim, slot)
                        else:
                                print "[InitNimManager] disable hotswitchable tuner"
+                               eDVBResourceManager.getInstance().setFrontendType(nimmgr.nim_slots[fe_id].frontend_id, "")
                                nim.configMode.value = nim.configMode.default = "nothing"

        def createConfig(nim, slot):

Can you try above change?

[littlesat]

Then it sounds like we might also have an unicable and longitude and nim.advanced.lnb[0] storage issue... everything where ConfigNothing is initialized the first time.... I suggest we shoud get 'rid' if that....

[littlesat]

@athoik about post #177 that is indeed required... please merge....

[athoik]

The change for disabling tuner was pushed.

Although trying to enable only T part on S/C/T tuner is not working now.

1. Enable only T

 screenshot_20190316185245.jpg   126.68KB   1 downloads

2. Return to tuner list (there are some Sat info mentioned there)

 screenshot_20190316185311.jpg   120KB   1 downloads

3. Restart the box

 screenshot_20190316185435.jpg   41.46KB   2 downloads

4. The tuner list shows tuner as not configured

 screenshot_20190316185536.jpg   106.44KB   2 downloads

5. But tuner T is enabled

 screenshot_20190316185612.jpg   114.33KB   2 downloads


I thought problems solved, but I cannot confirm, something still needs improvement.

PS. Deleted all config.Nims values from settings, some issue gone now, will post update.

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