<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Feb 1, 2011, at 3:20 PM, Clifford Snow wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><br><br><div class="gmail_quote">On Tue, Feb 1, 2011 at 1:32 PM, Brent Bolin <span dir="ltr"><<a href="mailto:brent.bolin@gmail.com">brent.bolin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> On Wed, Jan 26, 2011 at 7:42 PM, Michael T. Dean<br> <<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>> wrote:<br> > On 01/26/2011 08:32 PM, Kenni Lund wrote:<br> >><br> >> 2011/1/27 Clifford Snow:<br> <div class="im">>>><br> >>> In the last few days, I keep getting "Please Wait ..." when going to<br> >>> Watch<br> >>> TV. MythTV successfully records all the schedule programs and allows<br> >>> playback of the recorded items. It seems to be just the Watch TV<br> >>> selection<br> >>> that is not working.<br> >><br> </div>>> Just a "me too"...I had the *exact* same issue on one of my frontends<br> >> after upgrading to latest 0.24-fixes yesterday (I think it was ~10<br> >> days since the last upgrade), but i thought it was some local problem<br> >> (I've had other unrelated problems recently). I did try out a lot of<br> >> different things, but in the end I deleted all frontend settings, and<br> >> all of my channels on the backend. After rescanning the channels and<br> >> configuring audio and video on the frontend, the problem was solved -<br> >> or at least it didn't occur any more.<br> >><br> >> Someone who still has the issue should probably hook gdb into the<br> >> process, to see what's going on.<br> ><br> > Note, also, that it seems that 2 of our experts may be hot on the trail of<br> > fixing this issue.<br></blockquote><div><br></div><div>If the experts need any additional logs or other data, they just need to ask.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> ><br> > Which capture devices are you all using? They seem to have found an issue<br> > that may affect Live TV for all HD-PVR users (and possibly other slow-tuning<br> > devices)<br></blockquote><div> </div><div>I have two HVR-1600 capture cards. </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> I've seen this a couple of times. Only when using LiveTV. Rarely use<br> LiveTV only for news in the morning.<br></blockquote><div><br></div><div>I only experience the hanging with LiveTV. Never any problems with playback of previously recorded material. My configuration allows me to watch live TV directly on the TV without using MythTV or its capture cards. But it would be nice not having to keep explaining to my wife that if she wants to watch live tv, which setup to use. </div> <div><br></div><div>Clifford</div><div> </div></div></blockquote></div><br><div>I'm using two KWorld ATSC-110 DVB cards.</div><div><br></div><div>I too had to drag out the old rabbit ears to hook-up to TV so wifee can watch Live TV. Just when I finally had her convince to using MythTV, now this happens. Oh well WAF is back at zero!</div><div><br></div><div>FWIW, I have done the following steps, still unsuccessful at watching Live TV on Linux frontend. Live TV works fine on Backend. Frontend on MAC OSX also works fine.</div><div>1. Delete all capture cards and Input sources on backend. Rescan channel listings and ran mythfilldatabase.</div><div>2. Reinstall frontend with Mythbuntu 10.10 on new hard disk. Sudo apt-get update/upgrade to pull latest packages and kernel.</div><div>3. Re did lircd.conf and lircrc files. IRW responds to all key presses correctly in terminal, but seems to be borked in frontend that causes hang when I navigate to "Watch TV" with my Harmony remote. Note that if I use my keyboard to navigate to "Watch TV", everything works fine.</div><div><br></div><div>Please devs, let us know if you need any more info. I would love for this issue to be fixed soon.</div><div><br></div></body></html>