<br><br><div class="gmail_quote">On Tue, Jan 10, 2012 at 10:39 AM, Greg Woods <span dir="ltr"><<a href="mailto:greg@gregandeva.net">greg@gregandeva.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Mon, 2012-01-09 at 14:14 -0600, James Roberts wrote:<br>
> At first I was going to set it to run after the mythfilldatabase and<br>
> have it automatically set any channel with the string "protected" in<br>
> it to not be visible, and I might still do that. The problem is I<br>
> still need to remove the channel from both Myth and Schedules Direct<br>
> to keep the family from screwing up the front end.<br>
<br>
</div>You might be able to avoid having to mess around with Schedules Direct<br>
if you run mythfilldatabase with --remove-new-channels. That will<br>
prevent it from creating or modifying a channel that appears in SD once<br>
you have removed it locally. The drawback is that genuine new channels<br>
in SD won't appear locally until you deal with it manually.<br>
<span class="HOEnZb"><font color="#888888"><br>
--Greg</font></span><br></blockquote></div>I'm hoping that one of the 2 better solutions will emerge, <br>1) Making a channel not visible, will make it not show when browsing the up/down buttons in live<br>2) Tuning a protected channel will display a nice, can't view this message, and let you change to another channel.<br>
<br>If either of those were the current state, I could have my script simply make the channels not visible, and run it every night, updating visible/not based on actual status, so as Charter makes changes I can enjoy as much of the paid-for content as possible.<br>