Universal Media Server | Forum

Thanks for these logs, and your great support and investigation mik_s, you are the best! I think I can see a problem. UMS is sending an API request without the filename. I need to investigate and fix this. In your logs it is sending: https://api.universalmediaserver.com/api/media/video/v2?osdbHash=4...

Worth noting that the old interface is still able to control devices from UMS like before. That's one reason we have kept it around

This depends on the device support, and our config for it, and the other file attributes. I can see on page 138 of your TV manual https://downloadcenter.samsung.com/content/UM/201506/20150604125114309/ENG-US_NMATSCH-1.107-0528.pdf that the TV does not support H.265, so UMS is transcoding the video f...

I think you would need to delete the whole database, by deleting the folder C:\ProgramData\UMS\database\

Can you please confirm that the bug exists in 13.0.0? I ask this because I can see a code change in 13.0.1 that might cause the problem. Either way, please provide logs from a version that works, and a version with the bug. Instructions for that are at https://www.universalmediaserver.com/forum/view...

Thanks for reporting this problem, I have created a GitHub issue for it to track progress https://github.com/UniversalMediaServer ... ssues/3879

General: This release focuses on HDR and UPnP searching support, along with some stability and Docker support improvements. Newer Mac users should notice a huge performance increase too with our ARM builds! We had 8 non-project members contribute code and translations to this release, so thank you,...

Did you see that we have included fixes for these situations in 13.2.0 and 13.2.1? Please let me know if you know of any remaining bugs. Since it should be cleaning itself

You have good timing because our next major version is all about privacy. Keep an eye out for feature previews soon, which will include ways to do these things via the browser settings

I think the initialization bug was a problem with our metadata API which I have now fixed, and have set up an alerting system so it doesn't happen again. Are the settings working now with 13.2.0?