Mailing List Archive: MythTV stopped tuning into HDHomerun connect device

MythTV stopped tuning into HDHomerun connect device

Jul 19, 2019, 5:20 PM

Post #1 of 3 (411 views)

Hi

I had added a newly purchased HDHR Connect device to my backend a couple
of weeks back. It seems to work fine and I could watch OTR channels fine.

Today when I tried to watch live TV, it could not tune to any channel.
I tried HDHR Config and it could tune to channels on the HDHR. The
backend seems to be able to scan for channels fine. When I looked at the
backend logs I found....

Jul 19 20:07:03 HP-DVR mythbackend: mythbackend[2091]: I TVRecEvent
tv_rec.cpp:1050 (HandleStateChange) TVRec[5]: Changing from None to
WatchingLiveTV
Jul 19 20:07:03 HP-DVR mythbackend: mythbackend[2091]: I TVRecEvent
tv_rec.cpp:3602 (TuningCheckForHWChange) TVRec[5]: HW Tuner: 5->5
Jul 19 20:07:03 HP-DVR mythbackend: mythbackend[2091]: E TVRecEvent
dtvmultiplex.cpp:327 (ParseTuningParams) DTVMux: ParseTuningParams --
Unknown tuner type = 0xffffffff80000000
Jul 19 20:07:03 HP-DVR mythbackend: mythbackend[2091]: E TVRecEvent
recorders/dtvchannel.cpp:319 (SetChannelByString)
DTVChan[5](104E4F32-0): SetChannelByString(2_3): Failed to initialize
multiplex options
Jul 19 20:07:03 HP-DVR mythbackend: mythbackend[2091]: E TVRecEvent
tv_rec.cpp:3792 (TuningFrequency) TVRec[5]: Failed to set channel to
2_3. Reverting to kState_None
Jul 19 20:07:03 HP-DVR mythbackend: mythbackend[2091]: I TVRecEvent
tv_rec.cpp:1050 (HandleStateChange) TVRec[5]: Changing from
WatchingLiveTV to None
Jul 19 20:07:13 HP-DVR mythbackend: mythbackend[2091]: I ProcessRequest
mainserver.cpp:1420 (HandleAnnounce) MainServer::ANN Playback
Jul 19 20:07:13 HP-DVR mythbackend: mythbackend[2091]: I ProcessRequest
mainserver.cpp:1422 (HandleAnnounce) adding: hp-dvr as a client (events: 0)
Jul 19 20:07:13 HP-DVR mythbackend: mythbackend[2091]: I ProcessRequest
mainserver.cpp:1538 (HandleAnnounce) MainServer::HandleAnnounce FileTransfer
Jul 19 20:07:13 HP-DVR mythbackend: mythbackend[2091]: I ProcessRequest
mainserver.cpp:1540 (HandleAnnounce) adding: hp-dvr as a remote file
transfer

Apparenlty it is unable to find the 'tuner type'. Any idea what could be
happening?

Thanks for any help.

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

Re: MythTV stopped tuning into HDHomerun connect device [ In reply to ]

stephen_agent at jsw

Jul 20, 2019, 1:15 AM

Post #2 of 3 (406 views)

Permalink

On Fri, 19 Jul 2019 20:20:14 -0400, you wrote:

