home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
General Forums
OffTopic
EPG Collector for MHEG5, EIT, OpenTV & MediaHighway
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 1144842" data-attributes="member: 82144"><p>Correct, no program image support. I'd speculate that's for a number of reasons:</p><ul> <li data-xf-list-type="ul">no support in broadcast EPG formats</li> <li data-xf-list-type="ul">space in the guide screen/layout at a premium; more channel "timelines" generally preferred<br /> </li> <li data-xf-list-type="ul">historically, low internet data caps => users don't want a ton of images downloaded<br /> </li> <li data-xf-list-type="ul">historically, no/few good metadata databases available</li> </ul><p></p><p>There are a series of limitations that have to be overcome in order to have something displayed in the guide:</p><ul> <li data-xf-list-type="ul">acquisition - Don't underestimate this one; people often seem to assume that [for example] "new" flags, season and episode numbers, artwork etc. are readily available. Fact is they're not in broadcast EPG formats, which have traditionally been the main source for EPG content. That means such details usually have to be pulled in by matching against a metadata database. Frankly that's a pain point for TV Server because of how many EPG sources/plugins we have to co-ordinate and/or remain compatible with (XMLTV, WebEPG, SD, TV Movie ClickFinder, broadcast etc.).</li> <li data-xf-list-type="ul">storage - At minimum this usually means adding a field in TV Server's database. However, that's usually followed by "shot gun surgery" through TV Server's various EPG sources to patch in support for the new content. With images we have a ton of questions due to the existence of client (MP or KODI) + server setups and the range of skins available. Does the data reside on the server? ...in which case, how does it get to the client? ...and how do we handle setups where multiple skins or low-powered clients are used (implying the need for different image styles/sizes? ...or does the data reside on the client, in which case how do we manage/update it?<br /> </li> <li data-xf-list-type="ul">retrieval - As with storage: not particularly straightforward.<br /> </li> <li data-xf-list-type="ul">display - Obviously MP has a fair few community skins available (and so does KODI), which is great for user choice. This makes it tricky to manage the compatibility issues and/or community expectations ("OMG, why isn't <new field XYZ> available in <favourite skin name here>!?! Useless @#$%@#% developers!!!") when we want to add, modify or remove skin properties.</li> </ul><p>So, the situation is "challenging". <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p></blockquote><p></p>
[QUOTE="mm1352000, post: 1144842, member: 82144"] Correct, no program image support. I'd speculate that's for a number of reasons: [LIST] [*]no support in broadcast EPG formats [*]space in the guide screen/layout at a premium; more channel "timelines" generally preferred [*]historically, low internet data caps => users don't want a ton of images downloaded [*]historically, no/few good metadata databases available [/LIST] There are a series of limitations that have to be overcome in order to have something displayed in the guide: [LIST] [*]acquisition - Don't underestimate this one; people often seem to assume that [for example] "new" flags, season and episode numbers, artwork etc. are readily available. Fact is they're not in broadcast EPG formats, which have traditionally been the main source for EPG content. That means such details usually have to be pulled in by matching against a metadata database. Frankly that's a pain point for TV Server because of how many EPG sources/plugins we have to co-ordinate and/or remain compatible with (XMLTV, WebEPG, SD, TV Movie ClickFinder, broadcast etc.). [*]storage - At minimum this usually means adding a field in TV Server's database. However, that's usually followed by "shot gun surgery" through TV Server's various EPG sources to patch in support for the new content. With images we have a ton of questions due to the existence of client (MP or KODI) + server setups and the range of skins available. Does the data reside on the server? ...in which case, how does it get to the client? ...and how do we handle setups where multiple skins or low-powered clients are used (implying the need for different image styles/sizes? ...or does the data reside on the client, in which case how do we manage/update it? [*]retrieval - As with storage: not particularly straightforward. [*]display - Obviously MP has a fair few community skins available (and so does KODI), which is great for user choice. This makes it tricky to manage the compatibility issues and/or community expectations ("OMG, why isn't <new field XYZ> available in <favourite skin name here>!?! Useless @#$%@#% developers!!!") when we want to add, modify or remove skin properties. [/LIST] So, the situation is "challenging". ;) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
General Forums
OffTopic
EPG Collector for MHEG5, EIT, OpenTV & MediaHighway
Contact us
RSS
Top
Bottom
