Do you mean in the dng sdk build? As stated in the dng sdk readme,
"XMP SDK
Building DNG SDK requires the XMP SDK. This package includes the XMP
SDK headers and pre-built static libraries for Mac OS (64-bit) and
Windows (32-bit and 64-bit). Thus if you plan to build the DNG SDK on
Mac OS using Xcode and/or on Windows using Visual Studio/C++, no
further action is needed."
I'm not sure how to include it in the project as it said no further action is needed in Windows.
We do not provide direct user support for other's end user products (with the exception of ours end-user products, of course). If Affinity takes money from its users, they should be engaged in support without throwing this ball to us.
LibRAW is targeted to developers, we're ready to provide support for Affinity team, but they never contacted us.
Also, you may just wait: Panasonic DC-S5 II is supported since March, 2023; We'll release it in public snapshot according to our release schedule: https://www.libraw.org/#updatepolicy
If you need to get such support ASAP:
- if you're a software vendor, consider our extended support/advanced option: https://www.libraw.org/extended-support
- If you are just a user of some program using LibRaw: tell your vendor about early camera support access option.
Specific file you provided is recorded in HE/HE* Nikon pseudo-RAW format; this format is not supported yet, while other Z8 recording formats are supported.
Undefined symbols for architecture x86_64:
"_uncompress", referenced from:
LibRaw::deflate_dng_load_raw() in libraw.a(fp_dng.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1
I also tried using -lraw instead of adding the full path name to libraw.a still got the same error
Thank you very much. This is all new to me but I'm eager to get into it.
One last question - I'm completely new to working with RAW processing, but I've been a coder for 25 years. Can you recommend any conceptual documentation or reference material that will help me understand RAW processing better? There are lots of search results, but if you have a recommended resource I would love to know about it. (Apologies if it's on page 1 of your documentation and I just missed it.)
Yes, one of *image pointer in libraw_rawdata_t will be non-zero after LibRaw::unpack() and will contain imgdata.sizes.raw_height rows, imgdata.sizes.raw_width items each, with imgdata.sizes.raw_pitch byte pitch.
Ahh thanks, I think you just helped me understand something.
I haven't checked, but I'm almost certain you're right about it using the rendered image. My understanding is that ImageMagick delegates all the decoding to libraw, libjpeg, libtiff, libpng, etc., and in my case it doesn't necessarily know it's dealing with a RAW image by the time it creates the signature.
So let's say I wanted to write my own signature program using LibRaw that only operates on the image data, leaving the metadata completely out of it. After a quick look at the API, my best guess is that I'd want to hash the contents of libraw_rawdata_t. Does that sound right?
Do you mean in the dng sdk build? As stated in the dng sdk readme,
"XMP SDK
Building DNG SDK requires the XMP SDK. This package includes the XMP
SDK headers and pre-built static libraries for Mac OS (64-bit) and
Windows (32-bit and 64-bit). Thus if you plan to build the DNG SDK on
Mac OS using Xcode and/or on Windows using Visual Studio/C++, no
further action is needed."
I'm not sure how to include it in the project as it said no further action is needed in Windows.
Sorry about that, I have changed to public, here is the link
https://drive.google.com/file/d/18QaZiL_YBEXwrmKd9638zHuWpOo54V5y/view?u...
Looks like you have not added required XMP SDK (XMPCore) to your build.
The link you provided is not for everyone, but asks for 'request access permissions'.
Please change to public
We do not provide direct user support for other's end user products (with the exception of ours end-user products, of course). If Affinity takes money from its users, they should be engaged in support without throwing this ball to us.
LibRAW is targeted to developers, we're ready to provide support for Affinity team, but they never contacted us.
Please send this link to Affinity team: https://www.libraw.org/extended-support
Also, you may just wait: Panasonic DC-S5 II is supported since March, 2023; We'll release it in public snapshot according to our release schedule: https://www.libraw.org/#updatepolicy
We're working on it but there is no estimated completion date.
HE/HE* will definitely NOT be supported in the next public snapshot.
If you're a software vendor: please consider extended support/early access option.
If you are just a user of some program - please inform your vendor about the possibility of access to early support for new cameras.
what do you think? How long do I have to wait?
Already replied here: https://www.libraw.org/comment/6577#comment-6577
Dear all, what about OM Digital Solutions OM-5 (not Olympus EM5) thank you
everything is publicly available and can be googled
here is some results of quick search
https://www.dpreview.com/forums/thread/4566327
https://www.fastcinemadng.com/info/dng/pgm-to-dng-converter.html
https://github.com/fastvideo/pgm2dng
https://github.com/horshack-dpreview/OctaveRawTools
https://www.dpreview.com/forums/post/65037078
also useful = https://github.com/Fimagena/raw2dng
I would be very interested in learning more. Could you please reach me at rijamo at gmail dot com
According to our release schedule/policy: https://www.libraw.org/#updatepolicy
If you need to get such support ASAP:
- if you're a software vendor, consider our extended support/advanced option: https://www.libraw.org/extended-support
- If you are just a user of some program using LibRaw: tell your vendor about early camera support access option.
New camera support will be provided according to our update policy: https://www.libraw.org/#updatepolicy
Consider signing up for extended support if you need support for new cameras faster: https://www.libraw.org/extended-support
Specific file you provided is recorded in HE/HE* Nikon pseudo-RAW format; this format is not supported yet, while other Z8 recording formats are supported.
> Does anyone know a create such artificial raw image?
Yes, I do.
I stripped down the
unprocessed_rawsample and achieved what I want (I think) by piping the output through a hash utility likesha256sumorxxh128sum.Posting here in case it helps someone later:
#include <stdio.h> #include "libraw/libraw.h" int main(int ac, char *av[]) { LibRaw RawProcessor; int ret; if ((ret = RawProcessor.open_file(av[1])) != LIBRAW_SUCCESS) { fprintf(stderr, "Cannot open %s: %s\n", av[1], libraw_strerror(ret)); return 1; } if ((ret = RawProcessor.unpack()) != LIBRAW_SUCCESS) { fprintf(stderr, "Cannot unpack %s: %s\n", av[1], libraw_strerror(ret)); return 1; } size_t bytes = RawProcessor.imgdata.sizes.raw_height * RawProcessor.imgdata.sizes.raw_pitch; fwrite(RawProcessor.imgdata.rawdata.raw_alloc, sizeof(uint8_t), bytes, stdout); fflush(stdout); }Compile with
g++ rawbytes.cpp -o rawbytes -Ofast -lraw -lm.Yes, doing that solved it!! thank you so much
You need to add libz (-lz) to your linker input
So I tried building my program again using the libraw 0.21.1 binaries provided for macos..
I used the command
g++ --std=c++17 -I/Users/aayush/Downloads/LibRaw-0.21.1/libraw -L/Users/aayush/Downloads/LibRaw-0.21.1/lib base64.cpp Server-mac.cpp -o Ninja -lm /Users/aayush/Downloads/LibRaw-0.21.1/lib/libraw.a
and I seem to get the following error
Undefined symbols for architecture x86_64:
"_uncompress", referenced from:
LibRaw::deflate_dng_load_raw() in libraw.a(fp_dng.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1
I also tried using -lraw instead of adding the full path name to libraw.a still got the same error
Thank you. This is helpful.
It is difficult to recommend any specific document/site. May be 'dcraw annotated' will help: https://ninedegreesbelow.com/files/dcraw-c-code-annotated-code.html
(at least, LibRaw postprocessing is derived from dcraw.c code, so this specific document is applicable to LibRaw::dcraw_process() code)
Thank you very much. This is all new to me but I'm eager to get into it.
One last question - I'm completely new to working with RAW processing, but I've been a coder for 25 years. Can you recommend any conceptual documentation or reference material that will help me understand RAW processing better? There are lots of search results, but if you have a recommended resource I would love to know about it. (Apologies if it's on page 1 of your documentation and I just missed it.)
Thanks again!
Yes, one of *image pointer in libraw_rawdata_t will be non-zero after LibRaw::unpack() and will contain imgdata.sizes.raw_height rows, imgdata.sizes.raw_width items each, with imgdata.sizes.raw_pitch byte pitch.
it looks like 'your file from another computer' is dynamically linked with libraw.23.dylib
We do not provide dynamic LibRaw for macOS, make -f Makefile.dist will also create static library only.
Please contact the 'file from another computer' vendor for libraw.23.dylib library
Ahh thanks, I think you just helped me understand something.
I haven't checked, but I'm almost certain you're right about it using the rendered image. My understanding is that ImageMagick delegates all the decoding to libraw, libjpeg, libtiff, libpng, etc., and in my case it doesn't necessarily know it's dealing with a RAW image by the time it creates the signature.
So let's say I wanted to write my own signature program using LibRaw that only operates on the image data, leaving the metadata completely out of it. After a quick look at the API, my best guess is that I'd want to hash the contents of libraw_rawdata_t. Does that sound right?
Pages