<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#006600">
<br>
<div class="moz-cite-prefix">On 19/08/12 22:54, Adrian Saul wrote:<br>
</div>
<blockquote cite="mid:5030E201.4090206@gmail.com" type="cite">On
19/08/2012 10:46 PM, Adrian Saul wrote:
<br>
<blockquote type="cite">
<br>
Picked up a slightly annoying bug with 0.26 tonight - my wife
was watching a show and decided to manually record the following
program in case this one ran overtime. She went to the guide,
picked the next show and did a manual record. Instantly the two
other shows in scheduled to be recorded tonight disappeared from
upcoming recordings.
<br>
<br>
If I look at the upcoming recordings there is nothing there to
say they are in conflict or anything, there are plenty of free
tuners and it seemed happy to record it before.
<br>
If I pick the show in the guide it has nothing to say it wants
to record it.
<br>
If I do a manual record in on the show, it shows up in upcoming
recordings and the guide as "Not Listed" (WTF does that mean,
yes it is, its right there).
<br>
If I look at the recording rules it is there and I see nothing
that would prevent it recording, and preview changes shows it as
"this will be recorded" but it never appears in upcoming
recordings.
<br>
<br>
Viewing via the frontend of mythweb seem to show nothing
different, and I can find no errors or messages in the logs
relating to this.
<br>
<br>
Any ideas what is going on here? The only work around seems to
be to switch to the show when it starts and hit record.
<br>
<br>
</blockquote>
<br>
Actually I think this is related to the new timezone setup in 0.26
- if I look at the recording rule in the database, the last
scheduled recording times etc are all local time, but the view in
the frontend shows the last recorded at Aug 15 07:33AM when in
fact it was Aug 14 09:33PM (I am GMT+10, so it seems to think the
times in the DB are GMT not AEST).
<br>
<br>
Also the frontend seems to think the show is scheduled for
10AM-10AM in the rules overview. The rule in the database has
the startdate and enddate of today at 0:00, so +10 would make it
be 10am.
<br>
<br>
I am not sure this should really affect it, because it is a
"record any time on this channel" rule, and nothing to do with
timeslots etc.
<br>
<br>
_______________________________________________
<br>
mythtv-users mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://www.mythtv.org/mailman/listinfo/mythtv-users">http://www.mythtv.org/mailman/listinfo/mythtv-users</a>
<br>
</blockquote>
Adrian, I've also been seeing this since performing <br>
1) the Mysql timezone load, and<br>
2) removing my daily mythbackend reboot as no longer necessary
(wrong!).<br>
<br>
Reinstating the daily mythbackend process restart is a workaround
and temporarily removes the problem, for about 24h.<br>
I had thought it may have been shepherd (and given your GMT+10 I'm
guessing you also might be in Australia)<br>
but disabling program guide updates had no effect, I've only seen
complaints on the mailing list from GMT+10 which is why I was
looking at shepherd.<br>
Setting every don't do EIT flag I could find (overall, tuner,
channel) has also had no effect.<br>
<br>
Something else is confusing mythbackends time sense.<br>
<br>
In the past this sort of problem is usually solved by someone else
the moment I start digging into the code. I might have to try
invoking that method again and see if it works. <br>
<br>
<div class="moz-signature">-- <br>
<font face="Helvetica, Arial, sans-serif"><font>
<small><font face="serif">
Carl Lewis<br>
Manager ICT<br>
Department of Primary Industries, Parks, Water and
Environment<br>
<b>Ph</b>: 0362125150 <b>email:</b> <a
href="mailto:Carl.Lewis@dpipwe.tas.gov.au">Carl.Lewis@dpipwe.tas.gov.au</a>
</font></small>
</font></font></div>
</body>
</html>