<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p style="margin-bottom: 0in; line-height: 100%; background:
#ffffff">
Hi Stephen!</p>
<p style="margin-bottom: 0in; line-height: 100%; background:
#ffffff">
<br>
</p>
<pre class="western"><font face="moz-fixed"><font style="font-size: 9pt" size="2">See what the output of these two commands is:</font></font>
<font face="moz-fixed"><font style="font-size: 9pt" size="2"><span lang="en-US"><b>fc-list | grep -i droid</b></span></font></font>
<font face="moz-fixed"><font style="font-size: 9pt" size="2"><span lang="en-US"><b>locate DroidSans.ttf</b></span></font></font>
</pre>
<dl>
<dd>
<table width="617" cellspacing="0" cellpadding="4">
<colgroup><col width="607"> </colgroup><tbody>
<tr>
<td style="border: 1px solid #000000; padding: 0.04in"
width="607" valign="top">
<p><font face="moz-fixed"><font style="font-size: 9pt"
size="2">barry@Backend-3:~$ fc-list | grep -i
droid</font></font></p>
<p><font face="moz-fixed"><font style="font-size: 9pt"
size="2">/usr/share/fonts/truetype/droid/DroidSansFallbackFull.ttf:
Droid Sans Fallback:style=Regular</font></font></p>
<p><font face="moz-fixed"><font style="font-size: 9pt"
size="2">barry@Backend-3:~$ </font></font> </p>
<p><font face="moz-fixed"><font style="font-size: 9pt"
size="2">barry@Backend-3:~$ </font></font> </p>
<p><font face="moz-fixed"><font style="font-size: 9pt"
size="2">barry@Backend-3:~$ locate DroidSans.ttf</font></font></p>
<p><font face="moz-fixed"><font style="font-size: 9pt"
size="2">/usr/share/mythtv/fonts/DroidSans.ttf</font></font></p>
<p><font face="moz-fixed"><font style="font-size: 9pt"
size="2">barry@Backend-3:~$ </font></font> </p>
<p><br>
</p>
<p><font face="moz-fixed"><font style="font-size: 9pt"
size="2">So the good news is I have the fonts, or
at least that font; the bad news is it wasn’t
installed. (Tangential side note: I seem to
remember similar “font not installed” errors on
the old Backends/Frontends – old problem with
installation instructions? Backend-3 is a
brand-new from-scratch install.)</font></font></p>
</td>
</tr>
</tbody>
</table>
</dd>
</dl>
<p style="margin-bottom: 0in; line-height: 100%; background:
#ffffff">
<br>
</p>
<pre class="western" style="background: #ffffff"><font face="moz-fixed"><font style="font-size: 9pt" size="2"><span lang="en-US"><span style="background: transparent">Yes, you now need to use mythtv-setup to change the master backend IP address to 192.168.0.3 if it is still on 127.0.0.1. Now that the fix for booting after the network is up is in place, that should work properly.</span></span></font></font></pre>
<dl>
<dd>
<table width="615" cellspacing="0" cellpadding="4">
<colgroup><col width="605"> </colgroup><tbody>
<tr>
<td style="border: 1px solid #000000; padding: 0.04in"
width="605" valign="top">
<p>I’ll admit that ‘should’ is scaring me a little! Here
goes! </p>
<p><br>
</p>
<p>mythtv-setup. Change at “General”. Exit (that long
pause <whimper!> mythfilldatabase</p>
<p><br>
</p>
<p>mythfrontend (on BE3) : OK, still seeing the correct
displays: Medial Library > Watch Recordings >
shows are there. </p>
<p><br>
</p>
<p>OK, now the big test: checking on a Remote Fronted
(RPi 3 B+)…</p>
<p>Super-long pause at GEC Adapter, turn TV on – I’ll
have to look in to that.)</p>
<p>Wohoo! BE3 stuff displays! </p>
<p>Ah poo! I see the TV programmes listed but select and
get </p>
<p style="margin-left: 0.49in">Can’t start playback</p>
<p style="margin-left: 0.49in">TV Player</p>
<p style="margin-left: 0.49in">Failed to open remote
file mytht:// </p>
<p style="margin-left: 0.49in">backend-3/<file
number>.ts</p>
<p><br>
</p>
<p>Reboot the RPi; try again. Same error.</p>
<p><br>
</p>
<p>(That recording does play properly on BE3’s
Frontend).</p>
<p><br>
</p>
<p>Reboot BE3. ...Test, its Frontend still works.</p>
<p>RPi Frontend – same error.</p>
<p><br>
</p>
<p><a class="moz-txt-link-freetext" href="https://pastebin.com/q3Msyr49">https://pastebin.com/q3Msyr49</a></p>
</td>
</tr>
</tbody>
</table>
</dd>
</dl>
<p style="margin-bottom: 0in; line-height: 100%; background:
#ffffff">
<br>
</p>
<pre class="western" style="background: #ffffff">Yes, you can move the database across to BE3. If you want to shut
down BE2 permanently, then that is probably the easiest thing to do -
just do a backup of the BE2 database, copy the backup file to BE3, and
then restore the database on BE3 using the hostname change options of
the restore program to change all the hostname bits in the backup to
BE3. Then when MythTV is started again, it will see an old database
schema and will upgrade it automatically to v30. You need to copy or
move all the recording files across (maybe just move the recording
drives of BE2 into the BE3 PC?). Doing it this way keeps all the
information about old recordings and all your recording rules.
However, if the tuners are different in BE3, you will need to set them
all up again, as the BE2 database will be set up for BE2's tuners. And
you will need to make sure the tuner setup you do matches what BE2 had
so that the recording rules still work. All of that is a very viable
thing to do, but it really depends on what you want out of BE3. Since
keeping all the recording history is very important to me, this is the
path I would be choosing.
</pre>
<dl>
<dl>
<dd>
<table width="605" cellspacing="0" cellpadding="4">
<colgroup><col width="595"> </colgroup><tbody>
<tr>
<td style="border: 1px solid #000000; padding: 0.04in"
width="595" valign="top">
<p><font face="Liberation Mono, monospace"><font
style="font-size: 10pt" size="2">OK, part of
this answer is based on reading the next
section. BE3 uses the ‘new and improved’
Hauppauge 1609 quad tuner while (BE1 and) BE2
use the older Hauppauge 1600 and 2250 tuners.
While it would be nice to ‘simply’ transfer over
the old database and re-install the new tuner
data I’m thinking with all the problem we have
the potential for error isn’t worth the minor
inconvenience of deleting a previously recorded
show. ...</font></font></p>
</td>
</tr>
</tbody>
</table>
</dd>
</dl>
</dl>
<pre class="western">Alternatively, if you just want to move the recordings across, I have
software that can do that (mythexport and mythimport). But doing it
for a large number of recordings could be pretty tedious. And as I
have not yet upgraded to v30 (which I hope to do this week), I have
not tested mythexport and mythimport with v30 yet. I would also need
to check that exporting from v28 to v30 was OK - the database entries
for the recording tables would need to match. I believe v28 to v29 is
OK, and I have not heard of anything in v30 that would be
problematical, but until I have v30 running I can not be sure. If
necessary I can probably do a modified version of mythexport that
would do a full export of all recordings, which would get rid of the
tedious bits.
- -
Since I wrote the above yesterday, I have been able to do my v30
upgrade. So in the next couple of days I should be able to test (and
if necessary fix) my mythexport and mythimport software.</pre>
<dl>
<dl>
<dd>
<table width="606" cellspacing="0" cellpadding="4">
<colgroup><col width="596"> </colgroup><tbody>
<tr>
<td style="border: 1px solid #000000; padding: 0.04in"
width="596" valign="top">
<p>OK – thanks (again!!). I’m thinking between the two
options the safer one for me is this one (move the
recordings across: mythexport/mythimport). I had a
thought of potentially copying the shows to Videos,
perhaps a subdirectory of each show series and the
dump the shows in there. Would probably just show
the date and the show number. I bet your utility is
a lot better!</p>
<p><br>
</p>
<p>Worst comes to worse (which isn’t all that bad) is
switching between two Frontends, one to BE3 (the new
one) and BE2 (the old one)</p>
<p><br>
</p>
<p>TIA! <br>
Barry </p>
</td>
</tr>
</tbody>
</table>
</dd>
</dl>
</dl>
<p style="margin-bottom: 0in; line-height: 100%; background:
#ffffff">
<br>
</p>
<p style="margin-bottom: 0in; line-height: 100%; background:
#ffffff">
<br>
</p>
<style type="text/css">td p { margin-bottom: 0in; }pre.cjk { font-family: "Courier New", monospace; }p { margin-bottom: 0.1in; line-height: 115%; }a:link { }</style>
</body>
</html>