Recent comments

Reply to: Libraw slowdown when updating 19.2 to 20.2   1 year 9 months ago

Thanks for your response,

But I would like to know what you mean with more detailed measurements?

So the behavior is quite ok-ish ? And depends on image 19.2 or 20.2 can win the race?

Thanks in advance.

Reply to: Compilation issues under Linux   1 year 9 months ago

I also tried autoreconf --install and then running configure.

I got:

$ autoreconf --install

configure.ac:11: warning: The macro `AC_PROG_LIBTOOL' is obsolete.
configure.ac:11: You should run autoupdate.
m4/libtool.m4:99: AC_PROG_LIBTOOL is expanded from...
configure.ac:11: the top level
configure.ac:14: warning: The macro `AC_LIBTOOL_WIN32_DLL' is obsolete.
configure.ac:14: You should run autoupdate.
m4/ltoptions.m4:148: AC_LIBTOOL_WIN32_DLL is expanded from...
configure.ac:14: the top level
configure.ac:14: warning: AC_LIBTOOL_WIN32_DLL: Remove this warning and the call to _LT_SET_OPTION when you
configure.ac:14: put the 'win32-dll' option into LT_INIT's first parameter.
./lib/autoconf/general.m4:2434: AC_DIAGNOSE is expanded from...
m4/ltoptions.m4:148: AC_LIBTOOL_WIN32_DLL is expanded from...
configure.ac:14: the top level
configure.ac:11: warning: The macro `AC_PROG_LIBTOOL' is obsolete.
configure.ac:11: You should run autoupdate.
m4/libtool.m4:99: AC_PROG_LIBTOOL is expanded from...
configure.ac:11: the top level
configure.ac:14: warning: The macro `AC_LIBTOOL_WIN32_DLL' is obsolete.
configure.ac:14: You should run autoupdate.
m4/ltoptions.m4:148: AC_LIBTOOL_WIN32_DLL is expanded from...
configure.ac:14: the top level
configure.ac:14: warning: AC_LIBTOOL_WIN32_DLL: Remove this warning and the call to _LT_SET_OPTION when you
configure.ac:14: put the 'win32-dll' option into LT_INIT's first parameter.
./lib/autoconf/general.m4:2434: AC_DIAGNOSE is expanded from...
m4/ltoptions.m4:148: AC_LIBTOOL_WIN32_DLL is expanded from...
configure.ac:14: the top level
libtoolize: `./ltmain.sh' is newer: use `--force' to overwrite
libtoolize: `m4/libtool.m4' is newer: use `--force' to overwrite
libtoolize: `m4/ltoptions.m4' is newer: use `--force' to overwrite
libtoolize: `m4/ltversion.m4' is newer: use `--force' to overwrite
configure.ac:11: warning: The macro `AC_PROG_LIBTOOL' is obsolete.
configure.ac:11: You should run autoupdate.
m4/libtool.m4:99: AC_PROG_LIBTOOL is expanded from...
configure.ac:11: the top level
configure.ac:14: warning: The macro `AC_LIBTOOL_WIN32_DLL' is obsolete.
configure.ac:14: You should run autoupdate.
m4/ltoptions.m4:148: AC_LIBTOOL_WIN32_DLL is expanded from...
configure.ac:14: the top level
configure.ac:14: warning: AC_LIBTOOL_WIN32_DLL: Remove this warning and the call to _LT_SET_OPTION when you
configure.ac:14: put the 'win32-dll' option into LT_INIT's first parameter.
./lib/autoconf/general.m4:2434: AC_DIAGNOSE is expanded from...
m4/ltoptions.m4:148: AC_LIBTOOL_WIN32_DLL is expanded from...
configure.ac:14: the top level
configure.ac:11: warning: The macro `AC_PROG_LIBTOOL' is obsolete.
configure.ac:11: You should run autoupdate.
m4/libtool.m4:99: AC_PROG_LIBTOOL is expanded from...
configure.ac:11: the top level
configure.ac:14: warning: The macro `AC_LIBTOOL_WIN32_DLL' is obsolete.
configure.ac:14: You should run autoupdate.
m4/ltoptions.m4:148: AC_LIBTOOL_WIN32_DLL is expanded from...
configure.ac:14: the top level
configure.ac:14: warning: AC_LIBTOOL_WIN32_DLL: Remove this warning and the call to _LT_SET_OPTION when you
configure.ac:14: put the 'win32-dll' option into LT_INIT's first parameter.
./lib/autoconf/general.m4:2434: AC_DIAGNOSE is expanded from...
m4/ltoptions.m4:148: AC_LIBTOOL_WIN32_DLL is expanded from...
configure.ac:14: the top level
configure.ac:11: warning: The macro `AC_PROG_LIBTOOL' is obsolete.
configure.ac:11: You should run autoupdate.
m4/libtool.m4:99: AC_PROG_LIBTOOL is expanded from...
configure.ac:11: the top level
configure.ac:14: warning: The macro `AC_LIBTOOL_WIN32_DLL' is obsolete.
configure.ac:14: You should run autoupdate.
m4/ltoptions.m4:148: AC_LIBTOOL_WIN32_DLL is expanded from...
configure.ac:14: the top level
configure.ac:14: warning: AC_LIBTOOL_WIN32_DLL: Remove this warning and the call to _LT_SET_OPTION when you
configure.ac:14: put the 'win32-dll' option into LT_INIT's first parameter.
./lib/autoconf/general.m4:2434: AC_DIAGNOSE is expanded from...
m4/ltoptions.m4:148: AC_LIBTOOL_WIN32_DLL is expanded from...
configure.ac:14: the top level
configure.ac:11: warning: The macro `AC_PROG_LIBTOOL' is obsolete.
configure.ac:11: You should run autoupdate.
m4/libtool.m4:99: AC_PROG_LIBTOOL is expanded from...
configure.ac:11: the top level
configure.ac:14: warning: The macro `AC_LIBTOOL_WIN32_DLL' is obsolete.
configure.ac:14: You should run autoupdate.
m4/ltoptions.m4:148: AC_LIBTOOL_WIN32_DLL is expanded from...
configure.ac:14: the top level
configure.ac:14: warning: AC_LIBTOOL_WIN32_DLL: Remove this warning and the call to _LT_SET_OPTION when you
configure.ac:14: put the 'win32-dll' option into LT_INIT's first parameter.
./lib/autoconf/general.m4:2434: AC_DIAGNOSE is expanded from...
m4/ltoptions.m4:148: AC_LIBTOOL_WIN32_DLL is expanded from...
configure.ac:14: the top level

$ configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C++... yes
checking whether g++ accepts -g... yes
checking for g++ option to enable C++11 features... none needed
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for gcc... gcc
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... -std=gnu11
checking whether gcc -std=gnu11 understands -c and -o together... yes
checking dependency style of gcc -std=gnu11... gcc3
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc -std=gnu11... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc -std=gnu11 object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc -std=gnu11 supports -fno-rtti -fno-exceptions... no
checking for gcc -std=gnu11 option to produce PIC... -fPIC -DPIC
checking if gcc -std=gnu11 PIC flag -fPIC -DPIC works... yes
checking if gcc -std=gnu11 static flag -static works... no
checking if gcc -std=gnu11 supports -c -o file.o... yes
checking if gcc -std=gnu11 supports -c -o file.o... (cached) yes
checking whether the gcc -std=gnu11 linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... no
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for OpenMP flag of C compiler... -fopenmp
checking for jpeg_mem_src in -ljpeg... no
configure: WARNING: libjpeg not found
checking for jas_init in -ljasper... no
configure: WARNING: libjasper not found
./configure: line 17242: syntax error near unexpected token `ZLIB,zlib,'
./configure: line 17242: ` PKG_CHECK_MODULES(ZLIB,zlib,'

Reply to: Understanding highlight modes   1 year 9 months ago

So bad that none has replied so far... I've tried to find any answer around the internet but couldn't much.
Anyone?

Reply to: LibRaw 0.20 supported cameras   1 year 10 months ago

L.S.,

Would you please be so kind as to add support for RAW files (.ORF) files of the OM-systems OM-1 camera?
Thank you in advance,
Jan.

Reply to: Strange 14bit output with libraw.dll + unprocessed_raw.exe   1 year 10 months ago

I do not see a question here, so just a general remark.

Sony ARW 2.3 (lossy compressed) format is:
- 11-bit values (11 bit base + 7 bit deltas)
- expanded by expansion curve w/ ~0..16383 range (really slightly more)

dcraw converts it to ~0...4095 range, this is OK for old cameras but not for A7 series. LibRaw uses 'natural' camera range.

Reply to: EOS R series camera support   1 year 10 months ago

Please make sure EOS R3 and R10 are listed as supported in the snapshot you use.....

Reply to: EOS R series camera support   1 year 10 months ago

Hi Alex,

Sorry for the late reply. I have since figured out my mistake. (basically I built the wrong checkout on my computer)

After I corrected my build mistake. the latest checkout works with R5 raw (both compressed and non compressed cr3).

It still have problem with cr3 files that are came from EOS R3 and R10.
https://www.dpreview.com/sample-galleries/3816867543/canon-eos-r10-sampl...
https://www.dpreview.com/sample-galleries/3141499184/canon-eos-r3-sample...

I also seem to have another issue with FUJI XT4 raw RAF file. When decoded to HALF and FULL, both works fine. However when I enabled FBDD denoise, the decoded image came out incorrect.

https://www.dpreview.com/sample-galleries/1969063349/fujifilm-x-t4-sampl...

Cheers
Fred

Reply to: integer overflow and some other bugs   1 year 10 months ago

Thank you for your effort.

Both bugs are 'garbage in/garbage out', so no plans to fix these bugs

Reply to: EOS R series camera support   1 year 10 months ago

Could you please specify EOS R5 files that are not processed right with 202110 snapshot?

Reply to: New Libraw Snapshot?   1 year 11 months ago

According to the update policy published on this site main page

Reply to: Libraw slowdown when updating 19.2 to 20.2   1 year 12 months ago

It probably makes sense to take more detailed measurements

Reply to: Where is RAW Image data stored and datatype   2 years 1 day ago

Thanks jantheman. I will contact you outside this forum.

Regards

Reply to: Where is RAW Image data stored and datatype   2 years 1 day ago

Hi Steve, I had the same requirements for colorimetry applications and ended up writing a C++/CLI wrapper for libraw some time ago (i.e. direct API rather than PInvoke). Look for the LibRawWrapper NuGet package, should be usable in VB.NET, with imgdata.rawdata accessible via LibRawProcessor.RawData.

Reply to: Where is RAW Image data stored and datatype   2 years 3 days ago

Sorry, know nothing about VB.NET

In C/C++ libraw/libraw.h is enough, all needed files will be included automatically via #include directives in libraw.h

Reply to: Where is RAW Image data stored and datatype   2 years 3 days ago

Hi Lexa

I have made some progress in VB.NET to get camera sensor data from "libraw.dll".
For example, I see image size data but all values in "libraw_rawdata_t" are 0 or Nothing, including pointer "raw_image". So therefore I don't see any pixel data.

Recall that I am only executing "libraw_init" , "libraw_open_file" and "libraw_unpack" as I only want to get the raw unprocessed data from the camera sensor.

I am not asking about how to use VB.NET, but whether I have included all typedefs from libraw_types.h.

I have created in VB.NET all the data structures that are defined in "libraw_data_t" (from "libraw_types.h").
I have also included all nested data structures that are referenced by those data structures in "libraw_data_t".

My question is: Are there any other data structures that I have to include from other C or C++ files to get the raw unprocessed data from the camera sensor? For example, in "unprocessed_raw.cpp", will I need to include data structures defined in "#include "libraw/libraw.h"?

Reply to: Generating ColorMatrix1 from input data   2 years 3 days ago

Apart from what Alex said, good colour can't be solved with a set of 3 by 3 matrices.

Reply to: LibRaw for Windows 32 bit?   2 years 4 days ago

Hi Alex,
thanks a lot for the fast response. Good to hear, that I can proceed with 32-bit. I am also surprised that there still seems to be the need for it.
My LibRaw is older. I started with https://github.com/hurlbertvisionlab/LibRawWrapper.git which includes LibRaw and is from July 2021. Will update the local copy of LibRaw with latest version from https://github.com/LibRaw/LibRaw.git and will let you know about the result.
Link to sample file is sent to info@libraw.org.

Norbert

Reply to: LibRaw for Windows 32 bit?   2 years 4 days ago

Could you please provide the sample file that is handled wrong in 32-bit mode? Use info@libraw.org for that :)

