Recent comments

Reply to: LibRaw 202110 snapshot supported camera list   1 year 6 months ago

Hello. Are you able to provide an estimate for when the next snapshot will be (I’m assuming the next snapshot will add support for recently released cameras like Fuji X-T5, X-H2, Sony A7R5, etc)?

Reply to: LibRaw 202110 snapshot supported camera list   1 year 6 months ago

I think you may suggest them to contact us, for a start...

Reply to: LibRaw 202110 snapshot supported camera list   1 year 6 months ago

1-4-6 beta definitely works. Does this mean that the GH6 .RW2 format will be supported in the next version? Is there an ETA on that?

If a company like Affinity is using LibRaw as a part of their developing engine, what can I do to let them know it is ready to be incorporated?

Reply to: LibRaw 202110 snapshot supported camera list   1 year 6 months ago

I get the error "File://( file name here) decoded with errors. Broken file or unsupported file format."

Reply to: LibRaw 202110 snapshot supported camera list   1 year 6 months ago

Dear Sir:

Does our RawDigger ( https://www.rawdigger.com ) open your files?

Reply to: LibRaw 202110 snapshot supported camera list   1 year 6 months ago

I am an avid user of Affinity Photo and I am told that Affinity Photo uses LibRaw as an essential element to the processing and development of RAW images. I recently purchased a Panasonic Lumix GH6 and was curious if this might be on the docket for updates to the .RW2 raw file processing? Affinity Photo was able to support earlier versions of the .RW2 format (I believe the Lumix GH5mII uses the same extension .RW2). If there is anything I can do to somehow contribute to getting camera or file data samples of the GH6 .RW2 files, I would be happy to spend the time.

Reply to: unexpected token `ZLIB,zlib,'   1 year 6 months ago

To get working autotools suite you need autoconf, automake, libtool and pkg-config installed.

Based on error message you provided, pkg-config is probably missing on your system

Reply to: unexpected token `ZLIB,zlib,'   1 year 6 months ago

Check your version of autoconf and compare to AC_PREREQ in aclocal.m4. Try re-installing autotools if something doesn't work.
On my focal 20.04 LTS, following https://www.libraw.org/docs/Install-LibRaw.html

$ apt-cache policy pkg-config
pkg-config:
  Installed: 0.29.1-0ubuntu4...
$ apt-cache policy automake
automake:
  Installed: 1:1.16.1-4ubuntu6...
$apt-cache policy libtool
libtool:
  Installed: 2.4.6-14...
$ autoconf -V
autoconf (GNU Autoconf) 2.69....
$ cd
$ git clone https://github.com/LibRaw/LibRaw.git
$ cd LibRaw
$ autoreconf --install
$ ./configure
$ make
$ bin/raw-identify 
Usage: /home/ib/LibRaw/bin/.libs/raw-identify [options] inputfiles
Options:
	-v	verbose output
	-w	print white balance
	-u	print unpack function
	-f	print frame size (only w/ -u)
	-s	print output image size
	-h	force half-size mode (only for -s)
	-M	disable use of raw-embedded color data
	+M	force use of raw-embedded color data
	-L filename	read input files list from filename
	-o filename	output to filename
Reply to: unexpected token `ZLIB,zlib,'   1 year 6 months ago

FYI: I did not really solve it, but the 0.19 version works without problems!

Thanks again, Jan

Reply to: unexpected token `ZLIB,zlib,'   1 year 6 months ago

Yes, I checked that: automake-1.15

I will try to reinstall.

Thank you anyway for your quick reply!

Reply to: unexpected token `ZLIB,zlib,'   1 year 6 months ago

It looks like you have incomplete automake/pkg-config suite installed, see comments above.

You may use make -f Makefile.dist

Reply to: unexpected token `ZLIB,zlib,'   1 year 6 months ago

Sorry, I was confused. Repeated it so many times that I got a bit lost. Here is what happens:

./configure seems to work

make produces some warnings and errors:

configure.ac:16: error: possibly undefined macro: AC_SUBST
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.ac:41: error: possibly undefined macro: AC_MSG_WARN
make: *** [Makefile:651: configure] Fehler 1

ignoring these, sudo make install produces the aforementioned error:

configure: WARNING: libjasper not found
./configure: line 12807: syntax error near unexpected token `ZLIB,zlib,'
./configure: line 12807: ` PKG_CHECK_MODULES(ZLIB,zlib,'
make: *** [Makefile:648: config.status] Fehler 2

Thanks! Jan

Reply to: unexpected token `ZLIB,zlib,'   1 year 6 months ago

I do not see the PKG_CHECK_MODULES substring in the provided ./configure script

Reply to: unexpected token `ZLIB,zlib,'   1 year 6 months ago

Hi, just ./configure.

Reply to: unexpected token `ZLIB,zlib,'   1 year 6 months ago

Do you use ./configure provided with LibRaw distiibution or generate own configure script?

Reply to: unexpected token `ZLIB,zlib,'   1 year 6 months ago

Hi, same problem here, but different line:

checking for jas_init in -ljasper... no
configure: WARNING: libjasper not found
./configure: line 12807: syntax error near unexpected token `ZLIB,zlib,'
./configure: line 12807: ` PKG_CHECK_MODULES(ZLIB,zlib,'

any ideas? Thanks very much, Jan

Reply to: CR2 to jpg exposure too bright   1 year 6 months ago

Your file has data corruption, so processing result may depend on how such corruption is handled in the calling code, please contact your library developers for details.

Here are processing results using LibRaw's dcraw_emu -w -T: https://www.dropbox.com/s/d7g25khy96nw4z8/20221010163318528158294_ori_00...

Reply to: libraw_rawdata_t not being populated with C API   1 year 6 months ago

Thank you for the clarification, I was confused by the documentation, but now I understand.

Reply to: libraw_rawdata_t not being populated with C API   1 year 6 months ago

raw_image is also an '*_image' field

Reply to: libraw_rawdata_t not being populated with C API   1 year 6 months ago

From the documentation (which can be sometimes confusing, I agree): "After call to unpack() only one of *_image fields is non-NULL."

Reply to: libraw_rawdata_t not being populated with C API   1 year 6 months ago

C-API is just a thin layer over C++ API, so no difference here.

Based on your source code (w/ built-in filename) I assume you use normal/unaltered bayer-pattern Sony-produced image.
For such images, decoded data is in libRaw->rawdata.raw_image

Reply to: LibRaw 202110 snapshot supported camera list   1 year 6 months ago

LibRaw supports most DNG files (all DNG files if compiled w/ DNG SDK)

Reply to: LibRaw 202110 snapshot supported camera list   1 year 7 months ago

Dear sir or madam,
I am an enthusiastic user of all of your products. I use it for my Sony and Canon cameras successfully. I also Use a 360 VR Insta360 X3 and older One X2 cameras and I would be delighted if your package would support the RAW DNG files captured by these two cameras.
Best regards,
Frank Tornyai

Reply to: Camera Makes and Models   1 year 7 months ago

No cameras produces floating-point data raw images (yet?), one may use (different) HDR-convertor software to create floating point images.

Regarding color3/color4:
- full-color images unpacked by LibRaw itself are (mostly) color4_image, you may use any full-color (not bayer) RAW file for that, for example Canon sRAW/mRAW CR2

- full-color images unpacked by 3rd-party decoders (Adobe DNG SDK, RawSpeed) are usually color3_image images. You may use the same sRAW/mRAW CR2 and RawSpeed decoder (via LibRaw)

Pages