Silicondust

emveepee

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.

emveepee

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

emveepee

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 ...

emveepee

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

emveepee

Thanks for checking that, I've passed that on to the author. I rebooted my PC a couple of days ago and the scheduled updates have started working.

It would be nice if the BDA dead connection timeout issue could be looked at deeper, the rtp method on Linux seems more stable.

Thanks again.

emveepee

Thanks for looking.

From the description "The BDA driver detected a dead connection" it does sounds like BDA doesn't timeout on its own and it took NextPVR reintialized BDA on the manual run to make the tuner available.

Can you tell me how long it took 587 to respond after 539 in the earlier ...

emveepee

emveepee wrote: Tue Apr 22, 2025 12:23 am Update after a failed 2:45 (Eastern) run I restarted a manual run just before 3:09 and it completed and successfully reset the tuner. The question is can you detect what is failing in BDA around 02:47:48

At 4:44 you would also see a Linux test using rtp which was successful.

Martin

emveepee

Update after a failed 2:45 (Eastern) run I restarted a manual run just before 3:09 and it completed and successfully reset the tuner. The question is can you detect what is failing in BDA around 02:47:48

Martin

emveepee

Hours later I still get

"c:\program files\Silicondust\HDHomeRun\hdhomerun_config" 10528531 set /tuner0/channel none
ERROR: resource locked by 172.16.3.3

emveepee

Please turn on "send diagnostic information" in HDHomeRun Setup... then we can see what the BDA driver is doing.

OK thanks I just enabled it. You should focus on 10528531-0

I am running a control now, basically you should see an 8197 PID scan with the found PID's being added and running for ...

emveepee

There is a keepalive system. If the original app terminates the HDHomeRun will drop the lock in about a minute or so.

After terminating the app with taskkill I didn't see it timeout after much more than a minute, that is why I thought BDA internals were potentially keeping it alive. I expect ...

emveepee

jasonl wrote: Sun Apr 20, 2025 5:39 pm Yes, the BDA driver automatically locks the tuner while streaming (and unlocks it when done).

So if BDA locks the tuner and the original calling program fails and is no longer running is there a solution other than reboot?

Martin

emveepee

I am trying to figure out why NextPVR OTA updates fail for me on Windows every night after a connection. In debugging this does using a BDA tuner prevent use from hdhomerun_config on the "hung" tuner? I couldn't do anything with the HDHR until an HDHR reboot. I am running on 172.16.3.3

[D:\temp ...

emveepee

To conclude the thread the the 4DT device works fine here with the modulator. My only issue is the annoying logic of the Silicondust scan which remove channels from the http interface when a recan takes place but that annoyance is on ATSC too with weak signals.

Martin

emveepee

That's fine in BDA and RTP modes only the required PIDs are requested. It is only the special case when we need to do full mux for testing scan, OTA EPG etc that we need the full mux.

Martin

Search found 23 matches

Re: DVB-T LCN descriptor.

DVB-T LCN descriptor.

Re: Device ID info

Device ID info

Re: BDA tuner locked.

Re: BDA tuner locked.

Re: BDA tuner locked.

Re: BDA tuner locked.

Re: BDA tuner locked.

Re: BDA tuner locked.

Re: BDA tuner locked.

Re: BDA tuner locked.

BDA tuner locked.

Re: DVB-T in North America

Re: DVB-T in North America