[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mythtv-users
Subject:    Re: [mythtv-users] Schedule conflicted with itself causing show to
From:       Kevin Kuphal <kkuphal () gmail ! com>
Date:       2009-01-30 19:49:29
Message-ID: 3a83b0a90901301149t71233e00q4582f9c74b006185 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Fri, Jan 30, 2009 at 1:44 PM, Allen Edwards <allen.p.edwards@gmail.com>wrote:

>
>
> On Fri, Jan 30, 2009 at 11:00 AM, Michael T. Dean <mtdean@thirdcontact.com
> > wrote:
>
>> On 01/30/2009 01:45 PM, Allen Edwards wrote:
>>
>>> On Fri, Jan 30, 2009 at 9:40 AM, Brad DerManouelian wrote:
>>>
>>>
>>>> On Jan 30, 2009, at 9:23 AM, Marc Randolph wrote:
>>>>
>>>>  On 1/30/09, Allen Edwards wrote:
>>>>
>>>>
>>>>> 2) Stop recording the first show when the second show starts and start
>>>>>> recording the second show
>>>>>>
>>>>> I believe Myth's default is intended to be #2.  At least, that is what
>>>>> I recall that the wording implies when you configure how much time
>>>>> before and after to record... the comment at the bottom says something
>>>>> to the effect of "Extra time (before and after) are ignored when
>>>>> back-to-back recordings occur."
>>>>>
>>>> This is when you use soft-padding (the global setting). If you set hard
>>>> padding (on the individual rule) it will assume the extra time is part
>>>> of
>>>> the rule and you really want it all the time.
>>>>
>>> I put the pad in the individual rule. I guess that is my problem...
>>>
>>
>> No, actually you scheduled correctly for several reasons:
>>  a) the maximum for the "Time to record before start/past end of show (in
>> seconds)" can be set to a maximum of 1800 seconds (30 minutes).
>>  b) the "Time to record before start/past end of show (in seconds)" is
>> designed for a completely different purpose
>>  c) the above description of the "Time to record before start/past end of
>> show (in seconds)" is a naive simplification.  The time will be completely
>> ignored if you have 2 back-to-back recordings--even if they're on different
>> channels as it's a capture card start up/shut down capability (and Myth will
>> use the same capture card--technically, the most preferred input--if
>> possible).  The only time this isn't true is when you specify:
>>
>> Avoid back to back recordings from different channels
>> If set, the scheduler will avoid assigning shows from different channels
>> to the same card if their end time and start time match. This will be
>> allowed when necessary in order to resolve conflicts.
>>
>> Which is there to placate people who believe that Myth should read their
>> minds.  It has the wonderful placebo effect of making people think Myth just
>> does the right thing and they seldom see the issues that are caused by their
>> refusing to just do conflict resolution/tell Myth what to do.
>>
>> It's really not that hard to click on the Upcoming Recordings page in
>> MythWeb once every 2 weeks and fix any conflicts listed.
>>
>> Mike
>>
>
> I have removed my special rule and set end late to 0 relying on my general
> setting of 300 seconds and that should take care of it until I get to a show
> and get to hear "and the winner is" and it stops recording.  At that point,
> the knowledge of who won will be replaced by a sexy voice explaining how
> myth is ruining her life.
>
> But the idea that you can check conflicts every 2 weeks is naive.  You
> really have to check every time you add a show.
>
> That said, I don't see any technical reason why myth could not have
> actually recorded what I wanted as it did not require the tuner to switch
> channels.  It would just have required myth to record one tuner twice.
>

It *could* have, but that feature does not exist and instead it did exactly
what you told it to do: Record this show for X time + 20 minutes which
introduced a conflict with the following show which was told to record at
the same time.

Kevin

