View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 1 post ] 
Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Fri Mar 23, 2018 11:48 am 
Offline
Joined: Thu Sep 27, 2007 5:44 pm
Posts: 459
I have two HDHomeruns using OTA signals and I have a separate antenna on each HDHomerun. Each unit is dual tuner. So let's say I have HDHR1-1
HDHR1-2
HDHR2-1
HDHR2-2

I prioritize them so that HDHR*-1 is for recordings and HDHR*-2 is for live TV. I noticed yesterday that some recordings failed on HDHR2-1 and rather than using the 2nd priority, they just did not record. Further digging showed the backend could not connect to it on startup:
Code:
2018-03-22T06:16:08.689778-05:00 mythbackend[1781]: E CoreContext recorders/hdhrstreamhandler.cpp:389 (Connect) HDHRSH(10487E39-0): Unable to connect to device
2018-03-22T06:16:08.790307-05:00 mythbackend[1781]: E CoreContext dtvmultiplex.cpp:379 (ParseTuningParams) DTVMux: ParseTuningParams -- Unknown tuner type = 0xffffffff80000000
2018-03-22T06:16:08.790668-05:00 mythbackend[1781]: E CoreContext recorders/dtvchannel.cpp:300 (SetChannelByString) DTVChan[11](10487E39-0): SetChannelByString(43.1): Failed to initialize multiplex options
2018-03-22T06:16:08.790938-05:00 mythbackend[1781]: E CoreContext dtvmultiplex.cpp:379 (ParseTuningParams) DTVMux: ParseTuningParams -- Unknown tuner type = 0xffffffff80000000
2018-03-22T06:16:08.791148-05:00 mythbackend[1781]: E CoreContext recorders/dtvchannel.cpp:300 (SetChannelByString) DTVChan[12](10487E39-0): SetChannelByString(43.1): Failed to initialize multiplex options


I'm not sure if the backend automatically attempts to set the channel on all of its tuners when it starts up? The frontend wouldn't have been on and I feel confident that nothing would have been recording on that channel, this was 1 minute after the machine woke up in the morning. In any case, when I noticed this in the evening, I found that if I tuned to that channel with live tv on the other tuner on the same HDHomerun, it would work fine. If I tried to switch inputs to that specific tuner, the screen would go blank for maybe 20 seconds and then it would drop back to the frontend menu. Resetting the HDHomerun did not help. Restarting mythbackend resolved the problem.

I found a pretty detailed post about similar issues experienced as far back as Mythtv 0.27. That person came to the conclusion that the most reliable solution was to leave mythbackend running:
http://gedakc.users.sourceforge.net/dis ... -recording

Unfortunately, I can't keep the backend running because I want to let mythwelcome shutdown and wake up my machine each day, so this is not a workable solution for me. This is the first time I noticed it, so I almost didn't even post anything, but I realized I should before the logs disappear. I searched for other logs containing the text "Unable to connect" and did not find anything, so hopefully this is a one time thing, but it would be useful to receive some sort of notification automatically if this happened on startup of mythbackend in the future if anybody has any suggestions.


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 1 post ] 


All times are UTC - 6 hours




Who is online

Users browsing this forum: Google [Bot] and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu