[mythtv-users] HDHomerun Prime with CableCard on Myth 0.29 via External (black box) Tuner

Peter Bennett pb.mythtv at gmail.com
Tue Jul 12 13:01:44 UTC 2022


On 7/12/22 08:23, Christopher Sean Hilton wrote:
> Good morning,
>
> I'm trying to connect my HDHomerun Prime to my Mythtv using the
> External (black box) tuner interface and the mythhdhrrecorder
> program. I think I've followed the instructions correctly but I
> probably haven't.
>
> My environment is CentOS 7 with mythtv packages installed from the
> nux-dextop repo and xmltv installed from the rpmfusion repo.
>
> I created a wrapper shell script that runs mythhdhrrecorder with
> dependecies from a python venv. I'll detail the steps to do that below.
>
> I'm having trouble with the following step:
>
>>   * Specify the executable and (usually) append an arbritary unique device
>>     name, for example: /home/mythtv/bin/mythhdhrrecorder --devicename 0
> In my UI, this is lookup box that allows me find the wrapper shell
> script I created but does not allow me to enter: '--devicename 0'?
>
> **How do I fix the '--devicename 0' issue?**
>
>
> ----------------------------------------------------------------
>
> I'm having trouble verifying that things work this way. I have two
> inputs connected to one logical video source. The video source is my
> CATV feed. Once way to consume it is via my HD-PVR connected to cable
> box. This gives me 1 tuner that can see all channels in my CATV feed. The
> other way of consuming this source is via the HDHomerun Prime. This
> gives me 3 tuners but they can only see the unecrypted
> channels. Because of problems setting up the HDHomerun initially, I
> setup the HD-PVR first and I think that Myth is prioritizing that
> tuner. E.g. the Mets show on SNYHD, channel 60 on the Cable Box feed
> and Channel 718 on the HDHomerun Prime feed. When I select 718 for
> viewing in the guide in the front end, the Cable box changes to
> channel 60.
>
> ----------------------------------------------------------------
>
>
> To build the wrapper script, I've:
>
> - Cloned the git repository for mythhdhrrecorder into:
>      `/home/mythtv/lib/mythhdhrrecorder`
>
> - Installed python3.6 and the various devel packages needed to
>    satisfy building Python packages from C-source for mythhdhrrecorder:
>    E.g.
>      * python3-devel
>      * systemd-devel
>
> - Created a venv under python3.6 with the requirements needed to
>    run myththdhrrecorder
>
> - Created a shell script in `/home/mythtv/bin/mythhdhrrecorder` which
>    does the following:
>
>    > ```
>    #! /bin/sh
>
>    . /home/mythtv/lib/mythhdhrrecorder/venv/bin/activate
>
>    exec /home/mythtv/lib/mythhdhrrecorder/venv/bin/python
>    /home/mythtv/lib/mythhdhrrecorder/mythhdhrecorder "${@}"
>    ```
>
> The purpose of the above steps was to create a self-contained venv
> where the mythhdhrrecorder program could run with all of it's
> dependecies installed.
>
> I've tested that they mythhdhrrecorer program works this way. From my
> logs, it looks functional.
>
Is there some problem with the built-in hd homerun support in MythTV, 
that you want to use it via an external recorder? I used an HD Homerun 
Prime for a few years with the built-in support. Since then the built-in 
support has been improved with better reservation and allocation of tuners.

Peter



More information about the mythtv-users mailing list