Requesting Images via API with UnplayedCount uses Emby colors #592

Closed
opened 2025-12-21 16:57:51 +01:00 by backuprepo · 12 comments
Owner

Originally created by @SenorSmartyPants on GitHub (Apr 17, 2019).

Describe the bug

API generated images with an UnplayedCount uses emby green and not Jellyfin color.

To Reproduce

  1. Go to '...'
    http://localhost:8096/emby/Items/<seriesID>/Images/Primary?UnplayedCount=2

Expected behavior

Circled number should use Jellyfin color.

Screenshots

Primary

System (please complete the following information):

  • OS: Docker
  • Browser: Chrome
  • Jellyfin Version: 10.2.2
Originally created by @SenorSmartyPants on GitHub (Apr 17, 2019). **Describe the bug** <!-- A clear and concise description of what the bug is. --> API generated images with an UnplayedCount uses emby green and not Jellyfin color. **To Reproduce** <!-- Steps to reproduce the behavior: --> 1. Go to '...' http://localhost:8096/emby/Items/\<seriesID\>/Images/Primary?UnplayedCount=2 **Expected behavior** <!-- A clear and concise description of what you expected to happen. --> Circled number should use Jellyfin color. **Screenshots** <!-- If applicable, add screenshots to help explain your problem. --> ![Primary](https://user-images.githubusercontent.com/991618/56256657-407c7980-608f-11e9-83b5-b4d9b120a7b3.jpg) **System (please complete the following information):** - OS: Docker - Browser: Chrome - Jellyfin Version: 10.2.2
backuprepo 2025-12-21 16:57:51 +01:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@thornbill commented on GitHub (Apr 17, 2019):

Well the good news is the color was fixed in #1043 which will be present in Jellyfin 10.3.0.

The bad news is when I verified this on 10.3.0-RC1 I noticed the count is not displaying in the generated image.

mythbusters

@thornbill commented on GitHub (Apr 17, 2019): Well the good news is the color was fixed in #1043 which will be present in Jellyfin 10.3.0. The bad news is when I verified this on 10.3.0-RC1 I noticed the count is not displaying in the generated image. ![mythbusters](https://user-images.githubusercontent.com/3450688/56299357-e10b8180-6101-11e9-8452-9129b403d600.png)
Author
Owner

@SenorSmartyPants commented on GitHub (Apr 17, 2019):

It's always something. :)

Any chance some anti-aliasing could be added to the circle edge to smooth it out?

Thanks.

@SenorSmartyPants commented on GitHub (Apr 17, 2019): It's always something. :) Any chance some anti-aliasing could be added to the circle edge to smooth it out? Thanks.
Author
Owner

@bugfixin commented on GitHub (Apr 19, 2019):

I can't reproduce the missing number in the circle thornbill showed on any current releases (or 10.3.0-rc1), what platform was that on?

@bugfixin commented on GitHub (Apr 19, 2019): I can't reproduce the missing number in the circle thornbill showed on any current releases (or 10.3.0-rc1), what platform was that on?
Author
Owner

@SenorSmartyPants commented on GitHub (Apr 20, 2019):

I'm getting JF blue on my requests now with 10.3.0.

But only with unplayed counts that I hadn't already requested. Some caching is happening in JF I'm assuming.

@SenorSmartyPants commented on GitHub (Apr 20, 2019): I'm getting JF blue on my requests now with 10.3.0. But only with unplayed counts that I hadn't already requested. Some caching is happening in JF I'm assuming.
Author
Owner

@sparky8251 commented on GitHub (Apr 20, 2019):

JF has stupid caching we inherited from Emby. It likes to really falsify info at the server side, tricking the browser into not requesting updated data.

I'd try refreshing the page with caching disabled in the network tab of the browsers F12 menu, that almost always clears up this odd crap.

@sparky8251 commented on GitHub (Apr 20, 2019): JF has stupid caching we inherited from Emby. It likes to really falsify info at the server side, tricking the browser into not requesting updated data. I'd try refreshing the page with caching disabled in the network tab of the browsers F12 menu, that almost always clears up this odd crap.
Author
Owner

@bugfixin commented on GitHub (Apr 20, 2019):

These images are cached in the jellyfin cache dir on the server-side, it is beyond browser caching. You can view your current cache dir in the admin dashboard and remove the images/ folder within it to clear them.

@bugfixin commented on GitHub (Apr 20, 2019): These images are cached in the jellyfin cache dir on the server-side, it is beyond browser caching. You can view your current cache dir in the admin dashboard and remove the images/ folder within it to clear them.
Author
Owner

@SenorSmartyPants commented on GitHub (Apr 20, 2019):

I deleted the /cache/images/resized-images and that cleared up all my green. This is closed as far as I am concerned.

@SenorSmartyPants commented on GitHub (Apr 20, 2019): I deleted the /cache/images/resized-images and that cleared up all my green. This is closed as far as I am concerned.
Author
Owner

@sparky8251 commented on GitHub (Apr 20, 2019):

In that case, I'll give it a proper close.

If it comes back feel free to open a new issue!

@sparky8251 commented on GitHub (Apr 20, 2019): In that case, I'll give it a proper close. If it comes back feel free to open a new issue!
Author
Owner

@anthonylavado commented on GitHub (Nov 29, 2020):

@SenorSmartyPants I know this was an old issue but - are you actively consuming the image with the played indicator in any project?

@anthonylavado commented on GitHub (Nov 29, 2020): @SenorSmartyPants I know this was an old issue but - are you actively consuming the image with the played indicator in any project?
Author
Owner

@SenorSmartyPants commented on GitHub (Nov 29, 2020):

@SenorSmartyPants I know this was an old issue but - are you actively consuming the image with the played indicator in any project?

Yes. I use them in my jellyfin-nmt project.

@SenorSmartyPants commented on GitHub (Nov 29, 2020): > @SenorSmartyPants I know this was an old issue but - are you actively consuming the image with the played indicator in any project? Yes. I use them in my jellyfin-nmt project.
Author
Owner

@SenorSmartyPants commented on GitHub (Nov 29, 2020):

Are you wanting to drop this functionality?

@SenorSmartyPants commented on GitHub (Nov 29, 2020): Are you wanting to drop this functionality?
Author
Owner

@anthonylavado commented on GitHub (Nov 29, 2020):

@SenorSmartyPants AFAIK you're fine, don't worry.

I wanted to know if there was anything using it at the moment. We don't need it in Android TV anymore, and Roku was the only official project that still used it, though they're probably just going to move away from it. We'll revisit this on a later version.

@anthonylavado commented on GitHub (Nov 29, 2020): @SenorSmartyPants AFAIK you're fine, don't worry. I wanted to know if there was anything using it at the moment. We don't need it in Android TV anymore, and Roku was the only official project that still used it, though they're probably just going to move away from it. We'll revisit this on a later version.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: starred/jellyfin#592
No description provided.