On Nov 26, 2021 we fixed one 32-bit related error via this commit: https://github.com/LibRaw/LibRaw/commit/30595a731f3bea78f0410426b73ef3af...
Probably it will fix the issue but we need sample file to be sure.

If your LibRaw is older consider upgrade via github (or just apply this patch)

The easiest way to build 32-bit LibRaw for windows is
1) start Visual Studio developer shell in 32 bit mode
(e.g: run cmd.exe and execute
call "C:\Program Files ... path to VisualStudio installation...\VC\vcvarsall.bat" x86
)
2) run nmake -f Makefile.msvc to build LibRaw

32-bit windows (and even more broadly, 32-bit apps) don't look relevant in 2022, nevertheless, it is still too early to completely stop 32-bit systems support.

Reply to: Generating ColorMatrix1 from input data   2 years 5 days ago

LibRaw's main goal is RAW data extraction (plus metadata needed for RAW processing).

RAW conversion is very basic and no plans to improve it (or even touch it).

Generally speaking, raw color data is also out of LibRaw's scope (unless contained in RAW metadata), although we provide some basic data enough for basic processing.

Reply to: Generating ColorMatrix1 from input data   2 years 5 days ago

I think for me the real question is why libraw only uses one color matrix? Why not use two like DNG 1.5 and before or even three like DNG 1.6?

