Nick,
I was trying to track down why WCRN-LD (3.0 signal in Boston) never scans in on the Live Bandscan for a participant who receives it. I got a screenshot from him of the HDHR Config GUI showing the BSID present in the PLP Info section, but when the command line scan is done, no "TSID" value is populated. This is what his receiver shows on the command line:
SCANNING: 569000000 (us-bcast:30)
LOCK: atsc3 (ss=82 snq=48 seq=100)
PROGRAM 1: 131.1 Intrigue TV
PROGRAM 2: 131.2 Paranormal TV
PROGRAM 3: 131.3 Retro TV
PROGRAM 4: 131.4 Heartland TV
SCANNING: 563000000 (us-bcast:29)
LOCK: 8vsb (ss=100 snq=100 seq=100)
A 1.0 signal would have a "TSID:" row right after the "LOCK:" row. Any chance of getting it to provide the BSID value in a "TSID:" row (not "BSID:" if at all possible, for backwards compatibility) for 3.0 signals when it's available?
Thanks.
- Trip
BSID in HDHomeRun Config Scan Mode?
Re: BSID in HDHomeRun Config Scan Mode?
Done. It will be in the next beta firmware release.
Note that doing a scan like that from hdhomerun_config will only detect ATSC 3.0 channels that are listed in the LLS on PLP 0. If the station has multiple PLPs with isolated LLS data this scan won't detect the extra channels.
Nick
Note that doing a scan like that from hdhomerun_config will only detect ATSC 3.0 channels that are listed in the LLS on PLP 0. If the station has multiple PLPs with isolated LLS data this scan won't detect the extra channels.
Nick
Re: BSID in HDHomeRun Config Scan Mode?
Understood. The important part is that the overall signal gets properly detected, if at all possible.
- Trip
- Trip