Canon R5 CR3 Support?

Using the official release 0.20, I found that Canon R5 CR3 image is decoded with a purple tint and the image is shifted a little to the right and down.

Will support for the R5 CR3 be coming soon?

Albert

Forums: 

Usually we publish snapshots

Usually we publish snapshots (or releases) every 5-7 months. LibRaw 0.20 was released in July, so....

-- Alex Tutubalin @LibRaw LLC

R5 support --> libraw 0.21 release?

Hi, it has been 9 months since the last release, is there any update on 0.21?
I'm also asking because of Canon R5 support.

kind regards
randfee

Latest Snapshot

Ah, thanks guys, i was looking at the latest available(Windows) binaries.
Tried to build the latest snapshot using Makefile.mingw just now, getting an error at line 78: library: lib/libraw.a on two machines. 😐
Are the Windows binaries available for download somewhere, sorry, didn’t see them anywhere.

Thanks!

We do not create binaries for

We do not create binaries for snapshot/intermediate releases.

What is make's error message?

-- Alex Tutubalin @LibRaw LLC

creating binary of current snapshot on windows 10

this is the error message:
rm -f lib/libraw.a
process_begin: CreateProcess(NULL, rm -f lib/libraw.a, ...) failed.
make (e=2): The system cannot find the file specified.
mingw32-make: *** [Makefile.mingw:134: lib/libraw.a] Error 2

here's the entire console output:
Screenshot

never stumbled upon this error, but I suppose it must be my setups then. Tried on two machines one with msys, one with mingw freshly installed.
I don't compile a lot for windows, but I need it running on there since I'd implement it for automation. I wish github would just offer some virtual machines for compiling binaries for whatever platform one needs, still seems a hassle on Win-machines.
Thanks for your comments and help.

'normal' rm should not raise

'normal' rm should not raise return error code if rm -f [nonexistent-file] is used

Because your rm is not 'normal', you may try to remove rm -f lib/libraw.a statement from makefile

-- Alex Tutubalin @LibRaw LLC

works

right... so I removed line 134: rm -f lib/libraw.a
from the Makefile.mingw and it finished as expected. Not sure why the rm throws an error. Running it again throws no error even with the rm sinc the 'lib/libraw.a' then exists. Windows... :-/

thanks for the help. Now I'm working on windows defender accepting the compiled *.exe and NOT starting thread alerts everytime they run. Only happens to compiled ones. I'll get it done.

thanks again. Any usage questions I'll post elsewhere.

You are running mingw32-make

You are running mingw32-make from cmd.exe shell, and rm command does not exist in DOS. Even if you have the MSYS bin directory in your PATH where MSYS rm.exe lives, its behavior is probably strange/undefined under cmd.exe...

I prefer to use the MINGW (bash) shell from the start menu and traditional make (installed under MSYS) instead of ming32-make, the behavior is much more consistent with all other *nix platforms and build scripts.

obviously no 'rm' in Windows CMD me =>fail

right you are, now that is shameful.
Yeah, I barely ever develop/compile any code on windows. I wouldn't try and use 'rm' in the Win CMD but I thought the Makefile.MinGW will be fully Win-compatible.... I guess not, didn't think straight, this lack of movement due to COVID is eating away on my braincells.

Good find and lazy me, great community here!