The squares in the upper image part represent overexposed areas within the RAW data. Which means the light was so bright that the sensor data is corrupt.
Programs like Rawtherapee or others can only try to âimagineâ what data could have been there.
Resulting problems often are flawed white balances:
To set the white balance I first tool a sample from the âgreyâ sky in the top-right. The result is a greenish image, which you can see in the left half of the screenshot
On the right side you see the white balance taken from a sample from the stonewall in the center (where the small rectangle is). Here the white balance looks good.
What works different in various programmes are the algorithms for highlight reconstructions for overexposed areas.
Sometimes they look good, sometimes they create weird colors.
My recommendation: Take a properly exposed photo and load it into Rawtherapee and Photoshop. I donât think that there will be bigger problems.
Edit: For highlight reconstruction programs look for colors around the overexposed areas and try to move them into them. Could be that some details like these fine lines are lost. In these areas it is not easy to detect valid data.
Iâm guessing that this, plus the fact that the Galaxy S10 has three back-facing cameras (plus 2 front facing, although itâs hard to imagine taking the selfie cameras seriously), will make things difficult unless each camera/sensor combination can be identified.
Cameras:
12 Megapixel f/1.5-2.4 variable aperture camera with 960 FPS slow-mo, 4k, etc
is true, but not affect our case, bc only one camera can shoot in raw in all devicesâŚ
and different models have different code name SM-G9*** but only two mods.
@heckflosse
its ok, im wait, but please just dont forget about me compleatly
Please donât make your prejudice about open source projects into a self-fulfilling prophecy. You need to adjust your expectations for open source projects.
Itâs entirely up to the developers to decide if they want to work with timelines and so forth, or just cherry-pick issues along the way. You might think this means a project is badly organised, but thatâs the reality whenever something is done entirely by volunteers.
Donât assume your issue needs priority, simply because it affects you.
Keep a constructive dialogue when the developers arenât as quick as you would like, donât get defensive.
hey bro, with all respect, but what the hell self-fulfilling prophecy???
from the start i ask only for easy and short answer that clear situation -
âyes, we will take about for X-weeksâ
or
âno, we will not take, until there is no possibility and we do not see it in the next six months, later - perhaps.â
like that, itâs so simple and itâs damn banal politeness.
I do NOT command âquickly add urgently, bastards,â NO.
Iâm not aware of your situation, right? simple explanation of intentions, and approximate timelines âŚ
why make me a villain?
@Morgan_Hardwood
This link was needed from the beginning!
we would not have lost almost 2 months ⌠then you answered me about the color target, I thought that it was necessary to have it âŚ
So I took pictures, because the article does not contain words about white balance, I left the auto.
I hope I did everything right, shoot all in 1 sec, for all available modes of ISO, for each available aperture (there are only 2).
but there is one photo exception.
The fact is that the stock camera in manual mode has a restriction of only ISO800 when the module itself and third-party applications can choose FREE value up to ISO1250! but at the same time 1s, can only be selected in the stock application, and the rest are limited to 1/10.
so please let me know if i do something wrong or need something else, i do again. @heckflosse
ps i have error upload for Filebin, so i put files here GalaxyS10.7z (268.6 KB)
@Morgan_Hardwood
ok, thank for say it! no problem
but can you at least just look and say im do correct samples or no? so i can fix them for this weak.
or check this take lot of time too?