86 replies to this topic

[Huevos]

Original commit is Athoik's work. I pushed one based on it to OpenWebIF,

Edited by Huevos, 16 December 2017 - 00:49.

[Abu Baniaz]

Original commit is Athoik's work. I pushed one based on it to OpenWebIF,

Thanks for clarifying

 

https://github.com/O...095a315a52f6fe8

[Erik Slagter]

That sounds indeed like more of a fool-proof solution.

Also looks more technically sound.

 

And then the hardcoded exceptions can go (I hope) and if not, they should be in a data file instead.

[dhwz]

Holy cow.

If would be great if that could be configured without having to add it to a piece of C++ code...

Hm no scan_tp_valid_check.py on PLi? Because Dream supports this file for many years now to extend the internal static list.

Oh and they recently droped most of the internal fixed entires.

Edited by dhwz, 16 December 2017 - 11:28.

[dhwz]

Personally I think it would be better if namespace subnet was permanently on... and then something in EpgCache that only reads the first 4 digits of the namespace so EPG Import works both ways.

But remember that we would get in new trouble with that solution (always on), as every box would possibly use different namespaces in lamedb. So settings would no longer be really interchangeable anymore (e.g. you also would no longer be able to merge different settigns).

I think staying the old way and adding a readable list (e.g. like the py used by Dream) is the better way.

 

PS: many of the entries on your list are also old or not necessary (e.g. all with ONID = 1 are matched per default in C++), and the entry on 19,2 1:1028 is not existing as duplicate.

[Huevos]

@dhwz I made that list just a few weeks ago. So yes it is possible things have changed in that time (certainly not years out of date like the current list). If it were an xml file that could be created by the satellites.xml creator script. But I think just turning on subnet is the best, and most maintenance free solution.

 

Only place there is currently a problem is importing xml epg files that contain service ref. EPG from SI tables works fine.

Edited by Huevos, 16 December 2017 - 14:51.

[WanWizard]

I'll wait how this discussion develops (it's a bit out of my league), but if the lyngsat grabber needs to produce an additional xml, that shouldn't be a big issue.

[athoik]

If there is a way to use the full dvbnamespace would be great, no extra job, parsers etc.

What should be fixed is the epg import to allow imports using trimmed dvbnamespace.

[WanWizard]

If you can tell me what that exactly means, I can have a look at the EPGimporter.

[Abu Baniaz]

Surely it is not the import that needs adapting, it is the correlation of EPG that needs adapting.

EPG data is present but E2 does not accept it for the different namespace.

Edited by Abu Baniaz, 16 December 2017 - 15:40.

[Abu Baniaz]

Hmmm, I stand corrected EPG works.

I used CrossEPG-OpenTV to grab initially. I then toggled the namespace option and "scanned" using ABM. Services in the sat list were duplicated but all had EPG.

I deleted EPG, then re-imported with CrossEPG- Rytec. Apart from odd missing pairs, EPG worked.

I deleted EPG again, restarted and then used EPG Importer. Same as above.

I then deleted 28.2 services, then scanned using conventional scan. EPG still shows.

Perhaps someone can test on another satellite.

I have not checked timers.

[WanWizard]

Something that just popped into my mind while responding to another topic.

 

Can the mechanism for sub-namespace perhaps also be used to make DVB-T and DVB-C providers unique? Currently they use hardcoded namespaces, so you can never have multiple providers on a single box.

[Huevos]

Something that just popped into my mind while responding to another topic.

 

Can the mechanism for sub-namespace perhaps also be used to make DVB-T and DVB-C providers unique? Currently they use hardcoded namespaces, so you can never have multiple providers on a single box.

DVB-T: Turn on namespace subnet and and multiplexes that are duplicated on several frequencies can now all be accessed. Before this was impossible.

 

DVB-C. Same would apply now for DVB-C. Why would you have multiple cable providers? Anyway if you did this it should not be handled in namespace. Proper way to handle that is a mechanism that can select the correct tuner based on a new flag in lamedb. But really how many people have multiple cable providers? If they do, they can have multiple receivers and stream between receivers.

 

But why introduce a buggy system to utilise more and more obscure configurations that almost no one is going to have.

Edited by Huevos, 16 December 2017 - 17:50.

[Abu Baniaz]

I think @wanwizard is asking if separate option for just dvbt and dvbc

maybe it should be on automatically for non-sat

Edited by Abu Baniaz, 16 December 2017 - 17:52.

[Huevos]

Having subnet on in DVB-C doesn't allow multiple providers. Something new would need coding for this combination that most users would never use. Seriously, how many domestic properties have access to multiple cable providers, let alone would consider contracting from both.

 

And anyway a lesson can be learned from ATSC, which is not to try to change the use of a variable to another job. In this case, that is even more important as the namespace is used by many different pieces of software, i.e. enigma, settings editors, bouquet editors, etc.

Edited by Huevos, 16 December 2017 - 18:01.

[dhwz]

@Abu Baniaz

Thats what Dream does but only for DVB-T(2)

 

So for EPG/Picons only the lookup on EEEE is used, but the namespace is stored fully with frequency EEEExxxx

Edited by dhwz, 16 December 2017 - 18:08.

[WanWizard]

Yes, that is what I mean.

 

An alternatief would be to look at the first 3 positions only, so instead of using EEEE0000 you could have EEE00000 to EEEF0000, giving you 16 different providers? But than again, you'll bump into the EPG issue...

 

I mentioned DVB-C because someone in another thread asked about it, having a cable provider and an FTTH provider which delivers TV in DVB-C over fiber.

[dhwz]

But I think just turning on subnet is the best, and most maintenance free solution.

Yes ok, but think about the consequences:

 

2 different LNBs with frequency drift will get two different frequencies (on Blindscan) which means two different namespaces then (remember you can have different tuners in one box) -> really BAD

You will no longer be able to compare any settings -> BAD

You will not be able to merge 2 different settings, because we'll get many duplicate services -> BAD

 

Using subnet in namespace calculation as default is really a bad idea for DVB-S(2). 

Edited by dhwz, 16 December 2017 - 18:20.

[Abu Baniaz]

@Abu Baniaz

Thats what Dream does but only for DVB-T(2)

 

So for EPG/Picons only the lookup on EEEE is used, but the namespace is stored fully with frequency EEEExxxx

 

Thanks. Can you post a link to the commit, we can pick it in. Will hopefully resolve the problem people in middle England experience. They have transmitters all around.

Edited by Abu Baniaz, 16 December 2017 - 18:18.

[Huevos]

@WW, not sure what you mean about different providers on DVB-T. Different providers would have different ONIDs.

 

@dhwz, that is only a problem if you are not scanning from a predefined list. i.e. blindscan. And the blindscan plugin syncs with the predefined list. But I understand your argument when the values are unknown and are coming from the tuner.