Schedules Direct + 3.4.8 only 8 days of EPG?

[snagglewest]

On 3.3.8 with Schedules Direct I was getting 12 days of EPG, after upgrading to 3.4.8 I only get 8 days now. I understand the Schedules Direct interface changed, is 8 days going to be the new "norm or am I missing a new setting somewhere?

Snag

[BrettB]

In your config.xml file, what value do you have for

Code:

<SchedulesDirectDays>8</SchedulesDirectDays>

?

As I understand it, with the previous version of the Schedules Direct interface, NPVR ignored this value and got all available data from that older Schedules Direct interface (which was typically 10-12 days).

With the new Schedules Direct interface, NPVR can request a specific number of days and get them (at least with as much data as is available). I tested setting the value to 21, and I got at least 14 days of data for all channels and 21 days for some of them.

[snagglewest]

I had the SchedulesDirectDays setting in the config.xml set to 14 in the previous version but apparently it got reset. Changing it to 21 and doing a manual refresh worked. However, I did notice something different, while downloading the segments a pop up keeps appearing stating "The schedule you requested has been queued for generation but is not ready for download. Retry". It did this at least once for each 10 channel section but after 10-15 seconds or so the pop up would disappear and it would move to the next section. In the end it appears to have done a complete update. Not sure if this is because of the 21 days or if a shorter time frame would do the same. Didn't notice this when I did an update last night with SchedulesDirectDays set to 8.

Sub - will the extended period cause problems with the auto update? Would a shorter period of maybe 14 be better?

[ATTACH=CONFIG]40017[/ATTACH]

[rkulagow]

(I work for Schedules Direct)

I've seen as far as 27 days in the raw data, but of course the further out you go, the more things are subject to change. There's a mechanism in the API so that a client can check whether the schedule for a station on a particular date has changed since the last time the client download that station/date (so that the client doesn't need to download a schedule again if it's the same as the one that the client already has). I don't run NextPVR, and I don't know if sub has implemented that functionality.

[rkulagow]

(I work for Schedules Direct)

The retry / queued message is "normal" in that it's a soft error. Because we don't have "update windows" (clients can connect at any time) it's possible that the backend is already doing one of the daily updates, but your particular station isn't ready yet. As long as you get data for all the valid channels it's nothing to worry about. If you don't get data for a valid station then please open a ticket at the Schedules Direct website as an "Other" lineup issue.

[mvallevand]

I kept mine at 14 days as the data was better for one-off recordings.

Martin