Fixing Channel Logos from Schedules Direct

[broconne]

Finally converted over to Sage9 (remove old windows machine and running the docker image instead).

Everything is working well, except some of the channel logos are wrong and/or missing. From prowling around the forums, it appears those logos are coming from Schedules Direct.

However, I don't see any posts on what we are supposed to do when the logos don't match and/or are missing. Is this something we log with Schedules Direct or is there a different way to fix it?

[panteragstk]

Originally Posted by broconne

Finally converted over to Sage9 (remove old windows machine and running the docker image instead).

Everything is working well, except some of the channel logos are wrong and/or missing. From prowling around the forums, it appears those logos are coming from Schedules Direct.

However, I don't see any posts on what we are supposed to do when the logos don't match and/or are missing. Is this something we log with Schedules Direct or is there a different way to fix it?

You can drop your own logo into the channel logos folder to change them to whatever you want.

I think you can even download channel logos as a plugin.

[EnterNoEscape]

If you're seeing incorrect channel logos, I would first clear out the image cache folder (/opt/sagetv/server/GeneratedThumbnails or C:\Program Files (x86)\SageTV\SageTV\GeneratedThumbnails) and restart SageTV. If the logos are still wrong, notify Schedules Direct so they can fix it.

[Tiki]

Are they completely the wrong logo (like wrong channel) or are they corrupted somehow?

I have been noticing that I have several channels where the logos appear squashed horizontally (incorrect aspect ratio). All of these that are squashed also appear to be a bright green color. I don't know why this is happening or if this is related to the problem you are seeing.

[KarylFStein]

Originally Posted by Tiki

Are they completely the wrong logo (like wrong channel) or are they corrupted somehow?

I have been noticing that I have several channels where the logos appear squashed horizontally (incorrect aspect ratio). All of these that are squashed also appear to be a bright green color. I don't know why this is happening or if this is related to the problem you are seeing.

The squashed green logos are a known issue that I thought was resolved. There's a post on here about it anyway.

[EnterNoEscape]

Originally Posted by Tiki

Are they completely the wrong logo (like wrong channel) or are they corrupted somehow?

I have been noticing that I have several channels where the logos appear squashed horizontally (incorrect aspect ratio). All of these that are squashed also appear to be a bright green color. I don't know why this is happening or if this is related to the problem you are seeing.

https://github.com/google/sagetv/wik...)#known-issues

Someone has yet to pull together all of the requirements to re-compile ImageLoader.dll for Windows, so until someone tackles this (I tried and mostly gave up for now) SageTV will continue to load grayscale PNG images incorrectly. Linux doesn't have this problem because libImageLoader.so is being compiled with every build.

Edit: The code is actually fixed. The DLL with the changes just needs to be compiled and included in the next Windows release.

[t.ziu]

I've been using custom logos for quite some time now. I noticed this problem with the green squished logos a long time ago. I found that I could fix this easily. Simply open your logo in paint.net and then save it. This is quite strange Behavior since paint.net is not actually changing the image format. However, paint.net appears to be changing something that makes the image more agreeable to sagetv.

[Fuzzy]

Originally Posted by t.ziu

I've been using custom logos for quite some time now. I noticed this problem with the green squished logos a long time ago. I found that I could fix this easily. Simply open your logo in paint.net and then save it. This is quite strange Behavior since paint.net is not actually changing the image format. However, paint.net appears to be changing something that makes the image more agreeable to sagetv.

I'm guessing Paint.net in this case is saving the file as a full color image. The bug in question here has to do with greyscale images only, so saving the image again as full color (even if it only contains shades of grey), avoids the problem.

[Tiki]

Originally Posted by t.ziu

I've been using custom logos for quite some time now. I noticed this problem with the green squished logos a long time ago. I found that I could fix this easily. Simply open your logo in paint.net and then save it. This is quite strange Behavior since paint.net is not actually changing the image format. However, paint.net appears to be changing something that makes the image more agreeable to sagetv.

I didn't notice the problem until recently because I had been using custom logos (in the old days, Sage didn't download logos automatically with the guide data, so custom logos was the only way to go). But, over time as my lineup changed, I ended up with a hodgepodge of my old custom logos and new logos downloaded by Sage. So a few weeks ago, I got rid of my custom logos and let Sage download everything from a Schedules Direct. I've noticed about a dozen or so channels with funny logos.

Kind of a pain to go back and edit all those logos, but I guess I can give it a try. I'll have to see where Sage stores the downloaded logos (not sure if it puts them in the same place where you put your own custom logos and not home right now to check).

[SHS]

Originally Posted by EnterNoEscape

https://github.com/google/sagetv/wik...)#known-issues

