Try to clear terrestrial services now.
Do they clear? Or fix required?
(Is clearing only eeee not eeee+freq)
The channels work fine. I think the only problem now is auto/timers.
Edited by Abu Baniaz, 19 December 2017 - 01:01.
Posted 19 December 2017 - 07:56
See http://www.dvbservic...iers/network_id for 0x000 and >= 0XFF00. These are not invalid, but shouldn't occur in the wild.
Those are network IDs. This is ONID. Is enigma confusing the two?
Posted 19 December 2017 - 08:16
Ok, got it now. http://www.dvbservic...inal_network_id
But that only says "0" and above "FF00" are reserved. So what is the story with "1" and "0x1111"
Posted 19 December 2017 - 13:47
In a lot of cases the NID and ONID are the same, but you're right, I pasted the wrong link.
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.
Posted 19 December 2017 - 13:53
Posted 19 December 2017 - 15:10
Pull request here for consideration:
BTW, that commit extends Athoik's original commit as suggested by @dhwz to allow users to switch namespace subnet on and off individually by DVB type. It is not intended as a substitute for the provider workaround that WanWizard is discussing.
Posted 19 December 2017 - 15:32
Ok, got it now. http://www.dvbservic...inal_network_id
But that only says "0" and above "FF00" are reserved. So what is the story with "1" and "0x1111"
Not invalid but atleast 1 may only be used on 19,2°E. If it's used somewhere else it should be treated as invalid. The stupidity it's default on many hardware components, thats why so many feeds are using 1.
Check the link when you click on allocation table on the top of that website.
Edited by dhwz, 19 December 2017 - 15:34.
0 members, 15 guests, 0 anonymous users