World Series

[HuMan321]

Guide data did not have game 7 listed so missed first 45 minutes. I had to make Manuel recordings to cover and then 13 minutes later the guide updated and Sage threw an error about the guide change and started recording game 7.

PO’d about this really and the rub is we now pay for this guide data...

[rkulagow]

[I work for Schedules Direct]

Did you open a ticket with us? We had 2 tickets open this afternoon about the Schedules Direct guide data not having the World Series game, but in both instances the client didn't have a fresh schedule, because Game 7 was there.

[HuMan321]

I did not as I only found it out when I went to start watching the game on delay.
I would have assumed the normal refreshing/updating of the guide would have had the game scheduled. ( I would have also scheduled manual recordings during the time slot if noticed earlier)
I have come to rely on that so not checking in advance to see for guide updates, but probably will in the future in best of 5, best of 7 type series.

[rkulagow]

Please open a ticket anyway so that I can check the affected stationID.

[HuMan321]

Ok - I can do that. Can you please post link on how to do that?
Thanks

[EnterNoEscape]

I'm not a sports person, but I think I observed this too because an airing changed titles on me when I looked at some recordings from last night. SageTV looks for updated/new guide data every 24 hours. I my case, that means the airing was there, but likely arrived within the 24 hour window. When the guide data updated again, it updated the already recorded airing to what it actually was. I've seen this happen in the past even with the free guide data we used to have, but I think I've been seeing it happen more frequently. Maybe we should change SageTV to check every 12 hours instead if this is going to be a trend. If I read correctly, Schedules Direct updates it's guide data at least 4 times a day for North America, so we are likely missing a lot of last minute schedule changes.

[Tiki]

Originally Posted by EnterNoEscape

I'm not a sports person, but I think I observed this too because an airing changed titles on me when I looked at some recordings from last night. SageTV looks for updated/new guide data every 24 hours. I my case, that means the airing was there, but likely arrived within the 24 hour window. When the guide data updated again, it updated the already recorded airing to what it actually was. I've seen this happen in the past even with the free guide data we used to have, but I think I've been seeing it happen more frequently. Maybe we should change SageTV to check every 12 hours instead if this is going to be a trend. If I read correctly, Schedules Direct updates it's guide data at least 4 times a day for North America, so we are likely missing a lot of last minute schedule changes.

When Sage does it's daily updates it checks for an updated hash and only actually downloads data if it changed, right? If so, I would think it should be Ok to check for updates a few times per day (maybe every 4-6 hours would be appropriate)? I'm sure we don't want to hammer their servers with constant requests, but I would think we could check more often than once per day.

[rkulagow]

The current "status" call indicates when the last update happened; it's a very lightweight call, so the client can determine if it even needs to go through the process of checking hashes for schedules.

[EnterNoEscape]

Originally Posted by Tiki

When Sage does it's daily updates it checks for an updated hash and only actually downloads data if it changed, right? If so, I would think it should be Ok to check for updates a few times per day (maybe every 4-6 hours would be appropriate)? I'm sure we don't want to hammer their servers with constant requests, but I would think we could check more often than once per day.

Correct. It relies on the hashes to determine if it needs to update anything, so actual traffic is very low even if you manually update frequently.

Originally Posted by rkulagow

The current "status" call indicates when the last update happened; it's a very lightweight call, so the client can determine if it even needs to go through the process of checking hashes for schedules.

Interesting. I hadn't considered using this approach. I assume that last update date and time is in UTC?

[rkulagow]

https://github.com/SchedulesDirect/J...getting-status

"lastDataUpdate": "2015-04-17T03:36:24Z",

[EnterNoEscape]

Originally Posted by rkulagow

https://github.com/SchedulesDirect/J...getting-status

"lastDataUpdate": "2015-04-17T03:36:24Z",

I don't know why I asked. I keep forgetting the Z means UTC.

[Tiki]

Originally Posted by EnterNoEscape

I don't know why I asked. I keep forgetting the Z means UTC.

I would assume the Z is for Zulu time (which is same as UTC or GMT).

[xjim1]

Currently, what determines the update time? Mine happens around 7:15 pm daily and interferes with playback.

Can it be changed?
Couldn't find anything in setup.

[EnterNoEscape]

Originally Posted by Tiki

I would assume the Z is for Zulu time (which is same as UTC or GMT).

You are correct. In my mind, it's just more common to say UTC. However, if you do any coding, don't use GMT when you mean UTC because they are actually different things.

[graywolf]

Originally Posted by xjim1

Currently, what determines the update time? Mine happens around 7:15 pm daily and interferes with playback.

Can it be changed?
Couldn't find anything in setup.

It starts 24 hours after the last epg completed and therefore the start times creep.

I have a schedule task that "calls " the sagetv URL to force an epg refresh at same time each afternoon (outside normal viewing time)