New Badge Overlay plugin

[eMoOak 9]

37 minutes ago, Amanade3 said:

This patch should fix it. but if you're still seeing high CPU after updating, let me know and I'll dig into what else might be causing it.

Hi, I’ve just tested version 1.3.5.0 after your fix.

Unfortunately, the CPU usage issue is still present. With EmbyNewOverlay enabled, the EmbyServer process goes to around 100% CPU continuously. As soon as I disable the plugin, CPU usage immediately returns to normal.

I also confirmed that Emby is actually loading version 1.3.5.0.

So it looks like the DateTime.MinValue / DateTimeOffset issue was fixed, but there is another issue causing the high CPU usage.

There are no obvious exceptions in the Emby log while this is happening, which makes it a bit harder to identify.

I’ve had to disable the plugin again for now because of the CPU usage.

[Neminem 1839]

@eMoOakI guess @Amanade3 would need your hardware info. 

And server logs with debug logging turned on. 

[Amanade3 74]

Well I suspected there is another issue causing your CPU to run at 100% because while testing it on my PC with no premiere date, I didn't have a CPU running at 100%.  like @Neminemsaid can you dump the emby server log and your hardware info. And i have one question for you. Is the v 1.3.4.0 the first version you tried on? and maybe one thing to try..... Try switching off some master switches like most watched, studio logos and the like and test the results.

 

Edited August 10 by Amanade3

[eMoOak 9]

The issue seems to be specifically triggered by the Seerr library synchronization. With EmbyNewOverlay enabled:

Seerr stopped → CPU normal
Seerr running, library sync disabled → CPU normal
Seerr running, library sync enabled → EmbyServer CPU goes to ~100%

So it looks like the large number of library/season/episode requests generated during Seerr's library synchronization triggers excessive processing in EmbyNewOverlay.

[Amanade3 74]

Oh so it was seerr after all? glad you figured it out your self.

[eMoOak 9]

3 minutes ago, Amanade3 said:

Oh so it was seerr after all? glad you figured it out your self.

Not exactly. Seerr itself doesn't cause the high CPU usage.

The important part is the interaction with EmbyNewOverlay:

• Seerr stopped + EmbyNewOverlay enabled → normal CPU
• Seerr running + library sync disabled + EmbyNewOverlay enabled → normal CPU
• Seerr running + library sync enabled + EmbyNewOverlay enabled → ~100% CPU

So the library synchronization in Seerr appears to trigger the issue, but I suspect something in EmbyNewOverlay is being executed excessively when Seerr scans the library.

If I disable EmbyNewOverlay while keeping Seerr's library sync enabled, CPU usage also stays normal.

So I don't think Seerr itself is the problem; rather, Seerr's library synchronization seems to trigger a problem in the overlay plugin.

[Amanade3 74]

Well this makes it hard to find the cause, if seerr is involved..... I don't even use seerr and i don't know what happens to the plugin during lib sync. I will try to look into it but not gonna promise this will be fixed

.

[Amanade3 74]

can you try it with most watched turned off?

 

[eMoOak 9]

9 minutes ago, Amanade3 said:

can you try it with most watched turned off?

 

Yes. I kept EmbyNewOverlay fully enabled and re-enabled Seerr library synchronization. The only thing I disabled was Most Watched.

With Seerr library synchronization running and Most Watched disabled, CPU usage stays completely normal.

So it looks like Most Watched is specifically triggering the high CPU usage during the Seerr library synchronization.

[Amanade3 74]

Okay good to know, that narrows it down... for now disable most watched... I will look into the issue. 

[WDPR4100 18]

6 hours ago, Amanade3 said:

Okay good to know, that narrows it down... for now disable most watched... I will look into the issue. 

Indeed, it's the same problem; above all, synchronization takes ages and can even block access (slowing down the server).

[Amanade3 74]

New Release

V 1.3.5.0

• Fixed high CPU usage during library synchronization with Seerr.
• Added Top Center and Bottom Center positions for badge overlays.
• Unified the “Most Watched” label across all content types, including movies, series, and episodes.

