ATSC 3.0: Washington, DC / Baltimore, MD

ATSC 3.0 Forum
bobchase
Posts: 66
Joined: Sun Nov 22, 2020 12:25 pm
Device ID: 10810736
x 10

Re: ATSC 3.0: Washington, DC / Baltimore, MD

Post by bobchase »

Nick

I've emailed Triveni as to why they don't include it in the L1 Detail once I enumerate it in the GuideBuilder's transport section. They don't even bring out the L1 BSID field in their StreamScope. Once I get their answer, I'll get with Enensys about their BSID too. Ch27 is on the air with the complete Enensys setup and so I/we have been using the Triveni GuideBuilder, RouteBuilder, Gateway for testing on 35 and, while we also have Enensys available, why duplicate efforts. By the way, 27 is broadcasting a BSID of 202 in their SLT, so Enensys is behaving the same as Triveni in that regards. Interesting times....

Bob

nickk
Silicondust
Posts: 16989
Joined: Tue Jan 13, 2004 9:39 am
x 109

Re: ATSC 3.0: Washington, DC / Baltimore, MD

Post by nickk »

Channel 27 and 35 are slightly different at the L1 detail level...

Channel 27 is sending a BSID (L1 detail version 1) however the value is 0x0000.

Channel 35 isn't sending a BSID field at all (L1 detail version 0).

I will take a look at the SLT tomorrow.

Nick

Trip
Posts: 56
Joined: Sat Aug 07, 2010 6:49 am
Location: Alexandria, VA, USA
x 8
Contact:

Re: ATSC 3.0: Washington, DC / Baltimore, MD

Post by Trip »

It seems like you should (in theory) be able to put the BSID in once and have it populate everywhere that the standard wants the BSID to be, including the L1 detail. I hope the companies get that sorted out.

- Trip

Trip
Posts: 56
Joined: Sat Aug 07, 2010 6:49 am
Location: Alexandria, VA, USA
x 8
Contact:

Re: ATSC 3.0: Washington, DC / Baltimore, MD

Post by Trip »

WNUV is up and running in Baltimore.

trip@trip-G752VY:~$ hdhomerun_config 10805D4A get /tuner0/plpinfo
0: sfi=0 mod=qam16 cod=11/15 layer=core ti=none lls=1
1: sfi=0 mod=qam64 cod=11/15 layer=core ti=none lls=0
2: sfi=1 mod=qam256 cod=11/15 layer=core ti=none lls=0

WNUV is on PLP0, WBFF on PLP1, and the rest on PLP2.

- Trip

bobchase
Posts: 66
Joined: Sun Nov 22, 2020 12:25 pm
Device ID: 10810736
x 10

Re: ATSC 3.0: Washington, DC / Baltimore, MD

Post by bobchase »

Trip wrote: Thu Jun 24, 2021 2:37 am It seems like you should (in theory) be able to put the BSID in once and have it populate everywhere that the standard wants the BSID to be, including the L1 detail. I hope the companies get that sorted out.

- Trip
Trip & Nick,
The L1 Detail was an late add to the spec that got missed by at least two manufacturers of signaling equipment. Talked to Triveni and they will get it done for both the GuideBuilder and the StreamScope products for the next release. Still waiting for France to answer but by the time I sent the email they would have all gone home.

jsmar
Posts: 33
Joined: Wed Aug 13, 2008 1:06 am
x 1

Re: ATSC 3.0: Washington, DC / Baltimore, MD

Post by jsmar »

Trip wrote: Thu Jun 24, 2021 8:01 am WNUV is up and running in Baltimore.

trip@trip-G752VY:~$ hdhomerun_config 10805D4A get /tuner0/plpinfo
0: sfi=0 mod=qam16 cod=11/15 layer=core ti=none lls=1
1: sfi=0 mod=qam64 cod=11/15 layer=core ti=none lls=0
2: sfi=1 mod=qam256 cod=11/15 layer=core ti=none lls=0

WNUV is on PLP0, WBFF on PLP1, and the rest on PLP2.

- Trip
Random question that probably only Nick can answer. The PLP numbers here are one less than the PLP numbers I find in the LMT. Are the numbers here just a sequential count or is it LMT number minus 1? i.e. if for some reason a station numbered the PLP's with a gap, i.e. 1, 2 and 4, would "get /tuner0/plpinfo" show 0, 1 and 2, or 0, 1 and 3?

nickk
Silicondust
Posts: 16989
Joined: Tue Jan 13, 2004 9:39 am
x 109

