Universal Media Server | Forum

Hi all,

I have been having this issue for a few months, I'm not even sure when it started. It's about wrong episode names and sometimes thumbnails, like this: As you can see, it's a Dexter episode with Monk thumbnail and King of the Hill name. I have cleared the cache several times, but things only change a little; it's never completely fixed.

Not all files are affected, though: For this report, I have two logs:

• before cache reset: https://www.dropbox.com/scl/fi/132qmdzp ... ldye5&dl=0

• after cache reset: https://www.dropbox.com/scl/fi/1mh1x9uk ... dtuz7&dl=0

After the cache is cleared, things change a lot, but the issues remain. Here are two examples with before and after: https://www.dropbox.com/scl/fi/2zlrdxze ... z3tfd&dl=0 and https://www.dropbox.com/scl/fi/7k4fcd0x ... o7ghq&dl=0

In this image, you can see that Family Guy is wrong, but it was right before the cache reset. Lower Decks didn't change, it was wrong both times: The files are located on different hard drives and with different file structures. I attached three examples here: https://www.dropbox.com/scl/fi/e2ejktu5 ... bpgwn&dl=0

The situations above happened with Prettify filenames checked. If I uncheck it, the names are displayed correctly, but the original names are too ugly.

Thank you for your great job!

I came across something recently where the wrong episode names and thumbnails was coming up for the new Doctor Who so there may be an issue on the API side of things not retrieving the correct metadata (does not help they reset the season number with the new Doc). I tried the reset cache option hoping it would refresh this but it appears to corrupt the database and messes up all video names too. This also messes up the media library so it will not show anything and a full rescan will not fix this.
I had to delete the database "C:\ProgramData\UMS\database\medias.mv.db" so UMS will build a new one to get it back.

I have not looked at your logs yet but I think this is the same problem.

I made an issue for this on Github and there appears to be a couple of similar issues related to this.

mik_s wrote: ↑Sat May 17, 2025 2:28 am I made an issue for this on Github and there appears to be a couple of similar issues related to this.

Great, thank you!

This is a really good bug report and I'm working on fixing the bugs now. I have already deployed a couple of related fixes to the API and will let you know when I have progress on UMS itself

I have fixed some bugs on the server related to resetting the cache, it was leaving out some database tables so they would have become mismatched. That doesn't explain the initial bad state, but maybe that was caused by an API bug. I will do some testing of my fixes soon and see if I can still make it break. If it goes well I'll upload a build for you to test

SubJunk wrote: ↑Thu May 22, 2025 8:25 am This is a really good bug report and I'm working on fixing the bugs now. I have already deployed a couple of related fixes to the API and will let you know when I have progress on UMS itself

I'm glad I could help

SubJunk wrote: ↑Thu May 22, 2025 8:59 am I have fixed some bugs on the server related to resetting the cache, it was leaving out some database tables so they would have become mismatched. That doesn't explain the initial bad state, but maybe that was caused by an API bug. I will do some testing of my fixes soon and see if I can still make it break. If it goes well I'll upload a build for you to test

Sure, anytime.

Please see if this version can properly reset the cache https://www.universalmediaserver.com/up ... x86_64.exe

I finally had time yesterday to test the new version. At first it was all the same as before and then I clicked on Clear Cache. It was acting weird, I had to click several times until it worked. Then the server restarted and it was unavailable, but using the old intercace I could see it was recreating the cache. It took a few hours to finish. This morning I tried to check it but the server was unavaliable: I tried restarting it, no change. So I reinstalled the previous version, 14.12.1, and all seems to be displaying fine: Here is the log from the test version, after the cache clear: https://www.dropbox.com/scl/fi/taok8day ... 6rvnb&dl=0. It was not created with the Create TRACE Logs, but I hope it has enough info for you.

Was this the expected result?

Sorry for taking so long.