<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
Hi Mike!<br>
<br>
<blockquote
cite="mid:mailman.5.1476014401.17091.mythtv-users@mythtv.org"
type="cite">
<pre wrap="">Because the tuners change around (depending on configuration, as little
as when you change your system or even as much as every reboot), the
information is not stored when we record a show (because it would be
either meaningless or--worse--misleading in many (most?) situations).
Instead, we output a message in the backend log file that includes the
tuner in use when we start a recording.</pre>
</blockquote>
<br>
OK, makes sense the tuners 'move' around. ...Went to Mythbuntu
Control Centre to enable to the "MythTV Backend Log" --
dum-de-dummm... "Bad API request, maximum paste file size
exceeded". ...The good news is there are only four tuners and
three coax lines (one's a dual tuner). "Noticed" two of the cables
were of the slide on/slightly skinny type (why on Earth did I use
those??!!); swapped in better cable -- probably RG-6/U (definately
not RG-59/U -- hope I remember my numbers correctly). <u>femon</u>
indicated a much better signal strength ; unfortunately I had
originally tested in the morning and then did the swap after dinner
and then ran <u>femon</u> again. <br>
<br>
<br>
<blockquote
cite="mid:mailman.5.1476014401.17091.mythtv-users@mythtv.org"
type="cite">
<pre wrap="">FWIW, I haven't used it in forever (since 0.24), but:
<a class="moz-txt-link-freetext" href="https://www.mythtv.org/wiki/Which_recorder.pl">https://www.mythtv.org/wiki/Which_recorder.pl</a>
If you try it out and it works with logs from more-current MythTV
versions, please update the wiki page. Or, if it doesn't and you fix it
(fix the regex), please feel free to update the script on the page.</pre>
</blockquote>
<br>
I'll have to take a look. As for the repair, um, yea. OTOH, we all
have to learn somehow! :)<br>
<br>
<br>
</body>
</html>