Re: ATSC 3.0: Washington, DC / Baltimore, MD

Post by nickk »

jsmar wrote: Thu Jun 24, 2021 2:31 pm
Trip wrote: Thu Jun 24, 2021 8:01 am WNUV is up and running in Baltimore.

trip@trip-G752VY:~$ hdhomerun_config 10805D4A get /tuner0/plpinfo
0: sfi=0 mod=qam16 cod=11/15 layer=core ti=none lls=1
1: sfi=0 mod=qam64 cod=11/15 layer=core ti=none lls=0
2: sfi=1 mod=qam256 cod=11/15 layer=core ti=none lls=0

WNUV is on PLP0, WBFF on PLP1, and the rest on PLP2.

- Trip
Random question that probably only Nick can answer. The PLP numbers here are one less than the PLP numbers I find in the LMT. Are the numbers here just a sequential count or is it LMT number minus 1? i.e. if for some reason a station numbered the PLP's with a gap, i.e. 1, 2 and 4, would "get /tuner0/plpinfo" show 0, 1 and 2, or 0, 1 and 3?
The first number is the PLP ID specified in the L1 detail. It is whatever is sent by the broadcaster. Odd that the LMT uses a +1 number.

Trip
Posts: 56
Joined: Sat Aug 07, 2010 6:49 am
Location: Alexandria, VA, USA
x 8
Contact:

Re: ATSC 3.0: Washington, DC / Baltimore, MD

Post by Trip »

I had a weird issue, which I've now worked around. I was trying to dump the WNUV feed out and it wasn't working. WIAV-CD did work.

Code: Select all

trip@trip-G752VY:~$ wget "http://10805D4A.local:5004/auto/ch30p0?duration=25&format=dbg" -O DC-ch30p0.dbg
--2021-06-24 20:30:33--  http://10805d4a.local:5004/auto/ch30p0?duration=25&format=dbg
Resolving 10805d4a.local (10805d4a.local)... 192.168.50.48
Connecting to 10805d4a.local (10805d4a.local)|192.168.50.48|:5004... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/octet-stream]
Saving to: ‘DC-ch30p0.dbg’

DC-ch30p0.dbg                    [                         <=>                 ]  10.10M   433KB/s    in 25s     

2021-06-24 20:30:59 (414 KB/s) - ‘DC-ch30p0.dbg’ saved [10587920]

trip@trip-G752VY:~$ wget "http://10805D4A.local:5004/auto/ch25p0?duration=25&format=dbg" -O Baltimore-ch25p0.dbg
--2021-06-24 20:32:07--  http://10805d4a.local:5004/auto/ch25p0?duration=25&format=dbg
Resolving 10805d4a.local (10805d4a.local)... 192.168.50.48
Connecting to 10805d4a.local (10805d4a.local)|192.168.50.48|:5004... connected.
HTTP request sent, awaiting response... 503 Service Unavailable
2021-06-24 20:32:07 ERROR 503: Service Unavailable.

trip@trip-G752VY:~$
Looking at the log, I was seeing this:

Code: Select all

20210625-00:30:33 Tuner: tuner0 tuning atsc3:569MHz
20210625-00:30:33 Tuner: tuner0 streaming http to 192.168.50.77:42044
20210625-00:30:58 Tuner: tuner0 http stream ended (requested time reached)
20210625-00:32:07 Tuner: invalid channel 8vsb:539MHz
20210625-00:32:07 HTTP: rejecting request from 192.168.50.77 - tune failed
I enabled diagnostics briefly, but have now turned them off again. It seems that the trick was to go to Channel Lineup and do Detect Channels, which admittedly is something I don't do very much as I do everything via command line, by direct tuning in hdhomerun_config_gui, or direct tuning through software like TSReader. Strange that even though I explicitly asked for PLPs and whatnot in the wget request, it still tried to tune 8vsb anyway.

- Trip

monroef
Posts: 1
Joined: Fri Feb 22, 2019 10:39 am

Re: ATSC 3.0: Washington, DC / Baltimore, MD

Post by monroef »

From Balto Media on Facebook:

"The Nextgen TV transition applications have started in DC. WTTG FOX 5 filed today. They will be on WHUT 32 on Aug. 13, most likely in 720p resolution but with HDR and WCG and hopefully Dolby Atmos sound."

jonw747
Posts: 6
Joined: Wed Oct 21, 2020 2:28 pm
x 1

Re: ATSC 3.0: Washington, DC / Baltimore, MD

