There is no way to help you without 'reproducers'. I need sample file (which definitely hang).
To fully emulate dcraw behavior you need to pass second argument (max_buf_size) to LibRaw::open_file(filename, max_buf_size).
By default, small files are processed using C++ buffered streams (faster), while large files use FILE* internal interface similar to dcraw. Default value of max_buf_size is 250M.
Set it to 0 or 1 and you'll use (slower) FILE* interface for all files.
Unfortunately, partial unpacking is not supported.
For several (most common: Canon CR2, Nikon NEF) formats it is not possible because of compressed data structure (no chunks, entire image compressed).
If you data is already clipped, the exposure correction will not help.
You may try to use highlight recovery (slow!), but it will help only if some details exists in some channels (e.g blue or red)
Just remembered I hadn't enabled the demosaic packs after the update. With the demosaic packs enabled the thumbnail extraction works. If you could still explain the out of order error for this case I'd appreciate it. Thanks!
Hi, I have downloaded VS project and succesfully comiled with VS desktop version 2012.
I am not C programmer but VB.NET
After compilation I got a bunch of exe files.
My mission is to create small thumbnail jpg image file from raw file. That is all.
How do I do that.
Well, after hitting this with 0.15.3 again, I banged my head against it some more. As far as I can tell, there was something cached in XCode that even a Project, Clean wasn't taking care of. I moved all prior LibRAWs away, did a clean, and rebuilt and voila! No signs things were pointing to these, but I can only assume some structure size difference b/n 0.14 and 0.15 was getting things off.
You need to
1) add LIBRAW_DEMOSAIC_PACK_GPL2 and/or LIBRAW_DEMOSAIC_PACK_GPL3 to C++ preprocessor defines
2) add path to Demosaic Pack(s) to #include path
could you provide sampe code you use?
The imgdata.image[] arraw is always 4-component (but not RGBA)
The dcraw_make_mem_image() call always creates 3-component output,
There is no plans to add subseconds because
Canon tags are canon specific
changing time_t to anything more precise will broke programs uses this field.
BTW, you can use exiftool and specific canon tags for file renaming
I solved the problem by creating another new project in VS2010 and copy everything to the new project. I don't know why this can solve the problem though. Btw, examples work well. :)
It may be caused by read-only memory in .Net Bitmap object (I know nothing about Bitmap type).
After you've called dcraw_make_mem_image, the RGB pixels are contained in image->data. You may try to create Bitmap directly from this array without extra copy_mem_image() call.
There is no way to help you without 'reproducers'. I need sample file (which definitely hang).
To fully emulate dcraw behavior you need to pass second argument (max_buf_size) to LibRaw::open_file(filename, max_buf_size).
By default, small files are processed using C++ buffered streams (faster), while large files use FILE* internal interface similar to dcraw. Default value of max_buf_size is 250M.
Set it to 0 or 1 and you'll use (slower) FILE* interface for all files.
Lightroom tries to recover highlights (i.e. modulate overexposed channel by differences in lower exposed channels) automatically.
You may try to use our RawDigger software ( www.rawdigger.com/download ) to explore the raw data histogram and see is real data clipping exists
Thanks for your reply Alex!
I was wondering why there's so much more definition if I expose the same raw file down using lightroom?
Thanks a lot,
Nhat
You may use LibRaw or Adobe DNG SDK to read DNG files and Adobe DNG SDK to write DNG files.
Unfortunately, partial unpacking is not supported.
For several (most common: Canon CR2, Nikon NEF) formats it is not possible because of compressed data structure (no chunks, entire image compressed).
If you data is already clipped, the exposure correction will not help.
You may try to use highlight recovery (slow!), but it will help only if some details exists in some channels (e.g blue or red)
I'm not VB.NET programmer.
use simple_dcraw.cpp sample as guide (you need open_file then extract_thumb, then write thumb to memory buffer).
But I do not now how to call C++ library from VB.NET
Also, you should not compile *all sources*
Both dcb-demosaic and wf-debanding are #included into demosaic-packs.cpp
You definitely need this define for compiling libraw sources.
No, I don't want to build libraw as a library, I want it to run from within the project like normal source code for debugging purposes like using gdb.
Yes, thumbnail extraction based on x3f tools library (i.e. without demosaic packs) do not work yet (0.16 still in Alpha)
You need additional define LIBRAW_LIBRARY_BUILD to build the library
Just remembered I hadn't enabled the demosaic packs after the update. With the demosaic packs enabled the thumbnail extraction works. If you could still explain the out of order error for this case I'd appreciate it. Thanks!
Hi, I have downloaded VS project and succesfully comiled with VS desktop version 2012.
I am not C programmer but VB.NET
After compilation I got a bunch of exe files.
My mission is to create small thumbnail jpg image file from raw file. That is all.
How do I do that.
Rgards,
Dusan
Yes, major LibRaw versions (0.14 vs 0.15 or 0.13 vs 0.12) are binary incompatible.
Well, after hitting this with 0.15.3 again, I banged my head against it some more. As far as I can tell, there was something cached in XCode that even a Project, Clean wasn't taking care of. I moved all prior LibRAWs away, did a clean, and rebuilt and voila! No signs things were pointing to these, but I can only assume some structure size difference b/n 0.14 and 0.15 was getting things off.
Hi Alex,
I am using your new version 0.15.3 and the error about the canon cr2 files (canon 50D) has gone.
Thanks for the very quick release :-)
All the best,
Michael
You need to
1) add LIBRAW_DEMOSAIC_PACK_GPL2 and/or LIBRAW_DEMOSAIC_PACK_GPL3 to C++ preprocessor defines
2) add path to Demosaic Pack(s) to #include path
user_sat is used to set RAW data saturation point (all values above user sat will be clipped).
This clipping occurs before white balance, so wrong user_sat may cause wrong colors, not only brightness change.
Use bright field if you wish to change output image brightness
could you provide sampe code you use?
The imgdata.image[] arraw is always 4-component (but not RGBA)
The dcraw_make_mem_image() call always creates 3-component output,
There is no plans to add subseconds because
Canon tags are canon specific
changing time_t to anything more precise will broke programs uses this field.
BTW, you can use exiftool and specific canon tags for file renaming
I solved the problem by creating another new project in VS2010 and copy everything to the new project. I don't know why this can solve the problem though. Btw, examples work well. :)
Are the LibRaw examples works OK?
You also need to turn off auto brightness. If not, values will be scaled to fill full data range.
It may be caused by read-only memory in .Net Bitmap object (I know nothing about Bitmap type).
After you've called dcraw_make_mem_image, the RGB pixels are contained in image->data. You may try to create Bitmap directly from this array without extra copy_mem_image() call.
Pages