OK I noticed on DVB-T scans that it looked to be based on sid:tsid:onid so interesting it is NZ specific.

For DRM-free ATSC 3 which I can't test in Canada, I assume the LCN is the base channel, hopefully the ATSC names the HDHR return will match.

Martin

In my region (the southeastern US), it returns guide data for every channel listed in my lineup which hasn't been disabled. That is, if a channel is enabled and it has guide data in the HDHomeRun app, my script returns the same.


I agree in my region in Ontario Canada is is perfect too. I ...

How complete is the guide data? Looking at a New Zealand DVB-T sample it didn't have 50% of the channels the HDHR detected.

Martin

Thanks it happened again and I did need the force not none before clearing the target and the channel.

Martin

As a follow up I could connect to the HDHR and BDA could still control and stop them, but that this should be able to be done with hdhomerun_config

Martin

Last night I was was doing some BDA development and I mustn't have done a clean shutdown so this morning I see steady UDP/RTP traffic from a HDHR to my Windows PC and booting the Windows PC doesn't stop it

20251203-23:09:42 Tuner: tuner0 streaming rtp to 172.16.3.3:52490
20251203-23:11:51 Tuner ...

Here is how many times tsduck found the LCN's in a 1 minutes mux https://pastebin.com/X6WKaDaP It looks like they were sent between 1 and 8 times in that minute. The one I noted was sid 0x4a75 which was twice.

I have a test stream that I loop and the LCN descriptor is not always being sent. Sometimes I get the correct LCN and sometimes it it is in the 5000 range depending on which NIT it picks up. Is there a way to wait longer in the HDHR scan?

Martin

You can gain a lot of additional information (presuming the device has recent firmware) from the http://<hdhr>/discover.json, and then decoding the json output.


Thanks I don't have access to the API where I am calling from so this is perfect https://github.com/Silicondust/libhdhomerun/blob ...

Is there a way to tell from the device ID if a device is legacy or not? If it is not legacy and perhaps an edge case in my own system can the device ID show if the device is ATSC/QAM vs DVB-T/C?

Martin

with the signal of the ATSC 3.0 channel being encrypted the broadcasters are in violation of both the emergency alert system and educational/informational rules established by the FCC.


Old analog TV's and capture cards don't receive ATSC 1.0 so that rule would apply to compatible TV receivers ...

They did give direction in this thread viewtopic.php?t=77340 although I don't know if they will have an account based solution by early 2024.

Martin

nickk wrote: Thu Mar 16, 2023 4:59 pm Best not to use the Series or Episode ID to determine type. The guide data for Australia does not follow this convention for example.

Thanks for that, as long as you don't use MV as your identifier for non-movies it probably isn't going to cause a problem. Is there sample JSON anywhere?

Martin

Two ideas come to mind...

1) App could search the category tags for the following categories we use regardless of the location in the list:
Series, Movie, News, Special, Sport, Shop, Audio, Adult

2) We could add an attribute to the category tag to indicate the high level category vs genre.

Nick ...

As an additional question, I'm attempting to get this data to mesh well with NextPVR. I'm able to pull both the channel lineup and this API's guide data, via my earlier posted updated script, but for some reason, NextPVR doesn't seem to be able to mate the two together

@Brak I had a look at ...