Schedules Direct EPG (integrated BETA)

[Opus4]

Returning to what to do about the images... There are a few considerations:

1) Have the types of images changed since the EPG grabber was originally written? I thought I saw some types in the samples I was sent which are not covered in the code.

2) SageTV now can handle more than just 1 series image and its thumb. We should figure out what is supported and whether we want any other images for series info.

3) For #2, if we add additional series images, I could add an option in Detailed Info, or somewhere, that would allow looking at the larger images, like is done for the pictures of the cast.

[EnterNoEscape]

I was not aware the size was such an issue. I wasn't sure what the different sizes would be needed for and erred on too big since I assumed it would be scaled and cached if it was too big which shouldn't have been a big deal performance-wise. If they are not being scaled before they hit the extender, I guess we should make some code changes.

[EnterNoEscape]

Originally Posted by Opus4

Returning to what to do about the images... There are a few considerations:

1) Have the types of images changed since the EPG grabber was originally written? I thought I saw some types in the samples I was sent which are not covered in the code.

2) SageTV now can handle more than just 1 series image and its thumb. We should figure out what is supported and whether we was any other images for series info.

3) For #2, if we add additional series images, I could add an option in Detailed Info, or somewhere, that would allow looking at the larger images, like is done for the pictures of the cast.

If we can gather the changes desired and open an issue on github, I'll get working on them and hopefully have something in a few weeks.

[peternm22]

Originally Posted by EnterNoEscape

If they are not being scaled before they hit the extender

This is just speculation as I don't know know if the images are scaled at the server or the extender. Even if the server was scaling all of the images before sending them to the extenders, if the images are really large then it could still result in a slow down (scrolling through the guide quickly doesn't give a lot of time to scale each image down).

[EnterNoEscape]

Originally Posted by peternm22

This is just speculation as I don't know know if the images are scaled at the server or the extender. Even if the server was scaling all of the images before sending them to the extenders, if the images are really large then it could still result in a slow down (scrolling through the guide quickly doesn't give a lot of time to scale each image down).

If they are being cached post scaling, this would be a one time issue. I was trying emphasis the caching.

[Opus4]

BTW: It was mentioned to me that perhaps the smaller thumbs and full sized images should default to fit with the extender's UI size, 1280x720, but base the sizes it looks for on a property which could then be adjusted in the UI for anyone using a much larger UI size. The thumbs would be a fraction of the UI size & the larger ones would be no larger than the UI window size.

I could easily add options to adjust the desired size(s) in the STV.

[mechling-burgh]

I like that idea, and thanks for the recent help