Recent comments

Reply to: DNG file causes crash in LibRaw 0.19-Snapshot-20170812   6 years 3 months ago

Also, no problems with
MSVC 2013/x64, nmake -f Makefile.msvc

dcraw_emu -T yourfile.dng produces TIFF file as expected

Could you please provide more details about the crash? May be binary + .pdb file + crash dump?

Reply to: DNG file causes crash in LibRaw 0.19-Snapshot-20170812   6 years 3 months ago

Thank you (again) for the file.

I'm unable to reproduce the crash using LibRaw compiled with gcc5/freebsd. Will check more with Windows/Visual studio

Reply to: Issue with Nikon Coolpix B700 files   6 years 3 months ago

OK, thanks for your fast reply. I will try with development snapshot.

Reply to: Issue with Nikon Coolpix B700 files   6 years 3 months ago

Thank you for the files.

There is bug in 0.18 in handling some NRW files.

Development snapshot handles these files OK, use it: https://github.com/LibRaw/LibRaw/

(this snapshot is stable for release use, it tested with our RawDigger/FastRawViewer sw).

Reply to: Issue with PEF file   6 years 3 months ago

LibRaw 0.18 will receive security fixes only. Use public development snapshot, it is stable enough to use in production

Reply to: Problem opening IIQ files   6 years 3 months ago

Ok, I will give it a try. Thanks a lot for your great work.

Reply to: Problem opening IIQ files   6 years 3 months ago

0.18 will receive only security fixes, no new cameras, sorry.

LibRaw is surely compatible with gcc 4+, clang 3+ (may be 2+ too), Visual Studio 2010+ (not sure about 2008). Most of these tools are available for free (including Visual Studio community edition), so I advise you to switch to current public snapshot (from github), it is stable enough for production use (and we use it for RawDigger and FastRawViewer).

Reply to: Problem opening IIQ files   6 years 3 months ago

Thanks for your reply and for taking time to find a solution so quickly.

I have not yet tried to build libRaw from sources, this is not easy for me because I have to use an old version of Visual Studio (2005) for my application. Do you plan to release a 0.18.x version including this fix or will it be in 0.19 ?

Thanks.
Eric

Reply to: Problem opening IIQ files   6 years 3 months ago

Thank you for sample.
This is due to additional raw metadata integrity check added somewhere before 0.18 version.
It is already fixed in development snapshot, please apply this patch to 0.18: https://github.com/LibRaw/LibRaw/commit/ade8d9a0be16079b177bdb5ec33dd880...

Reply to: Problem opening IIQ files   6 years 3 months ago

Thanks for yout fast reply. I am going to send you one samle file right now.

I just want to correct something that I said in my first post. Suspecting an authorization problem, I changed the location of the input file : now, I get an error code -2 (Unsupported file format or not RAW file) when using open_file.

Reply to: Problem opening IIQ files   6 years 3 months ago

You may upload sample to some file sharing service (Dropbox, Google drive, WeTransfer/free version, etc) and send link to info@libraw.org

Please do not use 'share for' Google/Dropbox service, because it requires account linked to specific email, just 'share for anyone who knows the URL'

Reply to: Problem opening IIQ files   6 years 3 months ago

Could you please provide sample file that do not open?

Reply to: Use LibRaw with CodeBlocks and mingw on windows   6 years 3 months ago

Do not use mingw, according to quick googling you need to add ws2_32 library to link options to get htons and other these functions for mingw: http://mingw.5.n7.nabble.com/Link-error-undefined-reference-to-htonl-4-w...

Reply to: Oneplus 5 DNGs don't look right   6 years 4 months ago

Well, if the "as shot" multipliers worked, I wouldn't have asked about the auto WB thing :)

Reply to: Oneplus 5 DNGs don't look right   6 years 4 months ago

Yes, auto balance does not work well for colored shots. Use as-shot (camera wb) instead.

Reply to: Oneplus 5 DNGs don't look right   6 years 4 months ago

Oh, so this won't work for a photo of the sea and sky, or a forest canopy with little sky, etc.
I will take a look at that code after I finish some other things, thanks!

Reply to: Oneplus 5 DNGs don't look right   6 years 4 months ago

sorry for geshifilter-c in previous message, sometimes code formatter on our site works strange :)

this is just [ c ]

Reply to: Oneplus 5 DNGs don't look right   6 years 4 months ago

There is no exposed function.

You may steal code from internal\dcraw_common.cpp:scale_colors() function;

Starting with

  if (use_auto_wb || (use_camera_wb && cam_mul[0] == -1))
  {

And up to final calculation of pre_mul:

 pre_mul[geshifilter-c] = dsum[c + 4] / dsum[c];


This code cycle through image[] 8x8 blocks, skip blocks with data near sensor saturation and calculates pixel sum/count for other (non-saturated) blocks to get mean per-channel values. This code assumes entire image is (average) gray. If not, auto-WB will not work well.[/geshifilter-c]

Reply to: Oneplus 5 DNGs don't look right   6 years 4 months ago

Sorry, I meant if there was a way to get the auto WB. I know I can get the "as shot" WB.

Right now, I do things like this:
Init, open, unpack, raw2image, black subtraction, apply WB, debayer, sRGB, gamma curve then I do things like contrast and saturation.

Is there a function I can call after black subtraction to make LibRaw return an auto calculated WB, preferably accessible from C, without doing further data processing?

Reply to: Oneplus 5 DNGs don't look right   6 years 4 months ago

as-shot balance (cam_mul) is avaliable just after LibRaw::open_file()

To calculate auto-wb you may use raw data with black subtracted (Libraw does this at LibRaw::scale_colors() call, before interpolation step)

Reply to: Oneplus 5 DNGs don't look right   6 years 4 months ago

I meant, if there was a way to only get the WB, without fully process the image (so that I can do my own processing).

Reply to: Oneplus 5 DNGs don't look right   6 years 4 months ago

params.use_camera_wb will force to use As-shot balance
params.use_auto_wb will switch to auto-balance
params.user_mul[4] allows to use user-specified WB

Reply to: Oneplus 5 DNGs don't look right   6 years 4 months ago

Any idea how RawTherapee gets it right?
Is there a way to force LibRaw to manually calculate the WB and put it in cam_mul or something like that? Or is it too orthogonal to it's purpose? :)

Reply to: Oneplus 5 DNGs don't look right   6 years 4 months ago

Also, with as-shot balance sky is 'too cyan' in FastRawViewer, that also points to not-so-correct embedded color profile.

Reply to: Oneplus 5 DNGs don't look right   6 years 4 months ago

From _01.DNG sample, using raw-identify -v:
Makernotes 'As shot' WB multipliers: 2.031746 1.000000 1.729730 0.000000
and
Derived D65 multipliers: 6.630021 0.866640 0.901968

This file is shot under daylight, so D65 mutipliers looks incorrect: too weak for blue and too strong for red.
D65 (daylight) multipliers are calculated from DNG ColorMatrix* tag(s). So, embedded profile for this file looks incorrect.

Use as-shot, or auto WB for this camera (I do not see any way to do this automatically in LibRaw because pre_mul is within 'more or less correct values' (6.63/0.86 = 7.7 does not 'high enough' to throw it out automatically)

Pages