You may choose LGPL or CDDL license and just use LibRaw in your (closed source) app. Most users (developers) do so. You don't need to notify us about your app.
The LibRaw own licensing is used only for compatibility with LibRaw-pre-0.9 (commercial version).
unpack() is not multithreaded because
1) it is not possible for Lossless JPEG format (Canon CR2 and so), you need to read input byte-to-byte
2) for simple formatts (e.g. Fuji RAWs) the code is disk limited already.
Postprocessing steps are partially multithreaded via OpenMP
Versioning is critical for normal use of libraw because different versions are binary incompatible, so app using .so.4 should not link with .so.5 and vice versa.
You may consider static linking (and ./configure --static)
Yes, added a simple missing function of swab did made it compile.
However, when I try to use the lib on android, I keep getting link errors, since it still searches for libraw.so.5 internally. Android doesn't support the .5 extension, it needs to have a .so file. So this one doesn't load.
Is there an option to just output a .so file instead of having versioned ones?
Good afternoon. I have downloaded the version of RAWSHECK to 64-bit Windows 7, but I do not know to use the programme, because there is not any exe file. In the zipped box folder, there are files with unknown formats and I do not know to open them. I have created pictures in CR2 format and I want to view the ADU values. Help me, please.
Это на 99% похоже на переполнение целого (или short, уж не знаю что там используется в dt).
LibRaw 0.14/dcraw_emu -T такого эффекта не дает.
Возможно какой-то постпроцессинг LibRaw такой эффект и даст, но мне за несколько попыток не удалось подобрать варианты и я бросил. Тем более, что я не знаю как именно dt использует LibRaw.
Не менее возможно, что это такое вычитание черного, без проверки выхода ниже нуля, но это точно не LibRaw так поступает, по сведениям LibRaw черный уже вычтен.
Я собираю darktable без rawspeed. Так как с моим Pentax K-x последний не умеет работать, вернее тот что встроен в 0.9.2 не умеет. Так вот с libraw 0.13.8 всё отлично, а c libraw 0.14.0 цветные точки появляются.
В darktable собранном с 0.14.0 (в gentoo есть патч с которым можно собрать dt с системным libraw) на многих снимках вылазят цветные точки. Не знаю проблема это со стороны darktable или libraw.
LibRaw-Lite is no longer exists since version 0.9 or so.
There are:
- main LibRaw, distributed under triple licensing
- GPL2+ licensed sources (demosaic-pack-GPL2): Foveon support and some demosaic methods
- GPL3+ licensed sources: several demosaics plus noise reduction.
Depending on your application license, you may use only main LibRaw (if your application is not GPLed), LibRaw+GPL2 pack (for GPL2+ app), LibRaw+GPL2+GPL3 (for GPL3+ apps)
Would it be possible to get support for X3F files from the newer Sigma camera models? Code might be based on the X3F Tools found here: https://github.com/rolkar/x3f
I'm in the very same step, chaining Cam_xyz with xyz_srgb matrixes, but can't get the color right... What am I missing? Also, which coeficients do I have to use to do white balance?
You may choose LGPL or CDDL license and just use LibRaw in your (closed source) app. Most users (developers) do so. You don't need to notify us about your app.
The LibRaw own licensing is used only for compatibility with LibRaw-pre-0.9 (commercial version).
unpack() is not multithreaded because
1) it is not possible for Lossless JPEG format (Canon CR2 and so), you need to read input byte-to-byte
2) for simple formatts (e.g. Fuji RAWs) the code is disk limited already.
Postprocessing steps are partially multithreaded via OpenMP
Ok, thanks.
Versioning is critical for normal use of libraw because different versions are binary incompatible, so app using .so.4 should not link with .so.5 and vice versa.
You may consider static linking (and ./configure --static)
Yes, added a simple missing function of swab did made it compile.
However, when I try to use the lib on android, I keep getting link errors, since it still searches for libraw.so.5 internally. Android doesn't support the .5 extension, it needs to have a .so file. So this one doesn't load.
Is there an option to just output a .so file instead of having versioned ones?
Thanks, it looks like bug. Unfortunately, I've now samples of this format, so this piece of code is not covered by tests.
To be fixed in 0.14.5
I know nothing about android.
But I googled good replacement for swab, using __arch_swab16: http://www.crystax.net/trac/ndk/attachment/ticket/32/swab.patch
This error is also there when I just use ndk-build on only the dcraw.c file.
Is android missing a library where this 'swab' function comes from?
Any chance someone can point to a guide to compile this for Android?
Thanks for report
This issue is fixed now. The fix will be available in LibRaw 0.14.4. Hope, we'll release this version today.
Thanks for report!
The code is surely incomplete, because call to postprocessing is missing. It is added now.
For real-life example take a look into samples/ folder in LibRaw distribution.
The code doesn't work. I get an null pointer exception inside the for loop for iProcessor.imgdata.image.
I'm using libraw 0.14.2 with MSVC10. My sample file is Canon 1DSM3. You can find here
http://www.rawsamples.ch/raws/canon/1dsm3/RAW_CANON_1DSM3.CR2
Christian
Maybe it should be RAWSHACK (http://www.testcams.com/rawshack/)?
could you please explain your problem in more detail. Google and I knows nothing about RAWSHECK
Good afternoon. I have downloaded the version of RAWSHECK to 64-bit Windows 7, but I do not know to use the programme, because there is not any exe file. In the zipped box folder, there are files with unknown formats and I do not know to open them. I have created pictures in CR2 format and I want to view the ADU values. Help me, please.
Thank you.
Да, жалко что мы на .org-сайте эту дискуссию развели, при наличии русскоязычного.
Иностранцев распугаем.
Это на 99% похоже на переполнение целого (или short, уж не знаю что там используется в dt).
LibRaw 0.14/dcraw_emu -T такого эффекта не дает.
Возможно какой-то постпроцессинг LibRaw такой эффект и даст, но мне за несколько попыток не удалось подобрать варианты и я бросил. Тем более, что я не знаю как именно dt использует LibRaw.
Не менее возможно, что это такое вычитание черного, без проверки выхода ниже нуля, но это точно не LibRaw так поступает, по сведениям LibRaw черный уже вычтен.
Тут raw с которым сильно проявляется и скрин программы
https://rapidshare.com/files/2640967101/sample.7z
Вообще-то, в libraw 0.14 довольно много всего поменялось. В частности, доступ к RAW-данным.
Вместе с тем, если вы выложите куда-то исходник (RAW-файл) то я на него, как минимум, посмотрю...
Я собираю darktable без rawspeed. Так как с моим Pentax K-x последний не умеет работать, вернее тот что встроен в 0.9.2 не умеет. Так вот с libraw 0.13.8 всё отлично, а c libraw 0.14.0 цветные точки появляются.
В darktable же полностью свой постпроцессинг, от libraw берут только RAW-данные (потому и может работать с rawspeed)?
В darktable собранном с 0.14.0 (в gentoo есть патч с которым можно собрать dt с системным libraw) на многих снимках вылазят цветные точки. Не знаю проблема это со стороны darktable или libraw.
LibRaw-Lite is no longer exists since version 0.9 or so.
There are:
- main LibRaw, distributed under triple licensing
- GPL2+ licensed sources (demosaic-pack-GPL2): Foveon support and some demosaic methods
- GPL3+ licensed sources: several demosaics plus noise reduction.
Depending on your application license, you may use only main LibRaw (if your application is not GPLed), LibRaw+GPL2 pack (for GPL2+ app), LibRaw+GPL2+GPL3 (for GPL3+ apps)
Would it be possible to get support for X3F files from the newer Sigma camera models? Code might be based on the X3F Tools found here: https://github.com/rolkar/x3f
Regards,
Niels Kristian Bech Jensen
I'm in the very same step, chaining Cam_xyz with xyz_srgb matrixes, but can't get the color right... What am I missing? Also, which coeficients do I have to use to do white balance?
Thanks in advance.
Pages