Number of Days to Schedule Recordings

[NetworkGuy]

Are there any plans to increase this beyond 14 days with the carney re-write?

[KeithAbbott]

Maybe I'm not understanding your post, but I would think this would be more a limitation of the EPG data than carny.

[EnterNoEscape]

That's just a UI change, there's nothing stopping you from changing it manually in Sage.properties. Someone just needs to edit the default STV to allow a greater range.

[wayner]

Originally Posted by KeithAbbott

Maybe I'm not understanding your post, but I would think this would be more a limitation of the EPG data than carny.

It appears to me that SD seems to contain data farther into the future. Under the old EPG I think the best I ever got was 14 days. Under SD I am pretty sure that I have seen close to 21 days at times. But I rarely plan that far into the future.

[stanger89]

The other question is what good does it do? The schedule beyond maybe 7 days seems to not be very useful already. When I look well into the future I see lot of stuff that's syndicated scheduled to record that never actually will be, because out past a week or so, the guide data (even SD I think) just has show IDs for the airings, but they eventually get updated with Episode IDs that have already been recorded so the scheduled recordings "disappear" as they get closer.

[EnterNoEscape]

Originally Posted by stanger89

The other question is what good does it do? The schedule beyond maybe 7 days seems to not be very useful already. When I look well into the future I see lot of stuff that's syndicated scheduled to record that never actually will be, because out past a week or so, the guide data (even SD I think) just has show IDs for the airings, but they eventually get updated with Episode IDs that have already been recorded so the scheduled recordings "disappear" as they get closer.

There is one benefit to having so much guide data, but it's not really related to the Schedule. Often I can add a favorite for a show that's premiering 3 weeks out instead of making a note of it to try again later. I know you could also do a keyword favorite, but I generally don't like that approach if I just want a specific show.

I found several favorite airings linked to a real episode on 6/13. Some of them actually have non-generic descriptions too. I do see some of what you're talking about too that far out, but my point is that it's not completely useless. Also extending out to 21 days resolved one of my conflicts, so that alone might make it worth doing.

[Fuzzy]

It really just comes down to there not being a real reason NOT to remove the 14 day cap in the UI. Just a matter of it getting done, that's all. Relatively simple change, but it is still a change in the UI - which is no fun to do. :-)

[EnterNoEscape]

Originally Posted by Fuzzy

It really just comes down to there not being a real reason NOT to remove the 14 day cap in the UI. Just a matter of it getting done, that's all. Relatively simple change, but it is still a change in the UI - which is no fun to do. :-)

The only reason I can think of for why not is how it could adversely affect performance for much slower computers. It will make the Scheduler churn a little longer and does make Carny process airings a little longer.

[Fuzzy]

True, I'm not saying make the default 21... just allow it to be set higher if so desired.

[stanger89]

Originally Posted by EnterNoEscape

There is one benefit to having so much guide data, but it's not really related to the Schedule. Often I can add a favorite for a show that's premiering 3 weeks out instead of making a note of it to try again later. I know you could also do a keyword favorite, but I generally don't like that approach if I just want a specific show.

Oh absolutely, that makes sense. The more guide data available, the better. I'm just wondering what the value is of telling Sage to actually schedule out farther. Just doesn't seem like the guide data is that reliable/complete even say 7 days out.

Only real case I can see for scheduling farther out is to avoid conflicts, Sage has more airings to attempt to resolve them with, but again, given the unreliability, incompleteness of the more distant data, that benefit seems somewhat dubious.

[EnterNoEscape]

Originally Posted by stanger89

Only real case I can see for scheduling farther out is to avoid conflicts, Sage has more airings to attempt to resolve them with, but again, given the unreliability, incompleteness of the more distant data, that benefit seems somewhat dubious.

I would agree with this and I will not argue that they don't change things often even up until a few hours before the actual airing, but I have seen conflicts disappear a few days after they appeared and the reason was because another airing just a little further out was now visible to the scheduler. I'd rather not see the conflict.

[Tiki]

Sage V9 made a change to the scheduled (at least in 9.012) where it no longer uses all available EPG data for conflict resolution. In v7, if you had 12 days of data, but told Sage to schedule 7 days in advance, if there was a conflict on day 7, it would look out to days 8-12 to see if it could resolve the conflict. In v9.012 it doesn't and instead just displays the conflict icon. Has this behavior been fixed with the latest update, or are there plans to do so?

[EnterNoEscape]

I'm not aware of any changes in that area. The Scheduler likely changed a bit between v7 and v9 which might have lead to some slightly different behavior than in the past. It also has a timeout for how long it will try to resolve conflicts before posting the new schedule that might be affecting you at random.

[Narflex]

Originally Posted by Tiki

Sage V9 made a change to the scheduled (at least in 9.012) where it no longer uses all available EPG data for conflict resolution. In v7, if you had 12 days of data, but told Sage to schedule 7 days in advance, if there was a conflict on day 7, it would look out to days 8-12 to see if it could resolve the conflict. In v9.012 it doesn't and instead just displays the conflict icon. Has this behavior been fixed with the latest update, or are there plans to do so?

At first I was going to tell you that you are wrong...but then I went and diff'd the V7 to V9 code and you are right. There was a change made to fix another bug where changing channel restrictions for a Favorite didn't properly remove the entries from the schedule...although I'm not sure why the change is actually needed, because it looks redundant to some degree.

If you're a dev, you can test it out by removing the checks for 'god.isMustSee(kitty[p])' in Scheduler.processMustSeeForAirs (lines 637 and 651). And that *should* revert to the old behavior. I don't have a problem approving a change like that because there was likely some other dependence relating to how we did things in Fiber that made me do it.

[Fuzzy]

Jeff... your object names man... :-)

[Tiki]

Originally Posted by Narflex

At first I was going to tell you that you are wrong...but then I went and diff'd the V7 to V9 code and you are right. There was a change made to fix another bug where changing channel restrictions for a Favorite didn't properly remove the entries from the schedule...although I'm not sure why the change is actually needed, because it looks redundant to some degree.

If you're a dev, you can test it out by removing the checks for 'god.isMustSee(kitty[p])' in Scheduler.processMustSeeForAirs (lines 637 and 651). And that *should* revert to the old behavior. I don't have a problem approving a change like that because there was likely some other dependence relating to how we did things in Fiber that made me do it.

Thanks for investigating. Unfortunately, I have not done any Java programming and don't have a dev environment set up. Any chance someone here could try the change?

[EnterNoEscape]

Originally Posted by Tiki

Thanks for investigating. Unfortunately, I have not done any Java programming and don't have a dev environment set up. Any chance someone here could try the change?

Check your PM.

[EnterNoEscape]

Tiki reports that this appears to have corrected the issue. I'll submit the changes with some comments on why we removed the check.

[GoAWest]

Manually setting the scheduling_lookahead = [e.g. 23x24x60x60x1000=big number] env in Sage.properties works (e.g. old EPG=14-days, new Schedules Direct EPG = 21 days, or so] and is reflected in the GUI. But if you open the setting via the GUI it reverts to the 14-day max value even if the user doesn't accept/change the value. Hopefully the proposed GUI update will set this range to a (much?) larger max value. And let the user select the best value he wants equal to or smaller than that value based on guide data length or his pref.

[EnterNoEscape]

The STV change was made and committed. The default is still 14 days, but the range now goes up to 21. The next SageTV release will have this change.