Light Channel Logo Always Used On Dark Theme And Incorrect Light Channel Logo

[Lid 4]

Hi all,

Bit of a weird one here. I've been making some changes to my IPTV setup recently and have an annoying issue going on with the channel logos. I was previously using IPTV Boss to output an m3u channel list and then matching these channels to the Emby Guide Data using Sky Q (London SATELLITE) E1 Postcode as the Lineup, this worked fine in terms of channel logos for about a year. I've recently setup Dispatcharr and now I do the same as before but just with a Dispatcharr creating the m3u file instead of IPTV Boss. I'm using the same guide data and linking it to the same channel number I did with the IPTV Boss setup but now in the channel guide "light with colour" logos are being used when I have a dark theme set. Also the Sky Sports Golf light logos seem to be incorrect. I haven't added a server log output at the moment as I'm not sure if that will show anything helpful for this. But I have included a number of screenshots below to show what I mean.

406 is Sky Sports Golf - See below for the 3 images scaped. The 4 TNT channels are all also using the "Light with Colour" logo, but for some reason TNT 4 is white. And also the "Dark Version" of the TNT logo is smaller vertically so I would prefer this as it makes the channel block narrower which is what I had before as it seemed to default to the "Dark Version"

Editing the Sky Sports Golf channel Logo from the guide view:

Editing the TNT 4 channel logo from the guide view: 

These are my display settings for the user. I assume it's meant to pick the logo based on the theme. I have also tried setting the settings theme to dark just in case.

I've tried deleting the images from the edit view and then refreshing the guide data and the same thing happens. The logos also display that way for all users I have setup and I've tested from my laptop browser and also from the Android App on my phone and they show the same.

 

Does anyone have any ideas on this as it's annoying me even though it's not breaking functionality.

 

Thank you,

 

Liam