(2015-06-12, 02:17)tilleke Wrote: I am coming from the Enigma2-world (read E2 i.e. Dreambox, Vu+ and similar STBs for those who don't know what it means) and just started out with Kodi on my brand new HTPC. I am mostly interested in IPTV but I might add a SAT-card later on to my set-up....

(2015-06-12, 02:17)tilleke Wrote: As to logos, there is another initiative, involving e2 and Kodi, namely picons-source which can be found on Github . They are trying to share logos and make easy lookup of them using a cross-table (see here). This is an example:

(2015-06-12, 09:01)tilleke Wrote: @Lunatixz
Perhaps I expressed myself not clearly (English is not my mother-tongue). Of course, TheLogoDB would not store any EPG-data, only a field indicating a ChannelID which would help to query the Rytec resources (Rytec has furnished EPG to the e2 platform for many years). I have edited my initial post to indicate what I meant better.

I am unsure what you mean with a "pipe dream"? However, I admit, a dream would come through if the "TheLogoDB" could hold some extra data which would permit and facilitate consulting other related resources.

(2015-06-12, 14:47)Lunatixz Wrote: Channel id's and display-names are relative to the epg data provider. They are not universally named. Every grabber, and every data provider uses their own naming schemes.

Gathering that information when you don't provide listing data IMO is a waste of resources.

Alternative channel names and alias on the other hand would be nice... Ie. Channel call letters.

(2015-06-12, 15:06)tilleke Wrote:

(2015-06-12, 14:47)Lunatixz Wrote: Channel id's and display-names are relative to the epg data provider. They are not universally named. Every grabber, and every data provider uses their own naming schemes.

Gathering that information when you don't provide listing data IMO is a waste of resources.

Alternative channel names and alias on the other hand would be nice... Ie. Channel call letters.

Of course there are different grabbers and providers but Rytec has been freely available for e2 for many years and probably the base-source for the e2-platform and as you surely know, there are milions of e2-users out there. Rytec covers probably nearly all European sat-broadcasters plus Russian, African, Australian and Asian. I guess data from the US may be less from Rytec but this is probably because there aren't many e2-users (and sat-users) in US. However, I am sure if it is now possible to implement support for Rytec, lots and lots of users would be grateful. I think this may be possible, using two different routes. I will look into this as soon as I have some time and then report back.

(2015-06-12, 15:20)tilleke Wrote: @Lunatixz
It's a matter of obtaining a channel-id (and perhaps a ServiceReference) to get it working if I have understood things right.
How would you implement "universal data" and convince major providers and grabbers to use them?

As mentioned in my first post, I am only suggesting things. Some may be feasible, others perhaps not. Some may be approved by people, others won't.

(2015-06-12, 15:39)tilleke Wrote: Sorry, I probably didn't make myself clear in my first post. TheLogoDB was created to obtain easily logos but my idea was to store some additional channel-data so the TheLogoDB could be used for other purposes as well (especially since there is no other central channel information db as far as I know). This is the reason why I wrote about EPG and display-names and so forth. Once again my apologies for not making that clear.