Question on why Sage is reporting a future conflict

[ace007]

I sent this to support yesterday and have not heard back yet but I thought I might pose it to you all to see if you have any ideas:

I’m running the latest beta version of Sage 7 and have 4 HDHR tuners and a hauppauge analog tuner to pick up non QAM channels via a Comcast box.

Curious why Sage is reporting a conflict next week on Monday. All of the channels are on the HDHR. All of the recording also have a small amount of buffer which is causing the overlap.

So can see below that “Chuck” and “House” recording from 7-8:02 will cross over with “The Event” and “The Chicago Code” which start around 7:58-9:02. So at the 8PM time I need 4 tuners which is what I have. At 9 PM I’ll have a cross over between “The Event” and “The Chicago Code” and “20/20” and “Hawaii Five-o” again needing 4 tuners max at the 9 pm block.

"The Event" at Mon, Apr 18 8:00PM on 653 KUSADT
from favourite: The Event KUSADT First Runs
• of "Chuck" at Mon, Apr 18 7:00PM on 653 KUSADT Silicondust HDHomeRun Tuner 101AEA75-0
• of "House" at Mon, Apr 18 7:00PM on 655 KDVRDT Silicondust HDHomeRun Tuner 101AEA75-1
• of "20/20" at Mon, Apr 18 9:00PM on 7 KMGH Silicondust HDHomeRun Tuner 101AEA75-1
• of "Hawaii Five-0" at Mon, Apr 18 9:00PM on 654 KCNCDT Silicondust HDHomeRun Tuner 10144529-1
• of "The Chicago Code" at Mon, Apr 18 8:00PM on 655 KDVRDT Silicondust HDHomeRun Tuner 10144529-0

I’d appreciate any thoughts on this and if you need any other info let me know. I have appended above what tuner Sage currently has scheduled for each recording as well so I can see that it is using all the tuners.

[gplasky]

You might want to look at the options in your Detailed Setup-Customize- "remove padding on back to back favorites on the same channel". Enable it and that may help. And you can always tell it to ignore the conflict.

Gerry

[ace007]

I would prefer to not tell it to ignore the padding since so many shows start earlier then the scheduled time by a min or two. I could also modify the favorites to remove the padding. I just want to know why Sage is reporting a conflict when I should have enough tuners to handle the crossover.

thanks

Rob

[GKusnick]

Have you looked at the Parallel Schedule to see what's happening with tuner 10144529-1 at 8:00?

[sleonard]

There have been a few occasions in the past when I tried to start watching something live and immediately get a conflict notification. When I look at the Parallel Schedule I find that there is a free tuner and there should not be a conflict but Sage insists that there is.

It's only happened a few times and it wasn't important right then so I just made a note to myself to report it on the forums or fill out a bug report but end up forgetting.

S

[ace007]

Originally Posted by GKusnick

Have you looked at the Parallel Schedule to see what's happening with tuner 10144529-1 at 8:00?

That tuner is doing nothing at all until Hawaii-five O kicks off at 9 or with the pad 8:58.

[ace007]

Originally Posted by ace007

That tuner is doing nothing at all until Hawaii-five O kicks off at 9 or with the pad 8:58.

Interesting. I went back and drew everything out on paper I can see there is no available slot. Even though 29-1 is doing nothing until 8:58 the conflicting recording needs a slot from 7:58-9:02.

I guess I'll add a request to the feature request link to have a setting that sys Sage can remove padding only if it creates a conflict.