<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Jul 19, 2020 at 7:00 AM Mike Perkins <<a href="mailto:mikep@randomtraveller.org.uk">mikep@randomtraveller.org.uk</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 19/07/2020 11:27, Jim Abernathy wrote:<br>
> <br>
> On 7/19/20 6:12 AM, Mike Perkins wrote:<br>
>> On 19/07/2020 10:59, Jim Abernathy wrote:<br>
>>><br>
>> (snip)<br>
>>><br>
>>> Thanks, just a few questions. The need for a slave backend is for many reasons and 2 that caught <br>
>>> my mind were:<br>
>>><br>
>>> 1.� adding more tuners.<br>
>>><br>
>>> 2.� adding more storage.<br>
>>><br>
>>><br>
>>> Having the tuners defined locally on the slave and no local video source makes sense because I <br>
>>> only use one video source and all my tuners could use it because there are one set up OTA TV <br>
>>> stations.<br>
>>><br>
>>> However, I'm confused on the Storage setup.� The Storage Groups are all defined on the master, <br>
>>> but how is the slave local storage defined and used?� It sound like you do all your recording on <br>
>>> the master.<br>
>>> A point on the remote tuners: Using a source on another host is only possible if the remote tuners <br>
>> are the same type.<br>
>><br>
>> A source defines a method of tuning as well as a selection of channels. Different tuner types <br>
>> require different sources.<br>
>><br>
> <br>
> So on my current master backend I have Hauppauge WinTV HD Quad PCIe card. My slave would have a <br>
> HDHomerun Quatro, so different types of tuners. They could use the same list of channels provided <br>
> by Schedules Direct, I think. The master backend could do the scan on one of the WinTV tuners, but <br>
> not the HDHR tuners, so it could only establish input connections for the WinTV tuners, unless <br>
> Mythtv can tell the slave to scan the HDHR tuners?<br>
> <br>
> Jim A<br>
> <br>
> <br>
You'll be using mythtv-setup on the slave to configure it, so you can provide a unique (to it) <br>
source and do whatever scan it requires there.<br>
<br>
You can reference the same channel list from SD, though, since SD doesn't care about tuner types, <br>
just what you watch.<br>
<br>
Mmm. Interesting point: presumably mythfilldatabase (mfdb) normally runs on the host that has a <br>
database, the master. How does it know about remote sources? Or do you run mfdb on every slave as <br>
well, updating the database over the network? I can't answer that one, can anyone else?<br>
<br>
-- <br>
<br>
Mike Perkins<br></blockquote><div><br></div><div>So I've made some progress. I installed Raspberry Pi OS on a fresh SD card and booted, updated, and then copied the SD image to a USB3 SATA SSD since the RPi4 now supports USB3 boot with the latest EEPROM bootloader.</div><div><br></div><div>Then I installed mythtv-light v31 per the wiki and I downloaded the pi-utils from: <a href="https://github.com/MikeB2013/pi-utils.git" style="background-color:transparent;color:rgb(0,0,128)">https://github.com/MikeB2013/pi-utils.git</a></div>
<div>I modified the pi-mythbackend-helper.sh so the only functions I ran were:</div><div>fn_get_git</div>fn_setup_mythtv_user<br>fn_setup_mythtv_backend_service<br>fn_setup_directories<br>fn_tidy_up<br></div><div class="gmail_quote"><br></div><div class="gmail_quote">After rebooting, I ran mythtv-setup on the slave and it can't find the database since there isn't one on the slave. So I use the manual setup option to fill in the info about the master backend, i.e. IP, mythconverge password, etc.</div><div class="gmail_quote"><br></div><div class="gmail_quote">It then found the master and I could add the tuner cards and it already knew about the Video Source (SD). I could set up the Input Connections and scan the first tuner only; the same as when you build a regular backend.</div><div class="gmail_quote"><br></div><div class="gmail_quote">You are not supposed to configure Storage groups on the backend, but that confuses me.</div><div class="gmail_quote"><br></div><div class="gmail_quote">I also copied my .mythtv/config.xml file to /etc/mythtv/config.xml and that is symbolic linked to /home/mythtv/.mythtv/config.xml</div><div class="gmail_quote"><br></div><div class="gmail_quote">I defined a mountpoint in the Storage Group Default and created that directory, but mythtv-setup will not let you create a path that doesn't exist, even though the wiki says to do that.The directory does exist on the slave backend. the master is supposed to ignore any directory that doesn't exit, but since you can't create one that doesn't exist, ????</div><div class="gmail_quote"><br></div><div class="gmail_quote">This is where I'm getting my Storage Group information and I can't seem to make it work. The errors I'm getting are related to the recordings not being accessible.</div><div class="gmail_quote"><br></div><div class="gmail_quote"><a href="https://www.mythtv.org/wiki/Setup_Storage_Directories#Multiple_Backends">https://www.mythtv.org/wiki/Setup_Storage_Directories#Multiple_Backends</a><br></div><div class="gmail_quote"><br></div></div>