Sigerr=100%

[hal9000]

I have some atrocious statistics in my logs showing sigerr=100%
Not sure how am I able to watch TV at all. It is being suggested I talk to Silicon Dust about .... some issues with the tuner?

Can somebody run

grep -a sigerr=100% channels-dvr.log

in their data directory and publish their findings. I am curious if there is anybody not affected by this.
I also get a lot 0s as the lower range for snq/seq

These can be found by running

grep -a ",0%-" channels-dvr.log

I have almost 11,000 lines like this in the last 18 months. I would never suspect anything wrong with anything given there are no issues with the picture.

No assistance from Fancy bits required at the moment, please.

[dschaper]

@hal9000

some issues with the tuner?

Yeah, that sigerr comes directly from the HD Homerun box. Nothing on Channels side to do with it.

Suggest you set up something like GitHub - djp952/hdhomeruntray: HDHomeRun system tray application for Windows to see real time what your signal status is. It's very possible to overdrive the HD boxes as well, signal amps will blow things away and often you'll need attenuation even without an amp.

But that's all things that Silicon Dust would help you with.

Edit: Or you can use the native tools from SD.

hdhomerun_troubleshooting.pdf

Check 2 - Signal Strength and Signal Quality.

● In your DVR application go into live TV mode. Choose a problem channel.
● Use the HDHomeRun software to determine Signal Strength and Signal Quality
○ Windows users: Open HDHomeRun Config (GUI). Click on one of the tuner icons to
select the tuner.
○ Other OS: Use the command: (Fill in the correct Device ID and tuner number)
hdhomerun_config get /tuner/status
Signal strength will be reported as ss, Signal Quality will be reported as snq.
● Digital Antenna:
○ Check that the signal strength is above 60% minimum (75% recommended).
○ Check that the signal quality is above 50% minimum.
○ Check that the symbol quality is 100%.
● Digital Cable:
○ Check that the signal strength is above 80% minimum (90% recommended).
○ Check that the signal quality is above 50% minimum.
○ Check that the symbol quality is 100%.

[chDVRuser]

@hal9000

I also get a lot 0s as the lower range for snq/seq
...
I have almost 11,000 lines like this in the last 18 months. I would never suspect anything wrong with anything given there are no issues with the picture.

The only issue I know about (first sample taken too early) with the [SNR] Signal statistics reporting, resulted in false values like seq=99%,0%-100% bps=2268479,0-2440992 pps=194,0-209 being reported in the log.

@chDVRuser

@eric
I think if you started sampling at 3 seconds, or threw away that first result from your first inquiry at 2 seconds I wouldn't be seeing this.

Still curious what your HDHR Prime results look like.

I've been recording eight 1hr back-back overlapping recordings from the same Prime channel for the past 3 weeks and see issues in the log that don't reflect reality. Not a big deal, UNLESS you rely on that log data. Still the same on v2020.08.12.1854 today.

The HDHR logs show the tuner was selected and not released for eight hours.

Every back-back overlapping recording shows that it was sharing the existing HDHR tuner connection, yet every one shows seq=99%,0%-100% bps=#######,0-####### pps=###,0-###

I know this is a result of your first 2 second sampling. If the code can't be fixed, than everyone should know that this is NOT an issue with their tuner, but your code. Led me to buy a new power adapter for my HDHR, which wasn't the issue.

This was fixed in Channels DVR Server Pre-Release v2024.01.22.2217

@fancybot

v2024.01.22.2217

• IMPROVED: Sometimes it takes 1-2 extra seconds for the pps, bps, etc to be reported from the HDHR stats collector. There is now an additional warmup period to handle this

I haven't seen the erroneous values reported in the log since I updated to that Pre-Release.

[chDVRuser]

@hal9000

I have some atrocious statistics in my logs showing sigerr=100%

Some background on how that number is determined.

@chDVRuser

Which of the following debug values from my example post go into determining sigerr?

get /tuner0/debug
tun: ch=qam:279000000 lock=qam256:279000000 ss=95 snq=100 seq=100 dbg=-450/9119
dev: bps=38810720 resync=0 overflow=0
cc:  bps=77621440 resync=0 overflow=0
ts:  bps=3869792 te=0 crc=0
net: pps=373 err=0 stop=0

Noticed these in my DVR log on different channels from my Prime tuner.

ss=95%     snq=100%         seq=100% bps=3922097,2884672-5333184 pps=376,284-507 sigerr=5%
ss=97%-98% snq=99%,98%-100% seq=100% bps=3409680,2078528-5378304 pps=336,210-523 sigerr=1%
ss=95%-96% snq=100%         seq=100% bps=1585849,792608-2280064  pps=168,97-233  sigerr=5%
ss=96%     snq=100%         seq=100% bps=2035246,1815328-2341728 pps=208,190-238 sigerr=5%
ss=96%-97% snq=100%         seq=100% bps=1767367,395552-2528224  pps=185,67-256  sigerr=5%

@tmm1

sigerr tracks tun/seq dips and ts/te increments.

[hal9000]

I was able to track it down to 807 status from the tuner: no video data

503 Service Unavailable 
X-HDHomeRun-Error: 807 No Video Data

We could probably use better reporting here. It seems like couple stations here dropped signal between 5:10AM and 5:24AM CST which resulted in calls for hardware replacement.

Thank you @chDVRuser and @dschaper