On Sun, Mar 10, 2013 at 5:58 PM, Robert M. Riches Jr. <span dir="ltr"><<a href="mailto:rm.riches@jacob21819.net" target="_blank">rm.riches@jacob21819.net</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
With the version 0.25-20120418.3.mga2 packages on Mageia 2, all<br>
three items that were supposed to record Friday evening (March 8)<br>
were basically zero length--effectively failed to record. Two<br>
were based on the off-the-air program guide, and one was a manual<br>
entry. Also, the red light on the Hauppauge USB tuner was off,<br>
and live TV was not working. After a restart of mythbackend,<br>
live TV worked, and yesterday evening's two recordings appear to<br>
have been recorded. I was not able to find a needle in the<br>
haystack of logs that appeared to indicate the cause.<br>
<br>
With other/past experiences with MythTV not correctly handling<br>
the transition to DST (recordings off by an hour), I'm wondering<br>
whether the switch to DST last night (just over 24 hours after<br>
the missed/empty recordings) might have been the trigger. It<br>
seems a little unlikely that a temporary USB tuner outage would<br>
happen so close to a DST transition.<br>
<br>
Has anyone else noticed a correlation between DST transitions<br>
and missed/empty recordings?<br></blockquote><div><br></div><div>My understanding is that 0.26 is the only version of Myth that current is DST "proper" in how it handles the change. I could be wrong but I believe that is the case.<br>
</div></div>