Post by jonw747 »

I'm seeing some new HEVC channels in the DC area, here's what I see:

102.1 WMAR
111.1 WBAL
122.1 WMPT
145.1 WBFF
154.1 WNUV
158.1 WIAV
158.3 WIAVMMT

The two WIAV stations have been live for a while. At the moment 154.1 is broadcasting, but last night I think a couple of others were too.

Thunderthud
Posts: 526
Joined: Sun Apr 12, 2015 6:59 am
Device ID: 1080B565, 1322B8A6, 13257C3D, 1041CFDB, 10514020, 101886A, 10120815
Location: Virginia
x 4

Re: ATSC 3.0: Washington, DC / Baltimore, MD

Post by Thunderthud »

I see them too, but no video on any except wiav. Northern Virginia

kyl416
Posts: 250
Joined: Wed Sep 17, 2014 12:09 pm
Device ID: 1080DB11
Location: Tobyhanna, PA
x 42
Contact:

Re: ATSC 3.0: Washington, DC / Baltimore, MD

Post by kyl416 »

Everything except for WIAV are the Baltimore stations. If you're outside of the usual coverage area of the Baltimore stations and don't get them now, it was likely atmospheric boost pulling them in during an overnight autoscan.

DC's own ATSC 3.0 service using WHUT's RF 32 signal is slated to go live on August 13th. That will carry WHUT, WJLA, WTTG, WRC and WUSA:
https://www.whut.org/nextgentv


On a side note, they really should prevent autoscans from taking place overnight and mornings, that's perhaps the worst time to do an autoscan since that's when the atmospheric boost conditions are most common, and if the conditions are strong enough to pick up stations several DMAs away, it can lead to virtual number conflicts, especially if a distant station has a higher resolution than more local one. Like here 2.1 WCBS (1080i) frequently comes in during autoscans, which ends up overriding 2.1 WDPN (720p) in my channel list, so I have to do a manual scan when condtions return to "normal" to get rid of WCBS so I can watch MeTV in HD.

jonw747
Posts: 6
Joined: Wed Oct 21, 2020 2:28 pm
x 1

Re: ATSC 3.0: Washington, DC / Baltimore, MD

Post by jonw747 »

kyl416 wrote: Tue Jul 20, 2021 11:06 am Everything except for WIAV are the Baltimore stations. If you're outside of the usual coverage area of the Baltimore stations and don't get them now, it was likely atmospheric boost pulling them in during an overnight autoscan. (On a side note, they really should prevent autoscans from taking place overnight and mornings, that's perhaps the worst time to do an autoscan since that's when the atmospheric boost conditions are most common)

DC's own ATSC 3.0 service using WHUT's RF 32 signal is slated to go live on August 13th. That will carry WHUT, WJLA, WTTG, WRC and WUSA:
https://www.whut.org/nextgentv
Makes sense. Any idea where the ATSC3 Baltimore tower is located? I normally do not receive Baltimore stations this well, especially since the switch to Digital unless I point my antenna and I disconnected the rotor controller years ago. It's CM3021 bowtie in the attic.

fwiw, 154.1 is coming in pretty well right now with minor macro blocking, and yes it is overcast.

kyl416
Posts: 250
Joined: Wed Sep 17, 2014 12:09 pm
Device ID: 1080DB11
Location: Tobyhanna, PA
x 42
Contact:

Re: ATSC 3.0: Washington, DC / Baltimore, MD

Post by kyl416 »

The Baltimore ATSC 3.0 signals come from WNUV's RF 25 signal:
https://www.rabbitears.info/contour.php ... te=1&map=Y

154.1 WNUV is on the more robust QAM 16 PLP, so it's easier to decode in weak reception areas. 145.1 WBFF is on the QAM 64 PLP, while the rest of the channels are on the QAM 256 PLP which has a coverage area similar to the ATSC 1.0 signals.

joblo
Posts: 25
Joined: Fri Mar 05, 2021 2:45 am
x 5

Re: ATSC 3.0: Washington, DC / Baltimore, MD

Post by joblo »

kyl416 wrote: Tue Jul 20, 2021 11:06 am On a side note, they really should prevent autoscans from taking place overnight and mornings
Autoscans?!? What autoscans? I don't think my 4K has ever changed the channel list without my explicitly requesting a rescan. Is that an HDHR thing or an app thing? And why can't you just disable it, and if so, why don't you? I would never want something like that to happen, unless I could specify the time, for exactly the reason you stated, with which I agree 100%.

Post Reply