77 replies to this topic

[littlesat]

Whenit is avc the box cannot regulate volume over hdmi or digital output... No box can do that...

Edited by littlesat, 16 October 2016 - 19:48.

[isteric2005]

it is as if the skin tag a value which does not correspond to reality

Edited by isteric2005, 16 October 2016 - 19:53.

[Huevos]

Currenly with our image you can only scan the tuner type you select... There is some work in progress here... The other images make as far we can see a dirty patch... (Lets now wait for the comments)...

I don't know what dirty patch you are talking about, but it must be nasty if it wasn't written by a PLi member.

 

I said in the other thread months ago, ABM (which is on PLi feeds) can scan UK and NL terrestrial and cable and sort into LCN order, as well as the same for about 40 other providers. And OE-A TerrestrialScan plugin can scan terrestrial in the conventional fashion. TerrestrialScan would probably work in PLi with very minor adjustment or none at all. Both options work fine for OSMiniPlus. So with TerrestrialScan and CableScan plugins you already have working options.

[littlesat]

I don't know what dirty patch you are talking about, but it must be nasty if it wasn't written by a PLi member. 

Grmmmmbl..... 

 

In the UI it is required when you have such "multi tuner" that you see always the DVB-S option en at the bottom of the DVB-S option you should be able to select between DVB-T or DVB-C or eventually "off -or- "do not use").... when select DVB-T or DVB-C you see the extra options. This is different from the "pages" approach which I saw at OE-A. Then in Scan you should see all "available" options... It is just work that needs to be done -but- without having the hardware connected it might take a longer time "until" we see more boxes having these combi options...

 

And indeed we could need help here .... And possibly again we need to create it by scratch... It is what it is... 

Edited by littlesat, 17 October 2016 - 14:59.

[sergiodi]

I would return to the subject "tuner management" os mini plus to ask if the problem lies in OpenPLi or is in the hardware.
In the first case I am certain that the team will fix; otherwise I will have to replace the box

[littlesat]

The problem is that it is working right now... Only in the UI part "something" needs to be adapted and to do it properly it is relatively a lot of work as the UI was not designed for these kind of multi type of tuners with two modes together.... And this is really "hammering"

 

E.g. the tuner type can set only one type at once... and when you enable more the "nothing connected / enabled / advanced,...)...

 

So to really do it properly it means a lot of modifications and also testing (if it does not break the normal stuff aswell) when you really want to do this properly...

 

And currently I'm more working with Solo4K and HD51.... this limits my already limited available time...

 

So hopefully I can "guide" someone else to do this "job" in a proper accepted way...

 

Note all cpp stuff is ready (and therefore the tuner can tune when you put it afterwards in DVB-S mode).... so it needs a lot of python (re)coding... As far I know practically only in NimManager.py and SatConfig.py... (and I also perfer to wait for the JESS/unicalbe-II integration as this need also big changes in these two fails...)

Edited by littlesat, 19 October 2016 - 15:46.

[isteric2005]

It notes that even in today's version of the volume indicator in the skin is not correct.
E 'to zero for all the green section

Edited by isteric2005, 20 October 2016 - 21:30.

[Huevos]

The problem is that it is working right now... Only in the UI part "something" needs to be adapted and to do it properly it is relatively a lot of work as the UI was not designed for these kind of multi type of tuners with two modes together.... And this is really "hammering"

 

[...]

 

Note all cpp stuff is ready (and therefore the tuner can tune when you put it afterwards in DVB-S mode).... so it needs a lot of python (re)coding... As far I know practically only in NimManager.py and SatConfig.py... (and I also perfer to wait for the JESS/unicalbe-II integration as this need also big changes in these two fOails...)

 

Or just a dirty hack, without any guidance. Oh and no changes in NimManager or SatConfig. I can leave that to the professionals

 

 s.jpg   129.35KB   3 downloads

 

 t.jpg   131.7KB   3 downloads

 

 c.jpg   128.14KB   3 downloads

Edited by Huevos, 21 October 2016 - 09:51.

[littlesat]

That is on the (manual) scan page.... it might be very welcome when you offer us that solution....This should also be done... (and possibly later extended). For the time being your suggestion will help the users of these kind of tuners...

 

Just in a nutshell that needs to be done....

 

In NimManager and Satconfig you need a big patch with risk of breaking other things... The way how this was build not designed for multi tuner functionality....

 

We should start with showing all possible options in the sat config and we need to "split"  the connection type (nothing connected, simple, advanced field)... between DVB-C/T/S/ATSC.... And we need to remove a lot of "else if" and replace them by simply an "else....". And the DVB-C/T switchable option might be removed.... Just show all DVB-C and T options with as first option to turn them on or off.... 

 

Or consider to keep switching between DVB-T/C and always show DVB-S with a multituner..... but stull split the connected value for S and a combined T/C.... (this makes the list shorter and I suggest you never use T and C together).

 

