Please find the log attached.
Arraound 434 there are some requests from the Samsung TV which look like this:
2019-07-08 21:02:23.109 Info HttpServer: HTTP Response 200 to 192.168.178.34. Time: 20ms. http://192.168.178.25:8096/emby/Items/12815/Images/Primary?maxWidth=1536&tag=f7dacec04228d2bff412aa9cda32833f&quality=50
2019-07-08 21:02:31.339 Info HttpServer: HTTP GET http://192.168.178.25:8096/dlna/9261ce1d65c840019b5e6b1be14ff5d3/description.xml. UserAgent: Microsoft-Windows/6.1 UPnP/1.0 Windows-Media-Player-DMS/12.0.7601.17514 DLNADOC/1.50
Looks like the image size is limited to 1536px width and compression quality is set to 50. I'd expect something more like maxWidth=3840 and quality=90 on a 4K TV.
But why resize and recompress the images anyway and not just "direct play" them to the TV?
On line 679 you'll find some request from a Firefox 67 on a Windows PC which look like this:
2019-07-08 21:05:16.492 Info HttpServer: HTTP GET http://stardust:8096/emby/Items/12805/Images/Primary?maxWidth=1920&tag=67d877d24239120a57b61f00e969965c&quality=90. UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:67.0) Gecko/20100101 Firefox/67.0
It got some slightly better 1920px resolution and way better quality=90 compression.
This photo looks perfectly sharp and with no visual pixels or compression artifacts when directly played from an USB-drive on the TV or when played over DLNA from my Fritz Box's (Router) Media Server.
Edited by lejared, 08 July 2019 - 03:27 PM.