Thanks, just trying to understand a user's problem that he said started after many years. I noticed that he had t7qam64 in his stored scanning info and I don't see that in my /sys/features Would that cause any problems?

Martin

Ok, it just doesn't seem logical that the scan and http play work but the rtp logic doesn't.

Martin

Looks like the problem is more limited than I thought t8dvbt does seem to work with auto.


hdhomerun_config 172.16.3.37 set /tuner0/channel auto:585500000

hdhomerun_config 172.16.3.37 get /tuner0/status
ch=auto:585500000 lock=t8dvbt ss=100 snq=100 seq=100 bps=26181632 pps=0


Do I have to set ...

Could it be auto is broken? Comparing things with the working http video I tried t7dvbt and auto7t and they work?


hdhomerun_config 172.16.3.37 set /tuner0/channel auto:585500000

hdhomerun_config 172.16.3.37 get /tuner0/status
ch=auto:585500000 lock=none ss=100 snq=0 seq=0 bps=0 pps=0

hdhomerun ...

Has there been an any change in rtp streaming? The code which has worked in the past to support gettingg the EPG sets this


hdhomerun_config 172.16.3.37 set /tuner0/channel auto:585500000
hdhomerun_config 172.16.3.37 set /tuner0/filter "0x0012"
hdhomerun_config 172.16.3.37 set /tuner0/target rtp ...

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