Recent comments

Reply to: LibRaw on RPi   8 months 5 days ago

Dear Sir:

Since your goal is to make rawpy work, please follow suggestions from rawpy folks.

RPi raw support is for Raspberry cameras only.

Reply to: LibRaw on RPi   8 months 5 days ago

Thanks - the rawpy folks mentioned the terminal output all looks fine, but that perhaps I should try again and enable the RPi RAW support. When compiling LibRaw I made the folder ~/Desktop/libraw into which I cloned the LibRaw repo.

- Can I remove that folder and try compiling again, or were LibRaw files installed elsewhere that need to be removed?
- In the future, what folder do you recommend I clone the LibRaw repo into?

Reply to: LibRaw on RPi   8 months 5 days ago

> it indicates a few files were not found.

No, it indicates that you haven't installed some optional libraries before running cmake, and haven't selected some options. You can ask at rawpy if they use those options.

Reply to: LibRaw on RPi   8 months 5 days ago

Thank you for the reply. I followed the instructions (below) provided by rawpy (which uses LibRaw), as suggested by Iliah Borg (see further up for this discussion). Should I instead follow the LibRaw provided instructions?

git clone https://github.com/LibRaw/LibRaw.git libraw
git clone https://github.com/LibRaw/LibRaw-cmake.git libraw-cmake
cd libraw
git checkout 0.20.0
cp -R ../libraw-cmake/* .
cmake .
sudo make install
Reply to: LibRaw on RPi   8 months 5 days ago

We dropped Cmake support in LibRaw in 2014, so we do not know what cmake scripts you use and what they do and whether it is correct or not.

Supported build methods are ./configure && make and also just make -f Makefile.dist

Reply to: LibRaw on RPi   8 months 5 days ago

Hi - I just wanted to confirm I installed from source correctly. Below is the terminal output resulting from my cmake command. As you'll note, it indicates a few files were not found. Additionally, can I remove the ~/Desktop/libraw folder I created to clone the libraw repo?

cmake .
-- CMake version: 3.18.4
-- LibRaw string version: 0.20.0
-- LibRaw ID version: 0x0200
-- LibRaw SO version: 20.0.0
-- The CXX compiler identification is GNU 10.2.1
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check for LCMS2 availability...
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.2")
-- Checking for module 'lcms2'
-- No package 'lcms2' found
-- lcms2 NOT found
-- Check for LCMS availability instead LCMS2...
-- Checking for module 'lcms'
-- No package 'lcms' found
-- Could NOT find LCMS (missing: LCMS_LIBRARIES LCMS_INCLUDE_DIR)
-- Found ZLIB: /usr/lib/arm-linux-gnueabihf/libz.so (found version "1.2.11")
-- Could NOT find JPEG (missing: JPEG_LIBRARY JPEG_INCLUDE_DIR)
-- Could NOT find JPEG (missing: JPEG_LIBRARY JPEG_INCLUDE_DIR)
-- Found OpenMP_CXX: -fopenmp (found version "4.5")
-- Found OpenMP: TRUE (found version "4.5")
-- Could NOT find JPEG (missing: JPEG_LIBRARY JPEG_INCLUDE_DIR)
-- Could NOT find Jasper (missing: JASPER_LIBRARIES JASPER_INCLUDE_DIR JPEG_LIBRARIES)
--
-- ----------------------------------------------------------------------------------
-- Libraw 0.20.0 configuration
--
-- Libraw will be compiled with OpenMP support .................. YES
-- Libraw will be compiled with LCMS support .................... NO
-- Libraw will be compiled with example command-line programs ... YES
-- Libraw will be compiled with RedCine codec support ........... NO
-- Libraw will be compiled with DNG deflate codec support ....... YES
-- Libraw will be compiled with DNG lossy codec support ......... NO
-- Libraw will be compiled with RawSpeed support ................ NO
-- Libraw will be compiled with debug message from dcraw ........ NO
-- Libraw will be compiled with Foveon X3F support .............. NO
-- Libraw will be compiled with Raspberry Pi RAW support ........ NO
-- Libraw will be compiled as a shared library
-- ----------------------------------------------------------------------------------
--
-- Configuring done
-- Generating done
-- Build files have been written to: /home/pi/Desktop/libraw/libraw

Reply to: LibRaw on RPi   8 months 1 week ago

RPi is indeed ARM-based, and we never performed extensive LibRaw testing on RPi. Based on my quick test, based on the fact that LibRaw is among Raspberry Pi libs packages (can be installed using apt), and based on experience of many RPi users, it does work.

Reply to: LibRaw on RPi   8 months 1 week ago

LibRaw works fine on Apple M1 ARM chip

Reply to: LibRaw on RPi   8 months 1 week ago

Yep, no problem! One final question about all this for my own edification - my initial confusion about whether LibRaw could be installed on an RPi stemmed from here, which states "LibRaw has been tested on 32- and 64-bit Unix systems working on x86- (and AMD64-) compatible processors.". I am admittedly inexperienced with this, but I believe the RPi is ARM-based, so I wasn't sure if it was included on that list of tested systems. Please let me know if I've misunderstood. Thank you!

Reply to: LibRaw on RPi   8 months 1 week ago

> it seems LibRaw can be installed on an RPi

Why "seems", I checked with my RPi before posting.

Which method of installation to use depends on your needs.

Generally if you want a package (rawpy in your case), it's a good idea to follow the instructions accompanying the package, especially when those instructions refer to a particular (not the latest) version of a library. You will need to install git and cmake,

> sudo apt update
> sudo apt upgrade
> sudo apt install git
> sudo apt install cmake

After LibRaw is installed the way rawpi instructions suggest, check

> echo $LD_LIBRARY_PATH

If it's empty, and you want to use LibRaw independently / check the installation:

> LD_LIBRARY_PATH=/usr/local/lib
> export LD_LIBRARY_PATH
Reply to: LibRaw on RPi   8 months 1 week ago

Re "seems" - I was half-joking, I got your meaning, but wanted to make it clear to readers that I checked the things.
Good luck!

Reply to: LibRaw on RPi   8 months 1 week ago

My apologies re. "seems" - I did not intend to cast doubt on your reply. Thank you very much for all the helpful information, and for checking these installation instructions on your own RPi - that is greatly appreciated! I am looking forward to using LibRaw.

Reply to: LibRaw on RPi   8 months 1 week ago

The easy way to install is:

> sudo apt update
> sudo apt upgrade
> sudo apt install libraw-dev

To compile, install git, and after that:

> git clone https://github.com/LibRaw/LibRaw.git
> cd LibRaw/
> make -f Makefile.dist

To check,

> bin/dcraw_emu
Reply to: LibRaw on RPi   8 months 1 week ago

Thank you for the helpful information! So it seems LibRaw can be installed on an RPi - this is great!

Just to clarify, in the case where both options are available (apt install or compiling), is there a reason why I would choose one over the other (e.g. will the compiling option give me a newer version)?

Additionally, re. compiling, I found these instructions on rawpy's website (a package I'm hoping to use), which look similar to the instructions you provided above, but there are some differences - will either set of instructions work?

git clone https://github.com/LibRaw/LibRaw.git libraw
git clone https://github.com/LibRaw/LibRaw-cmake.git libraw-cmake
cd libraw
git checkout 0.20.0
cp -R ../libraw-cmake/* .
cmake .
sudo make install
Reply to: LIBRAW Thread Safety   8 months 2 weeks ago

Yes, you need to link with libraw_r on Mac/Linux (and, yes, Windows build is thread-safe)
Also, thread stack may be too small for on stack allocation (LibRaw rawProcessor), so dynamic allocation is preferred (LibRaw *rawProcessor = new LibRaw;)

Reply to: Fuji X-Trans files washed out colors in 2021   8 months 2 weeks ago

Thank you for your help.
Than I there is another issue related to the Java wrapper - Sorry for that. The output_color=0 was already commented out therefore was never active (leading slashes).

I have now removed the options and use the lib with the default options. After JDK18 I have to generate the sources from the header file again and will see if that helps.

Nevertheless under windows I had troubles with ljpeg-8d which is not compiling. For now I have removed libjpeg from all builds because it is not so important for the users.

Reply to: LibRaw 202101 snapshot   8 months 2 weeks ago

samples/raw-identify.cpp sample: removed lot of extra output used only by development team
I'm not sure this was a good change. It was great to be able to get more info about the files. Please add it back.

Reply to: Fuji X-Trans files washed out colors in 2021   8 months 2 weeks ago

I do not see color change due to user_qual=0 (output_tiff=0, half_size=0 are the default value).

BTW, you set output_color=0 too. This turns off camera color to sRGB (or other known colorspace) conversion and will result in washed colors.

Reply to: Fuji X-Trans files washed out colors in 2021   8 months 2 weeks ago

I have now found the issue which parameter is causing the problem. If one of those parameters below are set the colors are washed out. In 0.20.2 this is not happening.

libraw_output_params_t.output_tiff$set(params$slice, 0);
libraw_output_params_t.half_size$set(params$slice, 0);
libraw_output_params_t.user_qual$set(params$slice, 0);

Reply to: Fuji X-Trans files washed out colors in 2021   8 months 2 weeks ago

I try's the sample applications and you are right that all is working.

The problem is that the sample applications are not setting any params. As soon as you add my param list the output colors are also washed out.

I am using the following params to speed up decoding of x-trans files (For Canon/Nikon it doesn't matter). Without those parameters the encoding is much slower. But if I set only one parameter the color are washed out independently which parameter I set:
use_camera_wb$set(params$slice, 0);
use_auto_wb$set(params$slice, 0);
output_tiff$set(params$slice, 0);
half_size$set(params$slice, 0);
user_qual$set(params$slice, 0);

Reply to: Fuji X-Trans files washed out colors in 2021   8 months 2 weeks ago

Tested with dcraw_emu -T -w, for both 0.20-stable branch (from github) and for master branch (also from github).
I do not see great color difference here: https://www.dropbox.com/s/vdlbhfyd6e53pu0/Screenshot%202022-01-11%2021.4...

Files produced are also (temp.) stored on dropbox for your inspection: https://www.dropbox.com/sh/ek4rezjhju4xmmx/AACVcj-2X4G1EvI6cpkbpA3xa?dl=0

Please try to reproduce the problem using LibRaw's sample application (dcraw_emu or simple_dcraw). If these applications produces correct results, the problem source is probably in your code or in Java wrapper you use.

Reply to: Canon R5 CR3 Support?   8 months 3 weeks ago

EOS R5 (released in 2020) and R3 (released in 2021) are different cameras.

R3 will be supported in the next public version (snapshot or beta/release, whatever come first)

Reply to: Canon R5 CR3 Support?   8 months 3 weeks ago

Hi, i have same problem from cannon R3 cr3 (decoded with a purple tint) , that confuse me if R5 is supported

Reply to: CR3 to Tiff conversion results in different brightness levels   9 months 4 weeks ago

Brightness adjustement and maximum level adjustement are different things (wrong maximum may/will result into 'pink highlights' problem and auto-adjust works against it).

I agree, set_maximum_adj_threshold should be added to C-API.

Pages