Las Vegas - Channel 29 or Channel 1?

[jasonl]

The first link isn't accessible, but the second one is.

We temporarily turned on the dev features on your HDHomeRun so it will report the signal quality in dB instead of %. Can you please reboot your HDHomeRun and wait about 5 minutes for it to pick that up then check plp1 again and see what the signal quality shows as now? No need for a picture or video, just text is fine. qam256 11/15 is definitely going to require higher SNR to receive but knowing the actual number will be useful for comparison.

[kingcoldcuts]

Awesome. Thanks.

I updated the link to the first video. Hopefully you can access it now. Everything in the first video is exactly the same, except the Signal Quality on PLP1 was 100%, rock solid.

Current Readings:

PLP1

Signal Strength - -43dBm
Signal Quality - 23.8dB to 24.9dB

Again, none of the parameters for PLP1 have changed. Only the Signal Quality.

Thanks again!

[jasonl]

The first video is still not accessible.

[kingcoldcuts]

Let's try this one?

Screen Recording - 2025-03-11 - Config GUI - NW LV

[jasonl]

That one works. That SNR on an ATSC 1.0 broadcast would be about 80% signal quality, so it is definitely lower than what you're getting on the other major station. I sent a PM to Stryker7314 asking if they're also seeing lower quality, as that would at least rule out something specific with your HDHomeRun device.

[kingcoldcuts]

Symbol quality is basically a ratio of uncorrupted packets vs total packets. If there isn't anything being transmitted on the PLP except LLS data, then there won't be any packets most of the time, and thus it will mostly sit at 0% except for spikes to 100% when the LLS comes in.

Is there a way to tell the Flex 4K to stop trying to select that PLP then?

[kingcoldcuts]

That one works. That SNR on an ATSC 1.0 broadcast would be about 80% signal quality, so it is definitely lower than what you're getting on the other major station. I sent a PM to Stryker7314 asking if they're also seeing lower quality, as that would at least rule out something specific with your HDHomeRun device.

Off-topic, but not sure where else to ask...

Are PMs enabled for User to User interaction? I have tried to send PMs this week but they remain in my Outbox.

Thanks!

[signcarver]

They remain on outbox until opened.

As for plp, for most apps that will always be based on scan and I thought that question was answered aa being a bug with the adjacent channel which if that is the issue will require new firmware.

[kingcoldcuts]

They remain on outbox until opened.

As for plp, for most apps that will always be based on scan and I thought that question was answered aa being a bug with the adjacent channel which if that is the issue will require new firmware.

I've only tested it with HDHR apps, and unfortunately this predates the channel scan issue. Channel 28 only recently started broadcasting ATSC 3, but I've been having issues with channel 29 defaulting to PLP0 for almost 2 years. The issue with channel 28 is/was something different. Only appeared when 28 went live in March (?). It's notable that the PLPs have been changed on 28, and no longer appear to interfere with the HDHR.

Thanks for answering about the Outbox! That's good to know. Like an incognito "read-receipt"!

[nickk]

Beta firmware is out to fix this issue:
https://bsky.app/profile/silicondust.co ... hc2tab722r

[kingcoldcuts]

Beta firmware is out to fix this issue:
https://bsky.app/profile/silicondust.co ... hc2tab722r

Thanks! I think the MacOS installer is for 20250130beta1 though? I can run the Windows version in a VM if that link is updated?

[jasonl]

Try https://download.silicondust.com/hdhome ... 5beta1.dmg . Sometimes it takes some time for the caching to sort itself out on the redirect link.

[kingcoldcuts]

Try https://download.silicondust.com/hdhome ... 5beta1.dmg . Sometimes it takes some time for the caching to sort itself out on the redirect link.

Appreciate that! The HDHR Flex 4k is now on the new firmware. Unfortunately, I am still experiencing the issue with low Signal Quality. Today it is below the threshold, and I am unable to tune anything on channel 29. The stuff on 28 looks good though! I have sent another batch of diagnostic data for Device ID: 10A64085

[jasonl]

The signal quality is low because the signal quality is low. That's not a firmware issue, that's a reception issue. I'm not sure why it's low, which is why I was hoping to get some corroboration from someone else in the area to see if it has also changed for them, since a change in the broadcast is the most likely explanation for why that one dropped significantly but nothing else has.

The firmware fix is for a separate issue where it was picking up the wrong frequency for some channels with multiple PLPs when there are 2 adjacent ATSC 3.0 channels (it was thinking the channels carried on RF 29 were actually on RF 28).

[kingcoldcuts]

The signal quality is low because the signal quality is low. That's not a firmware issue, that's a reception issue. I'm not sure why it's low, which is why I was hoping to get some corroboration from someone else in the area to see if it has also changed for them, since a change in the broadcast is the most likely explanation for why that one dropped significantly but nothing else has.

The firmware fix is for a separate issue where it was picking up the wrong frequency for some channels with multiple PLPs when there are 2 adjacent ATSC 3.0 channels (it was thinking the channels carried on RF 29 were actually on RF 28).

Cool.

Regarding the Signal Quality, as previously stated, I am more or less trying to rule out anything I can do on my end to triage. I understand the broadcast configuration is probably the culprit here, but want to check as many boxes as I can before reaching out to the engineers at the local station. I started with SD because according to the Config GUI, nothing visible changed in the broadcast data that is presented.

I understand what the firmware update addresses. My previous post was simply to state I cannot verify the fix in the firmware on my end, as one of the channels that was experiencing crossover is not tunable, at my location, at this time. I don't think it's unusual to expect the user that reported the bug to also follow up after a fix. Furthermore, when the stations made changes to the way their broadcasts were configured, I no longer experienced the problem - that's before the firmware update. You can see that information noted a few posts above.

Lastly, I'm not trying to be a sore-spot for you or the team. Your last reply was borderline condescending, but of course, written text can be mistaken for many things tonally. As a customer of yours for nearly 15 years, I trust I'm misinterpreting it, and that we are still working toward the same goals. I want to be able to watch as many of the ATSC 3 broadcasts that are available in my area as possible, with minimal bugs or UX issues. Thanks in advance for your understanding and continued customer service.

I'll reach out to engineering and let you know if I find anything out.