After getting dtv-scan-tables-git installed, I went to do an ATSC scan and it gives:
And yes I did try restarting NextPVRServer.dll and logout/login to the web client. The log didn't seem to provide any better clue as to what path is causing the 'status' failure.
As an aside, regarding the thread that mentioned the Devices being generically named (ref: https://forums.nextpvr.com/showthread.ph...047&page=3), please use my logs if it helps that endeavor. :-)
My ATSC and QAM adapters are both named "Local Recorder (adapter0)" while the log shows e.g.:
and...
Maybe something like {type}: {name} or similar would be better to populate the 'Devices' ? I can instead reply to the other thread with this if that's preferred (don't want to necro).
Thanks!
Code:
[4] {"stat":"ok",
"complete":true,
"status":"Error: No such file or directory",
"channels": [
]
And yes I did try restarting NextPVRServer.dll and logout/login to the web client. The log didn't seem to provide any better clue as to what path is causing the 'status' failure.
As an aside, regarding the thread that mentioned the Devices being generically named (ref: https://forums.nextpvr.com/showthread.ph...047&page=3), please use my logs if it helps that endeavor. :-)
My ATSC and QAM adapters are both named "Local Recorder (adapter0)" while the log shows e.g.:
Code:
<name>adapter0 (Samsung S5H1409 QAM/8VSB Frontend)</name>
<type>ATSC</type>
<filter>adapter0</filter>
and...
Code:
<name>adapter0 (Samsung S5H1409 QAM/8VSB Frontend)</name>
<type>QAM</type>
<filter>adapter0</filter>
Maybe something like {type}: {name} or similar would be better to populate the 'Devices' ? I can instead reply to the other thread with this if that's preferred (don't want to necro).
Thanks!