[enen92]

I know that...my question is exactly where you will find this data from a script

<channel id="TVI24.pt">1:0:1:131:26:36:CE40000:0:0:0:</channel> <!-- TVI 24 -->
<channel id="TVI24.pt">1:0:19:85:65:53:CE40000:0:0:0:</channel> <!-- TVI 24 -->

As far as I know the rytec EPG doesn't have this information (?) So it will be a hell amount of work digging into every rytec xmltv file...
It might work for some channels by matching the channel name with the one present on thelogodb but still, you'll miss a huge ammount (that will require manual inspection).

I like the idea of storing those id's. Just wondering the technical details to accomplish that.
As a matter of fact rytec uses to be quite stable about those id's. There are a lot of channels that changed name on the past (at least for PT) and the channelId is still the same for years. For instance sportv.golfe is now sportv.5 but the id has been the same. benficatv is now btv but the id is also the same.

[Lunatixz]

@Lunatixz
Maybe you and your plugin cannot take advantage of it (sorry for you) but others could surely benefit from this data.
It is just a matter of extra data - your logos will always be there (or a link to them).
When someone would like to do something to improve things (and who knows maybe create some standards) based on concepts from a huge and well-working platform such as E2, then there is always someone who would like to hinder new work...I have seen it before and I guess I will always see it.
BTW: there are other E2 epg-providers other than Rytec that uses ServiceReference....

This has nothing to do with my plugin... and actually such a service, if it were possible would be great!

I guess my years of project planning has me able to see something you can't? For me it's as clear as day... waste all the time you want... I was just trying to have you look beyond your idea and to the bigger picture!

You are now on a pursuit to create a very limited database of information that will be useful to a small minority of users, over the bigger picture this project started as...

I think the perfect analogy would be, what if the fanart.tv db was only able to search via the first letter of the movie title... how many incorrect movie titles would you get and have to sort through?
or better yet how about if the fanart.tv db could only returned data for movies that started with a 's'? sure the users that only like movies that start with a "s" would be happy...but the rest? not so much...

Good luck, this will be my last input on the subject...

[tilleke]

I know that...my question is exactly where you will find this data from a script

<channel id="TVI24.pt">1:0:1:131:26:36:CE40000:0:0:0:</channel> <!-- TVI 24 -->
<channel id="TVI24.pt">1:0:19:85:65:53:CE40000:0:0:0:</channel> <!-- TVI 24 -->

As far as I know the rytec EPG doesn't have this information (?) So it will be a hell amount of work digging into every rytec xmltv file...
It might work for some channels by matching the channel name with the one present on thelogodb but still, you'll miss a huge ammount (that will require manual inspection).

Code:

http://rytecepg.wanwizard.eu/rytec.WW.sources.xml

Look at the URL after the channels tag

This is one source of many (which are updated and synced between themselves).

Hope that clarifies it...

[enen92]

Ah that would make things easier, thanks for clarifying.
I like the idea and think it can be really usefull to create a standard or (at least group standards). Let me know if you need any help.

[tilleke]

This is for instance the current output from a channel-search in TheLogoDB (searching for TVI 24)

Code:

{
            "idChannel": "2569",
            "strChannel": "TVI 24",
            "strPackageIDs": ",75,155,157,195,196,",
            "strLyngsat": "http://www.lyngsat.com/tvchannels/pt/TVI-24.html",
            "strCountry": "Portugal",
            "strLyngsatLogo": "http://www.lyngsat-logo.com/tvchannel/pt/TVI-24.html",
            "strLogoWide": "http://www.thelogodb.com/images/media/logo/rspyuw1433341651.png",
            "strLogoWideBW": null,
            "strLogoSquare": null,
            "strLogoSquareBW": null,
            "strFanart1": null,
            "strDescription": null,
            "dateModified": "2015-06-03 15:27:35"
        },

If I manage to get hold of the ServiceReference for the channels present in TheLogoDB then a new output could look like this:

Code:

{
            "idChannel": "2569",
            "strChannel": "TVI 24",
            "strPackageIDs": ",75,155,157,195,196,",
            "strLyngsat": "http://www.lyngsat.com/tvchannels/pt/TVI-24.html",
            "strCountry": "Portugal",
            "strLyngsatLogo": "http://www.lyngsat-logo.com/tvchannel/pt/TVI-24.html",
            "strLogoWide": "http://www.thelogodb.com/images/media/logo/rspyuw1433341651.png",
            "strLogoWideBW": null,
            "strLogoSquare": null,
            "strLogoSquareBW": null,
            "strFanart1": null,
            "strDescription": null,
            "strRytecChannelID": "TVI24.pt",
            "strPiconsSource": "TV/tvi24",
            "dateModified": "2015-06-03 15:27:35"
        },