Reply to: Generating ColorMatrix1 from input data   2 years 5 days ago

I just put the cam_xyz into ColorMatrix1 and set the illuminant1 to D65.

The DNG output color is slightly off but acceptable.

I'm not sure if libraw can do this. Take the PixelShift2DNG application as an example, that one is built around libraw but only supports a few cameras, the ColorMatrix1 field can be easily copied from Adobe DNG Converter results.

Well, that's one possible solution, convert the images using Adobe DNG Converter first, then you have it.

Reply to: Nikon Z9   2 years 1 week ago

According to Update Policy section at this site homepage: https://www.libraw.org/

Reply to: Nikon Z9   2 years 1 week ago

Thanks. Do you have a timeframe for this snapshot release?

Reply to: Panasonic Lumix DC GH6 raw RW2 support   2 years 2 weeks ago

I tried to inspect a bit more the situation:

rawtherapee which uses some custom dcraw success in extracting the compressed raw data,
but it fails in decoding the decompressed structure.
I modified it to dump the uncompressed raw (which display as garbage currently).

For a 25 mb pixels image, there is exactly 50 mbytes of decoded data being decoded.
which correspond to 2 bytes per pixel, which seems to be confirming the 16 bits per pixel.

I tried making a black frame and a white frame,
just to see if I could understand something, but the result are not that great:

The first bytes of the frames are looking like that:

white frame:

00000000: dfce f87f 7b8c ffdb d77c 9d99 7c14 29bd  ....{....|..|.).
00000010: 91a7 d027 0405 22d3 147d 3371 f16b 0b07  ...'.."..}3q.k..

black frame:

00000000: 1ba4 1b9c 1b80 1bb0 b707 f8d9 cdf8 12fa  ................
00000010: f71f 4e32 e6ad f321 9dff d53f 2731 ead1  ..N2...!...?'1..

So...
either they are crypted or salted,
either the colorspace is uncommon,
either I am missing something, which can be possible as I am far from an expert in this domain.

The data are there : (including the two RW2 files)

http://esby.free.fr/perso/GH6-RW2/

See
http://esby.free.fr/perso/GH6-RW2/P1000404-black.info
and
http://esby.free.fr/perso/GH6-RW2/P1000407-white.info

for the filesizes and basic descriptions

(the dng were producted by Adobe Dngconverter 14_3 under wine staging 7.2 )

Reply to: Panasonic Lumix DC GH6 raw RW2 support   2 years 2 weeks ago

In the meantime conversion with the most recent Adobe DNG Converter works.

Pages