Schedules Direct EPG (integrated BETA)

[sflamm]

Just installed a brand new standalone version of 9.1.10 and configured SD EPG... getting same "NO DATA" on the EPG. (see attached)

Please advise....

[sflamm]

turned on the SD debug:

debug_sd=true

found it loading data... and it finally finished properly (see attached)

my main installation also seems to be loading some info... but not the whole EPG..?

[wnjj]

Originally Posted by Tiki

I don’t think the Sage version should matter - no changes in Sage related to SD in a long time. More likely a problem with Schedules Direct. I’ve seen a few posts here from time to time where SD drops or renames a particular lineup to something slightly different. This of course only affects the handful of people using that particular lineup. You may have to tell Sage to use a “new” lineup and then go through the process of setting up the lineup in Sage again.

From that old of a version (9.0.14) there have been some SD changes, one in particular that was causing null pointer exceptions.

Try an EPG update, then look in the sagetv_0.txt log file for errors (or post it on here).

EDIT: Didn't see the OP's later posts before writing this. Disregard.

[EnterNoEscape]

Originally Posted by sflamm

turned on the SD debug:

debug_sd=true

found it loading data... and it finally finished properly (see attached)

my main installation also seems to be loading some info... but not the whole EPG..?

SageTV doesn't do some activities until after the EPG update such as filling in all of the gaps with No Data. What stations are missing? I should be able to tell what's happening from the sdmd5sched file. sd_epg.log could also be helpful, but based on what you're saying about it finishing successfully, it's probably not going to reveal anything I can't reproduce myself.

[sflamm]

Thanks for the quick responses.

The EPG data remained at "No data" for almost 24 hours... During that time I attempted to force multiple manual EPG updates (toggling the channel assignments)... I also completely removed the old SD lineup and redid it ... but nothing seemed to resolve the issue.

I ended up purging my 9.0.14 installation then installing 9.1.10 and reloading my configuration. That seems to have worked fine. Now the EPG data is complete. When I imported my old wiz.bin it initially showed "no data" but it quickly resolved itself...

I have a second installation on 9.0.14... it too started suddenly is encountering the same issue at the same time. If I install 9.1.10 directly over it (upgrade) will / should that achieve the same result as starting from scratch?

[waynedunham]

Originally Posted by sflamm

Thanks for the quick responses.

The EPG data remained at "No data" for almost 24 hours... During that time I attempted to force multiple manual EPG updates (toggling the channel assignments)... I also completely removed the old SD lineup and redid it ... but nothing seemed to resolve the issue.

I ended up purging my 9.0.14 installation then installing 9.1.10 and reloading my configuration. That seems to have worked fine. Now the EPG data is complete. When I imported my old wiz.bin it initially showed "no data" but it quickly resolved itself...

I have a second installation on 9.0.14... it too started suddenly is encountering the same issue at the same time. If I install 9.1.10 directly over it (upgrade) will / should that achieve the same result as starting from scratch?

Just an FYI, but EPG updates take several hours to filter into the scheduled recordings on my system and have for a long time, probably longer than I remember since I wasn't looking for it.
For instance I'll get a notice shortly after an EPG update saying that 'xx' manual recording will no longer record program 'yy', the new program is 'zz', be it either a different program or even something that doesn't say what it is since the manual times don't match the EPG. However if I go to the recordings schedule and call up the program info it will show the new program name, however if it was for a favorite it will still show the favorite icon as well as if you go to the recording options it will still show the "favorite" even though the EPG data shows the correct new program.
After an hour or two everything will settle down and the EPG data and recordings schedule will agree.

[Opus4]

I'm not sure if EnterNoEscape is still maintaining the SD EPG grabber.

If not, is there anyone else interested in taking a look at the code?

One of the issues with Crash goes the extender(s) is that the series info images (and probably other images) being grabbed from SD are among the largest ones available, instead of smaller thumbnail-sized versions that SD provides. Many of the show images in SageTV are larger than the entire size allocated to the TV screen & end up needing to be greatly reduced in size when displayed in that small area in the upper right corner of the screen. I've emailed with rkulagow, the SD rep here, and he has shown me listings of images available for some of the shows & there are definitely smaller one that could be downloaded instead.

Andy

[KeithAbbott]

Originally Posted by Opus4

I'm not sure if EnterNoEscape is still maintaining the SD EPG grabber.

If not, is there anyone else interested in taking a look at the code?

