Raspberry Pi 4 in USA with OTA ATSC

[mvallevand]

It isn't practical it needs the zap logic tool. The bad implementation of software on one particular O/S configuration should not dictate how NextPVR works anyway.

Also I didn't know 32bit arm would work on the RPi4 I thought users might needed Docker for that, it's been a long time since I used mine.

Martin

[MattDuffy]

Sounds good -- I'll be returning to my Windows setup in the meantime.

To get back to my original post, I would be grateful to hear from anyone in out there in the USA who has successfully been able to scan for ATSC channels on the Raspberry Pi.

[mvallevand]

Well I am close, I am in Canada and I successfully scanned ATSC on an RPi4 via a Hauppauge USB 1950 tuner and dvbv5-scan did run outside NextPVR and NextPVR worked too. I was using Raspian Buster 64

Martin

[mvallevand]

I reinstalled my RPi4 with the base 32 Raspberry OS with the deb installer default and my Hauppauge USB tuner locks and tunes fine. There is nothing wrong with dvbv5-scan or NextPVR. It seems like you have a user-side problem so maybe dig into dmesg or journalctl.

Code:

pi@raspberrypi:~ $ dvbv5-scan /usr/share/dvb/atsc/ca-ATSC-Ottawa-center-frequencies-8VSB.txt
Scanning frequency #1 473028615
ERROR    command INVERSION (6) not found during store
ERROR    command INVERSION (6) not found during store
Lock   (0x1f) Signal= 91.43% C/N= 0.34% UCB= 225 postBER= 0

NextPVR logs

2021-03-16 15:47:02.024    [DEBUG][8]    method=setting.scan.status
2021-03-16 15:47:02.024    [DEBUG][8]    parameters:
2021-03-16 15:47:02.024    [DEBUG][8]       method: setting.scan.status
2021-03-16 15:47:02.024    [DEBUG][8]       format: json
2021-03-16 15:47:02.025    [DEBUG][8]       sid: 6fdfb104-2e8e-4902-804e-16da8f222d72
2021-03-16 15:47:02.025    [DEBUG][8]       client_ip: 172.16.3.219
2021-03-16 15:47:02.025    [DEBUG][8]       user_agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:86.0) Gecko/20100101 Firefox/86.0
2021-03-16 15:47:02.025    [DEBUG][8]       host_callback: 172.16.3.145:8866
2021-03-16 15:47:02.025    [DEBUG][8]    setting.scan.status
2021-03-16 15:47:02.025    [DEBUG][8]    {"stat":"ok",
"complete":false,
"status":">>> Scanning 473028615",
"channels": [
2021-03-16 15:47:02.390    [DEBUG][17]    GOT: ~1~CIII-HD~CIII-HD~1~473028615~6.1
2021-03-16 15:47:02.393    [DEBUG][16]    GOT: >>> Scanning@about to store
2021-03-16 15:47:02.393    [DEBUG][16]    GOT: >>> Scanning@about to free loop
2021-03-16 15:47:02.393    [DEBUG][16]    GOT: >>> Scanning@about t

I can only direct play but other than that it fine

Martin

[MattDuffy]

Right on, man. Like I said before, I decided I had spent enough time trying to get the Pi to work, so I've returned to my Windows machine.

To get back to my original post, I would be grateful to hear from anyone in out there in the USA who has successfully been able to scan for ATSC channels on the Raspberry Pi.

[mvallevand]

Do your really think our ATSC signals are different? You understand it is the same spectrum and Americans and Canadians on the border watch shows originating from both sides of the border.

Thinking about it I even got the tuner on ebay from the US.

Martin

[sub]

If it's working in Canada, it'll definitely be working in the US too.

[MattDuffy]

I would be grateful to hear from anyone in out there in the USA who has successfully been able to scan for ATSC channels on the Raspberry Pi.

Please, no more replies from anyone outside the USA.