ATSC 3.0

mokey_fraggle
Newcomer
Posts: 1
Joined: Mon May 11, 2020 2:56 am
United States of America

ATSC 3.0

Post by mokey_fraggle »

Greetings,

I'm hoping this is the right place to post this :) I just wanted to offer any help I can if the devs need any help with ATSC 3.0 and myth. I am in the Seattle area and we have a ton of ATSC 3.0 stations. I just picked up and installed a HDHR5-4K to us with mythtv. I should also add i've been using mythtv for at least 10 years... probably more.. and linux since 1998 so I'm not afraid to dig into stuff :)

Regards,
--Elizabeth
User avatar
kmdewaal
Developer
Posts: 641
Joined: Wed Dec 07, 2016 8:01 pm
Netherlands

Re: ATSC 3.0

Post by kmdewaal »

The ATSC 3.0 topic has been discussed in the user mailing list. There is consensus that work needs to be done.
It is not that I personally am going to receive ATSC 3.0 real soon... but nevertheless I am a curious if it works or not and I think that the topic of ATSC 3.-0 combined with HDHR5-4K is of interest to a lot of US mythtv users.

Assuming that the HDHR is connected to the mythtv, this are the questions I can think of:
- does mythtv-setup recognize the HDHR as a HDHR?
- can you configure the HDHR in mythtv-setup?
- can you do a channel scan in mythtv-setup?
- does mythtv-setup find all the channels that the HDHR can find on its own, using the HDHR utilities/apps?
- do you find ATSC 3.0 channels in the mythtv-setup channel list or are those skipped?
- can you make recordings of ATSC 3.0 channels?
- can you make recordings of ATSC 3.0 channels on all tuners (i.e. more than 2) at the same time?
- can you play back ATSC 3.0 recordings (this is more a HEVC/audio issue probably)?

Thanks,
Klaas.
User avatar
kmdewaal
Developer
Posts: 641
Joined: Wed Dec 07, 2016 8:01 pm
Netherlands

Re: ATSC 3.0

Post by kmdewaal »

Hi Elizabeth,

Any success yet with your ATSC 3.0 reception?

Kind regards,
Klaas.
Lost Dog
Junior
Posts: 36
Joined: Sat Feb 08, 2014 4:18 pm
United States of America

Re: ATSC 3.0

Post by Lost Dog »

