<!DOCTYPE html><html><head><style type="text/css">body { font-family:'DejaVu Sans Mono'; font-size:12px}</style></head><body><div>On Sun, 31 Jul 2016 21:02:01 +1200, Stephen Worthington <stephen_agent@jsw.gen.nz> wrote:<br><br>> On Sun, 31 Jul 2016 15:59:15 +1200, you wrote:<br>><br>><br>>> I started on this again this morning but was interrupted by a 5 hour<br>>> powercut.<br>>> First I changed tuning timeout from 3000 to 10000 as suggested and then<br>>> created the additional.args file.<br>>> I selected a program in the guide and chose the "watch" option and the<br>>> tuner worked perfectly.<br>>> Then I selected "record" and that works too.I did this several times and<br>>> it seems ok now.It was using the tuner card not the HDHR.<br>>> I wonder if the tuning timeout was responsible for this.<br>>> I will do some more testing over the next few days.I have a copy of<br>>> mythbackend.log on google drive,the link below should allow you to <br>>> access<br>>> it.<br>>> <a href="https://drive.google.com/open?id=0B5RRWPLTmilhVHdKN29obmpBWUU">https://drive.google.com/open?id=0B5RRWPLTmilhVHdKN29obmpBWUU</a><br>>><br>>> There may be messages relating to the recordings database due to <br>>> switching<br>>> the drive between the 2 OS versions.<br>><br>> That all seems fine - a normal LiveTV session. So I am wondering if<br>> your original problem may have been caused by a bad chanid as the<br>> DefaultChanid setting. That is the channel that is tuned when you go<br>> to Watch TV from the main menu. If you do not use Live TV much, you<br>> can have a problem where the channel that was last watched has<br>> disappeared from the database since then, due to the usual churn of<br>> channels. MythTV does not check for that and just tries to tune<br>> whatever channel is in the DefaultChanid setting. And on deleting a<br>> channel, it does not check DefaultChanid to see if it is set to the<br>> deleted channel. Going to Live TV by selecting a channel from the<br>> Guide gets around the bad DefaultChanid problem, if it exists.<br>><br>>> One more question you may be able to answer: When I boot the system I <br>>> get<br>>> mythbackend settings utility starting (every time) what do I do to stop<br>>> this?<br>><br>> This is likely the fix:<br>><br>> <a href="https://ubuntuforums.org/showthread.php?t=2329744">https://ubuntuforums.org/showthread.php?t=2329744</a><br>><br>> But there may be an underlying problem as I thought that Mythbuntu was<br>> supposed to remove that autostart entry automatically when the<br>> configuration was updated and mythbackend was able to be started. I<br>> have never found any script that would do that though.<br>><br>>> I got more familiar with navigating mysql too :)<br>>><br>>> Thanks for the help.<br>><br><br>The tuner problem is intermittent.Today it's back.I can't see the cause in the logs.<br>Here's a link to a new mythbackend log</div><div><a href="https://drive.google.com/open?id=0B5RRWPLTmilhZ2lzSHFUZjdsSUk">https://drive.google.com/open?id=0B5RRWPLTmilhZ2lzSHFUZjdsSUk</a></div><div>At 10:33 I selected a channel to watch live from the guide.</div><div>At 10:34 I selected to record that channel</div><div>PS The tip from the forum thread corrected the settings utility start issue.<br><br><br></div></body></html>