<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On May 17, 2022, at 7:12 AM, James Abernathy <<a href="mailto:jfabernathy@gmail.com" class="">jfabernathy@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><br class=""></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, May 7, 2022 at 7:42 AM Stephen Worthington <<a href="mailto:stephen_agent@jsw.gen.nz" class="">stephen_agent@jsw.gen.nz</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br class="">
To check for these messages, these commands are useful:<br class="">
<br class="">
grep -a "overall_score=\"0" /var/log/mythtv/mythbackend.log<br class="">
<br class="">
That will find any overall_score value that starts with a 0, so any<br class="">
where mythbackend calculated the value as less than 1.0.<br class="">
<br class="">
And this will find any non-zero continuity_error_count messages:<br class="">
<br class="">
grep -a "continuity_error_count=\"[1-9]" /var/log/mythtv/mythbackend.log<br class=""></blockquote><div class=""><br class=""></div><div class="">Stephen, I've added your-v record to a test mythtv-backend that uses only the HDHR Quatro. I set up 2 recordings.</div><div class=""> The 2 recordings from station 11701 are the ones in the log below that concern me. The earlier one is the one that was flagged in Yellow test in the media listing.</div><div class=""><br class=""></div><div class="">I ran the 2 commands you gave me and the results are below for 2 recordings. only the 2 from Station 11701 are of concern since they were both Prime time HD programs on a good signal station. Is there a way to tell if these problems were Tuner or Network traffic related??</div></div></div></div></blockquote></div><br class=""><div class="">As far as I know, the only way to check network problems is using the hdhomerun_config command to dump video to null and watch for errors in the output. I am pasting excepts from silicon dust on how to see the status during recording: Network errors will show up as ’n’ in the output below.</div><div class=""><br class=""></div><div class=""><div class="">excerpted from <a href="https://info.hdhomerun.com/info/hdhomerun_config" class="">https://info.hdhomerun.com/info/hdhomerun_config</a> :</div><div class=""><br class=""></div><div class="">Note that to use the below to set a frequency/channel for the tuner to capture from below:</div><div class=""><br class=""></div><div class="">Tuning a physical channel</div><div class="">----------------------------</div><div class=""><br class=""></div><div class="">To set a channel use the set channel command:</div><div class=""><br class=""></div><div class="">format: hdhomerun_config <id> set /tuner<n>/channel <modulation>:<frequency></div><div class="">format: hdhomerun_config <id> set /tuner<n>/channel <modulation>:<channel></div><div class="">eg: hdhomerun_config FFFFFFFF set /tuner0/channel auto:651000000</div><div class="">eg: hdhomerun_config FFFFFFFF set /tuner0/channel auto:60</div><div class=""><br class=""></div><div class="">Supported modulation types can be queried with the get sys-features command:</div><div class=""><br class=""></div><div class="">hdhomerun_config <id> get /sys/features</div><div class=""><br class=""></div><div class="">To stop the tuner set the channel to none:</div><div class=""><br class=""></div><div class="">format: hdhomerun_config <id> set /tuner<n>/channel none</div><div class="">eg: hdhomerun_config FFFFFFFF set /tuner0/channel none</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Saving a stream</div><div class="">---------------------------------------</div><div class=""><br class=""></div><div class="">The hdhomerun_config command can be used to automate the process of saving to the local filesystem:</div><div class=""><br class=""></div><div class="">format: hdhomerun_config <id> save /tuner<n> <filename></div><div class="">eg: hdhomerun_config FFFFFFFF save /tuner0 capture.ts</div><div class=""><br class=""></div><div class="">While saving the stream, a single period “.” will be displayed every second. Additionally, as of the 20080609 release, the hdhomerun_config will detect reception and network errors, replacing the “.” with an alternative character to indicate the problem.</div><div class=""><br class=""></div><div class="">Example output:</div><div class=""><br class=""></div><div class="">............n...............................n..........ts..........</div><div class="">-- Video statistics --</div><div class="">23323 packets recieved, 2 network errors, 1 transport errors, 1 sequence errors</div><div class=""><br class=""></div><div class="">Advanced: A filename of “null” indicates no file should be created, allowing the use of the save command as a diagnostic tool.</div><div class=""><br class=""></div><div class="">Advanced: “-” may be used as a filename to indicate standard output, allowing the save command to be used as a pipe on supported platforms.</div><div class=""><br class=""></div><div class="">eg: hdhomerun_config FFFFFFFF save /tuner0 - | vlc -</div><div class=""><br class=""></div><div class=""><br class=""></div></div></div></body></html>