hello,

I am author of http://code.google.com/p/delaboratory/
major version will be released soon, and after it I may think about new features, one of them is ability to import RAW files

I am just checking is libraw good candidate for that,
I looked into API but couldn't find answer to my question

I understand that standard output is in RGB, but is there any way to export image into LAB colorspace to avoid color profile dependency?

Hi
How find files extensions libraw support?

Thanks

When I want to use libraw in a closed source android app, do I need to actually get you to sign the libraw license copy and sign it with my own signature, or is just mentioning the attribution and the used license enough?

Great work by the way!

I'd like to ask about libraw (and libraw-lite) licensing.

Both libraries share the (almost) same code, and both are licenced under LGL 2.1; but libraw can be distributed choosing one of three available.

What are the main reason for this?

Reading the source, I can notice some comments like 'LIBRAW_DEMOSAIC_PACK_GPL3' or 'LIBRAW_DEMOSAIC_PACK_GPL2'... what is meaning? Portion of the code can be included only if distributed which some licences?

Thanks for your time!

I didn't find the update to enable me to treat my Pentax K5 raw (.pef) formated pictures.
It works well for the raw formated pictures of my old Pentax K20D, but not for the recent K5.
Could some one help me ?

Hello,

I noticed that when exp_shift is used, the "maximum", "channel_maximum[4]" data fields are corrected accordingly by the exp_shift value. Why is that needed. I mean if a 12bit raw value is for example 3000, what is the reason to double it (exp_shift == 2.0) when 6000 exceeds the 12bit max possible value 4095?

In the Festine Lente article, Iliah Borg concludes by saying:

"It looks like the time spent in postprocessing to get more details and counter-act artifacts might be better spent if demosaicking prepares a cleaner and more detailed image to start with. The processing time difference between integer and floating point implementations of demosaicking most of the times is less than 5 seconds, which is substantially less compared to the time spent on image editing to get close to the same result. Try it, and you will see."

On the "about" page, there is the comment:

Dear,

A bit on and off I'm contemplating to base my dlRaw on LibRaw.

dlRaw is GPL V3. Does it mean that I would have problems of licensing with most of the demosaicing packs ?

How is your process of tracking dcraw looking like ? I.e. how confident can I be that your approach is not going to give me more headaches then every now and then doing some 2 hours of intensive dcraw 3 way comparing to cope with the changes ?

Hi,
I'm a developer of Luminance HDR and in the next release (2.0.2, hopefully coming soon) we decided to use LibRaw has RAW converter instead of using dcraw as an external command line tool (old solution). After a bit of work, we implemented what we needed and it worked fine with Linux and OS X, but we are having problems in Windows, because our code is multithread so we need the thread-safe version.
When I tried to link (using MinGW) the DLL you provide (0.11.3), I get these errors:

./generated_obj\pfsinraw.o: In function `Z19readRawIntoPfsFramePKcS0_P16LuminanceOptionsb':

Hi,
I am a new user of LibRaw and I like very much what I see here so far, so thanks for the great work :)
Currently, I work with Canon cameras and the Canon SDK. When downloading and developing an image from eg a Canon 550D, its SDK will tell me that the image resolution for a still image is 5184 x 3456, which is also confirmed here: http://www.dpreview.com/reviews/specs/Canon/canon_eos550d.asp
However, when I use the newly integrated LibRaw 0.10-Beta2:

EdsStreamRef downloadStream;
EdsCreateMemoryStream( 0, &downloadStream );