-
Notifications
You must be signed in to change notification settings - Fork 28
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
Color artefacts #67
Comments
Looks like it could be ringing caused by bicubic interpolation. Maybe we Do we have X3F for this or some other Quattro X3F with serious fringing On vie, 2015-07-31 at 04:23 -0700, Roland Karlsson wrote:
|
Another thought, maybe resampling should not be done at the YUV level. On vie, 2015-07-31 at 17:58 +0200, Erik Karlsson wrote:
|
How about a less cosher upscaling? My idea is to do all computations at 5 Mpixel and then /Roland |
You mean nearest neighbor? On vie, 2015-07-31 at 09:55 -0700, Roland Karlsson wrote:
|
I am doing some experimentation with various interpolation methods and dp2q_SDIM0003.X3F, but the differences are not very obvious. I would need an X3F file with more obvious fringing issues. |
Yes ... the first 5 to 20 MP upscaling is nearest neighbor. /Roland On 2015-07-31 18:58, Erik Karlsson wrote:
|
Our Quattro expansion has another edge-related problem that is apparent in dp2q_SDIM0003.X3F. At the edge between the light blue sky and the dark gray building, there is a dark blue line. This is obviously a combination of the blue color of the sky and the darkness of the building. Changing the interpolation to bilinear (maybe necessary to get rid of fringing) unsurprisingly worsens this problem. Nearest neighbor makes it even worse. SPP does not seem to have this problem at all. Neither does it have the fringing problem. Some trickery going on? Edge detection maybe? |
I have tested converting back from YUV to BMT before resampling too. There is no visible difference. |
As I mentioned, nearest neighbor does not seem to work very well at all. On vie, 2015-07-31 at 10:44 -0700, Roland Karlsson wrote:
|
I assume they have a pattern based algorithm. In our case. It is not likely that a dark gray area has a one Hmmmm ... this might explain why Quattro seems so sharp. /Roland On 2015-07-31 20:11, Erik Karlsson wrote:
|
In any case, our current approach of simply upsampling the chrominance On vie, 2015-07-31 at 11:48 -0700, Roland Karlsson wrote:
|
What about a variant of nearest neighbor, where the pixels just use the On Friday, July 31, 2015, Erik Karlsson notifications@github.com wrote:
|
I suppose you mean replicating each chroma pixel as a 2x2 square and On vie, 2015-07-31 at 12:28 -0700, mmroden wrote:
|
We could experiment with wackiness-- a few different methods, then choose On Friday, July 31, 2015, Erik Karlsson notifications@github.com wrote:
|
Yes, we can do some edge detection research :) |
I flag this as important since it seems to be a general Quattro issue. |
In this DPReview post some artefacts are evident.
http://www.dpreview.com/forums/post/56218184
The text was updated successfully, but these errors were encountered: