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: 1144836" data-attributes="member: 82144"><p>Aside: a few comments from an interested dev who has attempted to implement ATSC EPG support for TVE 3.5...</p><p></p><p></p><p>I've heard of such an FCC requirement, but apparently a lot of channels ignore it or the data quality is not great. I was quite surprised to read Pat's comments and was wondering whether the better data came from the TVDB/IMDB lookup that EPGC does.</p><p></p><p></p><p>Title is a mandatory field in the ATSC EPG format ("PSIP") as well as XMLTV format.</p><p></p><p></p><p>Not surprising. The ATSC EPG format does not have an episode name/title field. Only a title and generic text (which is usually a description, perhaps with other content stuffed into it). Season and episode number fields are also not defined in the format. Broadcasters <em>could</em> use custom descriptors to convey this information, but this seems unlikely since they don't have any integration with the TV or set-top-box manufacturers. In other words: they could broadcast the data, but the TVs and STBs wouldn't know it existed ...unless TV and STB manufacturers integrated support for the custom descriptors.</p><p></p><p></p><p>That's my understanding too.</p><p></p><p></p><p>Agreed.</p><p></p><p></p><p>Zero-indexing is very common in code. It's not so strange for a developer. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p></p><p>Correct. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p></blockquote><p></p>
[QUOTE="mm1352000, post: 1144836, member: 82144"] Aside: a few comments from an interested dev who has attempted to implement ATSC EPG support for TVE 3.5... I've heard of such an FCC requirement, but apparently a lot of channels ignore it or the data quality is not great. I was quite surprised to read Pat's comments and was wondering whether the better data came from the TVDB/IMDB lookup that EPGC does. Title is a mandatory field in the ATSC EPG format ("PSIP") as well as XMLTV format. Not surprising. The ATSC EPG format does not have an episode name/title field. Only a title and generic text (which is usually a description, perhaps with other content stuffed into it). Season and episode number fields are also not defined in the format. Broadcasters [I]could[/I] use custom descriptors to convey this information, but this seems unlikely since they don't have any integration with the TV or set-top-box manufacturers. In other words: they could broadcast the data, but the TVs and STBs wouldn't know it existed ...unless TV and STB manufacturers integrated support for the custom descriptors. That's my understanding too. Agreed. Zero-indexing is very common in code. It's not so strange for a developer. :) Correct. :) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
General Forums
OffTopic
EPG Collector for MHEG5, EIT, OpenTV & MediaHighway
Contact us
RSS
Top
Bottom