>Hi
>
>I had added a newly purchased HDHR Connect device to my backend a couple
>of weeks back. It seems to work fine and I could watch OTR channels fine.
>
>Today when I tried to watch live TV,? it could not tune to any channel.
>I tried HDHR Config and it could tune to channels on the HDHR. The
>backend seems to be able to scan for channels fine. When I looked at the
>backend logs I found....
>
>Jul 19 20:07:03 HP-DVR mythbackend: mythbackend[2091]: I TVRecEvent
>tv_rec.cpp:1050 (HandleStateChange) TVRec[5]: Changing from None to
>WatchingLiveTV
>Jul 19 20:07:03 HP-DVR mythbackend: mythbackend[2091]: I TVRecEvent
>tv_rec.cpp:3602 (TuningCheckForHWChange) TVRec[5]: HW Tuner: 5->5
>Jul 19 20:07:03 HP-DVR mythbackend: mythbackend[2091]: E TVRecEvent
>dtvmultiplex.cpp:327 (ParseTuningParams) DTVMux: ParseTuningParams --
>Unknown tuner type = 0xffffffff80000000
>Jul 19 20:07:03 HP-DVR mythbackend: mythbackend[2091]: E TVRecEvent
>recorders/dtvchannel.cpp:319 (SetChannelByString)
>DTVChan[5](104E4F32-0): SetChannelByString(2_3): Failed to initialize
>multiplex options
>Jul 19 20:07:03 HP-DVR mythbackend: mythbackend[2091]: E TVRecEvent
>tv_rec.cpp:3792 (TuningFrequency) TVRec[5]: Failed to set channel to
>2_3. Reverting to kState_None
>Jul 19 20:07:03 HP-DVR mythbackend: mythbackend[2091]: I TVRecEvent
>tv_rec.cpp:1050 (HandleStateChange) TVRec[5]: Changing from
>WatchingLiveTV to None
>Jul 19 20:07:13 HP-DVR mythbackend: mythbackend[2091]: I ProcessRequest
>mainserver.cpp:1420 (HandleAnnounce) MainServer::ANN Playback
>Jul 19 20:07:13 HP-DVR mythbackend: mythbackend[2091]: I ProcessRequest
>mainserver.cpp:1422 (HandleAnnounce) adding: hp-dvr as a client (events: 0)
>Jul 19 20:07:13 HP-DVR mythbackend: mythbackend[2091]: I ProcessRequest
>mainserver.cpp:1538 (HandleAnnounce) MainServer::HandleAnnounce FileTransfer
>Jul 19 20:07:13 HP-DVR mythbackend: mythbackend[2091]: I ProcessRequest
>mainserver.cpp:1540 (HandleAnnounce) adding: hp-dvr as a remote file
>transfer
>
>Apparenlty it is unable to find the 'tuner type'. Any idea what could be
>happening?
>
>Thanks for any help.

If this is your first network tuner, you may not have done the fix for
getting mythbackend to start up only after the network is actually
available. So every time you reboot, mythbackend will not see the
network tuner as it starts when only localhost is up. If it is unable
to test a tuner at startup, it marks it as bad and does not use it. To
test if this is your problem, just restart mythbackend, and as the
network is up now, it will see the network tuners and everything will
work unitl the next reboot.

If you need that fix, see my post on the recent "Need mythtv-backend
startup advice" thread.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

Re: MythTV stopped tuning into HDHomerun connect device [ In reply to ]

stephen_agent at jsw

Jul 20, 2019, 2:18 AM

Post #3 of 3 (405 views)

Permalink

On Sat, 20 Jul 2019 09:37:03 +0100, you wrote:

>On 20/07/2019 09:15, Stephen Worthington wrote:
>>
>> If this is your first network tuner, you may not have done the fix for
>> getting mythbackend to start up only after the network is actually
>> available. So every time you reboot, mythbackend will not see the
>> network tuner as it starts when only localhost is up. If it is unable
>> to test a tuner at startup, it marks it as bad and does not use it. To
>> test if this is your problem, just restart mythbackend, and as the
>> network is up now, it will see the network tuners and everything will
>> work unitl the next reboot.
>>
>> If you need that fix, see my post on the recent "Need mythtv-backend
>> startup advice" thread.
>>
>This is getting old. Is anyone going to fix the backend systemd service file so that it does the
>right thing - wait for the ACTUAL network to be up, not just localhost?
>
>That way, we won't keep getting puzzled calls from users whose systems can't find network tuners, etc.

There are plenty of users who do not need the full network to be up -
they do not have network tuners and are running just a combined
backend/frontend. For them, localhost is all they need. The
Mythbuntu install package already asks if you are going to need
outside access for frontends, or something like that, if I remember
correctly. It should change the question to make it clear that
network tuners are included, and when the answer to that question is
that the network is needed, it should install the proper systemd
setup. Anyone adding network tuners later would then only need to run
dpkg-reconfigure and change their answer to that question.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org