2010-01-16, 01:14
Hi Bobo1on1 !
I made a few tests with the great new shader based upscalers you implemented.
I have to tell they really make a difference . To my eyes Lanczos 3 optimized is the same quality as the software implementation. It looks really really good.
However i realized that i can't use one specific upscaler to all SD and HD videos, because my HW can not take it. For example Lanczos 3 is too slow for my Nvidia 9400 even in SD scenario, but Lanczos 3 optimized works really awesome with excellent quality. But even Lanczos 3 optimized is not fast enough in case of 720p material upscaled to 1080p.
Also i realized that in case of vdpau used, if i change the upscaler, nothing happens. I guess it uses vdpau internal upscaler in any case.
So to solve all these problems i have a suggestion. Maybe we could divide the gui setting for video "Render method" into two lines:
1. Render method for SD videos: Auto detect
2. Render method for HD videos: Auto detect
The default setting could be Auto detect, which could work just like before.
If the user sets the renderer different from Auto Detect, he gets another setting line appear for the available upscaler types for that specific renderer where he can set the desired upscaler separately for SD and for HD videos.
For example:
1. Render method for SD videos: GLSL
Upscaler used for SD videos: Lanczos 3 optimized
2. Render method for HD videos: Auto detect
Or:
1. Render method for SD videos: GLSL
Upscaler used for SD videos: Lanczos 2
2. Render method for HD videos: Crystal-HD
Upscaler used for HD videos: Bicubic
What do you think about the idea ?
Some kind of separation between SD and HD methods is really needed i think.
One other thing i realized is that now with SW upscalers i get a magnified portion of the movie. But this started before you started implementing these great HW upscalers.
Great work and thanks also in the name of all ION users who can from now enjoy HQ upscaled SD videos with minimal CPU utilization.
Thanks again, cheers,
Alan
I made a few tests with the great new shader based upscalers you implemented.
I have to tell they really make a difference . To my eyes Lanczos 3 optimized is the same quality as the software implementation. It looks really really good.
However i realized that i can't use one specific upscaler to all SD and HD videos, because my HW can not take it. For example Lanczos 3 is too slow for my Nvidia 9400 even in SD scenario, but Lanczos 3 optimized works really awesome with excellent quality. But even Lanczos 3 optimized is not fast enough in case of 720p material upscaled to 1080p.
Also i realized that in case of vdpau used, if i change the upscaler, nothing happens. I guess it uses vdpau internal upscaler in any case.
So to solve all these problems i have a suggestion. Maybe we could divide the gui setting for video "Render method" into two lines:
1. Render method for SD videos: Auto detect
2. Render method for HD videos: Auto detect
The default setting could be Auto detect, which could work just like before.
If the user sets the renderer different from Auto Detect, he gets another setting line appear for the available upscaler types for that specific renderer where he can set the desired upscaler separately for SD and for HD videos.
For example:
1. Render method for SD videos: GLSL
Upscaler used for SD videos: Lanczos 3 optimized
2. Render method for HD videos: Auto detect
Or:
1. Render method for SD videos: GLSL
Upscaler used for SD videos: Lanczos 2
2. Render method for HD videos: Crystal-HD
Upscaler used for HD videos: Bicubic
What do you think about the idea ?
Some kind of separation between SD and HD methods is really needed i think.
One other thing i realized is that now with SW upscalers i get a magnified portion of the movie. But this started before you started implementing these great HW upscalers.
Great work and thanks also in the name of all ION users who can from now enjoy HQ upscaled SD videos with minimal CPU utilization.
Thanks again, cheers,
Alan