[mythtv-users] Connecting Mythtv Leanfront to a VM running mythtv-backend?

[James Abernathy]

On Mon, Jul 25, 2022 at 12:38 PM Peter Bennett <pb.mythtv at gmail.com> wrote:

>
> On 7/25/22 10:13, James Abernathy wrote:
>
>
>
> On Mon, Jul 25, 2022 at 9:47 AM James Abernathy <jfabernathy at gmail.com>
> wrote:
>
>>
>>
>> On Mon, Jul 25, 2022 at 9:29 AM Tom Bishop <bishoptf at gmail.com> wrote:
>>
>>>
>>> On Mon, Jul 25, 2022 at 8:25 AM James Abernathy <jfabernathy at gmail.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Mon, Jul 25, 2022 at 9:05 AM Tom Bishop <bishoptf at gmail.com> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Mon, Jul 25, 2022, 7:57 AM James Abernathy <jfabernathy at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> First this is not critical, but I discovered it during testing some
>>>>>> different backend configurations using a VM.  I got my backend working
>>>>>> under libvirt/kvm and I could even run the frontend but the video quality
>>>>>> was a little jerky, so I wanted to test it with a remote frontend to see if
>>>>>> this was purely a lack of video acceleration under the VM.  So I set up my
>>>>>> Leanfront on my FIreTV 4K to point to the backend running on the VM.  BTW,
>>>>>> I disabled the firewalld on the VM so that wouldn't trip me up.
>>>>>>
>>>>>> When I changed the backend IP on Leanfront  and refreshed I saw the
>>>>>> one recording I had, but I could not play it.  After a few seconds of
>>>>>> spinning circles, I got an error message:
>>>>>>
>>>>>> "Play Failed. Unable to obtain file length."
>>>>>>
>>>>>> If I select continue, I get another error:
>>>>>>
>>>>>> Playback Failed. Error Loading data from the MediaSource. Source
>>>>>> error.
>>>>>>
>>>>>> This was all using Status Port 6744.  Which is what I use for
>>>>>> Leanfront with my Production backend. But I get the same error with Port
>>>>>> 6544.
>>>>>>
>>>>>> My PC running the VM has a Network Bridge setup so all VMs are on the
>>>>>> same subnet as my HDHR tuners and all my FIreTV 4k sticks.
>>>>>>
>>>>>> Any idea why this isn't working?
>>>>>>
>>>>>> Jim A
>>>>>>
>>>>>> That is odd, running the frontend on the vm would make sense in
>>>>> regards to video acceleration etc but I have run my backend forever as a
>>>>> kvm vm and I have never had any issues with it working properly soni assume
>>>>> there is something else at play, should work just fine.
>>>>>
>>>>
>>>> That's kind of what I thought. I just used Kodi on a PC and set its IP
>>>> to match the VM's IP and It works great and confirms that my Frontend on
>>>> the VM being jerky is a VM lack of Video acceleration issue.  Kodi plays
>>>> what the backend on the VM recorded very well.
>>>>
>>>> Jim A
>>>>
>>>>
>>>>
>>> There is a pvr plugin for mythtv on kodi, that is what I use if you want
>>> to try to play with it from a myth perspective. I've only used kodi to
>>> connect to mythtv but it really shouldn't matter from a frontend
>>> perspective.
>>>
>>>
>> I'm using the mythtv pvr plugin for kodi and have for years. If I'm
>> testing a backend it's always easier to use Kodi to test it than
>> mythfrontend, since there are a million and 1 ways to screw that up.
>> Leanfront has become my replacement frontend that's easy to use and change
>> from one backend to another. However, this is the first time I've had it
>> fail.  If I'm using a new backend on a RPI4 or PC Leanfront is my goto.
>> The VM issue is the first time I've noticed a hiccup  with it.
>>
>> Jim A
>>
>
> I'll post this as an issue on github for Leanfront.
>
> Jim A
>
>
>
> leanfront uses http on the specified port to access the lists as well as
> the actual playback data. So it should work.
>
> If it can see the list but not play the video, most likely is that the ip
> address in backend settings is wrong. On the backend run mythtv-setup,
> general, host address backend settings and check the primary ip address/DNS
> name. Make sure that is the same ip address that you have used in the
> leanfront setup.
>
> Peter
>

I think the IP address in mythtv-setup is 127.0.0.1. I'll change it and
retest. If the problem is solved I'll close the issue on github.

Thanks,

Jim A
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20220725/c23558a7/attachment.htm>