<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On 2012-03-04, at 6:09 PM, Daniel Kristjansson wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">But really this is good enough as is. An input group will<br>prevent the scheduler from trying to record things that it<br>can not. That a more complicated setup might be able to<br>record a few more things isn't worth worrying about.</span></blockquote></div><div><br></div>Bringing a little empirical evidence to the discussion, the script has been in place since last summer and I've never had a problem due to antenna direction. I do lots of recording and regularly max out my tuners. Initially I was going to wait for problems until a few weeks into the fall heavy recording season but I soon forgot about the script until that ticket change comment popped up. So, basically it has seen a decent number of scenarios.<div><div><br></div><div>Oh, at the time I did notice that I was always getting two RecStarted events within a few seconds of each other. I added throttling to my script but maybe there should only be one started event per recording?</div><div><br></div><div>I just added logging to my script to see if there are still duplicate events.</div><div><br></div><div>- George</div></div></body></html>