Tuner config 'Priority' setting
Re: Tuner config 'Priority' setting #2
Posted 23 April 2014 - 17:11
It has something to do with DiSeqC. All I know is that if I change it to something else, it stops working.
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.
Re: Tuner config 'Priority' setting #3
Re: Tuner config 'Priority' setting #4
Re: Tuner config 'Priority' setting #5
Posted 23 April 2014 - 18:59
It works great.
I would call this the advanced settings option for priority tuners.Please could you explain exactly. When in auto I can predict tuner selection 100% of the time. Anything else and I haven't got a clue.
Sorry, I do not know the principle of operation of this option.
But in my receiver it works.
GigaBlue UHD Quad 4K /Lunix3-4K/Solo 4K
Re: Tuner config 'Priority' setting #6
Re: Tuner config 'Priority' setting #7
Re: Tuner config 'Priority' setting #8
Re: Tuner config 'Priority' setting #9
Posted 24 April 2014 - 08:23
take a look here:
http://sourceforge.n...860c9ee2765d6e/
add possibility to set manual lnb priority (only in advanced sat config)
range 0..64 to decrease priorities (this is lower as all auto given priorities)
range 14000..14064 this is higher than auto given rotor priorities
range 19000..19064 this is higher than each auto given priorities
but I have no idea if this decreasing/increasing priority applies only in regard to 'auto' option in lnb priority, or also to 'auto' option set up in preferred tuner/ preferred tuner for recordings...
Re: Tuner config 'Priority' setting #10
Re: Tuner config 'Priority' setting #11
Re: Tuner config 'Priority' setting #12
Posted 24 April 2014 - 10:55
We need to do so, it will be useful for everyone!!!
--- a/NimManager.py +++ b/NimManager.py @@ -1182,8 +1182,17 @@ ("5", "SatCR 5"), ("6", "SatCR 6"), ("7", "SatCR 7"), ("8", "SatCR 8")] prio_list = [ ("-1", _("Auto")) ] - prio_list += [(str(prio), str(prio)) for prio in range(65)+range(14000,14065)+range(19000,19065)] + for prio in range(65)+range(14000,14065)+range(19000,19065): + description = "" + if prio == 0: + description = _(" (disabled)") + elif 0 < prio < 65: + description = _(" (lower as all auto given priorities)") + elif 13999 < prio < 14066: + description = _(" (higher than auto given rotor priorities)") + elif 18999 < prio < 19066: + description = _(" (higher than each auto given priorities)") + prio_list.append((str(prio), str(prio) + description)) advanced_lnb_csw_choices = [("none", _("None")), ("AA", _("AA")), ("AB", _("AB")), ("BA", _("BA")), ("BB", _("BB"))] advanced_lnb_csw_choices += [(str(0xF0|y), "Input " + str(y+1)) for y in range(0, 16)]
P.S.can only be reduced in size text
Edited by Dima73, 24 April 2014 - 10:56.
GigaBlue UHD Quad 4K /Lunix3-4K/Solo 4K
Re: Tuner config 'Priority' setting #13
Re: Tuner config 'Priority' setting #14
Posted 24 April 2014 - 15:39
I can describe one situation where this is usefull. Assume you have one large motorized dish and one multilnb dish. You can receive a specific satellite with both. Let's say 4.8E. You leave in southern Greece, where you can only receive the nordic beam of 4,8E with your large motorized dish. So, you set the priority of the motorized LNB for this satellite to be 19000 and it will always be preferred. The satellite will be received by the non-motorized lnb only if the motorized dish is being used by a recording on a different satellite.
Same examples with 2 or more motorized dishes etc.
Re: Tuner config 'Priority' setting #15
Re: Tuner config 'Priority' setting #16
Posted 24 April 2014 - 16:16
As soon as you change the priority on the preferred tuner, the preferred tuner seems to be ignored for that satellite. But anyway so far no one seems to be able to come up with anything more than vague ramblings as to what this really does or the logic behind it.
Edited by Huevos, 24 April 2014 - 16:16.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users