<div><div class="gmail_quote">On Sat, Oct 1, 2011 at 1:31 AM, Doug Scoular <span dir="ltr"><<a href="mailto:dscoular@cisco.com">dscoular@cisco.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br>
Been having a problem for a while now with my mythbuntu combined<br>
backend/frontend:<br>
<br>
MythTV Version : v0.24.1-85-ge16613a<br>
MythTV Branch : fixes/0.24<br>
Network Protocol : 63<br>
Library API : 0.24.20110505-1<br>
QT Version : 4.7.2<br>
<br>
In live tv, quite frequently, the frontend tunes to a channel and<br>
gets a picture without issue but then a couple of seconds later I'll get<br>
the tuning dialog trying to tune again to the already tuned channel.<br>
Then the "you should have got a signal by now..." dialog pops up under<br>
the tuning dialog and the tuning dialog will eventually tune and<br>
disappear. This may seemingly pointless tuning may repeat a couple or<br>
more times.<br>
<br>
I'm wondering if my constant upgrading of the mythtv database from<br>
~0.12 over the years has led to this problem.<br>
<br>
I'm beginning to wonder if I should do a clean install after<br>
exporting my recordings and then import them or if there is some other<br>
better approach.<br>
<br>
Has anyone seen a similar issue ?<br>
<br>
Any thoughts hugely appreciated.<br>
<br>
Cheers,<br>
<br>
Doug<br>
<br>
_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org" class="vt-p">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank" class="vt-p">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
</blockquote></div><div><br></div>What a coincidence. My wife just noticed the same thing today (at least mentioned it to me today). <div>I had the backend logging turned up to try to catch the 0B recording issue (haven't seen it since I did that though), but after the upgrade it slowed the machine down too much. Once I went back to informative, the locking issues went away.</div>
<div><br></div><div>After I upgraded to 0.24.1 today, I noticed it took a second or two longer to tune than previously (used to go to TLAM almost instantly, after the upgrade it went to TL__, then TLa_, then TLAM over the span of about 2 seconds).</div>
<div><br></div><div>Reducing the logging fixed that. For reference, I was logging "important,record,file,network,commflag" before. Now just "important."</div><div><br></div><div>Don't know if that's the same issue you're seeing or not though.<br>
<br>Daniel</div></div><div><br></div>