EmbyNewOverlay.dll

[GrimReaper 5075]

1 hour ago, Amanade3 said:

New Release

V 1.3.5.0

• Added Top Center and Bottom Center positions for badge overlays.

4.9.5.0. stable

Not seeing those options, only 4 previously available ones.

Edited Sunday at 08:07 PM by GrimReaper

[GrimReaper 5075]

Hm, possibly version mismatch/wrong dll, maybe this latest version should be 1.3.6.0, as you already had 1.3.5.0. last week?

On 8/10/2026 at 5:50 PM, Amanade3 said:

New Release

V 1.3.5.0

• Fix high CPU usage caused by an exception in badge cache-key generation for items with no premiere date.

EmbyNewOverlay.dll 1.8 MB · 9 downloads

 

1 hour ago, Amanade3 said:

New Release

V 1.3.5.0

• Fixed high CPU usage during library synchronization with Seerr.
• Added Top Center and Bottom Center positions for badge overlays.
• Unified the “Most Watched” label across all content types, including movies, series, and episodes.

EmbyNewOverlay.dll 1.8 MB · 1 download

 

[Amanade3 74]

sorry my bad i thought the last one was 1.3.4.0 i will update the version. thanks for pointing that out.

[Amanade3 74]

EmbyNewOverlay.dll CORRECTION,

New Release

V 1.3.6.0

• Fixed high CPU usage during library synchronization with Seerr.
• Added Top Center and Bottom Center positions for badge overlays.
• Unified the “Most Watched” label across all content types, including movies, series, and episodes.

[Amanade3 74]

21 hours ago, GrimReaper said:

Not seeing those options, only 4 previously available ones.

I thought I updated the version from 1.3.4.0 to 1.3.5.0 but apparently the last version was 1.3.5.0 and the new should have been 1.3.6.0 (which is corrected now)

[GrimEvil 92]

The plugin works fine, but when I use an Emby dark theme, the layout does not match and is hard to read the tabs etc.

[GrimReaper 5075]

1 hour ago, GrimEvil said:

The plugin works fine

Unfortunately it doesn't for me, I cannot un-exclude libraries. If excluded library un-checked/library included, upon pressing Save it appears like it caught but upon navigating away and back or refreshing page, it's back to initial condition (and no badges applied).

[GrimEvil 92]

@GrimReaperdid you clear the cache, I had do this on my setup?

[GrimReaper 5075]

44 minutes ago, GrimEvil said:

@GrimReaperdid you clear the cache, I had do this on my setup?

Did, tried another/fresh browser as well, same behavior.

Edit: Uninstalled plugin, deleted xml configuration file, started anew - all libraries included but no badges applied. No errors thrown in debug log, either.

 

Edit2: Rebooted server machine, getting them badges at last.

Edited 1 hour ago by GrimReaper
Reinstalled plugin

[GrimReaper 5075]

@Amanade3Can you exclude Season 1 (ONE) when weighing "New Season" detection rules?

On 8/10/2026 at 6:24 PM, Amanade3 said:

When a movie matches more than one rule at once, the plugin picks whichever rule has the highest priority, in this particular order

• Tag rules
• Folder rules
• Most watched
• Release date ( by the movie's premiere date)
• New Season
• And finally Date Added (by when it was added to the library)

To clarify, with default settings:

Days since added to library: 30

Days since item premiere: 60

Days since first episode of latest season aired: 90

If a brand new TV show is added within last month, but had Premiere date 60-90 days ago, it gets blue "New Season" badge - looks odd on single season series, IMHO it should get green "Recently added" badge instead.

[GrimReaper 5075]

Also, could you introduce additional logic for TV shows based on underlying episodes added?

What I'm referring to is that currently, if an existing TV show (that is neither New, Recently added or has a long season (>90 days)) gets episodes(s) added, either "Recently added" or "New episode" ones, it gets no badge as TV show itself doesn't fit any criteria/rule - however, there are new episodes there and maybe it should indicate that, orange (or whatever color one chooses) "New episode" on TV show poster maybe, when it falls out of all other existing rules?