rekit 18 Posted 24 minutes ago Posted 24 minutes ago Forgive me if I'm misunderstanding how the setting works. I assume it works by looking at pixel width and not total pixels, but I could be wrong. The problem, in short: When a 4k video is a few pixels narrower than standard 4k, the setting seems to identify it as the next smaller resolution (hd instead of 4k). The problem, longer explanation: When match video resolution is enabled and a video that has a horizontal resolution less than a particular threshold such as 3840 for 4k or 1920 for hd (maybe 3838, or 1918 for example, sometimes due to having a couple pixels trimmed off the edges horizontally to crop out minuscule black bars, or more noticeably when the aspect ratio is more square), match video resolution seems to identify this as something smaller than the intended resolution of 4k or hd, and matches the video resolution to the next smallest resolution. So a 4k movie is being displayed at 1080, and any scaling the tv is doing is doing it unnecessarily or inaccurately for the source resolution. Proposed solution: I assume the way the setting works is by telling emby "any horizontal pixel width less than x should be identified as y". And instead of setting that pixel width to the normal 3840 for 4k, change it to something slightly smaller like 3820. (Or if it uses total pixels, then the total pixels could be adjusted accordingly.)
ebr 16488 Posted just now Posted just now Hi. We already do that as far as our processing goes. However, some of the "match resolution" during playback is handled by the player or device instead so the best thing to do here is look at a specific example. Please attach the information requested in how to report a media playback issue. Thanks!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now