-
-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
image scaling filters #245
Comments
For reference. |
They didn’t mean it that way. I have wanted to do this for a long time, hence I kept the “canvas-based renderer” around even after the scrolling issue was fixed. It just had a lower priority on my list. |
Also, with "canvas-based renderer" off, it uses native image element to display images for performance and low RAM usage. |
You mean, it displays the original image, when canvas-based renderer is off, right? |
example -- 1280 x 1024 screen and hq source, canvas renderer disabled |
With canvas on image is sharp, but not ideal (visible patterns) - it's close to what Nearest-neighbor filter would do ~ |
|
obviously yes it would provide identical to source result in 1:1 mode, as it dosn't scale image to screen size. 1.1 mode is unusable for 1080p or less, due to a simple fact that image is generally too big to fit. So there is downscaling for that. You would also benefit from filtering (and scaling/fitting) when you upscale 1080p image to a larger screen resolution like 4k or 5k, otherwise your image will be too small :) |
They will be useful for upscaling and also depended on canvas, so it would not affect ram without enabling it. |
If possible, can you provide more info on this?
There were more questions but i cant remember them for now, so I will ask multiple times. |
I dont know the details of how it can be implemented, but people including me just want the resizing algorhitm to be changeable from Bilinear to lancroz which the benefits of can be seen above. |
Normal users ignore this comment.
|
+1 Biliniar doesn't seem a good choice anyway, even in that wiki link - Bicubic seems much better (and it's usually chosen as a default medium quality option everywhere) but a killer-feature would be to have an option to use https://github.com/nagadomi/waifu2x upscaling cuz sadly even now in 2024 there are tons of places where comic images are provided in downscaled as heck format |
Its actually not bilinear for every image. Because of internal optimizations, when "upscaling" ie size of image displaying is larger than original resolution, it will use linear interpolation. But when downscaling it uses lanczos3. As I have said above, Yomikiru dont handle image rendering by default because it can be complex in resource management (which you can already notice in "canvas based rendering", it uses a lot higher amount of RAM and CPU). Resampling images is very expensive task and takes lot of RAM and CPU time. Even with "Magic Kernel Sharp", which is faster than lanczos3, it takes too long to load the images. In case of CDisplayEx, I think it only shows one or two image at a time, thats how its able display manga fast. Even when resizing, you can notice a big delay before image resolution (not size) updates. And as I have already mention in #289, its not possible to use waifu2x (+ it takes significantly longer to resample). |
I like the reader! However, adding an option for various scaling algs would benefit user experience, i.e lanczos, sinc, mitchel etc. Yomikiru has a Bilinear scaling, which produces softer than desired look in =< 1080p configurations (a single image fit to width)/ except for vertical 1080p. Thanks!
The text was updated successfully, but these errors were encountered: