Las Vegas - Channel 29 or Channel 1?

[fri1038sd]

Is there a way for me to reproduce your results on ATSC 3.0 channels that report no video data in my area if I don’t have an Nvidia Shield? I have a FireTV 4K for the HD Homerun App. I also run HD Homerun and Channels on iOS and iPadOS.

On which channels are you getting 'no video data'?

EDIT: I think you are in the Balt/Wash area from previous posts. I can confirm WNUV ATSC 3.0 on RF25 is having a problem. I see 'no video data' on all five "subchannels" there when trying to view in the Windows or Onn GoogleTV HDHR app - even the DRM ones. While watching hdhomerun_config_gui, when I try to watch any subchannel on WNUV 3.0 in the app, I see an attempt to tune on the correct RF channel and PLP, then the no video message, then hdhomerun_config_gui falls back to channel 0. So blame the broadcaster for that ... lots of changes to WNUV lately. I can watch, with no audio, in VLC. Additionally 154.1 WNUV has a streaming problem with lots of tiling and breakups as seen in VLC - the ATSC 1.0 stream is fine. Broadcasts on WHUT 3.0 RF33 in DC are working properly.

Maybe Sinclair has a bad configuration in Las Vegas, too.

[kingcoldcuts]

...
Now what?
...

Funky.

Using the View button in config_gui to tune the channel, instead of the Shield and App, do you see the odd PLP selection behavior?

Probably not relevant, but I wonder if this station is configured as LDM. Look for "layer=enhanced" and "ti=cti" in the PLP parameters shown in config_gui. If it's like WIAV-CD in DC, both PLPs need to be tuned in to view a channel.

Here's a video: https://1drv.ms/v/c/844f4e8298117e6b/EW ... w?e=diT4IW

When I click "View" within config_gui the channel has successfully tuned each time I have tried. It opts for only qam256, and it works. Unfortunately, I still get No Data errors through the app on any device. Any ideas?

Thanks!

KCC

[kingcoldcuts]

Is there a way for me to reproduce your results on ATSC 3.0 channels that report no video data in my area if I don’t have an Nvidia Shield? I have a FireTV 4K for the HD Homerun App. I also run HD Homerun and Channels on iOS and iPadOS.

It happens to me on all devices, including Fire TV, iOS, etc.

I have Windows computers, too, though. I think hdhomerun_config_gui is only available on Windows. It is a useful tool for seeing added data related to your tuner. It is what I am using in the video I linked. If you have access to Windows, install the HDHomerun software, navigate to C:\Program Files\Silicondust\HDHomeRun, and double click hdhomerun_config_gui.

I'm not sure what else to recommend if you do not have access to Windows.

KCC

[fri1038sd]

This is looking just like WNUV in Baltimore, including the 0-100% symbol quality bouncing every second on PLP0. I updated my post a couple back on what I see. It's normal to see 'no data' in config_gui until you tune something on the necessary PLP, then it should go blank or say 'encrypted' in the Program pull-down menu. Something in the broadcast is goofed up I expect. I'll ask on AVSForum if anyone in the area using a non-hdhomerun tuner is having problems.

[fri1038sd]

I ran through the failing tuning scenario with diags on between 1245 and 1255 eastern if that is of any use. First in the Windows app, then on the Flex4k.

dev id: 10A22F05

A Hisense TV owner on AVSForum says all is ok with WNUV 3.0.

PS. I am not worried about the PLP0 symbol quality bouncing because there is no TV on it in WNUV's case. A data stream probably.

--

EDIT: one more data point. hdhomerun_config_gui -> View -> VLC will tune in a channel on WNUV 3.0. But if you try to view in VLC via View -> Playlist -> uPnP, it gets the same sort of timeout/no video data the hdhr app is probably seeing. Sorry to derail the original question.

From VLC:

http debug: incoming response: HTTP/1.1 503 Service Unavailable Server: HDHomeRun/1.0 Connection: close Content-Length: 0 Cache-Control: no-cache X-HDHomeRun-Error: 807 No Video Data
access error: HTTP 503 error
http debug: connection failed
http debug: querying proxy for http://10.0.0.7:5004/auto/v122.1
http debug: no proxy
http debug: http: server='10.0.0.7' port=5004 file='/auto/v122.1'
main debug: net: connecting to 10.0.0.7 port 5004
main debug: connection succeeded (socket = 1860)
http debug: sending request: GET /auto/v122.1 HTTP/1.0 Host: 10.0.0.7:5004 User-Agent: VLC/3.0.20 LibVLC/3.0.20 Icy-MetaData: 1
http debug: HTTP answer code 503
http error: error: HTTP/1.1 503 Service Unavailable
main debug: no access modules matched
main debug: dead input

