<div class="gmail_quote">On Wed, Oct 10, 2012 at 12:26 PM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com" target="_blank">mtdean@thirdcontact.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 10/09/2012 11:18 AM, Tom Dexter wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, Oct 3, 2012 at 12:45 PM, Steven Adeff wrote:<div class="im"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, Oct 3, 2012 at 12:19 PM, Monkey Pet wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have been happy with mythtv 0.26 and LiveTV using HD Homerun tuners, so<br>
what specifically are you refering to? can you point to some bugs? I have<br>
been running it for a few weeks now and haven't noticed anything major.<br>
</blockquote>
If you are watching live tv and Myth needs to use the tuner to record<br>
something it will set that recording to the LiveTV recording group and<br>
set the autoexpire to what you have set for LiveTV. If you exit from<br>
watching during the recording it will stop recording the show as well.<br>
</blockquote></div>
Wow...am I glad I happened to read this one. Thanks for pointing that<div class="im"><br>
out. I may have to hold off on going to 0.25. Is there an existing<br>
bug on this one I can follow?<br>
<br>
</div></blockquote>
<br>
FWIW, I'm pretty sure we've had similar problems with Live TV affecting recording groups and/or recordings to terminate when exiting Live TV since at least 0.21, so it's nothing new to 0.25 or 0.26.<br>
<br>
Mike<br></blockquote></div><br>Possibly that's true for certain scenarios, but 0.25 is the first version where I encountered this bug, and judging from some other responses, quite a few other users first encountered this in 0.25 as well. Has anyone done a git bisect to find the offending commit, or is it a case where major changes were made and this problem occurred as a byproduct?<br>
<br>Karl<br>