[mythtv-users] Upgrading old mythtv

[faginbagin]

On 6/28/2024 4:51 PM, Christopher Sean Hilton wrote:
> I'm upgrading my MythTV setup. Currently my backend is MythTV v29.x. running on
> CentOS-7. The frontend will be anything that can consume the backend, preferrably an App
> installed on my AppleTV. I plan to upgrade to MythTV v34.y running on either Rocky or Alma
> Linux. I support a variety of RedHat based Apps for work. My programming comes from either a
> set of HDHomerun devices, or a Hauppage HD-PVR usb device whcih is connected to a
> Scientific Atlanta SA4200 CATV box with firewire. I use the firewire for channel changing
> and the Hauppage for video capture. This whole rig lives in a server rack in my basement. I
> exclusively consume MythTV content via my home network with a mixture of Apps.
>
>
> I have two questions. The specific question one first: My CATV company, Altice/Optimum is
> discontinuing my cable box. As I figure it this means that I have to change my channel
> changing script from something the ancient C code that I have which supports the firewire
> stack to a USB IR transmitter. The one that I have reports as FTDI FT230X Basic UART and
> creates `/dev/ttyU0` when I plug it in. I'm assuming that this is serial so I just need a
> serial IR transmitter program and the set of codes for the replacement CATV box. The new box
> is a Samsung SMT-C5320. My question is that I'm having trouble locating an appropriate
> serial channel changer script outside of lirc. I literally only need to send the appropriate
> codes to change to channel 2 on the CATV box. Every set of instructions that I've seen
> assumes that my MythTV is in my entertainment center next to my TV and that in order to use
> an IR blaster, I must first setup a remote control.
>
> Q: Is there a way to simply setup just the IR transmitter? For that I assume I need a
> program that can setup and handle the serial port an a set of codes for the SMT-C5320.
>
> My second question is a bit more broad. I need to upgrade this box and it looks like setting
> up MythTV on Rocky 9 from the rpmfusion repo is a painless process. My upgrade plans are as
> follows:
>
> * Figure out the IR transmitter situation separately and stash the code/data that solves
>    that.
>
> * Figure out how to create a brand new MythTV that only consumes the HDHomerun devices to
>    get comfortable with MythTV v34.
>
> * Merge the first two steps as follows:
>
>    - Backup the v29 mysql database and stash the resulting mythconverg.sql.gz file.
>
>    - Using a custom python script that I wrote, preserve my recordings to a different disk
>      drive under appropriate program names.
>
>    - Perform a fresh install of Rocky 9 over the existing O/S drive on the current MythTV V29
>      box.
>
>    - Install mysql and restore the v29 database. (I was a mysql adminstrator in a previous
>      life, this will be very easy.)
>
>    - Perform the rest of the MythTV V34 installation. (I've heard that there's an ansible
>      script. Ansible is also in my wheelhouse.)
>
>    - Allow the new mythtv code to fix what needs to be fixed. And cross my fingers that my
>      recordings were preserved but don't weep if they are lost because step 2.
>
>    - Profit.
>
> ----------------------------------------
>
> The third of my two questions is: Can anyone describe how multiple backend systems work? The
> much longer story here concerns my sources:
>
> * An HDHomerun Flex 4k connected to a TV antenna in my vacation place outside of Boston. Right now
>    this has a mini-mythtv setup running mythtv v31. The backend machine is a VM and storage
>    goes to a small raspberry pi based NAS in that home.
>
> * An HDHomerun Flex 4k connected to a TV antenna pointed to NYC in my house here in Connecticut/CT.
>
> * An HDHomerun Flex 4k connected to a TV antenna pointed to Hartford-CT in my house here in CT.
>
> * An HDHomerun Prime connected to a CableCard attached to my local Cable provider
>    (Altice/optimum) in CT.
>
> * The Hauppage HD-PVR I mentioned above again connected to a locally provided CATV box. All
>    of the CT sources are connected to the "big" backend running MythTV v29 on real hardware.
>
> The problems I want to solve with multiple backend is this: I expect the CATV connected
> stuff to go away in the mid-term either because of cost or because the CATV company decides
> to stop selling that stuff as a product. Specifically, I'm talking about CableCards. So I
> would have the CT connected antenna source connected directly to the main? master?
> backend. The CATV stuff would be on a second backend such that when Altice kills off their
> coax based products, could be next week, could be next decade, hopefully my life is simple.
>
> Thanks
>
>
I'm guessing the interest in IR blaster is to use the cable company's 
cable box with your HD-PVR. You may find that's no longer possible. I 
have never had an HD-PVR, but don't they depend exclusively on component 
in? Do you know if your new cable box will support component out? If 
not, there may be no point in spending time on lirc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20240629/f2055f2a/attachment.htm>