2019-12-01, 03:58 PM
Ok I see it on Windows so I am willing to test too.
Martin
Martin
2019-12-01, 03:58 PM
Ok I see it on Windows so I am willing to test too.
Martin
2019-12-01, 04:04 PM
2019-12-01, 04:20 PM
Ok it still disappears but does come back with the previous name.
I don't know if it makes a difference but device.log shows a different name 2019-12-01 11:11:20.543 [DEBUG][4] Using tuner: Silicondust HDHomeRun Tuner 10528531-0 (1) Changing the identifier name to match doesn't help Martin
2019-12-01, 06:03 PM
With dual tuner ATSC and live tv or recordings on both tuners, both tuners disappear from the status list (and api calls)
Martin
2019-12-01, 06:34 PM
Another interesting thing, I just ticked keep digital tuners primed and when I do this the tuners don't come back to the status call at all after playback, but they will play.
Martin
2019-12-01, 08:22 PM
(This post was last modified: 2019-12-01, 08:31 PM by Peter Ingham.)
Doing the status on the DVB-T tuner with a LiveTV running gives a blank page (on both FireFox and Chrome).
Doing a "save as text" of this blank status page gives a 0 byte file. In chrome developer tools, the "Elements Tab", shows:
2019-12-01, 09:21 PM
I'm just heading out for an hour or so, but I'll take another look when I'm back.
2019-12-01, 09:26 PM
I'm not sure if it is related but I would say that 25% of the time now hitting stop in the web browser doesn't stop transcoding with ffmpeg even when I shut down the browser. It is easily reproduced if you need logs.
Martin
2019-12-02, 04:38 AM
You could try this updated DeviceHostWindows.exe, and supply the logs. This adds some logging around the status query.
|
|