[danieljlevine]

On which channels are you getting 'no video data'?

EDIT: I think you are in the Balt/Wash area from previous posts. I can confirm WNUV ATSC 3.0 on RF25 is having a problem. I see 'no video data' on all five "subchannels" there when trying to view in the Windows or Onn GoogleTV HDHR app - even the DRM ones. While watching hdhomerun_config_gui, when I try to watch any subchannel on WNUV 3.0 in the app, I see an attempt to tune on the correct RF channel and PLP, then the no video message, then hdhomerun_config_gui falls back to channel 0. So blame the broadcaster for that ... lots of changes to WNUV lately. I can watch, with no audio, in VLC. Additionally 154.1 WNUV has a streaming problem with lots of tiling and breakups as seen in VLC - the ATSC 1.0 stream is fine. Broadcasts on WHUT 3.0 RF33 in DC are working properly.

Maybe Sinclair has a bad configuration in Las Vegas, too.

Curious 154.1 came in clear for me just now. 154.31 didn’t come in. It says Demo.

158.1 and 158.5 have me the no video data.

[fri1038sd]

Curious 154.1 came in clear for me just now. 154.31 didn’t come in. It says Demo.

158.1 and 158.5 have me the no video data.

WNUV's 154.31 Demo is not currently being broadcast. I'd suggest doing a fresh channel scan but that might break 154.1 and other Baltimore ATSC 3.0 channels, which you don't mention, that are all not working for me in the hdhr apps.

Can't comment on 158.x which is WIAV-CD as my reception is too weak to tune them in currently.

[danieljlevine]

I believe the only Baltimore ATSC 3.0 channels that aren’t DRM are Fox 145.x and WMPT.

[fri1038sd]

I believe the only Baltimore ATSC 3.0 channels that aren’t DRM are Fox 145.x and WMPT.

WMAR 102.1 and WBAL 111.1 are DRM. WMPT 122.1, WBFF 145.1, WNUV 154.1 are not.

What are we talking about, again?

[kingcoldcuts]

I ran through the failing tuning scenario with diags on between 1245 and 1255 eastern if that is of any use. First in the Windows app, then on the Flex4k.

dev id: 10A22F05

A Hisense TV owner on AVSForum says all is ok with WNUV 3.0.

PS. I am not worried about the PLP0 symbol quality bouncing because there is no TV on it in WNUV's case. A data stream probably.

--

EDIT: one more data point. hdhomerun_config_gui -> View -> VLC will tune in a channel on WNUV 3.0. But if you try to view in VLC via View -> Playlist -> uPnP, it gets the same sort of timeout/no video data the hdhr app is probably seeing. Sorry to derail the original question.

From VLC:

http debug: incoming response: HTTP/1.1 503 Service Unavailable Server: HDHomeRun/1.0 Connection: close Content-Length: 0 Cache-Control: no-cache X-HDHomeRun-Error: 807 No Video Data
access error: HTTP 503 error
http debug: connection failed
http debug: querying proxy for http://10.0.0.7:5004/auto/v122.1
http debug: no proxy
http debug: http: server='10.0.0.7' port=5004 file='/auto/v122.1'
main debug: net: connecting to 10.0.0.7 port 5004
main debug: connection succeeded (socket = 1860)
http debug: sending request: GET /auto/v122.1 HTTP/1.0 Host: 10.0.0.7:5004 User-Agent: VLC/3.0.20 LibVLC/3.0.20 Icy-MetaData: 1
http debug: HTTP answer code 503
http error: error: HTTP/1.1 503 Service Unavailable
main debug: no access modules matched
main debug: dead input

Great point! Back on topic...

This is the second time one of us has sent diagnostic data. Would be great to know someone at SiliconDust is taking a look. Or perhaps we should open a support ticket?

Thanks!

KCC

[fri1038sd]

Was looking at WNUV 3.0 again just now. Confirmed the no video data issue in VLC (View->Playlist) and the HDHR App. Did a fresh channel scan via the Flex4K web interface. Now VLC and the app are working as expected. Guessing something in the tuner's memory was out dated, which is why hdhomerun_config_gui -> View was working and the other methods didn't. Should have tried that earlier.

Enough of Baltimore. Back to Vegas.

[kingcoldcuts]

I see someone made a post in the "Encryption" thread describing identical issues in Denver. I also see an offer to assist if they post in a new topic.

How about here? Can someone help me out in Las Vegas?

Thanks!

KCC