[Attachment #5 (text/html)]

<br><br><div class="gmail_quote">On Fri, Jan 30, 2009 at 1:44 PM, Allen Edwards <span \
dir="ltr">&lt;<a href="mailto:allen.p.edwards@gmail.com">allen.p.edwards@gmail.com</a>&gt;</span> \
wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, \
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <br><br><div \
class="gmail_quote"><div><div></div><div class="Wj3C7c">On Fri, Jan 30, 2009 at 11:00 \
AM, Michael T. Dean <span dir="ltr">&lt;<a href="mailto:mtdean@thirdcontact.com" \
target="_blank">mtdean@thirdcontact.com</a>&gt;</span> wrote:<br> <blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"> On 01/30/2009 01:45 PM, Allen Edwards wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); \
margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div> On Fri, Jan 30, 2009 at 9:40 AM, \
Brad DerManouelian wrote:<br>  &nbsp;<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, \
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div> On Jan 30, 2009, at 9:23 \
AM, Marc Randolph wrote:<br> <br></div><div>
&nbsp;On 1/30/09, Allen Edwards wrote:<br>
 &nbsp; &nbsp;<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, \
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;">


2) Stop recording the first show when the second show starts and start<br>
recording the second show<br>
</blockquote></div>
I believe Myth&#39;s default is intended to be #2. &nbsp;At least, that is \
what<div><br> I recall that the wording implies when you configure how much time<br>
before and after to record... the comment at the bottom says something<br>
to the effect of &quot;Extra time (before and after) are ignored when<br>
back-to-back recordings occur.&quot;<br>
</div></blockquote><div>
This is when you use soft-padding (the global setting). If you set hard<br>
padding (on the individual rule) it will assume the extra time is part of<br>
the rule and you really want it all the time.<br>
</div></blockquote>
I put the pad in the individual rule. I guess that is my problem...<br>
</blockquote>
<br>
No, actually you scheduled correctly for several reasons:<br>
&nbsp;a) the maximum for the &quot;Time to record before start/past end of show (in \
seconds)&quot; can be set to a maximum of 1800 seconds (30 minutes).<br> &nbsp;b) the \
&quot;Time to record before start/past end of show (in seconds)&quot; is designed for \
a completely different purpose<br> &nbsp;c) the above description of the &quot;Time \
to record before start/past end of show (in seconds)&quot; is a naive simplification. \
&nbsp;The time will be completely ignored if you have 2 back-to-back recordings--even \
if they&#39;re on different channels as it&#39;s a capture card start up/shut down \
capability (and Myth will use the same capture card--technically, the most preferred \
input--if possible). &nbsp;The only time this isn&#39;t true is when you specify:<br>


<br>
Avoid back to back recordings from different channels<br>
If set, the scheduler will avoid assigning shows from different channels to the same \
card if their end time and start time match. This will be allowed when necessary in \
order to resolve conflicts.<br> <br>
Which is there to placate people who believe that Myth should read their minds. \
&nbsp;It has the wonderful placebo effect of making people think Myth just does the \
right thing and they seldom see the issues that are caused by their refusing to just \
do conflict resolution/tell Myth what to do.<br>


<br>
It&#39;s really not that hard to click on the Upcoming Recordings page in MythWeb \
once every 2 weeks and fix any conflicts listed.<br> <br>
Mike<div><div></div><div></div></div></blockquote><div><br></div></div></div><div>I \
have removed my special rule and set end late to 0 relying on my general setting of \
300 seconds and that should take care of it until I get to a show and get to hear \
&quot;and the winner is&quot; and it stops recording. &nbsp;At that point, the \
knowledge of who won will be replaced by a sexy voice explaining how myth is ruining \
her life.</div>

<div><br></div><div>But the idea that you can check conflicts every 2 weeks is naive. \
&nbsp;You really have to check every time you add a \
show.</div><div><br></div><div>That said, I don&#39;t see any technical reason why \
myth could not have actually recorded what I wanted as it did not require the tuner \
to switch channels. &nbsp;It would just have required myth to record one tuner \
twice.</div> </div></blockquote><div><br>It *could* have, but that feature does not \
exist and instead it did exactly what you told it to do: Record this show for X time \
+ 20 minutes which introduced a conflict with the following show which was told to \
record at the same time.<br> <br>Kevin</div></div><br>



_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic