When are you adding "Sony IMX490 imaging sensor (Bayer sensor, with a resolution of 2880 × 1856)" to the list. I need help with conversion of .raw file from this camera to 16-bit Tiff
auto balance is based on the idea of a "average gray" world, which is not true for global colored scenes.
If you take a photo of a green grass, then the result of automatic white balance will not satisfy you too.
I didn't know FastRawViewer has it's own processing. That's interesting...
I too was able to achieve that image, but only after i manually switched the wb method.
Anyway, since i cant invest in a whole new post-processing infra at the moment, and considering your comment:
"I do not think that auto-balance is well suited for such images with overall warm tint."
can you suggest a good way to detect said warm tints, so as to switch from auto to camera wb automatically, or is this something only human eye can detect and decern?
Separate user here. To clarify, if I’m interested in having the ProfileGainTableMap processed (so images don’t come out underexposed), would building with the DNG SDK and setting these flags accomplish this? I’m currently trying (and failing) to get a build for this, so it’d be helpful to know before I spend more time getting it to build.
I tried to extract the full image and the left image from an dual pixel cr3 RAW file. I have used dcraw_emu.exe -r 1 1 1 1 -M -o 0 -4 -T -s 0 "example.cr3". With changing the -s from 0 to 1 i get the second image. But the imagesis already debayered. Is it possible to get the non debayered images?
ARW files are really TIFF(like)-containers, so all ARW-specific code is specific tag values parsing/assignment to internal data structures.
The main analysis is common to all tiffs.
>> 1st: R6 Mark II is not supported yet
I know and I mentioned in my original post
I do not doubt that libraw will support R6 Mark II sooner or later that is why I am ready to provide sample files and take part in testing if needed.
>> 2nd: your 2298 file is damaged
Probably it is and there are many other files from my R6m2 damanged in same way.
I mention "probably" because it looks strange:
* other software (DXO PureRaw, Adobe Photoshop, FastStone Image Viewer) works with this file fine
* I took and processed thousands of images from this camera already and I got no issues until I tried to take astro images and load in into Siril
* I have many more samples of random files from the camera that are "damaged" (and could be processed fine with other software).
you can try to use FastRawViewer and see what per-channels multipliers "they" suggest ( that is assuming EasyHDR uses the same approach as FRV), then you can adjust as shot WB tag in DNG using exiftool or so and feed it to ACR/LR and use as shot WB there ... ___BUT___ the same colors of course is a different story because the whole color transform is more than just the WB ...
It is usually pointless to discuss problems in processing a file without having the file itself
open_bayer() call is also available via C-API: https://www.libraw.org/docs/API-C.html
If your python wrapper does not provide access to this call: ask your vendor to add it.
This library is in C++, i have done all of my work in python. Is there any other alternative?
I have tried rawpy it doesn’t support .raw images from above mentioned camera
LibRaw::open_bayer will probably help.
When are you adding "Sony IMX490 imaging sensor (Bayer sensor, with a resolution of 2880 × 1856)" to the list. I need help with conversion of .raw file from this camera to 16-bit Tiff
It will in some future public update.
You can start with our free preview extractor:
https://www.fastrawviewer.com/RawPreviewExtractor
Forgive me for my ignorance, but can this snapshot be used in Windows to preview RAW files in the folder? How then?
Thanks
ILCE-7RM5 (A7-R5) support is provided by the latest snapshot: https://www.libraw.org/news/libraw-202403-snapshot
auto balance is based on the idea of a "average gray" world, which is not true for global colored scenes.
If you take a photo of a green grass, then the result of automatic white balance will not satisfy you too.
Than you so much for the quick response.
I didn't know FastRawViewer has it's own processing. That's interesting...
I too was able to achieve that image, but only after i manually switched the wb method.
Anyway, since i cant invest in a whole new post-processing infra at the moment, and considering your comment:
can you suggest a good way to detect said warm tints, so as to switch from auto to camera wb automatically, or is this something only human eye can detect and decern?
Also: here is your file processed with dcraw_emu -w -T : https://www.dropbox.com/scl/fi/6gl21svjvs5wy1wzlb4fv/Y-Sigma24-70A-5D3-1...
I do not think that auto-balance is well suited for such images with overall warm tint.
FastRawViewer uses own postprocessing, not LibRaw's
Hello Alex,
sometimes I can't see the wood for the trees - sorry for the obvious mistake on my side :)
Many thanks for pointing it out,
Michael
You need to add LibRaw source files added in last public snapshot to your build.
(src/decoders/sonycc.cpp and src/decoders/pana8.cpp)
DNG SDK Applies ProfileGainTableMap in dng_renderer (RAW to RGB conversion), not in stage3 opcodes.
Separate user here. To clarify, if I’m interested in having the ProfileGainTableMap processed (so images don’t come out underexposed), would building with the DNG SDK and setting these flags accomplish this? I’m currently trying (and failing) to get a build for this, so it’d be helpful to know before I spend more time getting it to build.
To extract unprocessed data use unprocessed_raw sample
I tried to extract the full image and the left image from an dual pixel cr3 RAW file. I have used dcraw_emu.exe -r 1 1 1 1 -M -o 0 -4 -T -s 0 "example.cr3". With changing the -s from 0 to 1 i get the second image. But the imagesis already debayered. Is it possible to get the non debayered images?
What exactly are you doing and how and what are you failing at?
ARW files are really TIFF(like)-containers, so all ARW-specific code is specific tag values parsing/assignment to internal data structures.
The main analysis is common to all tiffs.
Please check with Adobe DNG Converter and select files that processed OK by this program, but damaged in LibRaw.
>> 1st: R6 Mark II is not supported yet
I know and I mentioned in my original post
I do not doubt that libraw will support R6 Mark II sooner or later that is why I am ready to provide sample files and take part in testing if needed.
>> 2nd: your 2298 file is damaged
Probably it is and there are many other files from my R6m2 damanged in same way.
I mention "probably" because it looks strange:
* other software (DXO PureRaw, Adobe Photoshop, FastStone Image Viewer) works with this file fine
* I took and processed thousands of images from this camera already and I got no issues until I tried to take astro images and load in into Siril
* I have many more samples of random files from the camera that are "damaged" (and could be processed fine with other software).
So, let me know if you need file samples.
1st: R6 Mark II is not supported yet
2nd: your 2298 file is damaged. Adobe DNG Converter also agrees with this: https://www.dropbox.com/scl/fi/s19zw6bylther2fvh6cyp/Screenshot-2024-03-...
you can try to use FastRawViewer and see what per-channels multipliers "they" suggest ( that is assuming EasyHDR uses the same approach as FRV), then you can adjust as shot WB tag in DNG using exiftool or so and feed it to ACR/LR and use as shot WB there ... ___BUT___ the same colors of course is a different story because the whole color transform is more than just the WB ...
Pages