I'm just a user stuck with a long-outstanding issue, trying to be as supportive as possible to reach a resolution, even if that's a kluge I need to incorporate. I will do whatever it takes (short of changing the camera system, or having to use LightRoom). I haven't gotten anywhere in a frustratingly long time. Anything constructive you can provide will be hugely appreciated.
Thanks!
This whole thing doesn't look right. Raw converter developers are supposed to open an issue with us if there is a bug in libraw raw data decoding. I don't see such an issue re Sigma, including opened by the Affinity team. That means the ball is in their court.
Your request doesn't make it clear what needs to be fixed on our side. We deliver the raw data, the rest is up to the raw converter programmers.
deejjjaaaa: yes, you're right, that link was one of about 20+ ongoing posts since December 2019 on the Affinity Photo support forum.
Alex: I apologize, as I can only trust what the authoritative people each tell me, and Affinity (as clearly as they seem to be able to) say they have escalated this to LibRaw, and that it is a LibRaw issue, having nothing to do with them. Pretty well the same as LibRaw feels it is not in their power to remedy this, but rather Affinity's.
Since I seem to have a "he said - he said' issue, would you be kind enough to provide any constructive steps to isolate whom I can work with to resolve this?
There's a good number of users for these 5 cameras with the same issues, and since this sensor's image processing works similarly to prior models, it might hopefully be something reproducible. I've lost nearly a year and a half unsuccessfully trying to obtain support on this one issue from Affinity, so anything that 'moves the needle forward' will be hugely appreciated!
Please also note that LibRaw will typically scale your raw values between the black and white levels during the linearization step (e.g. 65535*(x - black)/(white-black)), so you might get larger values even for gamma=1.0.
Unfortunately I found that if you set no_auto_scale as well to disable this, you also kill LibRaw's white balance for some reason, which is typically not good for the demosaicing step, see https://github.com/letmaik/rawpy/issues/101
I can’t understand what kind of additional support you require from our library.
LibRaw provides access to RAW data for calling application (e.g. Affinity). Calling application is responsible for this data interpretation and processing (e.g. channel mixing if one want to treat Foveon image as BW).
I think I found the issue (mix of versions in my lib folder). Sorry for that.
Sorry to ask you that but do you have any idea about the date of the next stable release ?
Attached one file, but I have same issue with other CR3,
Maybe I'm doing something wrong, but my code is working for all other formats. So I don't know.
I see. Thank you very much.
IIQ S is not (publicly) documented and not reverse engineered (at least, there is no any opensource decoders).
We do not expect IIQ S support in foreseeable future.
Dear Sir:
Without clear communication from Affinity we can't help, I'm afraid. We simply don't understand the issue they are having.
Again, my apologies Iliah.
I'm just a user stuck with a long-outstanding issue, trying to be as supportive as possible to reach a resolution, even if that's a kluge I need to incorporate. I will do whatever it takes (short of changing the camera system, or having to use LightRoom). I haven't gotten anywhere in a frustratingly long time. Anything constructive you can provide will be hugely appreciated.
Thanks!
There are two options for (no) auto-scaling:
1) params.no_auto_bright - disables ETTR(-like) automated brightness correction, entire image is scaled to 65535/(metadata_derived_maximum-black) instead of 65535/(real_data_max_by_histogram - black).
2) params.no_auto_scale - disables entire scale_colors() call (for example, to get not modified data in image array).
Second case is special use (e.g. someone may want to do own interpolation via callback and want to see unchanged data on this step).
In (normal) processing case scaling is significant to get same scaled data from all different sensor bit-counts.
This whole thing doesn't look right. Raw converter developers are supposed to open an issue with us if there is a bug in libraw raw data decoding. I don't see such an issue re Sigma, including opened by the Affinity team. That means the ball is in their court.
Your request doesn't make it clear what needs to be fixed on our side. We deliver the raw data, the rest is up to the raw converter programmers.
deejjjaaaa: yes, you're right, that link was one of about 20+ ongoing posts since December 2019 on the Affinity Photo support forum.
Alex: I apologize, as I can only trust what the authoritative people each tell me, and Affinity (as clearly as they seem to be able to) say they have escalated this to LibRaw, and that it is a LibRaw issue, having nothing to do with them. Pretty well the same as LibRaw feels it is not in their power to remedy this, but rather Affinity's.
Since I seem to have a "he said - he said' issue, would you be kind enough to provide any constructive steps to isolate whom I can work with to resolve this?
There's a good number of users for these 5 cameras with the same issues, and since this sensor's image processing works similarly to prior models, it might hopefully be something reproducible. I've lost nearly a year and a half unsuccessfully trying to obtain support on this one issue from Affinity, so anything that 'moves the needle forward' will be hugely appreciated!
All my best,
DLJ
Please also note that LibRaw will typically scale your raw values between the black and white levels during the linearization step (e.g. 65535*(x - black)/(white-black)), so you might get larger values even for gamma=1.0.
Unfortunately I found that if you set no_auto_scale as well to disable this, you also kill LibRaw's white balance for some reason, which is typically not good for the demosaicing step, see https://github.com/letmaik/rawpy/issues/101
dcraw_ppm_tiff_writer() applies gamma curve on write (imgdata.image[] is linear, while output is usually not).
To set gamma curve to linear use
imgdata.params.gamm[0] = imgdata.params.gamm[1] = 1.0;
Thanx.
I still do not see anything that should be *fixed* on our side (hope Affinity postprocessing is own, not demo code provided by our library)
I think he refers to this thread = https://forum.affinity.serif.com/index.php?/topic/93631-outstanding-bw-o...
Also, you wrote:
> This issue was escalated to the LibRaw dev team by the Affinity (Serif) devs about a year ago
Sure? Never heard of something like this
I can’t understand what kind of additional support you require from our library.
LibRaw provides access to RAW data for calling application (e.g. Affinity). Calling application is responsible for this data interpretation and processing (e.g. channel mixing if one want to treat Foveon image as BW).
That's right.
But package are built only on stable release :).
Cheers,
current master is stable enough for production usage.
I think I found the issue (mix of versions in my lib folder). Sorry for that.
Sorry to ask you that but do you have any idea about the date of the next stable release ?
Cheers,
I also have a good tiff file.
But for a reason a I don't understand, libraw_open_file returns an error.
OK thanks. I've no doubt the issue is on my system then, thank you so much.
Stay safe,
Cyril
I recloned the git repo.
I wrote:
printf("version: %s\n", LIBRAW_VERSION_STR);
return(libraw_open_file(rawdata, name));
And I have:
version: 0.20.0-WorkInProgress
Error in libraw Unsupported file format or not RAW file
I need to investigate then.
I've tested with fresh git clone:
git clone https://github.com/LibRaw/LibRaw.git LibRaw.gh && cd LibRaw.gh && make -f Makefile.devel CXX=clang++ CC=clang -j4 && ./bin/dcraw_emu -T -w ~/1/canon_eos_m50_07.cr3
This results in ~/1/canon_eos_m50_07.cr3.tiff as expected
(note CXX=.. CC=.. is for my system with clang installed as c++ compiler).
Thank you for the sample. I do not see any problems with this file.
Please make sure you're using up-to-date master branch from Github,
Attached one file, but I have same issue with other CR3,
Maybe I'm doing something wrong, but my code is working for all other formats. So I don't know.
https://www.dropbox.com/s/38yf9tcqtvnihll/canon_eos_m50_07.cr3?dl=0
Could you please share sample file with us
Hello, with the master version I have the following error with m50 cr3:
Unsupported file format or not RAW file
Cheers,
CR3 support is published in Oct 2019.
Pages