AMaZE a bit less sharp with the new multipliers (at least in some cases)

[ilia3101]

Two screenshots, could not get image saving to work. One is MLV App 1.3 (should be same as 1.4), other is 1.5 - the new one is a bit less sharp, sharpening for both was set at 60 (same MASXML)

Open in browser tabs, switch between to pixel peep.

Just making this issue so I don't forget.

[masc4ii]

Interesting. I agree it was a tiny little bit sharper before in your example. Can't find that with my own examples. For me just aliasing and artifacts are a tiny little bit better now (mostly cyan and magenta).

[masc4ii]

Have you had a look, what happens, if you comment out the WB converting completely? Is it still sharper then?

[ilia3101]

Have you had a look, what happens, if you comment out the WB converting completely? Is it still sharper then?

Doesn't this just make there be loads of moire like in the very early days of MLV App? Or I misinterpreted what that means?

[masc4ii]

No, you're right. But I don't know what should blur the picture. So if the new algorithm blurs, the old should blur too. Maybe the sharpest is untouched... nothing more was my question and idea.

[ilia3101]

I want to add a "Debayer white balance" option - a slider inside the raw corrections where you can set the temperature, maybe tweaking it would help for these cases where it's less sharp.

[bouncyball-git]

May be that Debayer WB also could be done with picker? Should be more accurate.

[ilia3101]

would be a good option to have as well

[masc4ii]

I don't expect big differences - just some more or less cyan/green edge artifacts. So I don't think for now a picker is needed. In the end you will have to pixel peep to see a difference - so I don't think a picker helps there. A slider should be interesting for finetuning.

[ilia3101]

Have there been any multiplier changes since I opened this?

My 5D3 shots are looking awfully badly debayered :(

[masc4ii]

No idea... I don't think there is much happened. Maybe the wb / wbundo function is newer than that?!

[ilia3101]

Ok I think it is because I'm using 12 bit in crop_rec, so the image is 14 bit and only using a small 12 bit sized range (so amaze cant work very well)