<br><br><div class="gmail_quote">On Sun, Nov 25, 2012 at 8:14 PM, John Pilkington <span dir="ltr"><<a href="mailto:J.Pilk@tesco.net" target="_blank">J.Pilk@tesco.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 25/11/12 06:56, Brett Randall wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
On Sun, Nov 25, 2012 at 5:48 PM, Nick Rout <<a href="mailto:nick.rout@gmail.com" target="_blank">nick.rout@gmail.com</a><br></div><div class="im">
<mailto:<a href="mailto:nick.rout@gmail.com" target="_blank">nick.rout@gmail.com</a>>> wrote:<br>
<br>
<br>
<br>
On Sun, Nov 25, 2012 at 6:50 PM, Brett Randall<br></div><div class="im">
<<a href="mailto:brett.randall@gmail.com" target="_blank">brett.randall@gmail.com</a> <mailto:<a href="mailto:brett.randall@gmail.com" target="_blank">brett.randall@gmail.<u></u>com</a>>> wrote:<br>
<br>
<br>
On Fri, Nov 23, 2012 at 11:42 PM, John Pilkington<br></div><div class="im">
<<a href="mailto:J.Pilk@tesco.net" target="_blank">J.Pilk@tesco.net</a> <mailto:<a href="mailto:J.Pilk@tesco.net" target="_blank">J.Pilk@tesco.net</a>>> wrote:<br>
<br>
On 23/11/12 12:02, Mike Perkins wrote:<br>
<br>
On 23/11/12 10:37, Brett Randall wrote:<br>
<br>
Hi all<br>
<br>
I've been running MythTV (under Mythbuntu 12.04.1<br>
LTS) as my media centre<br>
for the last year and, other than the occasional<br>
hiccup, it's been great<br>
and my family has loved it. I originally installed<br>
0.24 but a few months<br>
ago upgraded to 0.25. It remained stable after doing so.<br>
<br>
However, this last couple of weeks, it has lost the<br>
plot. In typical Myth<br>
fashion, the more I try to fix it with software<br>
updates, firmware<br>
changes,<br>
etc, the worse it gets. The version I'm currently<br>
running (from a Ubuntu<br></div>
package) is 0.25.0+fixes.20120410.1f5962a-<u></u>__0ubuntu1.<div class="im"><br>
<br>
The last few days, as soon as a particular program<br>
comes on ("Finley the<br>
Fire Engine" - NO it is not for me ;-) ), Myth<br>
freaks out with a PAT<br>
error<br>
and no longer records anything until I restart the<br>
backend process<br>
(normally having to use "kill -9" to stop it). The<br>
exact log entries are:<br>
<br>
...<br>
Nov 23 06:25:48 myth mythbackend[11231]: E DVBRead<br>
dtvsignalmonitor.cpp:321<br></div>
(HandlePAT) DTVSM(/dev/dvb/adapter0/__<u></u>frontend0):<div><div class="h5"><br>
Program #2370 not<br>
found in<br>
PAT!#012Program Association Section#012 PSIP<br>
tableID(0x0) length(41)<br>
extension(0x221)#012 version(16) current(1)<br>
section(0)<br>
last_section(0)#012 tsid(545)<br>
programCount(8)#012 program number<br>
0 has PID 0x0010#012 program number 544 has PID<br>
0x0102#012 program<br>
number 545 has PID 0x0100#012 program number<br>
546 has PID 0x0101#012<br>
program number 547 has PID 0x0103#012 program<br>
number 548 has PID<br>
0x0106#012 program number 550 has PID 0x0104#012<br>
program number 551<br>
has PID 0x0105<br>
...<br>
<br>
Definitely value any advice in getting around this!<br>
<br>
This generally means that since you last scanned, the<br>
contents of the<br>
transport stream have changed. Either a channel which<br>
was thought to<br>
exist no longer does[1] or something extra has now appeared.<br>
<br>
Since the internal table of channels within the<br>
multiplex which mythtv<br>
builds now no longer corresponds to what it is<br>
receiving, it is telling<br>
you so. Of course, this also means that there may be<br>
errors trying to<br>
extract a stream from the multiplex, which is what you<br>
are observing.<br>
<br>
The standard answer is to rescan, which may solve your<br>
problem. I'm not<br>
sure where in the world you are so it may mean you need<br>
to take other<br>
action, such as updating your SD lineup or editing your<br>
channel data in<br>
mythtv-setup.<br>
<br>
[1] It /is/ possible to have part-time channels; mythtv<br>
does the right<br>
thing in this case.<br>
<br>
<br>
That would be my suggestion too, but he says he's in<br>
Australia and did all the standard delete-and-rescan things<br>
and still has the problem. Maybe the EIT hasn't caught up<br>
yet; maybe the multiplex tables aren't fully populated. And<br>
don't people in Oz usually use Shephard(?) data? But I doubt<br>
that that is the problem - it sounds like reception rather<br>
than scheduling difficulties.<br>
<br>
Did the scans find duplicate channels? Perhaps you have<br>
more transports defined than you really need.<br>
<br>
<br>
Thanks for your thoughts. Reception isn't the problem - I get<br>
75% signal strength on that channel and can watch it just fine<br>
live, without drops. The entire program guide is there, too,<br>
even though it took about an hour to populate after I cleared<br>
the video sources, transports, etc out.<br>
<br>
I've managed to fix it, in a manner of speaking, for now. I<br>
deleted the Recording Rule for "Finley the Fire Engine" (the<br>
program which the backend would freeze on each morning with the<br>
PAT error) and the next day, the remainder of recordings worked.<br>
Today, the recordings also worked without a restart.<br>
<br>
<br>
Is Finley the only programme you record from that channel? Could it<br>
be a tuning problem needing a rescan of that transport? (Live TV can<br>
be set to use a different tuning method, I think they are called<br>
slow and fast and I can't recall where to set it or what it does,<br>
but it can result in a channel recording correctly but not working<br>
in Live TV, and presumably vice versa.)<br>
<br>
<br>
No, I record about 15 shows from that channel, the rest are recording<br>
fine. But looking back, every time Myth would freeze, it would be on<br>
that one show.<br>
<br>
Brett.<br>
<br>
</div></div></blockquote>
<br>
Is this a part-time channel? I haven't seen a freeze such as you report, but scheduling the first recording after startup will give me an apparently blank recording which plays fine after a run through mythcutprojectx with no cutlist. Similar funnies on recording over closedown. You could check by delaying recording start,<br>
<br>
In the UK this affects eg Cbeebies/BBC FOUR at 7 pm.<span class="HOEnZb"><font color="#888888"><br>
<br>
John</font></span></blockquote><div><br>Not part-time that I know of? I just noticed that it stopped recording again with the same error at 2pm yesterday (normally 7am). Again, recording from the same channel, same error, but different time.<br>
<br>I've written a Perl script (code below, in case anyone else ever wants it) which I've set in cron to run every minute. This will solve my problems for now :)<br><br>Thanks<br><br>Brett.<br><br><br>#!/usr/bin/perl -w<br>
<br>use strict;<br><br># Temporary file for storing the last time a PAT error occurred<br>my $tmp_file = "/tmp/last_pat_check_time";<br><br># Log file we're scanning<br>my $log_file = "/var/log/mythtv/mythbackend.log";<br>
<br># Code<br>my ($last_time,$need_to_restart,$cur_time);<br>if (-f $tmp_file) {<br> open (IN,$tmp_file);<br> $last_time = <IN>;<br> close IN;<br>}<br><br>open (IN,$log_file);<br>while (<IN>) {<br> chomp;<br>
($cur_time) = (/^(\w+\s+\d+\s+\d+\:\d+\:\d+)/);<br> if (/not found in PAT/) {<br> $need_to_restart = 1;<br> }<br> if ($last_time) {<br> $need_to_restart = 0 if $cur_time eq $last_time;<br> }<br>
}<br>close IN;<br><br>if ($need_to_restart) {<br> system "/etc/init.d/mythtv-backend stop";<br> system "/usr/bin/killall -9 mythbackend";<br> system "/etc/init.d/mythtv-backend start";<br>
open (OUT,">$tmp_file");<br> print OUT $cur_time;<br> close OUT;<br>}<br><br>exit 0; <br></div></div>