A blatantly missed recording, documented with screenshots and logs. [RESOLVED]

[lysdexical]

Originally Posted by Opus4

By default, version 6 created a recording schedule for the next 3 days; in version 7, it is 14 days

Thanks! Also, using a smaller window should prevent the wait-a-week-for-the-HD-version issue that happened tonight. If it only considers 3 days of airings it would have recorded the 9pm SGU episode, as it was the only one that had no conflicts.

[MattHelm]

Originally Posted by Spectrum

I caught SGU being not listed to record in my lineup tonight (Geeks unite!) and added it as a manual before it started. I dug a little deeper and the airing tonight @ 2100 EST was not labeled as HD and it was scheduled to record on 10/12 in HD. Yours looks to be the same. This image shows the airing scheduled on 10/12. My guess is the guide data is borked.

Bingo, ALL shows tonight are NOT marked as HD. 10/12 shows are marked HD. Channel is SYFYHD, and all newer shows are HD. (BTW, I manually recorded the 10-11 show)

[nick_l]

This is not necessarily true, as Sage will use all the guide data available to it if it encounters a conflict. In other words, if Sage can schedule all the recordings it is supposed to schedule, it only creates the schedule for the period requested (ie, 3 days in Sage 6), but if it does encounter a conflict it will use the guide data to fix the conflict and schedule the recording further out if possible.

[Brent]

I personally don't see why you wouldn't just limit the favorite setting to only record on the "HD" channel instead of telling it to only record HD airings. That would solve your problem also wouldn't it?

Oh, and the best way to avoid conflicts: Get at least one more tuner

[Fuzzy]

Originally Posted by nick_l

This is not necessarily true, as Sage will use all the guide data available to it if it encounters a conflict. In other words, if Sage can schedule all the recordings it is supposed to schedule, it only creates the schedule for the period requested (ie, 3 days in Sage 6), but if it does encounter a conflict it will use the guide data to fix the conflict and schedule the recording further out if possible.

Yeah, but that doesn't apply to this example, as this was not conflict resolution, it was simply the HD preference that caused the situation.

[bialio]

There's not a way to turn off the HD preference is there?

This happened to me also (although I caught it in time to set up a manual recording) but I'd just as soon that the scheduler used the encoder merit to make it's decisions, and not worry bout what the EPG has set for the HD field.....

btl.

[Opus4]

Originally Posted by Brent

I personally don't see why you wouldn't just limit the favorite setting to only record on the "HD" channel instead of telling it to only record HD airings. That would solve your problem also wouldn't it?

No; the EPG data on the HD channel didn't have the HD tag. And, you can't assume that all airings on HD channels are HD.

Originally Posted by bialio

There's not a way to turn off the HD preference is there?

You could try the prefer_hdtv_recordings_over_sdtv property.

- Andy

[Fuzzy]

Keep in mind, the HD preference still isn't going to prevent any show from being recorded, it is simply affecting WHEN a show is recorded. If, for some reason, NO show was tagged as HD, it would still record the 'SD' tagged airings.

[bialio]

True. But if that property eliminates that variable from the scheduling algorithm, I'm all for it. I only record shows that are in HD anyway, and the two tuners I have that are SD are well below the others in merit, so that should be all that is necessary (for me).
btl.

[stanger89]

Those of you with problem all on the same provider/lineup? Because SGU recorded fine for me last night (I forgot it was on until I saw it recording). I'm on Dish and recording SYFYHD.

Nevermind, I saw the same thing on Dish. But I'm so disconnected from what's on when I didn't even notice.

[bialio]

I'm on Dish with SYFYHD as well. It wasn't marked HD in my EPG, and there weren't any conflicts as far as tuners were concerned. It just wasn't recording it.

btl.

[MattHelm]

Originally Posted by stanger89

Nevermind, I saw the same thing on Dish. But I'm so disconnected from what's on when I didn't even notice.

That's true for me also, EXCEPT for Sci-Fi shows. I'm just a Sci-Fi nut (still don't watch them (shiver) live!)


I'm on cable in Skokie, IL.

[Spectrum]

I have Comcast in Knoxville, TN. It sounds like Zap2IT may have pooched the guide data all around on this one.

[Fuzzy]

As far as Zap2It is concerned, there are only 1 SyFyHD channel (ID:58623) in existance, so they all use the exact same guide data, and as such, everyone would be affected by the missing HD flag, regardless of what lineup you use. There is also a separate SYFY(11097), which is the same schedule as SyFyHD, and SYFYP(24533) that is the same schedule 3 hours delayed. I don't believe anyone carries a Pacific version of SyFyHD.

[Jynxed]

It's funny, I noticed that it missed SGU last night and I had to catch the later showing.

I was wondering what happened but was just going to watch for it to happen again. Good to know it's not my setup.

[UgaData]

I realized that the Tuesday night recording of SGU didn't happen on Wednesday evening. As I was looking into it, through the EPG guide data and descriptions, it appeared that both episodes were reruns.

Intervention was shown the week before.

Aftermath, although it was a new or first run, appeared to be a rerun or so I thought after reading the description given for the show in the guide (After finding the ninth chevron, Stargate personnel find themselves on the starship Destiny - not the exact wording but close enough.).

I will either watch it via Hulu or maybe I will record 2 episodes next Tuesday.

I am definitely in line with the guide data being incorrect.