Image rendering bug found

[bruor 43]

I've been trying to replicate/move my xteve/threadfin setup to a new server and found an image display glitch along the way. 

I had image caching enabled on threadfin, and when moving it to a new server the guide xml it was serving up had invalid image paths.   When I added the M3U (which had valid paths) the images looked scaled correctly into their boxes on the home screen.  When I added the XML to the configuration, the channels for which the XML contained an invalid link, would render the image unscaled and it would look zoomed in.  Disabling threadfin caching makes fixed the XML use the same custom image URLs that are provided in the m3u and the images appear scaled as expected.  So this only seems to be a problem when the M3U image is valid, but the XMLTV contains a URL that is invalid. 

[Luke 42081]

Hi, right, we only capture one image url. We do plan to allow you to configure which source you'd prefer it to come from, but ultimately you do have to make sure the urls are valid.

[bruor 43]

That makes sense, and I'm not seeing an image assigment/substitution issue.  The correct images are shown, they just look bad unless the XML url for the image is valid. 

Also, if I update the images I'm using in the m3u/xml, is there a way to get Emby to re-pull the new images without having to delete the m3u/xml and re-add them? 

[Luke 42081]

Just refresh the guide data.

[bruor 43]

Perfect thanks!

[bruor 43]

Perhaps that only works in the beta version?  I even tried deleting and re-adding the XMLTV source and the logos didn't update.  I ended up having to delete both, re-add the m3u, and then add the xml again. 

[Luke 42081]

Sorry, currently images only get assigned to channels that don't already have existing images. This is to preserve any custom edits directly in Emby Server. So yes for now you need to remove the whole thing.