One of the issues with Crash goes the extender(s) is that the series info images (and probably other images) being grabbed from SD are among the largest ones available, instead of smaller thumbnail-sized versions that SD provides. Many of the show images in SageTV are larger than the entire size allocated to the TV screen & end up needing to be greatly reduced in size when displayed in that small area in the upper right corner of the screen. I've emailed with rkulagow, the SD rep here, and he has shown me listings of images available for some of the shows & there are definitely smaller one that could be downloaded instead.

Andy

This sounds like the same issue that Jeff fixed a month or so back: https://forums.sagetv.com/forums/sho...7&postcount=39

Edit: Oops, just reread your post, Jeff's fix resizes the image that is being grabbed, sounds like you are referring to getting a smaller image from SD so that either no resizing needs to happen, or less resizing (and therefore less bandwidth required).

[Opus4]

Yes - I helped test Jeff's changes before they were posted there, and while those changes stopped the crashes & helped some other things, I'm still running into extender UI slowdowns which might benefit from both a) downloading smaller images (this topic) and b) just not displaying show images at all (the other topic).

Andy

[nyplayer]

I stopped displaying images and Icons because it slowed down the Android MiniClients ...

[waylo]

Originally Posted by nyplayer

I stopped displaying images and Icons because it slowed down the Android MiniClients ...

Is that a universal setting on the server for all clients?

I noticed on many of my Android phone/tablet devices, the miniclient is irredeemably slow and I could never figure out why. Only on my Nvidia Shield is it workable.

[nyplayer]

Originally Posted by waylo

Is that a universal setting on the server for all clients?

I noticed on many of my Android phone/tablet devices, the miniclient is irredeemably slow and I could never figure out why. Only on my Nvidia Shield is it workable.

No I did with with a GeneratedThumbnails symlink.

[nyplayer]

Originally Posted by waylo

Is that a universal setting on the server for all clients?

I noticed on many of my Android phone/tablet devices, the miniclient is irredeemably slow and I could never figure out why. Only on my Nvidia Shield is it workable.

No I did with with a GeneratedThumbnails symlink on my server.. But it works on al clients

[waylo]

Originally Posted by nyplayer

No I did with with a GeneratedThumbnails symlink on my server.. But it works on al clients

Got it, figured something like that was how you were doing it.

I actually enjoy the thumbnails and channel logos while watching on my server. Too bad you have to neuter that to get the miniclients to behave.

[Opus4]

I would really like to get back to the point of this topic:

Originally Posted by Opus4

I'm not sure if EnterNoEscape is still maintaining the SD EPG grabber.

If not, is there anyone else interested in taking a look at the code?

One of the issues with Crash goes the extender(s) is that the series info images (and probably other images) being grabbed from SD are among the largest ones available, instead of smaller thumbnail-sized versions that SD provides. Many of the show images in SageTV are larger than the entire size allocated to the TV screen & end up needing to be greatly reduced in size when displayed in that small area in the upper right corner of the screen. I've emailed with rkulagow, the SD rep here, and he has shown me listings of images available for some of the shows & there are definitely smaller one that could be downloaded instead.

[wnjj]

Do you know what is needed to grab the smaller thumbnails? Is it a matter of tweaking a path/filename or does it require some kind of intelligence or pulling properties? I can hack my way around in Java some but am pretty unfamiliar with the SD download methods.

[Opus4]

I'm not entirely sure. I was once going to be writing the EPG grabber, but then found I had lost just about all interest in programming.

The available images are in a json list & the appropriate one(s) could be chosen from that data, but I have to admit that I haven't looked at the SD code in SageTV's github to see how it is getting the images it uses currently.

[Opus4]

I'm recovering from my 2nd covid vaccine and browsed through the SD grabber code... the images are processed in SDImages.java. I'm more likely to work on the STV than I am to figure out if I still have a java development installation, but there's at least the start of tracking it down.

Edit: looks like it is grabbing the medium and large images, where it should probably grab the smaller ones.

[wnjj]

Originally Posted by Opus4

I'm recovering from my 2nd covid vaccine and browsed through the SD grabber code... the images are processed in SDImages.java. I'm more likely to work on the STV than I am to figure out if I still have a java development installation, but there's at least the start of tracking it down.

Edit: looks like it is grabbing the medium and large images, where it should probably grab the smaller ones.

I see that in the code, however large is only up to 1920 in the largest dimension. The image that was crashing the extender was 3840x2160 so I’m not even sure how it got through. Maybe a size check is needed in another code branch?

[Opus4]

Yeah, I didn't post it here last night, but I also figured it might need an actual size check, in case the size codes mean different things for different shows.

For example, the people pics, farther down, look for the smallest and largest, by actual size.