Hi guys,
I know a few people have asked this question, but no satisfied answer that I can find. So please help:
I am trying to install on Windows and using with visual studio.
And I don't understand this line in documentation:
"Set the environment parameters so that the compiler/linker would find the libraries and include-files. For Visual C++, this is done by running vcvars32.bat."
I'm experimenting with DNG images loading. I'm using LibRaw and I'm trying to achieve the same result as with dcraw processing, but I can't. White balance is different (see. image in the attachement).
dcraw command I'm using (it's dcraw 9.26 built from the source code):
dcraw -h sunset.dng
dcraw_emu command (it's LibRaw 0.20 built from the sources):
Hi there,
I am a student, who tries to implement a routine for homework. I am totally new to this library and it took me a while to link it to my VS2019 environment. But now it basically works fine, but...
I am currently starting with a vertical slice of my homework. So I try to figure out, how to read out indivduell pixel color information. Unfortunately I pick implausible values.
I downloaded latest beta1 of libraw 0.20, compiled it with gcc 7.3 inside CodeBlocks IDE.
All is working fine.
No I enabled gpr_sdk as follows:
- I set both compiler options USE_GPRSDK and USE_DNGSDK
- I downloaded gpr_sdk from https://github.com/gopro/gpr as given in file README-GoPro.txt
I did no modification to any of these files
- I put the options where to find the *.h files and tried to compile libraw
I have an issue with reading monochromatic DNG image. The result is pretty weird. I can't figure out if there are problems with the source DNG image itself, or with LibRaw. Maybe I'm using it wrong, but usually DNG images are loaded pretty well. But not this one.
In the attachement there is comparison image just to take a quick look at the problem.
Hello! For starters, thank you for putting together a wonderful toolkit!
I'm working on a C# project that currently uses FreeImage for raw image processing, and converting it over to libraw so it can support newer raw image formats.
I did a bit of searching, and an earlier thread mentioned setting DCRAW_VERBOSE when compiling to get verbose output when running dcraw_process. However, when I search the libraw code for DCRAW_VERBOSE, the only reference I can find to that string is in a changelog. Is this still the right way to turn on verbose output?
The 0.19.5 array of supported cameras says "Olympus E5 Mark II", but the camera reports "Olympus E5MarkII", so when I check against the array I don't get a match. Will you be able to fix this in the next release?
Are you yet in a position to say (plus or minus a few weeks) when you'll be releasing the next "Stable" release?
Recent comments