Someone has yet to pull together all of the requirements to re-compile ImageLoader.dll for Windows, so until someone tackles this (I tried and mostly gave up for now) SageTV will continue to load grayscale PNG images incorrectly. Linux doesn't have this problem because libImageLoader.so is being compiled with every build.

Edit: The code is actually fixed. The DLL with the changes just needs to be compiled and included in the next Windows release.

I was wonder when this was going to get fix

[crarbo1]

Originally Posted by Tiki

I'll have to see where Sage stores the downloaded logos (not sure if it puts them in the same place where you put your own custom logos and not home right now to check).

Tiki,
Did you find out where the logos reside? I did a search in the SageTV directories but couldn't find them.
Thanks,
Chuck

[SHS]

Originally Posted by crarbo1

Tiki,
Did you find out where the logos reside? I did a search in the SageTV directories but couldn't find them.
Thanks,
Chuck

logos reside in
C:\Program Files (x86)\SageTV\SageTV\GeneratedThumbnails\
Look for
url-https(numbers)amazonaws2ecom2fschedulesdirect2fassets2fstationLogos(numbers)png
Something like this
url-https3a2f2fs32eamazonaws2ecom2fschedulesdirect2fassets2fstationLogos2fs609645fh35faa2epng

[crarbo1]

Originally Posted by SHS

logos reside in
C:\Program Files (x86)\SageTV\SageTV\GeneratedThumbnails\
Look for
url-https(numbers)amazonaws2ecom2fschedulesdirect2fassets2fstationLogos(numbers)png
Something like this
url-https3a2f2fs32eamazonaws2ecom2fschedulesdirect2fassets2fstationLogos2fs609645fh35faa2epng

I can't find those files anywhere on my computer. Could I still be using the old default logos when I had the free epg? If so, where would those be located so I could check? Also, if that is what I have, how to I get the logos from schedules direct?
Thanks,
Chuck

[SHS]

Originally Posted by crarbo1

I can't find those files anywhere on my computer. Could I still be using the old default logos when I had the free epg? If so, where would those be located so I could check? Also, if that is what I have, how to I get the logos from schedules direct?
Thanks,
Chuck

That I don't know
Try del all file in the Logo and GeneratedThumbnails

[crarbo1]

Originally Posted by SHS

That I don't know
Try del all file in the Logo and GeneratedThumbnails

I found them in the GeneratedThumbnails folder. For some reason searching for schedules didn't find them, but *schedules* did. I thought the windows search feature didn't need wild cards. The way I figured that out was that I did delete the thousands of items in that folder and then went into the program guide. I then looked back in that folder and there they were. I lot less than a thousand to look through, so I found them without searching. I then tried a search both ways and only *schedules* worked. Anyway, thanks for pointing me in the right direction.

Does anyone know why they would be named without the "." before the extension? All of these are like this "url-https3a2f2fs32eamazonaws2ecom2fschedulesdirect2fassets2fstationLogos2fs585325fh35fba2epng" so I can't see the image without opening them up manually.

[SHS]

Originally Posted by crarbo1

I found them in the GeneratedThumbnails folder. For some reason searching for schedules didn't find them, but *schedules* did. I thought the windows search feature didn't need wild cards. The way I figured that out was that I did delete the thousands of items in that folder and then went into the program guide. I then looked back in that folder and there they were. I lot less than a thousand to look through, so I found them without searching. I then tried a search both ways and only *schedules* worked. Anyway, thanks for pointing me in the right direction.

Does anyone know why they would be named without the "." before the extension? All of these are like this "url-https3a2f2fs32eamazonaws2ecom2fschedulesdirect2fassets2fstationLogos2fs585325fh35fba2epng" so I can't see the image without opening them up manually.

That the way they should be just copy them rename them by add dot before png

[jusjoken]

Originally Posted by EnterNoEscape

https://github.com/google/sagetv/wik...)#known-issues

Someone has yet to pull together all of the requirements to re-compile ImageLoader.dll for Windows, so until someone tackles this (I tried and mostly gave up for now) SageTV will continue to load grayscale PNG images incorrectly. Linux doesn't have this problem because libImageLoader.so is being compiled with every build.

Edit: The code is actually fixed. The DLL with the changes just needs to be compiled and included in the next Windows release.

This is now resolved in 9.1.7. You may also want to update the Wiki that mentions this as a known issue.

k

[EnterNoEscape]

Originally Posted by jusjoken

This is now resolved in 9.1.7. You may also want to update the Wiki that mentions this as a known issue.

k

Do you mean this?

[jusjoken]

Originally Posted by EnterNoEscape

Do you mean this?

Perfect.