???SageTV makes the same mistake twice??

[zoundz]

Bear with me on this. Usually SageTV manages to get things right. Twice now, it appears to have made the same mistake in scheduling recordings. I have 1 HDHR and it was scheduled to record CSI, which was set to run from 9:00 to 10:01 and Grey's Anatomy from 9:00 to 10:02. Southland, scheduled from 10:00 to 11:00 in a lower priority favorite is set for any channel, but prefers the HD which meant that there was either a 1 or 2 minute conflict. Since Southland is also running on Saturday, SageTV correctly decided to record the HD Southland on Saturday instead of the SD version tonite. All well and good.

For some inexplicable reason, however, both last week and this week, SageTV has gone ahead and recorded Southland on the HDHR on Thursday and just skipped the first 2 minutes. Up until the middle of the evening, it still had Southland scheduled for Saturday, but when I looked up a little after 10:00, it had decided to record it anyway without the first 2 minutes. I'm mystified. The Saturday airing is still in the epg and there was never any indication of a conflict from SageTV. This is exactly what happened last week. I thought at the time that the epg must have gotten changed at the last minute and SageTV must have gotten confused. Today I forced an early update of the epg and I checked it WHILE the erroneous recording of Southland was taking place. It still shows the 01 and 02 ending times for the other 2 shows and they are both correctly recorded to those ending times.

Obviously, if I go ahead and delete the bad Southland recording, it will just schedule the Saturday one again and all will be well, but it appears to have made an actual error. First time I've seen this in 4 1/2 years.

Running 6.5.9 on WinXP Pro.

Thoughts anyone? I didn't get logs.

If the same conflict exists next week I will.

[Slugger]

This is the way Sage has always behaved (at least for me). And the exact same thing happened to me last night as well with the same shows. For whatever reason, SageTV is fine with losing the first 1-5 minutes of a recording so once the GA recording stops at 22:02 Sage realizes at that point that it now has a free tuner and sees that it can start recording Southland and since it's only missed the first two minutes then Sage decides that's ok and proceeds with the recording - less the first two minutes.

I've reported this as a bug in the past, but it has yet to be addressed. My guess is that fixing it will break something else.

[amg]

I too had the exact same thing happen, though I didn't know it until I saw this thread. CSI and GA until 10:01, 10:02 on the HDHR, and Southland scheduled to record Sat at 9pm. I had 2 pvr-150 tuners idle at 10pm, and Sage recorded Southland from 10:01-11m.

I have not been keeping up with Southland, I have only seen the pilot. I went and looked at the previously aired shows and saw the last 3 episodes have done this.

I am running the latest non-beta 6.5.9. I am running the stock UI, with dynamic menus and comskip, but for the first 2 of the recordings I was running stock STV, with no plugins.

It is also my opinion there is an error in the scheduler that it is preferring to loose 1-2 minutes from the beginning of an episode rather than record it at a later time fully uncut. Especially since it was scheduled to record at the later time.

[Tiki]

Has anyone filed a bug report about this?
I've seen the same problem too, but I never filed a report...

[zoundz]

Originally Posted by Tiki

Has anyone filed a bug report about this?
I've seen the same problem too, but I never filed a report...

Not yet, I guess, but since we can be fairly certain that the first request after the bug report will be to ask for logs, we might as well wait until next week and get the logs first. If anyone sees a similar situation brewing before that, let us know up here and we can all try to get logs. What we have here is a little case of Sageheimers. It just forgot what it was doing.

[amg]

Originally Posted by Tiki

Has anyone filed a bug report about this?

I did today, after I posted to this thread.