<div dir="ltr"><div class="gmail_quote">On Tue, Aug 26, 2008 at 6:14 PM, Yeechang Lee <span dir="ltr"><<a href="mailto:ylee@pobox.com">ylee@pobox.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="Ih2E3d">Kevin Kuphal <<a href="mailto:kkuphal@gmail.com">kkuphal@gmail.com</a>> says:<br></div>
<div class="Ih2E3d">> I would agree that the autoexpire list could be improved to take<br>> this into account when displaying the list of shows eligable for<br>> expiration but at first blush, it seems that it would have to take<br>
> into account the current recording schedule in order to make such<br>> determinations and while possible, again falls into a feature<br>> request area.<br><br></div>I agree that, if discussing revamping the AutoExpire List, this is<br>
turning into a feature request thread. I do not think such a revamping<br>is necessary or even (in most cases) desirable, though. There is a<br>simple solution (if I understand the weightings right): Set<br>SGweightLocalStarting to 0 by default.<br>
<br>This solution has the advantage of meshing with the exsting AutoExpire<br>List, the existing documentation, and simple common sense. Advanced<br>users who prefer the current behavior can change SGweightLocalStarting<br>
to whatever they want. Meanwhile, average users who know enough to set<br>up a remote NFS/Samba mount (which are pretty easy in the grand scheme<br>of things Linux and MythTV) should not have to also learn SQL syntax<br>to manually create the requisite rows in the settings table.</blockquote>
<div> </div>
<div>I would tend to agree for the situation of the single tuner or solo recording scenario. A user that has only one tuner but local and remote storage will never use the remote storage if I understand the weighting properly. The same is true for multi-tuner configurations where multiple simultaneous recordings are infrequent. I'm not sure if a blanket 0 weight is best or dynamically weighting it to zero in single tuner/recording scenarios but leaving it as-is for others is best.</div>
<div> </div>
<div>Kevin</div></div></div>