<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Sep 23, 2014 at 10:46 AM, Carl Hunter <span dir="ltr"><<a href="mailto:cdhunter2@yahoo.com" target="_blank">cdhunter2@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 9/22/2014 1:25 PM, Rob Owens wrote:<span class=""><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
----- Original Message -----<br>
Carl, thanks for working on this. Unfortunately I'm not a developer so I can't help you w/ these errors, but I'm watching in anticipation...<br>
<br>
-Rob<br>
</blockquote>
<br></span>
I keep poking away at this but unless I get some insight from the Myth developers I'm really just jumping into the deep end and flailing away. I'm getting complaints from my parents about their set up now too so it still is a priority to me.<br></blockquote></div><br></div><div class="gmail_extra">This reply ended up in my spam filter for some reason. Anyway, I was going to suggest that you try to ping the mythtv-dev list. Although it's possible that the key developer(s) that worked on that code are no longer with the project. A git-bisect could be helpful here, too, to identify the exact commit which broke it, but those are a pain with mythtv because of the database versioning. You'd really need an isolated system (or chroot?) to test with.<br><br></div><div class="gmail_extra">Karl<br></div></div>