Is anything logged when there are recording errors?

[broconne]

I am trying to track down some errors I had in a few recordings on Monday. I had a few skips and some green blocks. I have debug mode enabled and have logs from that time period. However, there is a lot of info in there and nothing that jumps out to me as a recording error.

My source is two HDHRs - should I be able to find anything useful in the sage.log?

[stanger89]

Not unless the recording is actually halted/broken. Beyond that Sage can't detect errors in the bitstream.

[broconne]

That was what I expected. This will be difficult to track down as it seems to be intermittent. And I am unsure how to track down if its CPU, Network, or NAS related...

[matt91]

as these HDHRs fed cable or OTA? Either way, it's possible that signal strength is involved. You can of course monitor that via the HDHR tool that is installed (at least in Windows).

Have you already eliminated that cause?

[broconne]

Originally Posted by matt91

as these HDHRs fed cable or OTA? Either way, it's possible that signal strength is involved. You can of course monitor that via the HDHR tool that is installed (at least in Windows).

Have you already eliminated that cause?

Doing QAM and Signal strength is over 90%.

Does anyone know if the the HDHR TCP or UDP?

[gplasky]

Signal strength isn't the only thing to look for. Look at the signal quality coming thru. The strength can be 90% but if quality is low (60%) than you won't get a good picture.

Gerry

[drewg]

Originally Posted by broconne

Doing QAM and Signal strength is over 90%.

Does anyone know if the the HDHR TCP or UDP?

UDP.

You can get a decent idea of whether or not the HDHR is having tuning problems by looking at the debug counters when the show is recording. Use the command line hdhr_config utility:

# find HDHR
hdhomerun_config discover
hdhomerun device 1018F832 found at 172.31.193.14

# get stats
hdhomerun_config 1018F832 get /tuner0/debug
tun: ch=none lock=none ss=0 snq=0 seq=0 dbg=0
dev: resync=0 overflow=0
ts:  bps=0 ut=0 te=0 miss=0 crc=0
flt: bps=0
net: pps=0 err=0 stop=0

Mine's not recording anything, so I've got all 0s. You should look for resync, overflow, te, resync being non-zero.

Good luck!

Drew