I'm not Elizabeth but maybe my answers will help development!
- does mythtv-setup recognize the HDHR as a HDHR?
Yes, it sees it as a standard HDHR with four tuners.
- can you configure the HDHR in mythtv-setup?
Yes, it sets up as a normal HDHR. The first two tuners are the ATSC 3.0 + ATSC 1.0 tuners and the second two are only ATSC 1.0.
- can you do a channel scan in mythtv-setup?
- does mythtv-setup find all the channels that the HDHR can find on its own, using the HDHR utilities/apps?
Yes, on all four tuners it can do the scan. On the first two tuners it can detect the ATSC 3.0 channels but they have the same virtual number as the ATSC 1.0. This causes problems (SiliconDust's solution for the hdhomerun_config_gui app is to append a 1 to the start of the virtual number to separate the ATSC 3.0 from 1.0).
- can you make recordings of ATSC 3.0 channels?
I've not been able to do this.
- can you make recordings of ATSC 3.0 channels on all tuners (i.e. more than 2) at the same time?
Not sure, but two (or more) ATSC1.0 can be recorded at once, even using the first two tuners.
- can you play back ATSC 3.0 recordings (this is more a HEVC/audio issue probably)?
I've captured ATSC 3.0 streams using the hdhomerun_config app and tried playing them in MythTV. My video card cannot handle HEVC so it's basically a slide show. Mainline FFMPEG does not have AC-4 support so there is no audio (a branch of FFMPEG does have AC-4 support but that is not used by MythTV).

I hope this helps!
User avatar
kmdewaal
Developer
Posts: 641
Joined: Wed Dec 07, 2016 8:01 pm
Netherlands

Re: ATSC 3.0

Post by kmdewaal »

Interesting!
Yes, on all four tuners it can do the scan. On the first two tuners it can detect the ATSC 3.0 channels but they have the same virtual number as the ATSC 1.0. This causes problems (SiliconDust's solution for the hdhomerun_config_gui app is to append a 1 to the start of the virtual number to separate the ATSC 3.0 from 1.0).
Maybe there are possibilities.
Can you make a channel scan with the ATSC 3.0 tuner with these options:

Code: Select all

mythtv-setup -v channel,chanscan,record,siparser --loglevel=debug --logpath=.
And also one with the ATSC 1.0 tuner with the same command?
This will give log files that are too big to post here but you can send them to me directly.
I think the first step is to figure out how to differentiate between the 1.0 and the 3.0 channels; maybe I can do it similar to how the HDHR app does it.
For this a listing (or screendump) of how the channels look in the HDHR app would also be useful.

Thanks,
Klaas.
Lost Dog
Junior
Posts: 36
Joined: Sat Feb 08, 2014 4:18 pm
United States of America

Re: ATSC 3.0

Post by Lost Dog »

kmdewaal wrote:
Wed Mar 31, 2021 8:20 am
Interesting!
Yes, on all four tuners it can do the scan. On the first two tuners it can detect the ATSC 3.0 channels but they have the same virtual number as the ATSC 1.0. This causes problems (SiliconDust's solution for the hdhomerun_config_gui app is to append a 1 to the start of the virtual number to separate the ATSC 3.0 from 1.0).
Maybe there are possibilities.
Can you make a channel scan with the ATSC 3.0 tuner with these options:

Code: Select all

mythtv-setup -v channel,chanscan,record,siparser --loglevel=debug --logpath=.
And also one with the ATSC 1.0 tuner with the same command?
This will give log files that are too big to post here but you can send them to me directly.
I think the first step is to figure out how to differentiate between the 1.0 and the 3.0 channels; maybe I can do it similar to how the HDHR app does it.
For this a listing (or screendump) of how the channels look in the HDHR app would also be useful.

Thanks,
Klaas.
Klaas,

Thanks for the help. Looks like I was incorrect an item. MythTV cannot recognize the ATSC3.0 stations during a scan. The mythtv-setup log attached was done using Tuner 0 which is the ATSC 3.0 tuner. I'm not sure how to specify which tuner to use for a scan so I did not get one with the ATSC 1.0 tuner (each time I tried selecting a different tuner it still defaulted to Tuner 0).

I've also included a file called hdhrscan.txt which is done from the hdhomerun_config application. The ATSC3.0 stations have a 1 appended to their virtual tuner numbers:

Code: Select all

SCANNING: 569000000 (us-bcast:30)
LOCK: atsc3 (ss=100 snq=100 seq=100)
PROGRAM 1: 149.1 KPDX
PROGRAM 2: 112.1 KPTV
PROGRAM 3: 108.1 KGW
PROGRAM 4: 110.1 KOPB

Code: Select all

SCANNING: 207000000 (us-bcast:12)
LOCK: 8vsb (ss=97 snq=100 seq=100)
TSID: 0x097D
PROGRAM 3: 12.1 FOX 12
PROGRAM 4: 12.2 COZI
PROGRAM 5: 12.3 LAFF
PROGRAM 6: 12.4 DABL
PROGRAM 7: 49.1 Fox12+
PROGRAM 8: 49.3 Bounce
In these two examples 149.1 KPDX is the ATSC 3.0 feed of 49.1 Fox12+. Same with112.1 KPTV and 12.1 FOX 12.

A mythtv scan of frequency 569000000 does not detect anything:

Code: Select all

2021-03-31 09:45:55.070787 I [79121/79158] Scanner channelscan/channelscan_sm.cpp:2151 (ScanTransport) - ChannelScanSM(1080B767): ScanTransport Tuning to ATSC Channel 30 mplexid(0)
2021-03-31 09:45:55.070804 I [79121/79158] Scanner recorders/hdhrchannel.cpp:172 (Tune) - HDHRChan[11](1080B767): Tuning to 8vsb:569000000
2021-03-31 09:45:55.071384 I [79121/79158] Scanner recorders/hdhrstreamhandler.cpp:519 (TuneChannel) - HDHRSH[11](1080B767): Tuning channel 8vsb:569000000 (was 8vsb:563000000)
2021-03-31 09:45:55.126326 I [79121/79158] Scanner recorders/dtvsignalmonitor.cpp:201 (SetChannel) - DTVSigMon[11](1080B767)::SetChannel(-1, -1): 
2021-03-31 09:45:55.126348 I [79121/79158] Scanner recorders/dtvsignalmonitor.cpp:233 (SetDVBService) - DTVSigMon[11](1080B767)::SetDVBService(transport_id: 0, network_id: 0, service_id: -1): 
2021-03-31 09:45:55.126355 D [79121/79158] Scanner recorders/signalmonitor.cpp:278 (Start) - SigMon[11](1080B767)::Start: begin
2021-03-31 09:45:55.126526 D [79121/79158] Scanner recorders/signalmonitor.cpp:286 (Start) - SigMon[11](1080B767)::Start: end
2021-03-31 09:45:55.129423 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.157844 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.186530 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.215581 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.243802 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.272517 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.300796 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.329151 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.358481 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.387431 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.415692 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.446460 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.480589 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.509255 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.537231 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.565329 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.593464 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.621854 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.650126 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.680549 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.708682 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.737057 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.770244 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.798328 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.826627 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.855019 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.883386 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.913536 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.941901 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:55.984011 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.012253 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.040627 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.070428 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.098721 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.127005 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.155433 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.183769 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.212902 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.242065 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.270387 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.298586 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.327564 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.355851 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.384259 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.412504 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.445210 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.473652 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.502011 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.532985 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.561590 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.589913 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.624457 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.652891 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.681303 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.713932 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.742026 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.770316 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.798426 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.826634 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.858264 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.886586 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.914634 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.942844 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.971124 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:56.999539 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.029577 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.058098 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.086387 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.114571 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.143061 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.171441 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.200058 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.229014 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.257109 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.285440 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.313559 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.342686 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.374589 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.403077 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.431799 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.462390 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.490695 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.518987 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.547853 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.575904 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.603989 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.634012 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.662339 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.690261 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.718421 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.746929 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.775272 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.803830 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.832793 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.860952 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.889298 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.922459 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.950790 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:57.979076 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:58.009240 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:58.037878 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:58.066375 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:58.094724 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:58.122995 D [79121/79216] SignalMonitor recorders/hdhrsignalmonitor.cpp:120 (UpdateValues) - HDHRSigMon[11](1080B767): Tuner status: '100:0:0'
2021-03-31 09:45:58.137712 I [79121/79158] Scanner channelscan/channelscan_sm.cpp:961 (UpdateChannelInfo) - ChannelScanSM(1080B767): transport_tune_complete: wait_until_complete 0
2021-03-31 09:45:58.137814 I [79121/79158] Scanner channelscan/channelscan_sm.cpp:1096 (UpdateChannelInfo) - ChannelScanSM(1080B767): ATSC Channel 30 -- Timed Out, no channels
2021-03-31 09:45:58.137840 I [79121/79158] Scanner recorders/hdhrsignalmonitor.cpp:73 (Stop) - HDHRSigMon[11](1080B767): Stop() -- begin
2021-03-31 09:45:58.137852 D [79121/79158] Scanner recorders/signalmonitor.cpp:294 (Stop) - SigMon[11](1080B767)::Stop: begin
2021-03-31 09:45:58.148700 D [79121/79158] Scanner recorders/signalmonitor.cpp:304 (Stop) - SigMon[11](1080B767)::Stop: end
2021-03-31 09:45:58.148735 I [79121/79158] Scanner recorders/streamhandler.cpp:82 (RemoveListener) - SH[11](1080B767): RemoveListener(0x560ec27a5208) -- begin
2021-03-31 09:45:58.148747 I [79121/79158] Scanner recorders/streamhandler.cpp:94 (RemoveListener) - SH[11](1080B767): RemoveListener(0x560ec27a5208) -- locked
2021-03-31 09:45:58.148761 D [79121/79158] Scanner recorders/streamhandler.cpp:155 (Stop) - SH[11](1080B767): Stopping
2021-03-31 09:45:58.148774 D [79121/79158] Scanner recorders/streamhandler.cpp:158 (Stop) - SH[11](1080B767): Stopped
2021-03-31 09:45:58.148785 I [79121/79158] Scanner recorders/streamhandler.cpp:111 (RemoveListener) - SH[11](1080B767): RemoveListener(0x560ec27a5208) -- end
2021-03-31 09:45:58.148796 I [79121/79158] Scanner recorders/hdhrsignalmonitor.cpp:79 (Stop) - HDHRSigMon[11](1080B767): Stop() -- end
Here is a shot of the hdhomerun app tuning a ATSC3.0 station and the VLC media info:
atsc3.png
atsc3.png (127.27 KiB) Viewed 11232 times
Let me know what else I can provide!

Thanks for the help,
Neil
Attachments
hdhrscan.txt
(6.2 KiB) Downloaded 199 times
mythtv-setup.20210331164254.79121.log.zip
(83.72 KiB) Downloaded 197 times
User avatar
kmdewaal
Developer
Posts: 641
Joined: Wed Dec 07, 2016 8:01 pm
Netherlands

Re: ATSC 3.0

Post by kmdewaal »

Again interesting! Apparently we do not send yet the correct strings but I have an idea on how to move forward.

Question: can you compile the latest master from source? In that case I can make patches that you can then apply and test.
N.B. There is a Wiki page for that https://www.mythtv.org/wiki/Build_from_Source

Also, get you post the info from the hdhomerun_config app? On my DVB-C box I can do this:
$ hdhomerun_config 1410F45C get help
Can you do this for your box and then also do the "get help" for all the items on which you can get help?

Thanks,
Klaas.
Lost Dog
Junior
Posts: 36
Joined: Sat Feb 08, 2014 4:18 pm
United States of America

Re: ATSC 3.0

Post by Lost Dog »

kmdewaal wrote:
Wed Mar 31, 2021 9:22 pm
Again interesting! Apparently we do not send yet the correct strings but I have an idea on how to move forward.

Question: can you compile the latest master from source? In that case I can make patches that you can then apply and test.
N.B. There is a Wiki page for that https://www.mythtv.org/wiki/Build_from_Source

Also, get you post the info from the hdhomerun_config app? On my DVB-C box I can do this:
$ hdhomerun_config 1410F45C get help
Can you do this for your box and then also do the "get help" for all the items on which you can get help?

Thanks,
Klaas.
No problem! I compile my v31.0 build already so building master shouldn't be an issue. I'll do it on my desktop system that has the hardware to play HEVC. Is it possible to compile against a different ffmpeg source? I've got one I patched to add ac-4 support (which is the audio stream of ATSC3.0).

As for the hdhomerun_config:

Code: Select all

hdhomerun_config 1080B767 get help
Supported configuration options:
/lineup/scan
/sys/copyright
/sys/debug
/sys/features
/sys/hwmodel
/sys/model
/sys/restart <resource>
/sys/version
/tuner<n>/channel <modulation>:<freq|ch>
/tuner<n>/channelmap <channelmap>
/tuner<n>/debug
/tuner<n>/filter "0x<nnnn>-0x<nnnn> [...]"
/tuner<n>/lockkey
/tuner<n>/program <program number>
/tuner<n>/status
/tuner<n>/plpinfo
/tuner<n>/streaminfo
/tuner<n>/target <ip>:<port>
/tuner<n>/vchannel <vchannel>

Code: Select all

lostdog@desktop:~/Desktop$ hdhomerun_config 1080B767 get /lineup/scan
state=failed progress=100% found=76
lostdog@desktop:~/Desktop$ hdhomerun_config 1080B767 get /sys/copyright
Copyright © 2005-2021 Silicondust USA Inc. <www.silicondust.com>. All rights reserved.
lostdog@desktop:~/Desktop$ hdhomerun_config 1080B767 get /sys/debug
mem: ddr=256 nbk=1 dmk=319 fet=0
loop: pkt=0
t0: pt=12 cal=92
t1: pt=12 cal=92
t2: pt=12 cal=91
t3: pt=12 cal=92
eth: link=100f

lostdog@desktop:~/Desktop$ hdhomerun_config 1080B767 get /sys/features
channelmap: us-bcast us-cable us-hrc us-irc kr-bcast kr-cable
modulation: atsc3 8vsb qam256 qam64
auto-modulation: auto auto6t auto6c qam

lostdog@desktop:~/Desktop$ hdhomerun_config 1080B767 get /sys/hwmodel
HDHR5-4K
lostdog@desktop:~/Desktop$ hdhomerun_config 1080B767 get /sys/model
hdhomerun5_atsc3
lostdog@desktop:~/Desktop$ hdhomerun_config 1080B767 get /sys/version
20210224
Lost Dog
Junior
Posts: 36
Joined: Sat Feb 08, 2014 4:18 pm
United States of America

Re: ATSC 3.0

Post by Lost Dog »

kmdewaal wrote:
Wed Mar 31, 2021 9:22 pm
Question: can you compile the latest master from source? In that case I can make patches that you can then apply and test.
N.B. There is a Wiki page for that https://www.mythtv.org/wiki/Build_from_Source

Thanks,
Klaas.
Hi Klaas,

I've got master up and running! Let me know once you have patches and I'll give them a test. If you need any logs from master let me know and I'll run them.

Thanks!
Neil
User avatar
kmdewaal
Developer
Posts: 641
Joined: Wed Dec 07, 2016 8:01 pm
Netherlands

Re: ATSC 3.0

Post by kmdewaal »

Hi Neil,

Find attached patch 20210402-hdhr-atsc3-00.patch which can be applied to a recent master.
This is just for testing; it forces the modulation method from 8vsb to atsc3 for all HDHomeRun tuning attempts. This means you will not scan any of the atsc1.0 channels but with a bit of luck this gives us the atsc3.0 channels. A mythtv-setup scan log with full debug, as done the last time, is perfect.

FYI, the idea in this is that I did read somewhere that the HDHomeRun box does convert whatever it receives with ATSC3.0 to the standard transport stream format that we all know and love. That your box does work with the old ATSC channels gives us the hope that the ATSC3.0 channels will appear in a similar format. In which case mythtv-setup can recognize the channels.
If this test gets us the ATSC3.0 channels I will go make a more complete implementation in which also the 8vsb channels still work.
In that case you have a HDHomeRun box that still can use only two tuners because at this moment we cannot distinguish between the four tuners of the box; they get allocated dynamically so that they can be shared across the household. Previously, before mythtv v30, we did address the individual tuners but this precludes sharing across the household. We could revert to that but maybe SiliconDust comes up with something clever.

Next step is the audio decoding but we cross that bridge when we meet it.

Thanks,
Klaas.
Attachments
20210402-hdhr-atsc3-00.patch
(598 Bytes) Downloaded 202 times
Lost Dog
Junior
Posts: 36
Joined: Sat Feb 08, 2014 4:18 pm
United States of America

Re: ATSC 3.0

Post by Lost Dog »

kmdewaal wrote:
Fri Apr 02, 2021 5:09 pm
Hi Neil,

Find attached patch 20210402-hdhr-atsc3-00.patch which can be applied to a recent master.
This is just for testing; it forces the modulation method from 8vsb to atsc3 for all HDHomeRun tuning attempts. This means you will not scan any of the atsc1.0 channels but with a bit of luck this gives us the atsc3.0 channels. A mythtv-setup scan log with full debug, as done the last time, is perfect.

FYI, the idea in this is that I did read somewhere that the HDHomeRun box does convert whatever it receives with ATSC3.0 to the standard transport stream format that we all know and love. That your box does work with the old ATSC channels gives us the hope that the ATSC3.0 channels will appear in a similar format. In which case mythtv-setup can recognize the channels.
If this test gets us the ATSC3.0 channels I will go make a more complete implementation in which also the 8vsb channels still work.
In that case you have a HDHomeRun box that still can use only two tuners because at this moment we cannot distinguish between the four tuners of the box; they get allocated dynamically so that they can be shared across the household. Previously, before mythtv v30, we did address the individual tuners but this precludes sharing across the household. We could revert to that but maybe SiliconDust comes up with something clever.

Next step is the audio decoding but we cross that bridge when we meet it.

Thanks,
Klaas.
Hi Klaas,

Thank you for putting together the patch. It applied cleanly and I ran a scan. Log attached.

The ATSC 3.0 should have been at ATSC Channel 30 and 33.

Thanks!

Neil
Attachments
mythtv-setup.20210403005348.45479.log.zip
(48.48 KiB) Downloaded 204 times
User avatar
kmdewaal
Developer
Posts: 641
Joined: Wed Dec 07, 2016 8:01 pm
Netherlands

Re: ATSC 3.0

Post by kmdewaal »

The log shows that the "atsc3:<frequency>" command does indeed make a difference, it seems to go in lock now.
Next step is then to start the streamhandler (the "RunTS" line) but either no data is received or the data cannot be parsed.
To figure that out there is a new patch attached, 20210403-hdhr-atsc3-01.patch. Can again be applied to a clean source (i.e. first remove the old patch).
This patch has additional debug that will show if there is data coming out of the box.
Again please the mythtv-setup scan with full debug, as before.

BTW, it could just be that the "low-level" libhdhomerun interface that we use now can not be used for the ATSC3.0 signal. The alternative is, as I understand it, using the HTTP interface. Maybe we should ask SiliconDust if using libhhomerun is possible.

Thanks,
Klaas.
Lost Dog
Junior
Posts: 36
Joined: Sat Feb 08, 2014 4:18 pm
United States of America

Re: ATSC 3.0

Post by Lost Dog »

kmdewaal wrote:
Sat Apr 03, 2021 9:35 pm
The log shows that the "atsc3:<frequency>" command does indeed make a difference, it seems to go in lock now.
Next step is then to start the streamhandler (the "RunTS" line) but either no data is received or the data cannot be parsed.
To figure that out there is a new patch attached, 20210403-hdhr-atsc3-01.patch. Can again be applied to a clean source (i.e. first remove the old patch).
This patch has additional debug that will show if there is data coming out of the box.
Again please the mythtv-setup scan with full debug, as before.

BTW, it could just be that the "low-level" libhdhomerun interface that we use now can not be used for the ATSC3.0 signal. The alternative is, as I understand it, using the HTTP interface. Maybe we should ask SiliconDust if using libhhomerun is possible.

Thanks,
Klaas.
Hi Klaas,

No patch was included in your post. Could you please attach and I'll test?

I frequent the SiliconDust forum on the ATSC 3.0 section so if there are any questions you'd like me to ask I can post there.

Thanks much for all the help!

Neil
User avatar
kmdewaal
Developer
Posts: 641
Joined: Wed Dec 07, 2016 8:01 pm
Netherlands

Re: ATSC 3.0

Post by kmdewaal »

And now also the patch.....
Attachments
20210403-hdhr-atsc3-01.patch
(3.05 KiB) Downloaded 215 times
User avatar
kmdewaal
Developer
Posts: 641
Joined: Wed Dec 07, 2016 8:01 pm
Netherlands

Re: ATSC 3.0

Post by kmdewaal »

Hi Neil,

Can you please ask the following question to the HDHR folks?
In MythTV we support all HDHomeRun boxes using the libhdhomerun API. We want to support the new 4K box so that we can receive the programs in the ATSC3.0 streams. Is there documentation or a programming example on how to achieve this?
Thanks,
Klaas.
Post Reply