[mythtv] [mythtv-commits] Ticket #2604: Myth does not handle overlapping recordings on the same channel

[Kevin Kuphal]

MythTV wrote:
> #2604: Myth does not handle overlapping recordings on the same channel
> -----------------------------------+----------------------------------------
>  Reporter:  myth at studio442.com.au  |        Owner:  ijr    
>      Type:  defect                 |       Status:  closed 
>  Priority:  minor                  |    Milestone:  unknown
> Component:  mythtv                 |      Version:  0.20   
>  Severity:  medium                 |   Resolution:  invalid
> -----------------------------------+----------------------------------------
> Comment (by darkstarsword at gmail.com):
>
>  I third the original poster's comments. I also find this highly annoying
>  when recording two consecutive shows and have had to resort to scheduling
>  a manual record of the entire timeslot just to be able to record both.
>
>   
You can stop using Trac as a discussion forum.  The problem is not a 
bug.  You are telling MythTV to record over by X minutes and it does 
this, resulting in a conflict with another show at the same time.   This 
"over time" set on a recording rule will cause conflict with other 
recording as it should.  You have a number of options:

1.  Do not use per recording start/end early/late options.  This will 
cause the recordings not to conflict
2.  Use end late on the first show and start late on the second so that 
their times do not overlap.  This will cause the recordings not to conflict.
3.  Use the global start/end early/late options.  This will record extra 
time before or after a show *if possible* and there are no other 
conflicts.  This will cause the recordings not to conflict.

What you are asking for is a feature request to record the contents of a 
scheduled recording into two files so that neither conflict but both get 
the recording data.  This is possible but not implemented so rightly 
defined by Isaac in Trac as not a bug.  If you care to get together as a 
group and implement this feature, I'm sure it will be happily 
considered.  There is also work on a -softpad branch of the code that is 
working towards making the scheduler work differently in regards to soft 
padding.  This would be better explained by Bruce and David who have 
been working on it. 

Kevin