Resolve a conflict by splitting up a show?

[gapgapman]

I have run into this situation several times. You have a one hour show that you record every week, "Fringe" for example. Along comes another show like "American Idol" (for my wife, of course) and she would like me to record it as much of it as possible. So if the first hour or the second hour of Amer Idol overlaps with Fringe, I get a conflict message. All is good so far. The options it gives me on the conflict resolution are to cancel Fringe or cancel American Idol. Is there any way to have an conflict resolution option to record just the hour of American Idol that doesn't overlap with Fringe? i know I can set it up to record manually, but wondered if this was a reasonable wishlist item?

Thanks,
gapgapman

[eavdmeer]

I am really surprised to see no response to this wishlist request. I was about to start a wishlist entry of my own, but decided to do the right thing and do a search first.

This issue should really be addressed. I've run into it too many times and it's one of my big turnoffs in gbpvr. If you have two shows that overlap as little as a single minute, one of the two simply won't be recorded! That's nothing short of awful!

It would be so simple to implement a 'first come first served' kind of solution to this. Just add two options in the conflict resolution:

1. Shift up start time of recording B to resolve conflict
2. Shift down end time of recording A to resolve conflict.

If necessary, you could even issue a warning that shifting the start or stop time will effectively not record the entire show.

[johnsonx42]

sub,

In lieu of adding additional options and program logic, perhaps you could allow negative padding?

Then when setting up a recording, one could make the recording start late or end early as needed. Likewise, if a one-time conflict comes up, one could go update the padding in the problem recording to resolve the conflict as desired.

I realize that depending on how your code works, allowing backwards padding may be simple or may be a major undertaking because it invalidates a bunch of logic. I'm just tossing out the idea...

I've run into this situation too; some network shows here are scheduled to run 2 minutes past the top of the hour, or start 1 minute before the hour (yes, it's really stupid that they do that). Since I have 2 tuners it's rarely been a major problem, but for those who depend on an STB adding another tuner is non-trivial (another STB, another blaster, etc.) and may even add a monthly fee.

[sub]

There is already a <AllowedBeginningOverlap> setting in config.xml that specifies how long an overlap is allowed without causing a conflict. The default is three minutes. It'll always prefer to record the end of the previous show.

I dont intend to put anything in the GUI to control how overlaps behave. Too messy, and also confusing for a lot of people.

[johnsonx42]

one of these days someone should put together documentation on all config.xml options. not me of course, but someone

[martint123]

The usual response to this request is to get another tuner
I guess it is the real solution if the problem is happening enough to make the request.

[gapgapman]

Thanks for the input. Another tuner isn't really an option, since that would mean another STB, which also, isn't really an option. Thought it was worth a try, since I have run into this several times recently. Cheers.