<br><br><div class="gmail_quote">On Sat, Oct 29, 2011 at 11:20 AM, Greg Grotsky <span dir="ltr"><<a href="mailto:spikeygg.mythbox@gmail.com">spikeygg.mythbox@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="gmail_quote"><div class="im">On Mon, Oct 24, 2011 at 6:47 AM, Larry T <span dir="ltr"><<a href="mailto:larryt@gmail.com" target="_blank">larryt@gmail.com</a>></span> wrote:<br><blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204, 204, 204);border-left-width:1px;border-left-style:solid" class="gmail_quote">
Somewhere along the way I lost the currently playing functionality. I still get the clock and I still get Recording screens. I don't ever get the currently playing screens that show for example the current TV program being played. <br>
<br></blockquote><div> </div></div><div>Hi Larry, I have this problem too (and have for several months). I wrote to the distribution list back in June 2011 asking if anyone else had experienced the same thing and a couple of people responded. One of them told me that it was probably me interpreting it as "broken" and that it just had been implemented differently than I expected... anyway, a few weeks back someone else opened a ticket (#10099) regarding the connection from mythfrontend to mythlcd explaining the same thing you and I are seeing. So it has been recognized and flagged. I didn't want to open a ticket without proof that it wasn't just my system but no one had come forward with a compliant -- now there are three of us. :)</div>
<div> </div><div>I miss the status info on my lcd since it enabled me to navigate myth without turning the TV on. I didn't use it very often but it was handy on occasion.</div><span class="HOEnZb"><font color="#888888"><div>
</div><div>-Greg<br></div></font></span></div>
<br></blockquote></div>Hey - good to hear from you. I spoke with Beirdo about this issue briefly in IRC and showed him that ticket you reference above. I suspect that is why he took assignment of the ticket. <br><br>When I turned up logging on the components, I was able to confirm that I was seeing what was described in the ticket. From all debug and log notes, it appears that the socket that would be providing the frontend status to the LCD is not connecting and that is why we lost this functionality. It does not appear to be any sort of configuration error or hardware error.<br>
<br>I look forward to this functionality being restored but I suspect two things are against us here. The first is that LCD display is a nice-to-have feature and not the primary functionality of the system. The second is that I bet LCDs are not widespread amongst the user base.<br>