[SOLUTION] 7-day OTA EPG via MHEG-5 for DVB-T outside of Auckland NZ

I M · 2023-11-22T22:08:59+00:00

As I understand it, for people outside of Auckland, the stock (DVB-T) EIT-derived EPG doesn't provide anything more than now+next information? https://tvhea...

I M

PR is up now, and yes, passing a flag from the NZ Local module to run the few lines of code that translates the TSIDs.

In the 'mheg' system I have running the 'Episode' column is populated whenever such information is broadcast in the main body of data. With the EIT system it doesn't appear to populate, although the information is clearly there in the 'extra text' column.

I've assumed there's some minor anomaly with the scraper (episode scraping is enabled in the module btw) but haven't looked into it at all. It's not impossible I've done something wrong or created a bug of sorts, but for now it's enough for me that the EIT code is primarily working and provides all main EPG data.

DeltaMikeCharlie

@I M - I have just seen your PR. I will provide some programming feedback on GitHub, but I have already compiled it and tested it with my Sydney EPG and nothing seems broken thus far. 🙂

I M In the 'mheg' system I have running the 'Episode' column is populated whenever such information is broadcast in the main body of data. With the EIT system it doesn't appear to populate, although the information is clearly there in the 'extra text' column.

In the EIT, there are 3 possible text fields:

Short Event Descriptor - 'Name' eg, "M*A*S*H"
Short Event Descriptor - 'Text' eg, "Requiem for a Lightweight" (Sometimes called a Sub-Title)
Extended Event Descriptor eg "Trapper enters the inter-camp boxing tournament."

Not all broadcasters provide all fields and some broadcasters don't provide an extended description.

The WebUI 'Extra Text' column has some logic that will show either the short text or the extended text. From the test data that I have, the NZ broadcasters was only using the short text, not the extended description.

I have recently added some code to the 'Service' object that allows for these fields to be moved around.

I M

Thanks, FYI I deliberately kept the IF statements separate rather than combine with an OR for now (in case that was going to be a comment 🙂, it made things easier when I was specifying the translation rather than relying on the NIT TSID. If the latter proves to be ok in other situations then it could be simplified without issue I expect.

Ok on the EIT detail, I probably knew more about it when I did the MHEG thing but that's useful thank you. It may be your code will fix the issue so won't go into it until we see what it does.

« Previous Page