<!DOCTYPE html><html><head><style type="text/css">body { font-family:'DejaVu Sans Mono'; font-size:12px}</style></head><body><div><br><br>><br>> It looks like I was wrong about where the problem lies. Since you<br>> have only one real tuner card, even though it has dual tuners, it will<br>> never move its address around. The HDHR tuners are Ethernet, so they<br>> do not show up as hardware devices in /dev/dvb. So there is no need<br>> for adapter_nr settings unless you ever add another standard tuner.<br>><br>> The settings from the capturecard table look fine except for the<br>> channel_timeout value (3000), which is way too small for DVB-T here in<br>> New Zealand. In versions before 0.28, mythbackend recovered from that<br>> and managed to tune channels anyway, but took longer than necessary as<br>> it could retry several times. In 0.28, it can fail to ever tune<br>> properly, so those settings need to all be increased. I am using<br>> 10000 ms, and that seems to work well. TV3 can take between 7 and 8<br>> seconds to tune. However, that is unlikely to explain your symptoms,<br>> it is just another problem you would have had later in getting 16.04<br>> working properly. You change those values in mythtv-setup => Capture<br>> Cards. On each tuner there, on the first page of its settings, change<br>> the "Tuning timeout" from 3000 to 10000. That same change should also<br>> be done for your old 12.04 setup - it should make tuning work faster<br>> there too.<br>><br>> It looks like we need to see full logs of what is going on. So you<br>> will probably need to set the "-v record" log option on mythbackend.<br>> In 16.04, to work with systemd, that is done in a different way from<br>> previously. In the /etc/mythtv directory, create a file<br>> "additional.args" if it does not exist. Give it mythtv group and user<br>> (chown mythtv:mythtv additional.args). Change its permissions to make<br>> it only writeable by its user (chmod a=r,u=rw additional.args). In<br>> that file, you put one line with additional arguments that get added<br>> on to the end of the mythbackend command line, so put the -v record<br>> there.<br>><br>> Then restart mythbackend (systemctl restart mythtv-backend) and try<br>> tuning a channel - one of the SD ones as they tune more easily, so<br>> Prime or ChoiceTV are good ones to try. Then stop mythbackend<br>> (systemctl stop mythtv-backend) and post a copy of the section of<br>> /var/log/mythtv/mythbackend.log that contains all the output from just<br>> that run of mythbackend. To find where a run of mythbackend starts in<br>> the log, search for the text "mythbackend version:" which is on the<br>> first line mythbackend logs when it starts. The last thing that<br>> mythbackend logs when it shuts down is normally a line saying "Waiting<br>> for threads to exit.". The log will likely be way too big to post in<br>> an email, so putting it somewhere like pastebin.com is the way to go,<br>> unless you have a web server of your own you can put it on.<br>><br><br>I started on this again this morning but was interrupted by a 5 hour powercut.<br>First I changed tuning timeout from 3000 to 10000 as suggested and then created the additional.args file.<br>I selected a program in the guide and chose the "watch" option and the tuner worked perfectly.<br>Then I selected "record" and that works too.I did this several times and it seems ok now.It was using the tuner card not the HDHR.</div><div>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 mythbackend.log on google drive,the link below should allow you to access it.</div><div><a href="https://drive.google.com/open?id=0B5RRWPLTmilhVHdKN29obmpBWUU">https://drive.google.com/open?id=0B5RRWPLTmilhVHdKN29obmpBWUU</a></div><div><br></div><div>There may be messages relating to the recordings database due to switching the drive between the 2 OS versions.</div><div><br></div><div>One more question you may be able to answer: When I boot the system I get mythbackend settings utility starting (every time) what do I do to stop this?</div><div><br></div><div>I got more familiar with navigating mysql too :)</div><div><br></div><div>Thanks for the help.</div><div><br></div><div> <br><br><br><br><br></div></body></html>