2020-04-23, 06:07 PM
Hello,
Following the evolution of Teletext, the next standard that seems to have emerged and adopted by free to air TV is HbbTV.
Given that for a PVR server most likely the requirement to support this standard would be somehow simple as described in the below
TVheadend thread: https://tvheadend.org/issues/1711
"The HBB TV data is simply data PIDs linked to the channel in question. It's a table called AIT, and the data is a format called DSM-CC.
I don't think TVHeadend would have to do anything other than not filter out the AIT data PIDs (it does currently, even in a raw stream of a channel without "/play" in the URL).
Then the data would be available for processing by some kind of plug-in on the client side (Kodi via HTSP, etc.) I guess this is how teletext works currently?
For an example, I've attached a full mux TS dump of 11494H from Astra 1 19.2°E. This carries German ARD channels, and they all have PIDs carrying the HBBTV data. For example, Das Erste HD has HBBTV data on PID 1170, and then some more on PID 2171 (not sure what this latter one is for).
Looking at the data in PID 1170, it's carrying the URLs for the HBBTV service, for the HBBTV plugin on the receiver to receive the content from. PID2171 may be some of the data for offline viewing (I don't know).
I found a plugin for Firefox called FireHbbTV - with this installed, if you visit one of the URLs shown in the PID 1170 stream - http://itv.ard.de/ardstart/
You see the data that gets fetched, as if it were on a TV or receiver that supports HBBTV.
On the face of it, all I think TVHeadend needs to do is pass through any data PIDs marked as carrying HBBTV data!"
Is there something that NextPR can do and possibly go one step further and even expose somehow these PIDs also in the web client so that if somebody for instance uses an HbbTV emulator addon like for instance this one for Chrome (and Chromium Edge): https://chrome.google.com/webstore/detai...ated?hl=en
can use it?
Thanks and regards
Following the evolution of Teletext, the next standard that seems to have emerged and adopted by free to air TV is HbbTV.
Given that for a PVR server most likely the requirement to support this standard would be somehow simple as described in the below
TVheadend thread: https://tvheadend.org/issues/1711
"The HBB TV data is simply data PIDs linked to the channel in question. It's a table called AIT, and the data is a format called DSM-CC.
I don't think TVHeadend would have to do anything other than not filter out the AIT data PIDs (it does currently, even in a raw stream of a channel without "/play" in the URL).
Then the data would be available for processing by some kind of plug-in on the client side (Kodi via HTSP, etc.) I guess this is how teletext works currently?
For an example, I've attached a full mux TS dump of 11494H from Astra 1 19.2°E. This carries German ARD channels, and they all have PIDs carrying the HBBTV data. For example, Das Erste HD has HBBTV data on PID 1170, and then some more on PID 2171 (not sure what this latter one is for).
Looking at the data in PID 1170, it's carrying the URLs for the HBBTV service, for the HBBTV plugin on the receiver to receive the content from. PID2171 may be some of the data for offline viewing (I don't know).
I found a plugin for Firefox called FireHbbTV - with this installed, if you visit one of the URLs shown in the PID 1170 stream - http://itv.ard.de/ardstart/
You see the data that gets fetched, as if it were on a TV or receiver that supports HBBTV.
On the face of it, all I think TVHeadend needs to do is pass through any data PIDs marked as carrying HBBTV data!"
Is there something that NextPR can do and possibly go one step further and even expose somehow these PIDs also in the web client so that if somebody for instance uses an HbbTV emulator addon like for instance this one for Chrome (and Chromium Edge): https://chrome.google.com/webstore/detai...ated?hl=en
can use it?
Thanks and regards