where I have added "strRytecChannelID" and "strPiconsSource" (which of course must be added in the channel-table).

The ServiceReference may not be needed to store (perhaps in a separate table for future reference and consulting) - it is only needed by me during the first scan to match current channel-items in TheLogoDB with those used by Rytec and PiconsSource. Another reason for not storing and relying on the ServiceReference is that it may change over time due to frequency-changes - however most of the times Rytec channel IDs remain the same despite frequency change unless the channel name is changed too but that is rare.

You can start with TheLogoDB project already now - no need to wait for me. The extra fields can be added later to the channel-table and then it is a matter of just launching an SQL update operation on the database to fill in those fields. Also for developers who implements the API already now in their plugin, I don't foresee any problems. The output of the channel-api I showed above is just a simple json-file so if the developers run a json-parser looking for particular info, then the addition of other fields in future won't break their code. Of course if a developer "scrapes" the output and do a lot of string-parsing, then there might be surprises but then again why should they when there are json-parsers developed for these purposes.

Occasionally I would need at my end run some scripts again against Lyngsat and Rytec to see for any differences such as edits, deletions and new items but that is true also for TheLogoDB.. I guess that is something which can be looked into later...

Well, this is my idea. Since I am the new boy on the block I guess you ought to discuss this among yourselves and then perhaps let me know if I shall carry on or not. I don't want to put my foot on someone else's feet and make them all upset. I leave it up to you. Let me know if you're interested.

[Lunatixz]

What kind of api hits can the site take? should I cache results for longer than 24hrs?

Can we also include Studio logos to the db?
ex:

[enen92]

@zag please find below the csv file for MEO IPTV fixed as requested. Also tried to use the same names already on the db so the channels can be the same.

https://meocloud.pt/link/3d8cd9ce-923c-4...ed%29.csv/

After this I will review all the packages so some channels can be merged. Then finish up building/uploading the logos

many thanks

[zag]

@tilleke - that sounds great, just get me any data you can and I will try to import. Even an excel list of strRytecChannelID vs. strChannel would be easy to do.

@Lunatixz - well its hosted on www.theaudiodb.com server and that does a clear 7 million api hits A NIGHT, so it should be fine No studio logos for now, but maybe in future yeh.

@enen92 - cool will import today.

[bry]

I managed to pull some low res logos for my provider - they could be a great point of reference if some one would like to recreate in better resolution. https://www.dropbox.com/s/c5udi3dkcgcb73...0.zip?dl=0

they are 360x270

[zag]

I managed to pull some low res logos for my provider - they could be a great point of reference if some one would like to recreate in better resolution. https://www.dropbox.com/s/c5udi3dkcgcb73...0.zip?dl=0

they are 360x270

Most of those are already in the source folder in high resolution. Simply download, then upload to the site under your provider.

http://www.thelogodb.com/source/

[enen92]

Guys please pay attention to what you upload to the database. Don't forget 90% of the skins are dark. Make them in a light version or at least apply some white/grey shadow to them.

Logos like:
http://www.thelogodb.com/channel.php?c=7981

Won't really work well on the majority of kodi's skins.

[zag]

@zag please find below the csv file for MEO IPTV fixed as requested. Also tried to use the same names already on the db so the channels can be the same.

https://meocloud.pt/link/3d8cd9ce-923c-4...ed%29.csv/

After this I will review all the packages so some channels can be merged. Then finish up building/uploading the logos

many thanks

http://www.thelogodb.com/browse.php?p=204

[Lunatixz]

Is there anyway to submit a change when a logo is incorrectly categorized?
http://www.thelogodb.com/channel.php?c=6956 is under color wide, when it should be wide bw

Also how to you report bad logos: example
http://www.thelogodb.com/channel.php?c=6961
Image is not a good transparent image, has white pixels

[zag]

At the moment no reporting. But anyone can improve a logo by "re uploading" it, which will overwrite the old logo.

If someone identifies some really bad ones, I'll get GIMP out and start recreating some .

[zag]

Thanks to whoever added the Spanish and Finish Terrestrial channels.



https://docs.google.com/spreadsheets/d/1...sp=sharing

I've added them to the database now:

http://www.thelogodb.com/packages.php?t=Terrestrial