Then afterwards the (manual) scan page could check for enabled options on a tuner and only switch beteen the enabled features.

 

In a short term I suggest 4 to 8 hours of work just to do it really right....

 

And as currently the Jess(-ui) is pending and also impacted NimManager and SatConfig a lot I prefer to wait before implement this in the proper way....

 

And the biggest pain is that we need to do this currently for "low" profile receivers.....  But probably high end tuners might also end up with multy-tuners....

 

The most imported thing is that we need something that helpes ahead users with this kind of tuners... To do it properly that can be done later.... (or hopefully not never)... But when we consider to make work-a-rounds for now it must be clean work-a-rounds...

 

I suspect the (manual) can options derived from your screenshots is a clean work-a-round....

Edited by littlesat, 21 October 2016 - 10:09.

[athoik]

But probably high end tuners might also end up with multy-tuners....

Already here!

Edision osmega has two normal S2 Broadcom tuners and one multitype S2/T2/C.

So the change from @Huevos is very welcome!

[littlesat]

The overall correct change is also very welcome then...

 

But I'm thinking about specification now before make something...

 

I'm thinking about we need finally two tuner types...

 

DVB-S/DVB-T and DVB-S/DVB-C.... I suggest DVB-T and DVB-C can't used together (mixed).... as they interfere...

 

In SatSetup I give the option on top... you always see DVB-S options and selecting the "type" on top the DVB-T or DVB-C options will be added....

 

then slot.config.configMode.value I need to keep slot.config.configMode.value for DVB-S, and for DVB-C/T I change it to

slot.config.configMode_DVB-C.value, slot.config.configMode_DVB-T.value (so you can separately disable or enable it).

 

Then in the elsif stuff we need arrange that when we have DVB-S/DVB-T that the configs are declared/forwarded/shown for DVB-S and T and for DVB-C the same...

 

But first we need to agree to only choose between DVB-S/DVB-T or DVB-S/DVB-C (and not give 8 options or so as this will also interfere with the configMode).

[Huevos]

Ok. Here is the patch to work with the current NimManager/SatConfig combination. Code is pretty simple.

 

By default it opens on the currently playing transponder... and it doesn't show the "DVB type" option unless the tuner is multitype.

 

Tuner must be set up as satellite, as is currently the case.

 

https://github.com/H...705c1b1a06fc56b

Edited by Huevos, 21 October 2016 - 12:03.

[Huevos]

A bit more info.

 

When you first set the box up:

Go into tuner config.

Select DVB-T2.

Pick your terrestrial region.

Press GREEN to save.

 

Now reopen the config for the same tuner.

Select DVB-S2

Set up your satellite config.

Press GREEN to save.

 

Now, even though the tuner is configured for satellite when you do a scan of terrestrial it knows which terrestrial region (from terrestrial.xml) to scan.

 

The same should apply if you were setting up a cable provider.

Edited by Huevos, 21 October 2016 - 12:48.

[athoik]

Idea: The NimManager to return multiple times a tuner with every type available.

Tuner A (DVB-S) -> Tuner A (DVB-T) -> Tuner A (DVB-C)?

Is that possible?

[littlesat]

You can arrange a list or tupple and check for "dvb-c" in tunermodepossiblr

[Huevos]

Why not just cycle through the modes. i.e. ('DVB-S', 'DVB-T', 'DVB-C', 'ATSC', 'DVB-S/T', 'DVB-S/C')?

 

If it is a multi mode tuner show Extra options on the same page. T/C options only take up a few lines.

Edited by Huevos, 21 October 2016 - 20:10.

[Huevos]

Forget the UI for a minute. The main problem is isCapatible () and caBeCompatible (). Theseare used everywhere throughout the image.

We need to forget the compatiblity of the tuner at run time and instead use whatever value was set up in the original configuration.

If you look at the patch you can see I have removed isCompatible in various conditionals and replaced it with what the search actually relates to. Working out whether the tuner was compatible was done right at the start in createConfig.

A similar approach is required in NimManager and elsewhere throughout the image. I.e. workout what a tuner can do at setup time. Follow saved values at run time.

[littlesat]

In fact we need isEnabledfor(....) for what it is configured for...

 

and isCompatible(...) for what it can do

 

Naming is important...

Edited by littlesat, 22 October 2016 - 11:33.

[Erik Slagter]

The question is, why did they choose this approach to begin with? What will stop working when we change it?

[littlesat]

Look in the code and you see duplications... wierd thinks and work-a-rounds... adds without a real design.... really terrible....

 

For jess-ui I concentrated just on unicable and jess... and with added functionality I reduced 100+ lines of code... and tripple storage of the unicable.xml....

There is much more to gain there that helps supporting multy tuners...