2020-06-07, 06:41 AM
2020-06-07, 06:44 AM
It might be worth downloading the evaluation version of tscapture (from https://tscapture.com), and try scanning for channels. If it finds the channel in question, do a 1 minute 'full transport stream' recording of that channel, and put the file somewhere like onedrive or dropbox, and I'll try it here with my signal generator with nextpvr v5.
2020-06-07, 06:45 AM
What was the name of the channels missing? Any weird characters or punctuation symbols in the names?
2020-06-07, 04:19 PM
The call signs change sometimes with the scan. It is either WUPL-HD, WUPL-HD1, WUPL-HD2, WUPL-HD3 or the network names Quest, H & I, Escape, WUPLDT.
I did a tscapture scan and the channels show up.
2020-06-07, 05:13 PM
(2020-06-07, 06:44 AM)sub Wrote: ... do a 1 minute 'full transport stream' recording of that channel, and put the file somewhere like onedrive or dropbox (2020-06-07, 04:19 PM)hootie318 Wrote: I did a tscapture scan and the channels show up. You need to capture i minute of data and put the file somewhere.
2020-06-07, 05:32 PM
2020-06-07, 05:52 PM
(This post was last modified: 2020-06-07, 06:05 PM by mvallevand.)
I never even noticed the bad xml that NextPVR was creating until now.
<service> <service_id>0x3</service_id> <service_name>H est&a I</service_name> <service_provider_name>ATSC</service_provider_name> <major>54</major> <minor>3</minor> <service_type>0x1</service_type> <running_status>1</running_status> </service> Martin
2020-06-07, 06:05 PM
It was a bug introduced in the last release. There was an updated NPVRTSMon.ax file posted here somewhere for another user that fixed it.
2020-06-07, 06:06 PM
2020-06-07, 10:46 PM
Replaced the file, restarted, and bingo!
Thank you very much to sub, mvallevand, graham. Huge thanks for this application. |
|