Re: [darktable-dev] Resize panels in lightmode & darkroom

[Roman Lebedev]

On Fri, Feb 23, 2018 at 2:19 PM, giuseppe.in...@gmail.com
 wrote:
> Hi all,
> I'am using darktable on windows (version 2.4.1). I'm not able to resize the
> panels on the left and on the righe in lightmode and/or darkroom mode. Is
> this a problem for the windows version or either in Linux you cannot resize
> the panels?
https://www.darktable.org/usermanual/en/preferences_chapter.html#gui_options

width of the side panels in pixels

This controls the size of side panels in pixels. Side panels are found
left and right to the center view (default 350).


> Thanks,
> Giuseppe.
>
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] GCC 7

[Roman Lebedev]

You have already tried removing the build dir?

On Sat, Jan 27, 2018 at 5:14 PM, Jørn Villesen Christensen
 wrote:
> Ok. Thank you for your replies. I'll have another look later.
>
> One reason why I thought it might have been due to gcc 7 was these two posts
> (among others):
>
> https://github.com/svaarala/duktape/issues/1602
>
> https://github.com/collectd/collectd/issues/2423
>
> But thank you once again :)
>
> ~Jørn
>
>
>
> On 2018-01-27 16:04, Jean-Luc Coulon (f5ibh) wrote:
>>
>> Hi
>> 2018-01-27 9:57 GMT+01:00 Tobias Ellinghaus > >:
>>
>> Am Samstag, 27. Januar 2018, 06:38:57 CET schrieb Jørn Villesen
>> Christensen:
>> > Hi there,
>> >
>> > It seems (to me) that darktable does not support gcc 7. Is there any
>> > effort at the moment to support this? Or if not, what is the latest
>> > gcc-version that is supported?
>>
>> gcc 7 should be supported, several of us are building with it all
>> the time.
>>
>> I use gcc 7 and I dont experience any problem related to it.
>> And I build git version daily (or mostly)
>>
>> [ ... ]
>> > got gcc v7.2 along with it.
>>
>> I am using 7.3 at the moment, but I am fairly certain that I used
>> 7.2 before.
>>
>>
>> I have used 7.2 and I use 7.3 from debian
>>
>>
>>  > BR
>>  > Jørn
>>
>> Tobias
>>
>> Jean-Luc
>>
>>
>>
>> ___
>> darktable developer mailing list to unsubscribe send a mail to
>> darktable-dev+unsubscr...@lists.darktable.org
>
>
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] RawSpeed:Unable to find camera in database: 'Canon' 'Canon EOS 5D Mark II' 'dng'

[Roman Lebedev]

On Mon, Jan 22, 2018 at 7:49 PM, Mark Heieis  wrote:
> Hi,
>
> I'm getting this message:
>
> "RawSpeed:Unable to find camera in database: 'Canon' 'Canon EOS 5D Mark II'
> 'dng'"
Just ignore that message. Which dt version is that?

> The dng file is a resultant output of using magic latern's dual iso and
> processing with cr2hdr.
>
> Here's a link to a dng file
> https://www.dropbox.com/s/i3vb3ars0nfpxso/IMG_1636.DNG?dl=0
>
> I'll delete the link in a few weeks.
>
> Regards.
Roman.

> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Show maximum possible export size in light table?

[Roman Lebedev]

On Thu, Jan 11, 2018 at 7:17 AM, August Schwerdfeger
 wrote:
> There is currently no easy way to determine the dimensions of an image after
> processing occurs (i.e., the maximum size at which an image can be exported
> without upscaling). I either have to do the actual export at maximum size,
> or go into darkroom mode, open up the crop module, and try to hold the
> pointer as steady as I can while reading the dimensions off of the center of
> the crop box.
>
> Would it be feasible to have a light table module showing an image's maximum
> possible export size?
What for, what's the use-case?

> --
> August Schwerdfeger
> aug...@schwerdfeger.name
Roman.

> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Where Does Default Rotation Happen?

[Roman Lebedev]

On Mon, Jan 8, 2018 at 7:28 AM, Robert Bieber  wrote:
Hi.

Looking at exiftool output, i see:
[MakerNotes]CameraOrientation   : Horizontal (normal)

So i guess either exiv2 simply does not know about that tag,
or the exiv2 you have does not know about that tag yet.
Either way, it's between you and https://github.com/Exiv2/exiv2
Feel free to CC me though.

> I have a camera (Leaf Credo 40) for which Darktable doesn't recognize the
> orientation sensor.  I'll upload a vertical RAW file to raw.pixls.us
> tomorrow (I realize now all the ones I've already uploaded were horizontal),
> but if I wanted to start poking around at this myself where in the code
> would I look?  I'm assuming that this would be handled somewhere in DT
> itself, not in RawSpeed, since the orientation is just metadata, right?
Roman.

> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] add compress to history stack module

[Roman Lebedev]

On Tue, Jan 2, 2018 at 12:17 AM, William Ferguson <wpfergu...@gmail.com> wrote:
>
>
> On Mon, Jan 1, 2018 at 4:08 PM, Roman Lebedev <lebedev...@gmail.com> wrote:
>>
>> On Mon, Jan 1, 2018 at 11:52 PM, William Ferguson <wpfergu...@gmail.com>
>> wrote:
>> > Hello,
>> >
>> > I shoot lots of high school sports.  Bad light, high iso, fast action,
>> > etc.
>> > I usually pick one image, process it, then copy the history stack to the
>> > rest.  Then I go through them one by one and tweak the exposure, crop,
>> > rotation, noise reduction, exposure, etc. I try to remember to compress
>> > my
>> > history stack before I move to the next image, but often don't.
>>
>> > Once I've finished processing all the images, I'd like to compress all
>> > the
>> > history stacks prior to exporting.  The itch finally got bad enough that
>> > I scratched It.
>> Why though?
>> It solves nothing other than maybe acting like a placebo for OCD.
>
> Maybe my understanding of the pixelpipe is flawed.  I thought on export it
> performed all
> the steps in the history stack.  Multiple exposure steps probably aren't
> very expensive, but
> multiple noise reduction steps would be.  Does the pixelpipe evaluate the
> history stack prior
> to processing it and skip the unneeded steps?
https://www.darktable.org/usermanual/en/darkroom_concepts.html#pixelpipe

>>
>>
>> > I based the code on the delete function.  I noticed in the delete
>> > function
>> > there is a preference to ask before delete.  I'm wondering if there
>> > should
>> > be a ask before compress preference?  I'm also wondering where to hook
>> > into
>> > the GUI settings to add it?
>> >
>> > I ran it on a collection of 169 images with 102 that needed compressed.
>> > As
>> > soon as it started, thumbnails started regenerating.  The time to
>> > compress
>> > the stack is negligible compared to regenerating the thumbnail.
>> >
>> > Thoughts, comments, suggestions?
>> >
>> >
>> > Bill
>> Roman.
>>
>> >
>> > ___
>> > darktable developer mailing list to unsubscribe send a mail to
>> > darktable-dev+unsubscr...@lists.darktable.org
>
>
>
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] add compress to history stack module

[Roman Lebedev]

On Mon, Jan 1, 2018 at 11:52 PM, William Ferguson  wrote:
> Hello,
>
> I shoot lots of high school sports.  Bad light, high iso, fast action, etc.
> I usually pick one image, process it, then copy the history stack to the
> rest.  Then I go through them one by one and tweak the exposure, crop,
> rotation, noise reduction, exposure, etc. I try to remember to compress my
> history stack before I move to the next image, but often don't.

> Once I've finished processing all the images, I'd like to compress all the
> history stacks prior to exporting.  The itch finally got bad enough that
> I scratched It.
Why though?
It solves nothing other than maybe acting like a placebo for OCD.

> I based the code on the delete function.  I noticed in the delete function
> there is a preference to ask before delete.  I'm wondering if there should
> be a ask before compress preference?  I'm also wondering where to hook into
> the GUI settings to add it?
>
> I ran it on a collection of 169 images with 102 that needed compressed.  As
> soon as it started, thumbnails started regenerating.  The time to compress
> the stack is negligible compared to regenerating the thumbnail.
>
> Thoughts, comments, suggestions?
>
>
> Bill
Roman.

> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Canon Powershot G1X Mark II noise profile

[Roman Lebedev]

On Sat, Dec 30, 2017 at 5:21 PM, Thomas Krekler
 wrote:
> I've created a noise profile for the powershot G1X Mark II and it is
> available here:
>
> https://drive.google.com/file/d/1kY9ef6RT_v8tuhvA3QGJRZbgfRiXdNrO/view?usp=sharing
Best to open a new issue, and upload it there, that way it won't be lost.
https://redmine.darktable.org/projects/darktable/issues/new

> If there is something wrong with the link or the profile, please let me
> know.
> Cheers
> Thomas
Roman.

> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Support for Panasonic DMC-TZ81 in 16:9-mode

[Roman Lebedev]

On Sat, Dec 30, 2017 at 1:31 PM, Pythagoras  wrote:
> Hello,
Hi.

> But there is already a sample of this format submitted.
> When I open my own 16:9-files then they are opened in 4:3.

> the Camera Panasonic DMC-TZ81 is not supported in 16:9 mode.
That is not true. As you have said yourself, the raws load just fine.

In newer cameras, they have finally decided not to crop the raws.
And we never ever provided the same crop as the camera,
so there is no problem here.

> Same happens if I open the submitted 16:9-file.
> In the exifdata of the submitted 16:9-file I discovered
>
> Exif.PanasonicRaw.ImageHeight 3680
> Exif.PanasonicRaw.ImageWidth  4904
>
> wich is 4:3-mode.

> Do you need a new 16:9-file to get this format supported?
No, RPU already has all 4 required samples.

> Reiner
Roman.

> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] can't compile darktable 2.4 with ubuntu 16.04

[Roman Lebedev]

On Sun, Dec 24, 2017 at 4:50 PM, Holger Klemm
 wrote:
> Am Sonntag, 24. Dezember 2017, 16:22:49 CET schrieben Sie:
>> openjpeg2
>
> Hi Roman,
> libopenjp2-7-dev is installed and libopenjpeg-dev is not installed.
>
>
> klemmh@Trillian-Z400:~/Downloads/darktable-2.4.0/build$ dpkg -l | grep
> libopenjp2-7-dev
> ii  libopenjp2-7-dev2.1.2-1.1~16.04.york0
> amd64development files for OpenJPEG, a JPEG 2000 image library
>
> klemmh@Trillian-Z400:~/Downloads/darktable-2.4.0/build$ dpkg -l | grep
> libopenjpeg-dev
> klemmh@Trillian-Z400:~/Downloads/darktable-2.4.0/build$
Hmm, did you install it manually then?

What does this say: ?
$ dpkg -S /usr/include/openjpeg.h
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] can't compile darktable 2.4 with ubuntu 16.04

[Roman Lebedev]

On Sun, Dec 24, 2017 at 4:18 PM, Holger Klemm
 wrote:
> Hi,
> thanks for the new darktable version
>
> When compiles with ubuntu 16.04 there is a crash.
> See attachement
You have openjpeg2 (which dt requires since 2.2), and older openjpeg1
installed at the same time
IIRC openjpeg1 is doing very bad stuff by installing it's headers into
the root of /usr/include,
and not into some subdir, thus the wrong header is being included.

Purging openjpeg1 should solve it.

> Merry Christmas
>
> Holger
Roman.

> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] can't compile darktable

[Roman Lebedev]

On Fri, Dec 22, 2017 at 7:59 PM, Alexander Rabtchevich
<alexander.v.rabtchev...@gmx.net> wrote:
> Here it is
Thank you.

> ...
> -- Performing Test DARKTABLE_HAVE_C_FLAG_WNO_FORMAT_TRUNCATION
> -- Performing Test DARKTABLE_HAVE_C_FLAG_WNO_FORMAT_TRUNCATION - Success
> -- Performing Test DARKTABLE_HAVE_CXX_FLAG_WNO_FORMAT_TRUNCATION
> -- Performing Test DARKTABLE_HAVE_CXX_FLAG_WNO_FORMAT_TRUNCATION - Success
> ...
> cc1: error: unrecognized command line option '-Wno-format-truncation'
> [-Werror]
> cc1: all warnings being treated as errors
So it first says that the flag is supported, and then barfs at it. Touché.

Given the date, i will revert the change that exposed this issue,
but there is something *very* wrong going on here...

> Roman Lebedev wrote:
>>
>> On Fri, Dec 22, 2017 at 6:35 PM, Pascal Obry <pas...@obry.net> wrote:
>>>
>>> Le vendredi 22 décembre 2017 à 18:26 +0300, Alexander Rabtchevich a
>>> écrit :
>>>>
>>>> gcc (Ubuntu 5.4.0-6ubuntu1~16.04.5) 5.4.0 20160609
>>>>
>>>> Linux Mint 18.3
>>>
>>> Roman will confirm, but I think this is a way too old compiler not
>>> supported to build dt.
>>
>> No, gcc5 is fine. But i don't understand that failure.
>>
>> Please show all the output starting with stepping into new clean build
>> dir.
>>
>>
> With respect,
> Alexander Rabtchevich
Roman.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] can't compile darktable

[Roman Lebedev]

On Fri, Dec 22, 2017 at 6:35 PM, Pascal Obry  wrote:
> Le vendredi 22 décembre 2017 à 18:26 +0300, Alexander Rabtchevich a
> écrit :
>> gcc (Ubuntu 5.4.0-6ubuntu1~16.04.5) 5.4.0 20160609
>>
>> Linux Mint 18.3
>
> Roman will confirm, but I think this is a way too old compiler not
> supported to build dt.
No, gcc5 is fine. But i don't understand that failure.

Please show all the output starting with stepping into new clean build dir.

> In latest version of Mint you ought to have a more recent compiler, no?
>
> --
>   Pascal Obry /  Magny Les Hameaux (78)
>
>   The best way to travel is by means of imagination
>
>   http://www.obry.net
>
>   gpg --keyserver keys.gnupg.net --recv-key F949BD3B
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] can't compile darktable

[Roman Lebedev]

On Fri, Dec 22, 2017 at 5:47 PM, Alexander Rabtchevich
 wrote:
> Hello
>
> Current git master cannot be compiled on Linux Mint 18.3 Mate x64
Did you try   rm -rf build/  already? Does it help?

> [ 93%] Building C object
> src/iop/CMakeFiles/bilat.dir/introspection_bilat.c.o
> cc1: error: unrecognized command line option '-Wno-format-truncation'
> [-Werror]
> cc1: all warnings being treated as errors
> src/iop/CMakeFiles/colortransfer.dir/build.make:67: recipe for target
> 'src/iop/CMakeFiles/colortransfer.dir/introspection_colortransfer.c.o'
> failed
> make[2]: ***
> [src/iop/CMakeFiles/colortransfer.dir/introspection_colortransfer.c.o] Error
> 1
> CMakeFiles/Makefile2:6323: recipe for target
> 'src/iop/CMakeFiles/colortransfer.dir/all' failed
> make[1]: *** [src/iop/CMakeFiles/colortransfer.dir/all] Error 2
> make[1]: *** Waiting for unfinished jobs
> [ 93%] Built target clahe
> [ 93%] Built target dither
> [ 93%] Linking C shared module libexposure.so
> In file included from
> /home/sasha/Install/darktable/build/src/iop/introspection_colormapping.c:54:0:
> /home/sasha/Install/darktable/src/iop/colormapping.c:226:1: warning: ISO C90
> forbids variable length array 'mi' [-Wvla]
>  static void get_cluster_mapping(const int n, float mi[n][2], float wi[n],
> float
>  ^
> /home/sasha/Install/darktable/src/iop/colormapping.c:226:1: warning: ISO C90
> forbids variable length array 'wi' [-Wvla]
> /home/sasha/Install/darktable/src/iop/colormapping.c:226:1: warning: ISO C90
> forbids variable length array 'mo' [-Wvla]
> /home/sasha/Install/darktable/src/iop/colormapping.c:226:1: warning: ISO C90
> forbids variable length array 'wo' [-Wvla]
> /home/sasha/Install/darktable/src/iop/colormapping.c:227:33: warning: ISO
> C90 forbids variable length array 'mapio' [-Wvla]
>  const float dominance, int mapio[n])
>  ^
> /home/sasha/Install/darktable/src/iop/colormapping.c:258:1: warning: ISO C90
> forbids variable length array 'mean' [-Wvla]
>  static void get_clusters(const float *col, const int n, float mean[n][2],
> float
>  ^
> /home/sasha/Install/darktable/src/iop/colormapping.c:278:1: warning: ISO C90
> forbids variable length array 'mean' [-Wvla]
>  static int get_cluster(const float *col, const int n, float mean[n][2])
>  ^
> /home/sasha/Install/darktable/src/iop/colormapping.c:295:1: warning: ISO C90
> forbids variable length array 'mean_out' [-Wvla]
>  static void kmeans(const float *col, const int width, const int height,
> const i
>  ^
> /home/sasha/Install/darktable/src/iop/colormapping.c:296:20: warning: ISO
> C90 forbids variable length array 'var_out' [-Wvla]
> float var_out[n][2], float weight_out[n])
> ^
> /home/sasha/Install/darktable/src/iop/colormapping.c:296:20: warning: ISO
> C90 forbids variable length array 'weight_out' [-Wvla]
> [ 93%] Linking C shared module libbilat.so
> [ 93%] Built target exposure
> cc1: error: unrecognized command line option '-Wno-format-truncation'
> [-Werror]
> cc1: all warnings being treated as errors
> src/iop/CMakeFiles/colormapping.dir/build.make:67: recipe for target
> 'src/iop/CMakeFiles/colormapping.dir/introspection_colormapping.c.o' failed
> make[2]: ***
> [src/iop/CMakeFiles/colormapping.dir/introspection_colormapping.c.o] Error 1
> CMakeFiles/Makefile2:6360: recipe for target
> 'src/iop/CMakeFiles/colormapping.dir/all' failed
> make[1]: *** [src/iop/CMakeFiles/colormapping.dir/all] Error 2
> [ 93%] Built target bilat
> Makefile:149: recipe for target 'all' failed
> make: *** [all] Error 2
>
>
>
> With respect,
> Alexander Rabtchevich
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Noise profiles Fujifilm X-Pro2

[Roman Lebedev]

On Sat, Dec 16, 2017 at 12:19 AM, David Vincent-Jones
 wrote:
Hi.

> My results and profile data is available at:
> https://www.dropbox.com/sh/fnajmbsqdqbh48d/AACIXZfjmlfQLvv19DqQH1CWa?dl=0
Best to open a new issue in redmine, less chance of this being lost.

> Works very well.
>
> David
Roman.

> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] canon eos m6 noise profiles attached

[Roman Lebedev]

On Fri, Dec 15, 2017 at 11:56 PM, Brandon Dimcheff
 wrote:
> Hi there,
Hi.

> I made some noise profiles with my Canon M6.  It's the first time I've done
> it and they appear to work in 2.4.0rc1.  If I did something wrong I'm happy
> to take another crack at it.
>
> They should be publicly downloadable here:
> https://drive.google.com/open?id=17H_HNV9RzG1ga2H0thZdGJBRKlWQcYbK
Best to open a new issue in redmine, less chance of this being lost.

> Thanks!
> Brandon
Roman.

> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Re: Canon Powershot G9X II not supported

[Roman Lebedev]

On Fri, Dec 8, 2017 at 12:38 PM, Matthias Bodenbinder
<matth...@bodenbinder.de> wrote:
> Am 08.12.2017 um 10:31 schrieb Roman Lebedev:
>>> I found that RAW from Canon Powershot G9X Mark II are not supported 
>>> although the camera is listed as supported: 
>>> http://www.darktable.org/resources/camera-support/
>> Hmm, now that i actually look at the release notes, the camera is
>> supported in 2.4.0rc0, *NOT* in any stable release.
>>
>
> Thank you for this clarification. I was getting more and more confused.
Me too, somehow initially i missed the fact that it was not supported
in 2.2.5, sorry about that.

> So that means that http://www.darktable.org/resources/camera-support/ is 
> wrong in the sense that it is not referring to latest stable DT, which is 
> 2.2.5. But it actually shows the supported cameras for next release 2.4.
Possibly, but i'm not sure where it is stated that it is for the last
stable version.

> Matthias
Roman.

> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Canon Powershot G9X II not supported

[Roman Lebedev]

On Fri, Dec 8, 2017 at 9:12 AM, Matthias Bodenbinder
 wrote:
> Hi,
>
> since I did not get feedback on the user list I try it here.
>
> I found that RAW from Canon Powershot G9X Mark II are not supported although 
> the camera is listed as supported: 
> http://www.darktable.org/resources/camera-support/
Hmm, now that i actually look at the release notes, the camera is
supported in 2.4.0rc0, *NOT* in any stable release.

> I am using DT 2.2.5 on Manjaro Linux. I am testing with this RAW file: 
> https://raw.pixls.us/getfile.php/1575/nice/Canon%20-%20PowerShot%20G9%20X%20Mark%20II%20-%20RAW%20(3:2).CR2
>
>
> 7# darktable -d lighttable
> RawSpeed:Unable to find camera in database: 'Canon' 'Canon PowerShot G9 X 
> Mark II' ''
> Please consider providing samples on , thanks!
> [rawspeed] (Canon - PowerShot G9 X Mark II - RAW (3_2).CR2) Camera 'Canon' 
> 'Canon PowerShot G9 X Mark II', mode '' not supported, and not allowed to 
> guess. Sorry.
> [temperature] failed to read camera white balance information from `Canon - 
> PowerShot G9 X Mark II - RAW (3_2).CR2'!
> [temperature] failed to read camera white balance information from `Canon - 
> PowerShot G9 X Mark II - RAW (3_2).CR2'!
> allocation failed???
> [colorin] `Canon Canon PowerShot G9 X Mark II' color matrix not found!
> [colorin] `Canon Canon PowerShot G9 X Mark II' color matrix not found!
> [colorin] `Canon Canon PowerShot G9 X Mark II' color matrix not found!
> [temperature] failed to read camera white balance information from `Canon - 
> PowerShot G9 X Mark II - RAW (3_2).CR2'!
> [colorin] `Canon Canon PowerShot G9 X Mark II' color matrix not found!
> [colorin] `Canon Canon PowerShot G9 X Mark II' color matrix not found!
> [colorin] `Canon Canon PowerShot G9 X Mark II' color matrix not found!
> [temperature] failed to read camera white balance information from `Canon - 
> PowerShot G9 X Mark II - RAW (3_2).CR2'!
> [colorin] `Canon Canon PowerShot G9 X Mark II' color matrix not found!
> [colorin] `Canon Canon PowerShot G9 X Mark II' color matrix not found!
> [colorin] `Canon Canon PowerShot G9 X Mark II' color matrix not found!
>
> Matthias
>
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Canon Powershot G9X II not supported

[Roman Lebedev]

On Fri, Dec 8, 2017 at 9:12 AM, Matthias Bodenbinder
 wrote:
> Hi,
Hi.

> since I did not get feedback on the user list I try it here.
>
> I found that RAW from Canon Powershot G9X Mark II are not supported although 
> the camera is listed as supported: 
> http://www.darktable.org/resources/camera-support/
>
> I am using DT 2.2.5 on Manjaro Linux. I am testing with this RAW file: 
> https://raw.pixls.us/getfile.php/1575/nice/Canon%20-%20PowerShot%20G9%20X%20Mark%20II%20-%20RAW%20(3:2).CR2
Like i said before, this sample does load with git master, so i
suspect there may be some problems on your end...

> 7# darktable -d lighttable
> RawSpeed:Unable to find camera in database: 'Canon' 'Canon PowerShot G9 X 
> Mark II' ''
> Please consider providing samples on , thanks!
> [rawspeed] (Canon - PowerShot G9 X Mark II - RAW (3_2).CR2) Camera 'Canon' 
> 'Canon PowerShot G9 X Mark II', mode '' not supported, and not allowed to 
> guess. Sorry.
> [temperature] failed to read camera white balance information from `Canon - 
> PowerShot G9 X Mark II - RAW (3_2).CR2'!
> [temperature] failed to read camera white balance information from `Canon - 
> PowerShot G9 X Mark II - RAW (3_2).CR2'!
> allocation failed???
> [colorin] `Canon Canon PowerShot G9 X Mark II' color matrix not found!
> [colorin] `Canon Canon PowerShot G9 X Mark II' color matrix not found!
> [colorin] `Canon Canon PowerShot G9 X Mark II' color matrix not found!
> [temperature] failed to read camera white balance information from `Canon - 
> PowerShot G9 X Mark II - RAW (3_2).CR2'!
> [colorin] `Canon Canon PowerShot G9 X Mark II' color matrix not found!
> [colorin] `Canon Canon PowerShot G9 X Mark II' color matrix not found!
> [colorin] `Canon Canon PowerShot G9 X Mark II' color matrix not found!
> [temperature] failed to read camera white balance information from `Canon - 
> PowerShot G9 X Mark II - RAW (3_2).CR2'!
> [colorin] `Canon Canon PowerShot G9 X Mark II' color matrix not found!
> [colorin] `Canon Canon PowerShot G9 X Mark II' color matrix not found!
> [colorin] `Canon Canon PowerShot G9 X Mark II' color matrix not found!
>
> Matthias
Roman.

> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Camera support Sony a7rIII

[Roman Lebedev]

On Wed, Dec 6, 2017 at 11:50 PM, K. Adam Christensen
 wrote:
> So I've re-uploaded them to
> https://drive.google.com/drive/folders/1aGKdgR1NkwSdeDHPuvhQLqbjaUnA-QOq.
> I've moved the old ones to "Old".
(you need to upload to RPU, i can't just take some samples and upload
them there.)

> BUT...
>
> On Wed, Dec 6, 2017 at 11:31 AM Bob Tregilus  wrote:

 And Adam, once you get the shots up on , did you
 want me to open an camera support issue (bug) at
  or will you do 
 it?
 I'd be happy to do it.

>> Also, FYI, I just noticed that a couple of the ILCE-7RM2 submissions at
>> pixls.us state: "Kelvies stash: Vignetting and CA correction off; the one
>> with it on shows that Sony bakes the corrections into the raws."
>
>
> Bah. I just got back from the studio with the photos and now I see the
> Vignetting and CA correction note. When I look at the RAW file and the JPEG
> along side it, I see the JPEG has some correction, but the RAW does not --
> or more correctly I see that the images differ in pin-cushing adjustments. I
> also was unable to find documentation that this option does modify the RAW
> files. Is this actually a real thing?
Some mad camera manufacturers are mad and do modify their raw files, yes.
It's a shame.

> If so, then I don't think I'll be able to take some additional ones today. I
> will have to re-do later.
Nah, i don't care about that stuff for RPU.
So don't worry about it :)

> --
> Adam
Roman.

> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Camera support Sony a7rIII

[Roman Lebedev]

On Wed, Dec 6, 2017 at 9:30 PM, K. Adam Christensen
<p...@shifteleven.com> wrote:
> Crud. I didn't read the manual close enough - Hi+ drive mode goes to 12bit
> for compressed RAW only. I need to find another way. Perhaps by leaving Long
> Exposure NR on, but then doesn't that have issues on the RAW file too? Bah,
> I may need to keep reading.
Yes, others appear to have correct bitdepth/compression.

For reference:
$ exiv2 -Pkt raw.arw | grep Exif.SubImage1.BitsPerSample
^ that is the value you should be looking for.

> Sorry about that.
>
> --
> Adam
Roman.

> On Wed, Dec 6, 2017 at 10:17 AM Roman Lebedev <lebedev...@gmail.com> wrote:
>>
>> On Wed, Dec 6, 2017 at 9:06 PM, K. Adam Christensen
>> <p...@shifteleven.com> wrote:
>> > Hi.
>> Hi.
>>
>> > I've taken the sample photos -
>> > https://drive.google.com/open?id=1aGKdgR1NkwSdeDHPuvhQLqbjaUnA-QOq. I'm
>> > going to upload them to https://raw.pixls.us/ now.
>> The "Sony_-_ILCE-7RM3_-_12bit_uncompressed_(3:2).ARW" is still 14 bit.
>>
>> > --
>> > Adam
>> Roman.
>>
>> > On Wed, Dec 6, 2017 at 1:15 AM Roman Lebedev <lebedev...@gmail.com>
>> > wrote:
>> >>
>> >> On Wed, Dec 6, 2017 at 12:08 PM, Bob Tregilus <v2g...@gmail.com> wrote:
>> >> > Thanks Roman.
>> >> >
>> >> > If I get my hands on a camera, I can provide studio shots of a color
>> >> > card /
>> >> > target.
>> >> The exact content of the shots does not matter,
>> >> as long they *all* have the *same* content.
>> >>
>> >> > Any sense on when 2.4.0 might be final, a week, two?
>> >> No clue, certainly *not* this weekend.
>> >>
>> >> >...
>> >>
>> >> > I offered to donate to the project some time ago but was told to just
>> >> > use
>> >> > the software. you guys should add a donate button to your website and
>> >> > have a beer or two on those of us who unable to contribute code. :)
>> >> That suggestion was brought up a lot of times.
>> >> There are no legal entity/person to handle the legal matters (taxes,
>> >> etc).
>> >>
>> >> > Cheers,
>> >> > Bob
>> >> Roman.
>> >>
>> >> > ---
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > On Wed, Dec 6, 2017 at 12:39 AM, Roman Lebedev <lebedev...@gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> On Wed, Dec 6, 2017 at 11:28 AM, Bob Tregilus <v2g...@gmail.com>
>> >> >> wrote:
>> >> >> > Hi Roman -
>> >> >> >
>> >> >> > Yes, I was aware of the need to open an issue at
>> >> >> > <https://redmine.darktable.org/projects/darktable/issues/new>.
>> >> >> >
>> >> >> > The camera I'm trying to get samples uploaded to  is
>> >> >> > for
>> >> >> > the
>> >> >> > new Sony ILCE-7RM3, not the DSC-RX10M3.
>> >> >> Ah!
>> >> >>
>> >> >> > The ILCE-7RM3 just started shipping in Europe and Asia last month
>> >> >> > and
>> >> >> > a
>> >> >> > few
>> >> >> > are beginning to be shipped in the U.S., where I live. (I just
>> >> >> > ordered
>> >> >> > one,
>> >> >> > but it looks like it will be a few weeks before it arrives. A
>> >> >> > friend
>> >> >> > had
>> >> >> > one
>> >> >> > on preorder early, so he may get it in a week or so and I'll be
>> >> >> > able
>> >> >> > to
>> >> >> > get
>> >> >> > the samples at that time. It's an extremely popular camera that
>> >> >> > people
>> >> >> > are
>> >> >> > really going nuts over. So if at all possible, it really should be
>> >> >> > included
>> >> >> > in the upcoming 2.4.0 release--if at all possible. Of course, I
>> >> >> > understand
>> >> >> > if it's too late for this release.)
>> >> >> If the full sample set will be uploaded before the 2.4.0 final, then
>> >&

Re: [darktable-dev] Camera support Sony a7rIII

[Roman Lebedev]

On Wed, Dec 6, 2017 at 9:06 PM, K. Adam Christensen
<p...@shifteleven.com> wrote:
> Hi.
Hi.

> I've taken the sample photos -
> https://drive.google.com/open?id=1aGKdgR1NkwSdeDHPuvhQLqbjaUnA-QOq. I'm
> going to upload them to https://raw.pixls.us/ now.
The "Sony_-_ILCE-7RM3_-_12bit_uncompressed_(3:2).ARW" is still 14 bit.

> --
> Adam
Roman.

> On Wed, Dec 6, 2017 at 1:15 AM Roman Lebedev <lebedev...@gmail.com> wrote:
>>
>> On Wed, Dec 6, 2017 at 12:08 PM, Bob Tregilus <v2g...@gmail.com> wrote:
>> > Thanks Roman.
>> >
>> > If I get my hands on a camera, I can provide studio shots of a color
>> > card /
>> > target.
>> The exact content of the shots does not matter,
>> as long they *all* have the *same* content.
>>
>> > Any sense on when 2.4.0 might be final, a week, two?
>> No clue, certainly *not* this weekend.
>>
>> >...
>>
>> > I offered to donate to the project some time ago but was told to just
>> > use
>> > the software. you guys should add a donate button to your website and
>> > have a beer or two on those of us who unable to contribute code. :)
>> That suggestion was brought up a lot of times.
>> There are no legal entity/person to handle the legal matters (taxes, etc).
>>
>> > Cheers,
>> > Bob
>> Roman.
>>
>> > ---
>> >
>> >
>> >
>> >
>> > On Wed, Dec 6, 2017 at 12:39 AM, Roman Lebedev <lebedev...@gmail.com>
>> > wrote:
>> >>
>> >> On Wed, Dec 6, 2017 at 11:28 AM, Bob Tregilus <v2g...@gmail.com> wrote:
>> >> > Hi Roman -
>> >> >
>> >> > Yes, I was aware of the need to open an issue at
>> >> > <https://redmine.darktable.org/projects/darktable/issues/new>.
>> >> >
>> >> > The camera I'm trying to get samples uploaded to  is
>> >> > for
>> >> > the
>> >> > new Sony ILCE-7RM3, not the DSC-RX10M3.
>> >> Ah!
>> >>
>> >> > The ILCE-7RM3 just started shipping in Europe and Asia last month and
>> >> > a
>> >> > few
>> >> > are beginning to be shipped in the U.S., where I live. (I just
>> >> > ordered
>> >> > one,
>> >> > but it looks like it will be a few weeks before it arrives. A friend
>> >> > had
>> >> > one
>> >> > on preorder early, so he may get it in a week or so and I'll be able
>> >> > to
>> >> > get
>> >> > the samples at that time. It's an extremely popular camera that
>> >> > people
>> >> > are
>> >> > really going nuts over. So if at all possible, it really should be
>> >> > included
>> >> > in the upcoming 2.4.0 release--if at all possible. Of course, I
>> >> > understand
>> >> > if it's too late for this release.)
>> >> If the full sample set will be uploaded before the 2.4.0 final, then
>> >> it will fit.
>> >>
>> >> > So I've been lobbying various forums to try and get someone to upload
>> >> > the
>> >> > requisite samples to , after which, I had planned to
>> >> > open
>> >> > an
>> >> > issue at
>> >> > <https://redmine.darktable.org/projects/darktable/issues/new>.
>> >> I think there are 4 samples needed:
>> >> * compressed 14bit
>> >> * uncompressed 14bit
>> >> * compressed 12bit (high FPS shooting?)
>> >> * uncompressed 12bit
>> >>
>> >> As usual, the all the samples need to have the same content,
>> >> and the scene and the camera should be as static as possible.
>> >>
>> >> > Is that the correct process given I can't submit the samples myself
>> >> > as
>> >> > yet?
>> >> As long as the samples are uploaded by the person who owns the samples,
>> >> and not reuploaded e.g. from some review site, i don't see the problem.
>> >>
>> >> > Thanks for your help!
>> >> >
>> >> > Bob
>> >> > in Reno, NV
>> >> Roman.
>> >>
>> >> > ---
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > On Tue, Dec 5, 2017 at 11:55 PM, Roman Lebedev <lebedev...@gmail.com>
>> >>

Re: [darktable-dev] Camera support Sony a7rIII

[Roman Lebedev]

On Wed, Dec 6, 2017 at 12:08 PM, Bob Tregilus <v2g...@gmail.com> wrote:
> Thanks Roman.
>
> If I get my hands on a camera, I can provide studio shots of a color card /
> target.
The exact content of the shots does not matter,
as long they *all* have the *same* content.

> Any sense on when 2.4.0 might be final, a week, two?
No clue, certainly *not* this weekend.

>...

> I offered to donate to the project some time ago but was told to just use
> the software. you guys should add a donate button to your website and
> have a beer or two on those of us who unable to contribute code. :)
That suggestion was brought up a lot of times.
There are no legal entity/person to handle the legal matters (taxes, etc).

> Cheers,
> Bob
Roman.

> ---
>
>
>
>
> On Wed, Dec 6, 2017 at 12:39 AM, Roman Lebedev <lebedev...@gmail.com> wrote:
>>
>> On Wed, Dec 6, 2017 at 11:28 AM, Bob Tregilus <v2g...@gmail.com> wrote:
>> > Hi Roman -
>> >
>> > Yes, I was aware of the need to open an issue at
>> > <https://redmine.darktable.org/projects/darktable/issues/new>.
>> >
>> > The camera I'm trying to get samples uploaded to  is for
>> > the
>> > new Sony ILCE-7RM3, not the DSC-RX10M3.
>> Ah!
>>
>> > The ILCE-7RM3 just started shipping in Europe and Asia last month and a
>> > few
>> > are beginning to be shipped in the U.S., where I live. (I just ordered
>> > one,
>> > but it looks like it will be a few weeks before it arrives. A friend had
>> > one
>> > on preorder early, so he may get it in a week or so and I'll be able to
>> > get
>> > the samples at that time. It's an extremely popular camera that people
>> > are
>> > really going nuts over. So if at all possible, it really should be
>> > included
>> > in the upcoming 2.4.0 release--if at all possible. Of course, I
>> > understand
>> > if it's too late for this release.)
>> If the full sample set will be uploaded before the 2.4.0 final, then
>> it will fit.
>>
>> > So I've been lobbying various forums to try and get someone to upload
>> > the
>> > requisite samples to , after which, I had planned to open
>> > an
>> > issue at <https://redmine.darktable.org/projects/darktable/issues/new>.
>> I think there are 4 samples needed:
>> * compressed 14bit
>> * uncompressed 14bit
>> * compressed 12bit (high FPS shooting?)
>> * uncompressed 12bit
>>
>> As usual, the all the samples need to have the same content,
>> and the scene and the camera should be as static as possible.
>>
>> > Is that the correct process given I can't submit the samples myself as
>> > yet?
>> As long as the samples are uploaded by the person who owns the samples,
>> and not reuploaded e.g. from some review site, i don't see the problem.
>>
>> > Thanks for your help!
>> >
>> > Bob
>> > in Reno, NV
>> Roman.
>>
>> > ---
>> >
>> >
>> >
>> >
>> >
>> > On Tue, Dec 5, 2017 at 11:55 PM, Roman Lebedev <lebedev...@gmail.com>
>> > wrote:
>> >>
>> >> On Wed, Dec 6, 2017 at 2:10 AM, Bob Tregilus <v2g...@gmail.com> wrote:
>> >> > Hi -
>> >> Hi.
>> >>
>> >> > Love Darktable--thanks for a great product!
>> >> >
>> >> > As you are likely aware, Sony is now shipping the third version of
>> >> > the
>> >> > popular a7r series (the a7r III).
>> >> >
>> >> > Since it has been some time since a new version of Darktable has been
>> >> > released, I assume a new version maybe approaching the beta stage?
>> >>
>> >> > I've been working fanatically, to come up with a way to get Sony
>> >> > a7rIII
>> >> > RAW
>> >> > samples submitted to raw.pixls.us, so support will be included in any
>> >> > new
>> >> > release of Darktable that may be in the pipeline.
>> >> It does not work like that. Samples on RPU only guarantee that there
>> >> won't
>> >> be
>> >> any unwanted regressions in raw file decoding. Uploading samples *does
>> >> not*
>> >> automagically mean that we will add support for that. You need to open
>> >> an issue: https://redmine.darktable.org/projects/darktable/issues/new
>> >>
>> >> > I've made requests on an a7rIII user list on Facebook asking someo

Re: [darktable-dev] Camera support Sony a7rIII

[Roman Lebedev]

On Wed, Dec 6, 2017 at 11:28 AM, Bob Tregilus <v2g...@gmail.com> wrote:
> Hi Roman -
>
> Yes, I was aware of the need to open an issue at
> <https://redmine.darktable.org/projects/darktable/issues/new>.
>
> The camera I'm trying to get samples uploaded to  is for the
> new Sony ILCE-7RM3, not the DSC-RX10M3.
Ah!

> The ILCE-7RM3 just started shipping in Europe and Asia last month and a few
> are beginning to be shipped in the U.S., where I live. (I just ordered one,
> but it looks like it will be a few weeks before it arrives. A friend had one
> on preorder early, so he may get it in a week or so and I'll be able to get
> the samples at that time. It's an extremely popular camera that people are
> really going nuts over. So if at all possible, it really should be included
> in the upcoming 2.4.0 release--if at all possible. Of course, I understand
> if it's too late for this release.)
If the full sample set will be uploaded before the 2.4.0 final, then
it will fit.

> So I've been lobbying various forums to try and get someone to upload the
> requisite samples to , after which, I had planned to open an
> issue at <https://redmine.darktable.org/projects/darktable/issues/new>.
I think there are 4 samples needed:
* compressed 14bit
* uncompressed 14bit
* compressed 12bit (high FPS shooting?)
* uncompressed 12bit

As usual, the all the samples need to have the same content,
and the scene and the camera should be as static as possible.

> Is that the correct process given I can't submit the samples myself as yet?
As long as the samples are uploaded by the person who owns the samples,
and not reuploaded e.g. from some review site, i don't see the problem.

> Thanks for your help!
>
> Bob
> in Reno, NV
Roman.

> ---
>
>
>
>
>
> On Tue, Dec 5, 2017 at 11:55 PM, Roman Lebedev <lebedev...@gmail.com> wrote:
>>
>> On Wed, Dec 6, 2017 at 2:10 AM, Bob Tregilus <v2g...@gmail.com> wrote:
>> > Hi -
>> Hi.
>>
>> > Love Darktable--thanks for a great product!
>> >
>> > As you are likely aware, Sony is now shipping the third version of the
>> > popular a7r series (the a7r III).
>> >
>> > Since it has been some time since a new version of Darktable has been
>> > released, I assume a new version maybe approaching the beta stage?
>>
>> > I've been working fanatically, to come up with a way to get Sony a7rIII
>> > RAW
>> > samples submitted to raw.pixls.us, so support will be included in any
>> > new
>> > release of Darktable that may be in the pipeline.
>> It does not work like that. Samples on RPU only guarantee that there won't
>> be
>> any unwanted regressions in raw file decoding. Uploading samples *does
>> not*
>> automagically mean that we will add support for that. You need to open
>> an issue: https://redmine.darktable.org/projects/darktable/issues/new
>>
>> > I've made requests on an a7rIII user list on Facebook asking someone to
>> > take
>> > the time to submit samples to raw.pixls.us. So far, I've had no luck.
>> >
>> > A friend preordered the camera, when it was first announced, so he
>> > should be
>> > getting his soon. When he does, I'll be able to get the necessary
>> > samples
>> > uploaded to raw.pixls.us.
>> >
>> > The camera has been shipping elsewhere in the world and is only now
>> > beginning to ship in the U.S., so it still may be several weeks before
>> > I'll
>> > be able to submit the samples.
>> >
>> > By all accounts, the a7rIII is selling very well, with many Nikon and
>> > Canon
>> > DSLR users making the jump to mirrorless. And, of course, many a7rII
>> > users
>> > upgrading to the new a7rIII as well.
>> >
>> > I'm just hoping that if a new version of Darktable is in the pipeline
>> > that
>> > it will include support for the new a7rIII.
>> >
>> > Whatever the case, be it known that I will get a7rIII samples upload to
>> > raw.pixls.us as soon as I'm able, which should be within the next
>> > several
>> > weeks.
>> That's SONY DSC-RX10M3, right? We already have a sample for that.
>> Looking at the PDF usermanual, *i think* that camera can only produce
>> one raw 'format', so 1 sample is all.
>>
>> > Thanks,
>> > Bob
>> > in Reno, NV
>> Roman.
>>
>> > PS: At the same time, or shortly thereafter when I get my camera (just
>> > ordered mine last night), I'll be sure to get lenses corrections
>> > submitted
>> > to the Lensfun project as well.
>> >
>> >
>> > ___
>> > darktable developer mailing list to unsubscribe send a mail to
>> > darktable-dev+unsubscr...@lists.darktable.org
>
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Failed to read camera white balance information

[Roman Lebedev]

On Tue, Dec 5, 2017 at 9:42 PM, steve <countci...@gmail.com> wrote:
> Roman,
>
> Thank you for responding to my note.  I love Darktable and greatly
> appreciate all the work you and the other developers do to make this such an
> amazing tool.
>
> In looking at the file, I realize it is an Olympus high resolution ORF file.
> The file size is 59.9 MB.  Will darktable support the high-resolution modes
> of Olympus RAW files?

We were looking for the full raw sample set for that camera not that long ago.
https://github.com/darktable-org/darktable/pull/1450#issuecomment-343576501
(but we are looking for the [full] sample sets for some other cameras still, see
https://discuss.pixls.us/t/raw-samples-wanted/5420?u=lebedevri)

We finally have it, and all the samples i have (including high resolution ORF)
do load in darktable.

> Thank you,
>
> Steve
Roman.

> On 12/05/2017 01:25 PM, Roman Lebedev wrote:
>
> On Tue, Dec 5, 2017 at 8:50 PM, steve <countci...@gmail.com> wrote:
>>
>> Running today's build off github.  Darktable unable to read Olympus ORF
>> files for OMD E-M1 Mark II.
>
> Works fine with the samples we have on RPU.
> https://redmine.darktable.org/projects/darktable/issues/new
> and attach at least one raw that does not work for you.
>
>>
>> Also, the EM1 mark II is not recognized by lens correction
>
>
> That is lensfun's problem.
>
>>
>> and doesn't have full white balance modes.  Could this be addressed in
>> this release please?
>
>
>
> Roman.
>>
>>
>>
>> ___
>> darktable developer mailing list to unsubscribe send a mail to
>> darktable-dev+unsubscr...@lists.darktable.org
>
>
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Failed to read camera white balance information

[Roman Lebedev]

On Tue, Dec 5, 2017 at 8:50 PM, steve  wrote:

> Running today's build off github.  Darktable unable to read Olympus ORF
> files for OMD E-M1 Mark II.
>
Works fine with the samples we have on RPU.
https://redmine.darktable.org/projects/darktable/issues/new
and attach at least one raw that does not work for you.


> Also, the EM1 mark II is not recognized by lens correction
>

That is lensfun's problem.


> and doesn't have full white balance modes.  Could this be addressed in
> this release please?
>


Roman.

>
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
>

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Debugging of darktable.

[Roman Lebedev]

On Tue, Dec 5, 2017 at 12:28 AM, Jørn Villesen Christensen
 wrote:
> Hi there,
>
> I have been trying to debug darktable (with gdb) but without any luck.

> My main problem of running darktable from the build directory is that it
> will not load any modules. I have tried to play with --datadir, --moduledir,
> and symlinks, but without any luck. I can get the UI up 'n' running - but no
> modules are loaded.
It's not designed to be runnable without installation.
You may want to
$ sudo mkdir -p /opt/darktable
$ sudo chown youruser:yourgroup -R /opt/darktable

And now when you do  ./build.sh --install  it will end up in there.

(Of course, you can pick any other directory, but then you need to
pass it e.g. via --prefix to build.sh)

> Alternatively I have tried to install darktable in a temporary directory
> next to the build dir, but that fails as well. It launches well, but then
> gdb fails to debug any other files than main.c and I suspect it is due to
> the changed file structure.
>
> So... is it possible for any of you to sketch up how you debug darktable?
>
> BR
> Jørn Christensen
Roman.

> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Cubic Spline in RawSpeed

[Roman Lebedev]

On Wed, Nov 29, 2017 at 6:19 PM, Robert Bieber <d...@biebersprojects.com> wrote:
> On 11/29/2017 02:13 AM, Roman Lebedev wrote:
>>
>> and RawSpeed is LGPL2. so that not is even an option.
>
> Ahh, good point.
>>>
>>> 1. Will any of those curve_tools functions in DT do what the cubic_spline
>>> function in dcraw (reproduced below for reference) does?  I'm not really
>>> familiar with calculating curves, but I'm a bit worried that it seems
>>> like
>>> they're all geared towards interpolating a single point on a curve, which
>>> I'm assuming would be very slow compared to the approach dcraw takes of
>>> calculating all the points on the curve and then just doing a lookup for
>>> each pixel.
>>
>> Let's not do premature optimizations :)
>> Implement the most dumbest/simplest variant, that is actually readable,
>> then i'll add tests and a benchmark; and *then* a specialized, faster
>> implementation *may* be added.
>
>
> So I should implement cubic spline from scratch?  I'll have a go at it,
> what's the worst that could go wrong? ;)
Well, to put it another way, that dcraw cubic_spline() is just plain hideous.
I don't feel like merging it as-is just so that i will have to
remplement it soon after.

> Thanks,
> Robby
>
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Cubic Spline in RawSpeed

[Roman Lebedev]

On Wed, Nov 29, 2017 at 6:16 AM, Robert Bieber  wrote:
> Hi all,
Hi.

> I'm a newcomer to RawSpeed (and raw decoding in general, for that matter),
> but I was hoping I might be able to port the Phase One sensor correction
> functionality in dcraw to RawSpeed's IiqDecoder.

> I think I've pretty well
> figured out how the correction I'm concerned with works: the RAW file
> includes four sets of control points (one for each quadrant of the image)
> that define curves to apply to all the pixels in each respective quadrant
> (this is to compensate for the fact that the "sensor" in these cameras is
> actually four separate sensors being read at the same time, and they can
> have slight variations).
Sounds easy-ish.

> The trickiest part for me right now, aside from making sure I get all the RS
> conventions and formatting right (which I'm hoping I'll get hammered into me
> in PR comments), is actually calculating the curves.  dcraw does it with a
> cubic spline function, but I can't find any comparable function looking
> through the Doxygen for RS.  I did find curve_tools.c/h in Darktable, which
> looks promising.  So, a couple questions:

0. 
https://github.com/darktable-org/darktable/blob/97e66ba84a2ce3c4d53027ebf7c81cc6302ff599/src/common/curve_tools.c#L5-L8

> darktable is free software: you can redistribute it and/or modify
> it under the terms of the GNU General Public License as published by
> the Free Software Foundation, either version 3 of the License, or
> (at your option) any later version.
and RawSpeed is LGPL2. so that not is even an option.

> 1. Will any of those curve_tools functions in DT do what the cubic_spline
> function in dcraw (reproduced below for reference) does?  I'm not really
> familiar with calculating curves, but I'm a bit worried that it seems like
> they're all geared towards interpolating a single point on a curve, which
> I'm assuming would be very slow compared to the approach dcraw takes of
> calculating all the points on the curve and then just doing a lookup for
> each pixel.
Let's not do premature optimizations :)
Implement the most dumbest/simplest variant, that is actually readable,
then i'll add tests and a benchmark; and *then* a specialized, faster
implementation *may* be added.

> 2. Assuming one of those is useful, how should I go about reusing it in RS?
> Should I just copy/paste it?  I could always make it a public function in
> RawSpeed and then use it from DT, but it seems like it would be odd to have
> a single utility function like that call out to the raw decoding library.
> My intuition is it's probably just okay to have them live in both places,
> but I'm open to suggestions.
Just add a new one into rawspeed.

> Thanks,
> Robby
Roman.

> dcraw's cubic_spline implementation follows:
> ---
>
>
> void CLASS cubic_spline (const int *x_, const int *y_, const int len)
> {
>   float **A, *b, *c, *d, *x, *y;
>   int i, j;
>
>   A = (float **) calloc (((2*len + 4)*sizeof **A + sizeof *A), 2*len);
>   if (!A) return;
>   A[0] = (float *) (A + 2*len);
>   for (i = 1; i < 2*len; i++)
> A[i] = A[0] + 2*len*i;
>   y = len + (x = i + (d = i + (c = i + (b = A[0] + i*i;
>   for (i = 0; i < len; i++) {
> x[i] = x_[i] / 65535.0;
> y[i] = y_[i] / 65535.0;
>   }
>   for (i = len-1; i > 0; i--) {
> b[i] = (y[i] - y[i-1]) / (x[i] - x[i-1]);
> d[i-1] = x[i] - x[i-1];
>   }
>   for (i = 1; i < len-1; i++) {
> A[i][i] = 2 * (d[i-1] + d[i]);
> if (i > 1) {
>   A[i][i-1] = d[i-1];
>   A[i-1][i] = d[i-1];
> }
> A[i][len-1] = 6 * (b[i+1] - b[i]);
>   }
>   for(i = 1; i < len-2; i++) {
> float v = A[i+1][i] / A[i][i];
> for(j = 1; j <= len-1; j++)
>   A[i+1][j] -= v * A[i][j];
>   }
>   for(i = len-2; i > 0; i--) {
> float acc = 0;
> for(j = i; j <= len-2; j++)
>   acc += A[i][j]*c[j];
> c[i] = (A[i][len-1] - acc) / A[i][i];
>   }
>   for (i = 0; i < 0x1; i++) {
> float x_out = (float)(i / 65535.0);
> float y_out = 0;
> for (j = 0; j < len-1; j++) {
>   if (x[j] <= x_out && x_out <= x[j+1]) {
> float v = x_out - x[j];
> y_out = y[j] +
>   ((y[j+1] - y[j]) / d[j] - (2 * d[j] * c[j] + c[j+1] * d[j])/6) * v
>+ (c[j] * 0.5) * v*v + ((c[j+1] - c[j]) / (6 * d[j])) * v*v*v;
>   }
> }
> curve[i] = y_out < 0.0 ? 0 : (y_out >= 1.0 ? 65535 :
> (ushort)(y_out * 65535.0 + 0.5));
>   }
>   free (A);
> }
>
>
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Manual lens corrections - feature request

[Roman Lebedev]

On Wed, Nov 15, 2017 at 3:35 PM, Heiko Bauke <heiko.ba...@mail.de> wrote:
> Hi,
>
> Am 15.11.2017 um 12:28 schrieb Roman Lebedev:
>>
>> On Wed, Nov 15, 2017 at 2:14 PM, Heiko Bauke <heiko.ba...@mail.de> wrote:
>
> [...]
>>>
>>> Contrary to the common believe that in-camera
>>> corrections are applied to JPEGs but not to the RAW file, in-camera lens
>>> correction in the EOS-1D X Mark II is applied to RAWs only.  See
>>>
>>> https://snapshot.canon-asia.com/article/en/eos-5d-mark-iv-lens-aberration-correctiona-close-up-look-part-1
>>
>>
>> Can you quote that part where it says what you think it says?
>> I don't see anything there about modifying the raw files.
>
>
> the article is about in-camera lens correction.  Lens corrections are stored
> in the image data, it's not about storing meta data for lens correction in
> post processing.  Do not be confused by the fact that there is also a
> software tool provided by Canon that implements the same kind of lens
> correction algorithms for post processing.
>
> The term RAW file is not included explicitly in the article that I
> mentioned.  It is, however, highlighted that »The Digital Lens Optimizer
> [...]  made its debut as an in-camera feature on the EOS-1D X Mark II. At
> that time, its effects could not be reflected in real time on JPEG images.«
> I understand this statement as that the RAW file image data is affected.
> The camera has a special hardware component to do the heavy math.  This
> would not be needed if just some meta data for lens correction in post would
> be included into the RAW file.
>
> Furthermore, another Canon article (see
> https://snapshot.canon-asia.com/article/en/eos-1d-x-mark-ii-in-camera-lens-optimization-for-high-quality-images
> ) says
>
> »The processing ability of the Dual DIGIC 6 + image processing engines is
> what makes in-camera image processing possible. They are capable of
> processing the vast amount of data that is yielded from the 20-megapixel
> sensor and the continuous shooting speed of 16 fps at a high speed, and
> achieve in-camera RAW image development and real-time aberration correction.
> A dedicated IC has been developed and employed to enable the incorporation
> of different aberration correction features during in-camera RAW image.«

> How would you understand »in-camera RAW image development«?  It does
> definitely not refer to the lens correction to the JPEG, because this camera
> does not have such a feature.
You are just plain wrong here. Lens correction for the jpeg's was always there,
provided the lens profile is stored in camera.

> According to
> https://photo.stackexchange.com/questions/35324/why-does-using-canons-digital-lens-optimizer-double-the-size-of-a-raw-file
> in-camera lens correction in Canon cameras doubles the RAW file size,
> because the processed image data is stored in addition to the unprocessed
> RAW data.
Those are just words, there is not a single confirmed fact there, e.g.
exif dumps
that would show that there is a two SubImages even though the
DualPixel is disabled.
But even if it is true, that violates your own words,
since the original unmodified raw is still there.

> Heiko
Roman.

> --
> -- Number Crunch Blog @ https://www.numbercrunch.de
> --  Cluster Computing @ http://www.clustercomputing.de
> --   Professional @ https://www.mpi-hd.mpg.de/personalhomes/bauke
> --  Social Networking @ https://www.researchgate.net/profile/Heiko_Bauke
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Manual lens corrections - feature request

[Roman Lebedev]

On Wed, Nov 15, 2017 at 2:14 PM, Heiko Bauke  wrote:
> Hi,
Hi.

> Am 15.11.2017 um 11:25 schrieb Jean-Luc Coulon (f5ibh):
>>
>> Personnaly, I think it is a bad idea [tm] to include anything in the raw
>> file.
>> If you change your mind, you cannot get back...
>
>
> I totally agree with that one should apply corrections to RAW files that are
> eventually baked into the RAW file with care.

> It is, however, a
> misconception that RAW files would contain plain sensor data.
>
> Virtually all cameras process, e.g., sharpen, the image to some degree
> before the RAW file is stored.  ISO settings and even white balance settings
> can have an effect on the RAW file.  In-camera lens correction is also done
> in some newer Canon cameras.
> Contrary to the common believe that in-camera
> corrections are applied to JPEGs but not to the RAW file, in-camera lens
> correction in the EOS-1D X Mark II is applied to RAWs only.  See
> https://snapshot.canon-asia.com/article/en/eos-5d-mark-iv-lens-aberration-correctiona-close-up-look-part-1

Yeah no, i'm calling bullshit on most of that.
There are some idiotic manufacturers that modify raws (namely, sony),
but i bet most others don't.

> Contrary to the common believe that in-camera
> corrections are applied to JPEGs but not to the RAW file, in-camera lens
> correction in the EOS-1D X Mark II is applied to RAWs only.  See
> https://snapshot.canon-asia.com/article/en/eos-5d-mark-iv-lens-aberration-correctiona-close-up-look-part-1

Can you quote that part where it says what you think it says?
I don't see anything there about modifying the raw files.

> Heiko
Roman.

> --
> -- Number Crunch Blog @ https://www.numbercrunch.de
> --  Cluster Computing @ http://www.clustercomputing.de
> --   Professional @ https://www.mpi-hd.mpg.de/personalhomes/bauke
> --  Social Networking @ https://www.researchgate.net/profile/Heiko_Bauke
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Nikon users: please read, one specific raw sample wanted.

[Roman Lebedev]

Hi everyone.

This mostly concerns all the Nikon users, please read
https://discuss.pixls.us/t/nikon-a-specific-raw-sample-wanted/5483

Roman.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Anyone with Canon EOS 5DS R ? Samples wanted

[Roman Lebedev]

Hi.

As you may or may not know, we have this site RPU[0],
used for raw sample collection for camera support
https://pixls.us/blog/2017/09/keep-the-raws-coming/

While we do already have a samples for that camera,
i would very much like to get those samples replaced.

What samples are wanted specifically? There are three shots,
with different modes - RAW, mRAW and sRAW. The camera
should be stable (tripod), the scene should be as static
as possible. Ideally it should be a landscape.
Also, do read the general sample requirements on [0]

So in case someone reading here owns that camera,
*please* consider helping :)

[0] https://raw.pixls.us/

Roman.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Olympus lens name mismatch

[Roman Lebedev]

On Fri, Oct 13, 2017 at 1:47 AM, Felipe Contreras Salinas
 wrote:
> The list of lenses of the Lens Correction Module lists the "Olympus M.Zuiko
> Digital ED 60mm f/2.8 Macro" as "Olympus M.Zuiko Digital 60mm f/2.8 Macro"
> (without the ED). This results in that you must select the lens manually,
> because DT says that the lens is not found.
>
> If I understand correctly, DT uses the Lensfun database for lens correction,
> and there the lens is listed with the "ED", so why there is a difference?
Because that is what lensfun says: http://lensfun.sourceforge.net/lenslist/

> Should I report the bug?
To lensfun - yes.
*Maybe* try https://github.com/lensfun/lensfun/issues

> Regards,
> Felipe Contreras
Roman.

> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Fixing the scroll-bar issue

[Roman Lebedev]

On Wed, Oct 11, 2017 at 8:04 PM, Jørn Villesen Christensen
 wrote:
> Hi there,
Hi.

> I have been using Darktable from time to time and think I will be using it
> more in the future. I have a few ideas of what modules I would like to see
> in Darktable and I thought I might throw in a few hours myself.
>
> Short about me: I have been working 7 years now as a software developer and
> architect in a Windows oriented environment. Mostly I have been working with
> Delphi, C#, and C++. In my private life I have been running Linux for ~15
> years and done some C++ programming - but without GUI.

> In order to get started and to do something useful, I thought I would look
> at a bug that I also find annoying. It is described in these two bug
> reports:
>   https://redmine.darktable.org/issues/10947
>   https://redmine.darktable.org/issues/10711
You should have pointed to https://redmine.darktable.org/issues/9439

> My idea was basically to move the scrollbar from the outer position (where
> it is currently) to just next to the film roll. See attached photo.
Which scrollbar? There is a scrollbar for the sidepanels.
There is no scrollbar for the lighttable view itself.

> Questions:
>  a) Are there already other people working on solving these bugs?
>  b) Does my proposed solution seem like a good idea?
>  c) Would you have any pointers to me on how to get started (which files I
> should look into or other tips on how *you* would go about solving this).
>
> BR
> Jørn Christensen
Roman.

> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] possible data loss scenario

[Roman Lebedev]

On Tue, Oct 10, 2017 at 8:28 PM, Alexander Rabtchevich
<alexander.v.rabtchev...@gmx.net> wrote:
> Yes, I'm pretty sure :)
>
> When cursor reaches another control somewhere within the main window, the
> edit window looses focus. It should be some control (slider, another edit
> window etc), not a label.

> I have standard Mate from 18.2 Mint and proprietary AMD GPUpro video driver.
(Yes, but that does not answer the question.
I have no clue what mint does by default. Is it X or not?)

> With respect,
> Alexander Rabtchevich
>
>
>
>
>
> Roman Lebedev wrote:
>>
>> The item 3 is the problematic one. Why does the edit control loose focus?
>> That sounds like a bug. It is *not* intended behavior.
>> Is this normal X or wayland/mir/etc?
>> Are you *sure* you don't accidentally mouseclick right after 3. and before
>> 4. ?
>>
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] possible data loss scenario

[Roman Lebedev]

On Tue, Oct 10, 2017 at 8:11 PM, Alexander Rabtchevich
 wrote:
> Hello
>
> And the scenario is still working.
> 1. Select an image in the lighttable mode.
> 2. Click into the edit window Max size in the export dialog.
> 3. Move mouse just slightly outside the edit window. It loses focus
> immediately.
> 4. Type the digit you want. It is recognized as rating for the image being
> selected.

> The item 3 is the problematic one. Why does the edit control loose focus?
That sounds like a bug. It is *not* intended behavior.
Is this normal X or wayland/mir/etc?
Are you *sure* you don't accidentally mouseclick right after 3. and before 4. ?

> One haven't clicked outside the control. A mouse is not guaranteed to keep
> its exact position just after it has been released - and it _is_ released to
> type digits on a keyboard.
>
> With respect,
> Alexander Rabtchevich
Roman.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev]

[Roman Lebedev]

On Tue, Oct 10, 2017 at 7:52 PM, Vlad Kuzba  wrote:
> I've got darktable cloned from GIT on my HDD. Today I did
>
> git pull
>
> and then
>
> ./build.sh
Start with $ rm -rf build/
Does it still happen then?

> and I got this error
>
> [ 21%] Building C object
> src/CMakeFiles/lib_darktable.dir/develop/masks/masks.c.o
> [ 21%] Building C object
> src/CMakeFiles/lib_darktable.dir/common/imageio_j2k.c.o
> [ 21%] Building C object src/CMakeFiles/lib_darktable.dir/lua/cairo.c.o
> [ 21%] Building C object src/CMakeFiles/lib_darktable.dir/lua/call.c.o
> /home/vlad/git/darktable/src/common/imageio_j2k.c:32:10: fatal error:
> openjpeg.h: Adresář nebo soubor neexistuje
>  #include 
>   ^~~~
> compilation terminated.
> make[2]: *** [src/CMakeFiles/lib_darktable.dir/build.make:2477:
> src/CMakeFiles/lib_darktable.dir/common/imageio_j2k.c.o] Chyba 1
> make[2]: *** Čeká se na nedokončené úlohy…
> make[1]: *** [CMakeFiles/Makefile2:1437:
> src/CMakeFiles/lib_darktable.dir/all] Chyba 2
> make: *** [Makefile:152: all] Chyba 2
>  ~/git/darktable  ⑂ master +  $
>
>
> What can I do to fix it? I'm on Arch Linux (4.13.4-1-ARCH). When I last
> built DT after "git pull" about 3 weeks ago everything went OK.
>
> Thanks for a reply.
> Vlad
Roman

> Vladimír Kuzba
> www.kuzbici.eu
> 4KvonRoudne
>
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: Re: Re: [darktable-dev] possible data loss scenario

[Roman Lebedev]

On Mon, Oct 9, 2017 at 2:53 PM, Alexander Rabtchevich
<alexander.v.rabtchev...@gmx.net> wrote:
> Pull from yesterday.
Sounds scary.
Can you please show the output of  $ cat darktable/build/src/version_gen.c
?

> With respect,
> Alexander Rabtchevich
>
> Gesendet: Montag, 09. Oktober 2017 um 13:51 Uhr
> Von: "Roman Lebedev" <lebedev...@gmail.com>
> An: "Alexander Rabtchevich" <alexander.v.rabtchev...@gmx.net>
> Cc: darktable <darktable-dev@lists.darktable.org>
> Betreff: Re: Re: [darktable-dev] possible data loss scenario
> On Mon, Oct 9, 2017 at 1:49 PM, Alexander Rabtchevich
> <alexander.v.rabtchev...@gmx.net> wrote:
>> git master
> Uhm, that is confusing. Which commit, specifically?
>
> I have expected that it was fixed by
> 5f87ee20f6589cb8ff995fd4dcce4506471dd5ec,
> which was first in 2.2.2
>
>> With respect,
>> Alexander Rabtchevich
> Roman.
>
>> Gesendet: Montag, 09. Oktober 2017 um 13:42 Uhr
>> Von: "Roman Lebedev" <lebedev...@gmail.com>
>> An: "Alexander Rabtchevich" <alexander.v.rabtchev...@gmx.net>
>> Cc: darktable <darktable-dev@lists.darktable.org>
>> Betreff: Re: [darktable-dev] possible data loss scenario
>> On Mon, Oct 9, 2017 at 9:50 AM, Alexander Rabtchevich
>> <alexander.v.rabtchev...@gmx.net> wrote:
>>> Hello
>>>
>>> Yesterday I almost lost a three-years work. I selected 4-stars images
>>> since
>>> 2015 in lighttable and started to type image resolution in export
>>> settings.
>>> Cursor shifted a little from the control window due to mouse movement and
>>> dt
>>> recognized typed digit as a rating number. For my luck it was zero, not
>>> 1,
>>> so dt assigned 0 stars to the images and later I found them all. If the
>>> mouse had shifted when I had been typing 1, I would not be able to
>>> recognize
>>> my selected works from 3 years anymore.
>>> That had happened not for the first time, but the last one could be the
>>> most
>>> critical for me.
>>>
>>> Is it possible to hook keybord actions for the images in the lighttable
>>> mode
>>> only when the cursor is within the lighttable area?
>> Which dt version?
>>
>>> With respect,
>>> Alexander Rabtchevich
>> Roman.
>>
>>>
>>>
>>> ___
>>> darktable developer mailing list to unsubscribe send a mail to
>>> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: Re: [darktable-dev] possible data loss scenario

[Roman Lebedev]

On Mon, Oct 9, 2017 at 1:49 PM, Alexander Rabtchevich
<alexander.v.rabtchev...@gmx.net> wrote:
> git master
Uhm, that is confusing. Which commit, specifically?

I have expected that it was fixed by 5f87ee20f6589cb8ff995fd4dcce4506471dd5ec,
which was first in 2.2.2

> With respect,
> Alexander Rabtchevich
Roman.

> Gesendet: Montag, 09. Oktober 2017 um 13:42 Uhr
> Von: "Roman Lebedev" <lebedev...@gmail.com>
> An: "Alexander Rabtchevich" <alexander.v.rabtchev...@gmx.net>
> Cc: darktable <darktable-dev@lists.darktable.org>
> Betreff: Re: [darktable-dev] possible data loss scenario
> On Mon, Oct 9, 2017 at 9:50 AM, Alexander Rabtchevich
> <alexander.v.rabtchev...@gmx.net> wrote:
>> Hello
>>
>> Yesterday I almost lost a three-years work. I selected 4-stars images
>> since
>> 2015 in lighttable and started to type image resolution in export
>> settings.
>> Cursor shifted a little from the control window due to mouse movement and
>> dt
>> recognized typed digit as a rating number. For my luck it was zero, not 1,
>> so dt assigned 0 stars to the images and later I found them all. If the
>> mouse had shifted when I had been typing 1, I would not be able to
>> recognize
>> my selected works from 3 years anymore.
>> That had happened not for the first time, but the last one could be the
>> most
>> critical for me.
>>
>> Is it possible to hook keybord actions for the images in the lighttable
>> mode
>> only when the cursor is within the lighttable area?
> Which dt version?
>
>> With respect,
>> Alexander Rabtchevich
> Roman.
>
>>
>> ___
>> darktable developer mailing list to unsubscribe send a mail to
>> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] possible data loss scenario

[Roman Lebedev]

On Mon, Oct 9, 2017 at 9:50 AM, Alexander Rabtchevich
 wrote:
> Hello
>
> Yesterday I almost lost a three-years work. I selected 4-stars images since
> 2015 in lighttable and started to type image resolution in export settings.
> Cursor shifted a little from the control window due to mouse movement and dt
> recognized typed digit as a rating number. For my luck it was zero, not 1,
> so dt assigned 0 stars to the images and later I found them all. If the
> mouse had shifted when I had been typing 1, I would not be able to recognize
> my selected works from 3 years anymore.
> That had happened not for the first time, but the last one could be the most
> critical for me.
>
> Is it possible to hook keybord actions for the images in the lighttable mode
> only when the cursor is within the lighttable area?
Which dt version?

> With respect,
> Alexander Rabtchevich
Roman.

> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Error in compiled libexr.so

[Roman Lebedev]

On Sun, Oct 8, 2017 at 9:25 PM, Jonathan Richards
 wrote:
> Hi
> I built darktable from the git head on 1 Oct, and everything seemed to
> go smoothly; I have been working with JPG, TIFF and Panasonic RW2 files
> successfully.  However, when I start darktable from the command line, I
> get a message about an error in libexr.so:
>
> jonathan@Odin:~$ darktable &
> [1] 12137
> jonathan@Odin:~$ [imageio_load_module] failed to open format `exr':
> /opt/darktable/lib/darktable/plugins/imageio/format/libexr.so: undefined
> symbol:
> _ZNK7Imf_2_014TypedAttributeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIc12writeValueToERNS_7OStreamEi
There is some kind of mismatch in openexr versions.
Try purging /opt/darktable and the build dir (!!!), and build from scratch.
Does it still happen then?

> Maybe I'm missing some header files?  Please let me know what
> information I need to supply.  Grateful for any help; as I say it's not
> actually hindering my use of darktable.
>
> Thanks,
> Jonathan
Roman.

> Platform info:
> jonathan@Odin:~$ uname -a
> Linux Odin 4.10.0-35-generic #39~16.04.1-Ubuntu SMP Wed Sep 13 09:02:42
> UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
>
> KDE Neon User LTS Edition 5.8
>
> jonathan@Odin:~$ file
> /opt/darktable/lib/darktable/plugins/imageio/format/libexr.so
> /opt/darktable/lib/darktable/plugins/imageio/format/libexr.so: ELF
> 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked,
> BuildID[sha1]=c92c020e24600e0d4b7656bb9f612b70db8dfb6a, not stripped
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Git-compiling error

[Roman Lebedev]

On Sat, Sep 30, 2017 at 7:47 PM, João Horta <jho...@gmail.com> wrote:
> yes i deleted the build folder and give me the same error again.
Don't reply off-list.
Should be fixed now..

> I'm on Ubuntu 16.04 Gnome
>
> On Manjaro KDE everthing was ok
>
> best regards
> ---
> kitgard
Roman.

> 2017-09-30 15:09 GMT+01:00 Roman Lebedev <lebedev...@gmail.com>:
>>
>> On Sat, Sep 30, 2017 at 4:41 PM, João Horta <jho...@gmail.com> wrote:
>> > [ 80%] Building C object
>> > src/iop/CMakeFiles/colortransfer.dir/introspection_colortransfer.c.o
>> > In file included from
>> >
>> > /home/jmhorta/darktable/build/src/iop/introspection_colortransfer.c:33:0:
>> > /home/jmhorta/darktable/src/iop/colortransfer.c:181:1: warning: ISO C90
>> > forbids variable length array ‘mi’ [-Wvla]
>> >  static void get_cluster_mapping(const int n, float mi[n][2], float
>> > mo[n][2], in
>> >  ^
>> > /home/jmhorta/darktable/src/iop/colortransfer.c:181:1: warning: ISO C90
>> > forbids variable length array ‘mo’ [-Wvla]
>> > /home/jmhorta/darktable/src/iop/colortransfer.c:181:1: warning: ISO C90
>> > forbids variable length array ‘mapio’ [-Wvla]
>> > /home/jmhorta/darktable/src/iop/colortransfer.c:201:1: warning: ISO C90
>> > forbids variable length array ‘mean’ [-Wvla]
>> >  static void get_clusters(const float *col, const int n, float
>> > mean[n][2],
>> > float
>> >  ^
>> > /home/jmhorta/darktable/src/iop/colortransfer.c:220:1: warning: ISO C90
>> > forbids variable length array ‘mean’ [-Wvla]
>> >  static int get_cluster(const float *col, const int n, float mean[n][2])
>> >  ^
>> > /home/jmhorta/darktable/src/iop/colortransfer.c:237:1: warning: ISO C90
>> > forbids variable length array ‘mean_out’ [-Wvla]
>> >  static void kmeans(const float *col, const dt_iop_roi_t *const roi,
>> > const
>> > int n
>> >  ^
>> > /home/jmhorta/darktable/src/iop/colortransfer.c:238:20: warning: ISO C90
>> > forbids variable length array ‘var_out’ [-Wvla]
>> > float var_out[n][2])
>> > ^
>> > cc1: error: unrecognized command line option ‘-Wno-format-truncation’
>> > [-Werror]
>> > cc1: all warnings being treated as errors
>> > src/iop/CMakeFiles/colortransfer.dir/build.make:67: recipe for target
>> > 'src/iop/CMakeFiles/colortransfer.dir/introspection_colortransfer.c.o'
>> > failed
>> > make[2]: ***
>> > [src/iop/CMakeFiles/colortransfer.dir/introspection_colortransfer.c.o]
>> > Error
>> > 1
>> > CMakeFiles/Makefile2:5884: recipe for target
>> > 'src/iop/CMakeFiles/colortransfer.dir/all' failed
>> > make[1]: *** [src/iop/CMakeFiles/colortransfer.dir/all] Error 2
>> > Makefile:149: recipe for target 'all' failed
>> > make: *** [all] Error 2
>> Start by purging the build dir.
>> Does it still happen then?
>>
>> Roman.
>> >
>> > ___
>> > darktable developer mailing list to unsubscribe send a mail to
>> > darktable-dev+unsubscr...@lists.darktable.org
>
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Git-compiling error

[Roman Lebedev]

On Sat, Sep 30, 2017 at 4:41 PM, João Horta  wrote:
> [ 80%] Building C object
> src/iop/CMakeFiles/colortransfer.dir/introspection_colortransfer.c.o
> In file included from
> /home/jmhorta/darktable/build/src/iop/introspection_colortransfer.c:33:0:
> /home/jmhorta/darktable/src/iop/colortransfer.c:181:1: warning: ISO C90
> forbids variable length array ‘mi’ [-Wvla]
>  static void get_cluster_mapping(const int n, float mi[n][2], float
> mo[n][2], in
>  ^
> /home/jmhorta/darktable/src/iop/colortransfer.c:181:1: warning: ISO C90
> forbids variable length array ‘mo’ [-Wvla]
> /home/jmhorta/darktable/src/iop/colortransfer.c:181:1: warning: ISO C90
> forbids variable length array ‘mapio’ [-Wvla]
> /home/jmhorta/darktable/src/iop/colortransfer.c:201:1: warning: ISO C90
> forbids variable length array ‘mean’ [-Wvla]
>  static void get_clusters(const float *col, const int n, float mean[n][2],
> float
>  ^
> /home/jmhorta/darktable/src/iop/colortransfer.c:220:1: warning: ISO C90
> forbids variable length array ‘mean’ [-Wvla]
>  static int get_cluster(const float *col, const int n, float mean[n][2])
>  ^
> /home/jmhorta/darktable/src/iop/colortransfer.c:237:1: warning: ISO C90
> forbids variable length array ‘mean_out’ [-Wvla]
>  static void kmeans(const float *col, const dt_iop_roi_t *const roi, const
> int n
>  ^
> /home/jmhorta/darktable/src/iop/colortransfer.c:238:20: warning: ISO C90
> forbids variable length array ‘var_out’ [-Wvla]
> float var_out[n][2])
> ^
> cc1: error: unrecognized command line option ‘-Wno-format-truncation’
> [-Werror]
> cc1: all warnings being treated as errors
> src/iop/CMakeFiles/colortransfer.dir/build.make:67: recipe for target
> 'src/iop/CMakeFiles/colortransfer.dir/introspection_colortransfer.c.o'
> failed
> make[2]: ***
> [src/iop/CMakeFiles/colortransfer.dir/introspection_colortransfer.c.o] Error
> 1
> CMakeFiles/Makefile2:5884: recipe for target
> 'src/iop/CMakeFiles/colortransfer.dir/all' failed
> make[1]: *** [src/iop/CMakeFiles/colortransfer.dir/all] Error 2
> Makefile:149: recipe for target 'all' failed
> make: *** [all] Error 2
Start by purging the build dir.
Does it still happen then?

Roman.
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] compiler warnings regarding variable length arrays

[Roman Lebedev]

On Sun, Sep 24, 2017 at 11:39 AM, johannes hanika  wrote:
> hi,
Hi.

> i disagree. i really like variable length arrays

> and std::vectors dynamically allocate memory on the heap
https://llvm.org/docs/ProgrammersManual.html#dss-smallvector

> with standard implementations locking a global mutex
> on the way causing slowdown for multithreaded cases.
That *might* be not so true today
https://sourceware.org/glibc/wiki/MallocInternals#Arenas_and_Heaps

> just incrementing the stack pointer is a simple thing, it's
> thread local and light weight. and memory resources will run out
> whether i do a complicated or a simple memory allocation scheme (with
> linux overcommitting, you can't even test malloc == 0, so i don't see
> how heap allocation is any safer).  also, variable sized arrays mean
> it's not known compile time, but once you enter the function you know
> exactly how large you need it (no need for dynamically growing
> complicated structures).

To add to that, it's somewhat even worse than with overcommitting,
if the VLA stack allocation fails, i believe it results in a SIGSEGV..

Though, less stack usage, less pages the kernel has to swap out,
mark dirty, etc

Also, i guess, having some default stack size can be compared to
each application [thread] doing malloc(512Mb), and then maybe
using it or maybe not. Assuming no overcommit, that already
puts some limits on the number of simultaneously running apps.

> i understand however that some libc implementations have issues with
> that and that it makes people feel uncomfortable about predicting
> whether the code is correct or not. so we do the inconvenient grown-up
> thing and warn about it in dt.
>
> cheers,
>  jo
Roman.

> On Sat, Sep 23, 2017 at 8:07 AM, Heiko Bauke  wrote:
>> Hi,
>>
>> Am 22.09.2017 um 15:35 schrieb Tobias Ellinghaus:
>>>
>>> No, you are missing the point of those pragmas: darktable from git always
>>> builds with "-Werror", thus the "-Wvla" switch actually throws an hard
>>> error
>>> when using VLAs. With the pragma we are relaxing that back to a warning
>>> again
>>> to be able to use VLAs in some places.
>>
>>
>> I understand, makes sense.  After reading the article about the save usage
>> of variable length arrays mentioned in my other mail, I thing variable
>> length arrays are actually not as great as I thought.  What one really wants
>> is probably a std::vector.  But this has not yet been invented in C.
>>
>>
>>
>> Heiko
>>
>> --
>> -- Number Crunch Blog @ https://www.numbercrunch.de
>> --  Cluster Computing @ http://www.clustercomputing.de
>> --   Professional @ https://www.mpi-hd.mpg.de/personalhomes/bauke
>> --  Social Networking @ https://www.researchgate.net/profile/Heiko_Bauke
>> ___
>> darktable developer mailing list
>> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>>
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] german documentation

[Roman Lebedev]

On Thu, Sep 7, 2017 at 11:18 PM, Matthias Bodenbinder
 wrote:
> Hello,
Hi.

> I just want to bring to your attention that there is a new translation engine 
> available which translates much, much better than anything google or 
> Microsoft are doing: https://www.deepl.com/translator
>
> May be it is a good idea to use this engine to translate the englisch 
> documentation to german, french, spanish, italian, netherlands.
All translations, usermanual translations are hand-made.
Any auto-translation will likely always(well...) be bad, and
unsuitable for inclusion.

> A few examples.
>
> #1)
> english:
>
> The basic element for organizing images in darktable is called a film 
> roll – a kind of virtual folder. Whenever you import images from disk, the 
> images are organized in a film roll whose name is derived from the name of 
> the disk folder. Re-importing a disk folder will add any new images to the 
> existing film roll; images already present in the film roll are not touched.
>
> german translation:
>
> Das Grundelement für die Organisation von Bildern in Darktable heißt 
> Filmrolle - eine Art virtueller Ordner. Immer wenn Sie Bilder von der 
> Festplatte importieren, werden die Bilder in einer Filmrolle organisiert, 
> deren Name sich vom Namen des Laufwerksordners ableitet. Beim Neuimport eines 
> Disk-Ordners werden neue Bilder zum bestehenden Filmlauf hinzugefügt; bereits 
> im Filmlauf befindliche Bilder bleiben unberührt.
>
> #2)
> english:
> First off, select what aspect ratio you want and size the crop 
> boundaries by dragging border and corner handles. Use the button right of the 
> aspect box, to swap between portrait and landscape mode. You can move around 
> the crop rectangle by holding down left mouse button and move around. When 
> you are done and want to execute the crop, just give focus to another module 
> or double-click into the image base. You can at any time change your crop 
> area by just revisiting this module.
>
> german translation:
>
> Wählen Sie zunächst das gewünschte Seitenverhältnis aus und ziehen Sie die 
> Rahmen- und Eckpunkte mit der Maus in die gewünschte Größe. Benutzen Sie die 
> Schaltfläche rechts neben dem Seitenfenster, um zwischen Hoch- und Querformat 
> umzuschalten. Sie können sich um das Rechteck herum bewegen, indem Sie die 
> linke Maustaste gedrückt halten und sich bewegen. Wenn Sie fertig sind und 
> den Zuschlag ausführen möchten, geben Sie einfach einem anderen Modul den 
> Fokus oder doppelklicken Sie in die Bilddatenbank. Sie können jederzeit Ihren 
> Schnittbereich ändern, indem Sie dieses Modul erneut aufrufen.
>
>
> I find the results pretty good!
>
> Matthias
Roman.

> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Compiling problem with rawspeed submodule

[Roman Lebedev]

On Thu, Aug 24, 2017 at 7:17 PM, Ingo Liebhardt  wrote:
> Hi all,
Hi.

> got a problem building, not only my fork, but also the upstream darktable 
> master.
> Cloned a clean one to be sure, did the
> git submodule update --init —recursive

> and git submodule update --recursive —remote
Wrong. drop that '--remote' option.

> and I get the results as in the attached logs.

Please try that again, and post the normal cmake output.
Those logs are strangely useless.

> Any help more than welcome.
>
> Cheers,
>
> ingo
Roman.

> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Re: compiling error

[Roman Lebedev]

On Thu, Aug 17, 2017 at 4:08 PM, Richard Hobday <rlhob...@gmx.co.uk> wrote:
> Roman
>
> Just wondering what this means - apart from the obvious!
>
>> You have called ADD_LIBRARY for library rawspeed without any source files.
>> This typically indicates a problem with your CMakeLists.txt file
>
> Program compiles and runs without issue now as far as I can see, so clearly
> NOT critical.
Just ignore it

I'm first calling ADD_LIBRARY(), and then using target_sources(),
which is cleaner, more modern way.

I'm not sure if there is a way to silence the warning.

> Cheers,
>
> Richard
Roman.

> On 15/08/17 14:43, Roman Lebedev wrote:
>>
>> This should be fixed in darktable git master.
>>
>> On Thu, Aug 10, 2017 at 2:48 PM, Alain Soucy <soucy...@gmail.com> wrote:
>>>
>>> Hi,
>>>
>>> I have the same bug with Gentoo-GCC-5.4.0:
>>>
>>> Gentoo's Bugzilla – Bug 627406
>>>
>>>
>>> Le 2017-08-10 à 04:17, Richard Hobday a écrit :
>>>>
>>>> Alexander, thanks for pushing that bug report.
>>>>
>>>> I have bumped the count by 1!
>>>>
>>>>
>>>> R.
>>>>
>>>>
>>>> On 08/08/17 04:55, Alexander Rabtchevich wrote:
>>>>>
>>>>> Hello, Roman
>>>>>
>>>>> Duplication of the bug is done in Linux Mint bugtracker.
>>>>>
>>>>> https://bugs.launchpad.net/linuxmint/+bug/1709234
>>>>>
>>>>> With respect,
>>>>> Alexander Rabtchevich
>>>>>
>>>>> Roman Lebedev wrote:
>>>>>>
>>>>>> Hi.
>>>>>>
>>>>>> Everyone:
>>>>>>
>>>>>> On Sun, Aug 6, 2017 at 11:34 PM, João Horta <jho...@gmail.com> wrote:
>>>>>>>
>>>>>>> -- The CXX compiler identification is GNU 5.4.0
>>>>>>> -- The C compiler identification is GNU 5.4.0
>>>>>>> Hello
>>>>>>> I have the same problem and the same compiler version from Mint 18.2.
>>>>>>> gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
>>>>>>
>>>>>> Please duplicate this issue into your's distribution's bugtracker:
>>>>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871250
>>>>>> And pass me the bug number.
>>>>>> After i have a few bugid's, i'll add a temporary workaround.
>>>>>>
>>>>>> Roman.
>>>>>
>>>>>
>>>>> ___
>>>>>
>>>>> darktable developer mailing list
>>>>> to unsubscribe send a mail to
>>>>> darktable-dev+unsubscr...@lists.darktable.org
>>>>>
>>>
>>> ___
>>> darktable developer mailing list
>>> to unsubscribe send a mail to
>>> darktable-dev+unsubscr...@lists.darktable.org
>>>
>>
>> ___
>> darktable developer mailing list
>> to unsubscribe send a mail to
>> darktable-dev+unsubscr...@lists.darktable.org
>>
>
> --
> http://lukecarville.jalbum.net
> https://facebook.com/rlc.hobday
>
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] camera color calibration images for Sony ILCE6300 and Canon S100

[Roman Lebedev]

On Tue, Aug 22, 2017 at 12:49 PM, Christopher Engelhard <c...@lcts.de> wrote:
> On 08/21/2017 02:59 PM, Roman Lebedev wrote:
>> We should just remove that column. We do not merge new custom matrixes,
>> because we do not have any means to validate them, and no one to do that.
>
> Just to be clear, I'm not talking about custom matrices, but raw image
> files to derive a matrix from. Still, one can't really tell about
> lighting quality and the state of the target etc. from the images, so I
> see how that would be problematic.
Yes, and that is all the same to us...
Maybe someday someone will volunteer and will handling doing that.

(rawtherapee does create some kind of custom matrixes IIRC, so maybe
check whether they already have custom matrixes for those cameras, etc)


> Thanks anyway,
> Christopher
Roman.

> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Sony DSC-RX100M4 Noise Profile

[Roman Lebedev]

On Tue, Aug 22, 2017 at 9:14 AM, Sean Cronin  wrote:
> Hi all,
Hi.

> I've created a noise profile for the Sony DSC-RX100M4:
> https://drive.google.com/open?id=0B36pCcDvKgCHSXFWTXF4UXpOaXM
Probably best to open a new issue, so this does not get lost.

> Based on my informal testing, it seems to work well. Any feedback on it
> would be appreciated.
>
> -Sean
Roman.

> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] camera color calibration images for Sony ILCE6300 and Canon S100

[Roman Lebedev]

On Mon, Aug 21, 2017 at 3:52 PM, Christopher Engelhard  wrote:
> Hi,
> the list of supported cameras shows Canon PowerShot S100 and Sony a6300
> (ILCE-6300) as missing a custom matrix [1].
We should just remove that column. We do not merge new custom matrixes,
because we do not have any means to validate them, and no one to do that.

> I have made raw images of a Wolf Faust C1 IT8 color target [2]. Exposure
> matches correct white level to within 0.15EV.
>
> Is there somewhere I can upload them (~33MB) or should I just send a
> link to this list?
>
> Cheers,
> Christopher
Roman.

> [1] https://www.darktable.org/resources/camera-support/
> [2] http://www.targets.coloraid.de/
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Sony A850 and A200 raws cause darktable hang

[Roman Lebedev]

Please reply to the list.

On Sun, Aug 20, 2017 at 7:45 AM, Bruce Williams <stu...@audio2u.com> wrote:
> I'm running Linux Mint, and shoot with an a850.
> Not having any issues here.
> I realise that doesn't help you much, but just wanted to stress that I don't
> think it's a dt issue.
Yes, it is probably a dt issue, if you look at the backtraces. They are crashes.
And a reproducer is needed.

>
> Cheers,
> Bruce Williams
Roman.

> --
> Mobile:  +61 41 250 6349
>
> brucewilliamsphotography.com
> shuttersincpodcast.com
> sinelanguagepodcast.com
> audio2u.com
>
> e-mail | Twitter | LinkedIn | Facebook
> ------
>
>
>
> On Sat, Aug 19, 2017 at 10:17 PM, Roman Lebedev <lebedev...@gmail.com>
> wrote:
>>
>> On Sat, Aug 19, 2017 at 11:40 AM, Alexander Rabtchevich
>> <alexander.v.rabtchev...@gmx.net> wrote:
>> > Hello
>> Hi.
>>
>> > It seems some of the latest git commits broke support for Sony A850 and
>> > A200
>> > RAWs. A99 is threated without problems.
>> As far as i can see, for all three cameras, we still don't have CC0 sample
>> on https://raw.pixls.us/ And there is no "sony A99" sample at all, only
>> for A99V
>>
>> >
>> > --
>>
>> Did not look at the reproduction yet, but it sounds strange.
>> There wasn't anything that would do it...
>>
>> > With respect,
>> > Alexander Rabtchevich
>> Roman.
>>
>> >
>> > ___
>> > darktable developer mailing list
>> > to unsubscribe send a mail to
>> > darktable-dev+unsubscr...@lists.darktable.org
>> >
>>
>> ___
>> darktable developer mailing list
>> to unsubscribe send a mail to
>> darktable-dev+unsubscr...@lists.darktable.org
>>
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Sony A850 and A200 raws cause darktable hang

[Roman Lebedev]

On Sat, Aug 19, 2017 at 11:40 AM, Alexander Rabtchevich
 wrote:
> Hello
Hi.

> It seems some of the latest git commits broke support for Sony A850 and A200
> RAWs. A99 is threated without problems.
As far as i can see, for all three cameras, we still don't have CC0 sample
on https://raw.pixls.us/ And there is no "sony A99" sample at all, only for A99V

>
> --

Did not look at the reproduction yet, but it sounds strange.
There wasn't anything that would do it...

> With respect,
> Alexander Rabtchevich
Roman.

> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Re: compiling error

[Roman Lebedev]

This should be fixed in darktable git master.

On Thu, Aug 10, 2017 at 2:48 PM, Alain Soucy <soucy...@gmail.com> wrote:
> Hi,
>
> I have the same bug with Gentoo-GCC-5.4.0:
>
> Gentoo's Bugzilla – Bug 627406
>
>
> Le 2017-08-10 à 04:17, Richard Hobday a écrit :
>> Alexander, thanks for pushing that bug report.
>>
>> I have bumped the count by 1!
>>
>>
>> R.
>>
>>
>> On 08/08/17 04:55, Alexander Rabtchevich wrote:
>>> Hello, Roman
>>>
>>> Duplication of the bug is done in Linux Mint bugtracker.
>>>
>>> https://bugs.launchpad.net/linuxmint/+bug/1709234
>>>
>>> With respect,
>>> Alexander Rabtchevich
>>>
>>> Roman Lebedev wrote:
>>>> Hi.
>>>>
>>>> Everyone:
>>>>
>>>> On Sun, Aug 6, 2017 at 11:34 PM, João Horta <jho...@gmail.com> wrote:
>>>>> -- The CXX compiler identification is GNU 5.4.0
>>>>> -- The C compiler identification is GNU 5.4.0
>>>>> Hello
>>>>> I have the same problem and the same compiler version from Mint 18.2.
>>>>> gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
>>>> Please duplicate this issue into your's distribution's bugtracker:
>>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871250
>>>> And pass me the bug number.
>>>> After i have a few bugid's, i'll add a temporary workaround.
>>>>
>>>> Roman.
>>>
>>> ___
>>>
>>> darktable developer mailing list
>>> to unsubscribe send a mail to
>>> darktable-dev+unsubscr...@lists.darktable.org
>>>
>>
>
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] error running darktable.generating.cache

[Roman Lebedev]

On Sat, Aug 12, 2017 at 9:42 AM, M.Bungert  wrote:
> I'm using DT latest git version from Arch Linux AUR darktable-git.
> Today I rebuild the cache and got the attached error.
>
> Generating cache stopps alway at 14.91%.
>
> Is this a bug from git version?
This backtrace is useless.
Please install debug symbols at least for darktable, gtk, glib, cairo
and try again.

> Regards,
> Marcus
Roman.

> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Re: compiling error

[Roman Lebedev]

Hi.

Everyone:

On Sun, Aug 6, 2017 at 11:34 PM, João Horta  wrote:
> -- The CXX compiler identification is GNU 5.4.0
> -- The C compiler identification is GNU 5.4.0

> Hello
> I have the same problem and the same compiler version from Mint 18.2.
> gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609

Please duplicate this issue into your's distribution's bugtracker:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871250
And pass me the bug number.
After i have a few bugid's, i'll add a temporary workaround.

Roman.
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] lens correction / Fujifilm X-T2

[Roman Lebedev]

On Mon, Aug 7, 2017 at 9:19 AM, Marcus Bungert  wrote:
> I just got my new gear, moving from D600 to Fujifilm X-T2.
>
> I'm wondering that the X-T2 is not recognized by "lens correction" but the
> lense.
> The camera is listed as supported
> (http://www.darktable.org/resources/camera-support/)
>
> A manual selection is not possible, the camera is not listed in the menu.
>
> Is this a known issue or do I have to install something else to get support
> for lens correction?
>
> I use always the actual darktable-git version from Arch User Repository, but
> it is the same with official release 2.2.5
Lens support is lensfun's problem.
http://lensfun.sourceforge.net/lenslist/

> Regards,
> Marcus
>
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] compiling error

[Roman Lebedev]

Please don't reply off-list.

On Sun, Aug 6, 2017 at 10:28 PM, João Horta <jho...@gmail.com> wrote:
> How can i see the compiler version? I'm on Ubuntu Gnome 16.04.
> Just have this problem with last git version
remove build dir if you did not do that yet
re-run cmake, the compiler info should be in the first few lines.

> best regards
>
>
> 2017-08-06 20:24 GMT+01:00 Roman Lebedev <lebedev...@gmail.com>:
>>
>> On Sun, Aug 6, 2017 at 10:18 PM, João Horta <jho...@gmail.com> wrote:
>> > ...
>> >
>> > /home/jmhorta/darktable/src/external/rawspeed/src/librawspeed/decompressors/FujiDecompressor.cpp:488:41:
>> > error: ‘line_width’ is not captured
>> > ...
>> Which compiler is that?
>>
>> Roman,
>> >
>> > ___
>> > darktable developer mailing list to unsubscribe send a mail to
>> > darktable-dev+unsubscr...@lists.darktable.org
>
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] compiling error

[Roman Lebedev]

On Sun, Aug 6, 2017 at 10:18 PM, João Horta  wrote:
> ...
> /home/jmhorta/darktable/src/external/rawspeed/src/librawspeed/decompressors/FujiDecompressor.cpp:488:41:
>  error: ‘line_width’ is not captured
> ...
Which compiler is that?

Roman,
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Problem with some Leica DNG files

[Roman Lebedev]

On Tue, Aug 1, 2017 at 12:02 PM, Laurent Latxague <bert...@free.fr> wrote:

> Yes yes yes, it works ! Gott sei Dank ! (und vielen Dank Tobias !)
>
> Reloading files I as did before was not enough obviously. I had to remove
> them from the DT database, quit DT and then import the whole directory
> again.
>
Slightly less intrusive solution would be to remove just the cache,  rm -rf
~/.cache/darktable
And, also see  man darktable-generate-cache  it would help you pre-generate
thumbnails

Le 01/08/2017 à 10:25, Tobias Ellinghaus a écrit :
>
> Am Dienstag, 1. August 2017, 10:14:24 CEST schrieb Laurent Latxague:
>
> Hi,
>
> Yes, I remember this option in the pref pane, unfortunately whatever it
> is checked or not the problem remains... To be sure I quit DT and
> reloaded the files (to avoid the possible presence of a cached file) but
> there was no improvement.
>
> Try to remove it from dt and import again. The thumbs are cached on disk and
> probably not removed in your case.
>
>
> This is indeed annoying since in my workflow I like to use the Z key in
> the lightable from the thumbnails to quickly check if the picture is ok
> or not. Now I'm compelled to copy the jpeg files too from the camera and
> check their quality instead, as a temporary solution...
>
> Le 01/08/2017 à 00:16, Roman Lebedev a écrit :
>
> On Tue, Aug 1, 2017 at 1:04 AM, Laurent Latxague <bert...@free.fr
> <mailto:bert...@free.fr> <bert...@free.fr>> wrote:
> Regarding this particular issue :
>
> (2) All DNG pictures appear strongly pixellized (with ctrl-Z
> in the lightable) contrary to my CR2 or RAF files
>
> That only shows low-quality thumbnail, so it is kind-of expected.
>
>
> In the lightable, using Z or ctrl-Z of JPEG files straight from
> the camera is ok; on the corresponding DNG files it pixellizes.
> But meanwhile, if I work on the DNG file (even a little, for
> example by putting a bit more exposure in the darkroom), and then
> come back to the lightable, then Z or ctrl-Z magnifies the
> thumbnail correctly...
> I'm sorry to insist, but don't you think it's a bug regarding the
> way DT handles Leica DNG files ? Why these Leica DNG thumbnails
> would be expected (initially at least) to be of low quality and
> not the others (from Canon or Fuji) ?
> https://www.darktable.org/usermanual/ch08.html.php#gui_options
> I suspect "don't use embedded preview JPEG but half-size raw" is disabled?
> The thumbnail embedded in leica raw's, as you can see, is really tiny.
> You could enable that option, and then you will never see the embedded
> thumbnail.
>
> --
>
> Roman.
>
>
> --
>
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
>

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Problem with some Leica DNG files

[Roman Lebedev]

On Tue, Aug 1, 2017 at 1:04 AM, Laurent Latxague  wrote:

> Regarding this particular issue :
>
> (2) All DNG pictures appear strongly pixellized (with ctrl-Z in the
>> lightable) contrary to my CR2 or RAF files
>>
> That only shows low-quality thumbnail, so it is kind-of expected.
>
>
> In the lightable, using Z or ctrl-Z of JPEG files straight from the camera
> is ok; on the corresponding DNG files it pixellizes. But meanwhile, if I
> work on the DNG file (even a little, for example by putting a bit more
> exposure in the darkroom), and then come back to the lightable, then Z or
> ctrl-Z magnifies the thumbnail correctly...
> I'm sorry to insist, but don't you think it's a bug regarding the way DT
> handles Leica DNG files ? Why these Leica DNG thumbnails would be expected
> (initially at least) to be of low quality and not the others (from Canon or
> Fuji) ?
>
https://www.darktable.org/usermanual/ch08.html.php#gui_options
I suspect "don't use embedded preview JPEG but half-size raw" is disabled?
The thumbnail embedded in leica raw's, as you can see, is really tiny.
You could enable that option, and then you will never see the embedded
thumbnail.


> --
>
Roman.

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Problem with some Leica DNG files

[Roman Lebedev]

On Mon, Jul 31, 2017 at 6:46 PM, Laurent Latxague <bert...@free.fr> wrote:

> Ok I was able to log to redmine.darktable.org etc. but don't know what to
> do then and how to attach my file (26Mb)...
>
Not sure what you mean, the link i posted has field "Files" with max file
size of 48.8 MB

>
> Le 31/07/2017 à 17:07, Roman Lebedev a écrit :
>
> On Mon, Jul 31, 2017 at 5:59 PM, Laurent Latxague <bert...@free.fr> wrote:
>
>> I'm currently using DT 2.2.5, and the compressed DNG + the JPEG
>> associated files are directly copied from the SD card to the computer.
>>
>> I first imagined those files corrupted in one way or another, but
>> RawTherapee on the other hand is indeed able to open them...
>>
>  Aha, interesting, https://redmine.darktable.org/projects/
> darktable/issues/new + attach one of such images...
>
> What's the reason for the low quality thumbnails BTW ?
>>
> Well, they are thumbnails, *thumb* *nails*, very small, pretty fast :)
>
>
>> Le 31/07/2017 à 16:18, Roman Lebedev a écrit :
>>
>> On Mon, Jul 31, 2017 at 5:04 PM, Laurent Latxague <bert...@free.fr>
>> wrote:
>>
>>> Hello !
>>>
>> Hi.
>>
>>> I have never experienced any problems with my former cameras (Canon 5D
>>> II, III, Fuji X-Trans) in DT, but since I switched to Leica some things are
>>> going wrong...
>>>
>> Which dt version?
>>
>>> (1) Generally speaking, Leica support seems rather poor in DT, hence my
>>> first disappointment (I recently purchased a used M typ 240). No lens
>>> support for example for the lens correction module. BTW how can I
>>> contribute as a user to help in this way ? (I read the following page
>>> https://raw.pixls.us/ but there is already a M240 picture, so what ?)
>>>
>> Lens correction is lensfun problem, http://lensfun.source
>> forge.net/lenslist/ http://lensfun.sourceforge.net/calibration/
>>
>>> (2) All DNG pictures appear strongly pixellized (with ctrl-Z in the
>>> lightable) contrary to my CR2 or RAF files
>>>
>> That only shows low-quality thumbnail, so it is kind-of expected.
>>
>>> (3) A few DNG pictures (actually one picture for the moment) can't be
>>> loaded in the darkroom, a message says that the white balance cannot be
>>> read from the camera, and then DT freezes...
>>>
>>> (4) Some thumbnails (2 actually and always the same ones despite several
>>> imports of the original files) appear as skulls...
>>>
>> That is the same problem.
>> Are those DNG straight out of camera, or?
>>
>>> (5) Last, but not least the above 3 "faulty" files appear flawlessly...
>>> in RawTherapee ! Very irritating since I don't intend to move to RT...
>>>
>>> Any help or suggestion please ?
>>> TY in advance ! --
>>>
>> Roman.
>>
>>
>>> --
>>>
>>>
>>> ___
>>> darktable developer mailing list to unsubscribe send a mail to
>>> darktable-dev+unsubscr...@lists.darktable.org
>>>
>> Roman.
>
>
>
> --
>

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Problem with some Leica DNG files

[Roman Lebedev]

On Mon, Jul 31, 2017 at 5:59 PM, Laurent Latxague <bert...@free.fr> wrote:

> I'm currently using DT 2.2.5, and the compressed DNG + the JPEG associated
> files are directly copied from the SD card to the computer.
>
> I first imagined those files corrupted in one way or another, but
> RawTherapee on the other hand is indeed able to open them...
>
 Aha, interesting,
https://redmine.darktable.org/projects/darktable/issues/new + attach one of
such images...

What's the reason for the low quality thumbnails BTW ?
>
Well, they are thumbnails, *thumb* *nails*, very small, pretty fast :)


> Le 31/07/2017 à 16:18, Roman Lebedev a écrit :
>
> On Mon, Jul 31, 2017 at 5:04 PM, Laurent Latxague <bert...@free.fr> wrote:
>
>> Hello !
>>
> Hi.
>
>> I have never experienced any problems with my former cameras (Canon 5D
>> II, III, Fuji X-Trans) in DT, but since I switched to Leica some things are
>> going wrong...
>>
> Which dt version?
>
>> (1) Generally speaking, Leica support seems rather poor in DT, hence my
>> first disappointment (I recently purchased a used M typ 240). No lens
>> support for example for the lens correction module. BTW how can I
>> contribute as a user to help in this way ? (I read the following page
>> https://raw.pixls.us/ but there is already a M240 picture, so what ?)
>>
> Lens correction is lensfun problem, http://lensfun.
> sourceforge.net/lenslist/ http://lensfun.sourceforge.net/calibration/
>
>> (2) All DNG pictures appear strongly pixellized (with ctrl-Z in the
>> lightable) contrary to my CR2 or RAF files
>>
> That only shows low-quality thumbnail, so it is kind-of expected.
>
>> (3) A few DNG pictures (actually one picture for the moment) can't be
>> loaded in the darkroom, a message says that the white balance cannot be
>> read from the camera, and then DT freezes...
>>
>> (4) Some thumbnails (2 actually and always the same ones despite several
>> imports of the original files) appear as skulls...
>>
> That is the same problem.
> Are those DNG straight out of camera, or?
>
>> (5) Last, but not least the above 3 "faulty" files appear flawlessly...
>> in RawTherapee ! Very irritating since I don't intend to move to RT...
>>
>> Any help or suggestion please ?
>> TY in advance ! --
>>
> Roman.
>
>
>> --
>>
>>
>> ___
>> darktable developer mailing list to unsubscribe send a mail to
>> darktable-dev+unsubscr...@lists.darktable.org
>>
> Roman.

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Problem with some Leica DNG files

[Roman Lebedev]

On Mon, Jul 31, 2017 at 5:04 PM, Laurent Latxague  wrote:

> Hello !
>
Hi.

> I have never experienced any problems with my former cameras (Canon 5D II,
> III, Fuji X-Trans) in DT, but since I switched to Leica some things are
> going wrong...
>
Which dt version?

> (1) Generally speaking, Leica support seems rather poor in DT, hence my
> first disappointment (I recently purchased a used M typ 240). No lens
> support for example for the lens correction module. BTW how can I
> contribute as a user to help in this way ? (I read the following page
> https://raw.pixls.us/ but there is already a M240 picture, so what ?)
>
Lens correction is lensfun problem, http://lensfun.sourceforge.net/lenslist/
 http://lensfun.sourceforge.net/calibration/

> (2) All DNG pictures appear strongly pixellized (with ctrl-Z in the
> lightable) contrary to my CR2 or RAF files
>
That only shows low-quality thumbnail, so it is kind-of expected.

> (3) A few DNG pictures (actually one picture for the moment) can't be
> loaded in the darkroom, a message says that the white balance cannot be
> read from the camera, and then DT freezes...
>
> (4) Some thumbnails (2 actually and always the same ones despite several
> imports of the original files) appear as skulls...
>
That is the same problem.
Are those DNG straight out of camera, or?

> (5) Last, but not least the above 3 "faulty" files appear flawlessly... in
> RawTherapee ! Very irritating since I don't intend to move to RT...
>
> Any help or suggestion please ?
> TY in advance ! --
>
Roman.


> --
>
>
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
>

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] duplicate noise profile for Fuji X-E1 as Fuji X-Pro1

[Roman Lebedev]

On Mon, Jul 3, 2017 at 8:39 PM, Ulrich Pegelow
 wrote:
> Hi,
>
> according to several sources (e.g.:
> http://www.techradar.com/reviews/cameras-and-camcorders/cameras/digital-slrs-hybrids/fuji-x-e1-1094565/review/4)
> the X-Pro1 and the X-E1 share the same make of sensor. I'd like to make a
> copy of the existing noise profile of the X-E1 for the X-Pro1.
Adobe color matrix does indeed seem to be the same for these two cameras.
So for local use - by all means.

> Any reasonable objections?
So far we *tried* to avoid doing that.
So if at all possible, it would be better to re-profile.

> Ulrich
Roman.

> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

[Roman Lebedev]

On Wed, Jun 21, 2017 at 7:35 PM, Moritz Mœller (The Ritz)
<virtualr...@gmail.com> wrote:
> On June 20, 2017 18:34:27 Roman Lebedev <lebedev...@gmail.com> wrote:
>>
>> On Tue, Jun 20, 2017 at 5:55 PM, Moritz Moeller <virtualr...@gmail.com>
>> wrote:
>>>
>>> On 20.6.17 11:43 , Tobias Ellinghaus wrote:
>>> I'm using a local build with [...] Wolfgang Mader's
>>> modern monochrome modules since about 4 months and wouldn't want to miss
>>> either.
>>> https://github.com/wmader/darktable/tree/color2gray
>>
>> That was merged initially, currently resides as a preset in "color
>> look up table" module
>
>
> This module has a parameter. How can this work with a single look up
> table???
Dunno, i'm simply stating the current status:

commit cf98370e253590e3a6e5844433a0cfae8e3df126
Author: johannes hanika <hana...@gmail.com>
Date:   Sun Nov 20 08:15:20 2016 +1300

   monochrome: remove module. use clut+local contrast

   clut has the hk-mono preset, local contrast (optionally) uses the
   local laplacian filter.

diff --git a/src/iop/mm.c b/src/iop/mm.c
deleted file mode 100644
index 19293c644..0
--- a/src/iop/mm.c
+++ /dev/null


> .mm
Roman.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

[Roman Lebedev]

On Wed, Jun 21, 2017 at 12:17 PM, Tobias Ellinghaus  wrote:
> Am Mittwoch, 21. Juni 2017, 09:33:13 CEST schrieb Robert William Hutton:
>> On 21/06/17 04:47, Germano Massullo wrote:
>> > It would be also interesting to know if there will be changes in
>> > darktable dependencies, so that package maintainers can early start
>> > working on them
>>
>> I'll do some testing and create a new page on the wiki for 2.4 based on
>> the one for 2.2:
>>
>> https://redmine.darktable.org/projects/darktable/wiki/Building_darktable_22
>>
>> Does anyone know if there are any new deps?
>
> One thing that comes to mind is the switch from Lua 5.2 to 5.3. IIRC we also
> bumped the required CMake version, but I am not sure about that and would have
> to dig through the git log. I'll help assembling the changed deps eventually.
Lua 5.3
CMake 3.1
Required: GCC 4.8 / clang 3.3   Recommended: GCC 5.0 / clang 3.5
New dependency: zlib

>> Regards,
>>
>> Rob
>
> Tobias
Roman.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

[Roman Lebedev]

On Tue, Jun 20, 2017 at 5:55 PM, Moritz Moeller  wrote:
> On 20.6.17 11:43 , Tobias Ellinghaus wrote:
>>
>> In order to plan for that we need to know if anyone is currently working
>> on
>> something that should go into the release. We would also need some hands
>> on
>> deck to help review and polish pull requests.
>
>
> I'm using a local build with Heiko Bauke's haze removal and Wolfgang Mader's
> modern monochrome modules since about 4 months and wouldn't want to miss
> either.
>
> https://github.com/wmader/darktable/tree/color2gray
That was merged initially, currently resides as a preset in "color
look up table" module

> https://github.com/rabauke/darktable/tree/haze_removal
What Pascal said.

> Modern monochrome could use some more algorithms. Their parameters and
> naming should also be reviewed by some UX savvy developer.
> Someone should also check it doesn't clip.
> But it is already useful as-is.
>
> Cheers,
>
>
> .mm
Roman.

> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Can't compile last git pull source (may, 31. 2017)

[Roman Lebedev]

On Wed, May 31, 2017 at 11:13 AM, André Felipe Carvalho
 wrote:
> Hi,
> Trying to compile the last git pull just now, it gives some errors.
Update rawspeed submodule.

> I have 4.8.0-35-generic #40~16.04.1-Ubuntu SMP Wed Feb 1 17:42:37 UTC 2017
> x86_64 x86_64 x86_64 GNU/Linux
>
> Thank you in advance for any help.
>
> Darktable build script
>
> Building directory:  /home/andre/compilar/darktable/build
> Installation prefix: /opt/darktable
> Build type:  RelWithDebInfo
> Build generator: Unix Makefiles
> Build tasks: 8
>
>
> -- Building SSE2-optimized codepaths: ON
> -- Found little endian system. Good.
> -- Is the target platform supported: 1
> -- multiarch triplet detected: x86_64-linux-gnu
> -- Performing Test C_COMPILER_UNDERSTANDS_-Wno-error=varargs
> -- Performing Test C_COMPILER_UNDERSTANDS_-Wno-error=varargs - Success
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-Wno-error=varargs
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-Wno-error=varargs - Success
> -- Performing Test
> C_COMPILER_UNDERSTANDS_-Wno-error=address-of-packed-member
> -- Performing Test
> C_COMPILER_UNDERSTANDS_-Wno-error=address-of-packed-member - Failed
> -- Performing Test
> CXX_COMPILER_UNDERSTANDS_-Wno-error=address-of-packed-member
> -- Performing Test
> CXX_COMPILER_UNDERSTANDS_-Wno-error=address-of-packed-member - Failed
> -- Performing Test C_COMPILER_UNDERSTANDS_-Wframe-larger-than=32768
> -- Performing Test C_COMPILER_UNDERSTANDS_-Wframe-larger-than=32768 -
> Success
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-Wframe-larger-than=32768
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-Wframe-larger-than=32768 -
> Success
> -- Performing Test C_COMPILER_UNDERSTANDS_-Wstack-usage=32768
> -- Performing Test C_COMPILER_UNDERSTANDS_-Wstack-usage=32768 - Success
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-Wstack-usage=32768
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-Wstack-usage=32768 - Success
> -- Performing Test C_COMPILER_UNDERSTANDS_-Wlarger-than=524288
> -- Performing Test C_COMPILER_UNDERSTANDS_-Wlarger-than=524288 - Success
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-Wlarger-than=524288
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-Wlarger-than=524288 - Success
> -- Looking for external programs
> -- Found perl
> -- Found intltool-merge
> -- Found desktop-file-validate
> CMake Warning at CMakeLists.txt:335 (find_package):
>   Could not find a package configuration file provided by "LLVM" (requested
>   version 3.9) with any of the following names:
>
> LLVMConfig.cmake
> llvm-config.cmake
>
>   Add the installation prefix of "LLVM" to CMAKE_PREFIX_PATH or set
>   "LLVM_DIR" to a directory containing one of the above files.  If "LLVM"
>   provides a separate development package or SDK, be sure it has been
>   installed.
>
>
> CMake Warning at CMakeLists.txt:364 (message):
>   Could not find LLVM 3.9+
>
>
> CMake Warning at CMakeLists.txt:365 (message):
>   Test-compilation of OpenCL programs can not be done.
>
>
> -- Test-compilation of OpenCL programs is disabled.
> -- Missing jsonschema, problems in noiseprofiles.json might go unnoticed
> -- Found xsltproc
> -- Found xmllint
> -- All external programs found
> -- Found msgfmt to convert .po file. Translation enabled
> -- Checking for -march=native support
> -- Checking for -march=native support - works
> -- Checking for -std=c++11 support
> -- Checking for -std=c++11 support - works
> -- Looking for PThreads
> -- Looking for PThreads - found
> -- Looking for OpenMP
> -- Looking for OpenMP - found
> -- Looking for pugixml
> -- Found Pugixml 1.70
> -- Looking for pugixml - found (system)
> -- Looking for JPEG
> -- Looking for JPEG - found
> -- Looking for ZLIB
> -- Looking for ZLIB - found (system)
> -- Looking for xmllint tool
> -- Looking for xmllint tool - found
> -- Found Glib 2.48.2
> -- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found suitable
> version "2.9.3", minimum required is "2.6")
> -- Checking for one of the modules 'libsoup-2.2;libsoup2'
> -- Found GIO
> -- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version
> "2.9.3")
> -- Found Sqlite3 3.11.0
> -- Found JsonGlib
> CMake Warning at cmake/modules/LibFindMacros.cmake:263 (message):
>   WARNING: MISSING PACKAGE
>
>   We only found some files of OpenJPEG, not all of them.  Perhaps your
>   installation is incomplete or maybe we just didn't look in the right
> place?
>   This package is NOT REQUIRED and you may ignore this warning but by doing
>   so you may miss some functionality of darktable.
>
>   Relevant CMake configuration variables:
>
> OpenJPEG_INCLUDE_DIR=/usr/include
> OpenJPEG_LIBRARY=
>
>   You may use CMake GUI, cmake -D or ccmake to modify the values.  Delete
>   CMakeCache.txt to discard all values and force full re-detection if
>   necessary.
>
> Call Stack (most recent call first):
>   cmake/modules/FindOpenJPEG.cmake:29 (libfind_process)
>   src/CMakeLists.txt:296 (find_package)
>
>
> -- 

Re: [darktable-dev] Compilation error - Ubuntu 16.04

[Roman Lebedev]

On Tue, May 16, 2017 at 9:08 PM, Aurélien PIERRE
 wrote:
> Hi,
>
> I'm trying to compile DT 2.2.4 from the sources on Ubuntu 16.04. I have
> installed the dependencies listed on the wiki, plus another required during
> the setup but not listed (LLVM 3.9).
>
> While executing build.sh, I get :
>
> aurelien@ouranos:~/Softwares/darktable$ ./build.sh Darktable build script
> Building directory:  /home/aurelien/Softwares/darktable/build Installation
> prefix: /opt/darktable Build type:  RelWithDebInfo Build generator:
> Unix Makefiles Build tasks: 8
> -- Building SSE2-optimized codepaths: ON -- Found little endian system.
> Good. -- Is the target platform supported: 1 -- multiarch triplet detected:
> x86_64-linux-gnu -- Performing Test
> C_COMPILER_UNDERSTANDS_-Wno-error=varargs -- Performing Test
> C_COMPILER_UNDERSTANDS_-Wno-error=varargs - Success -- Performing Test
> CXX_COMPILER_UNDERSTANDS_-Wno-error=varargs -- Performing Test
> CXX_COMPILER_UNDERSTANDS_-Wno-error=varargs - Success -- Performing Test
> C_COMPILER_UNDERSTANDS_-Wno-error=address-of-packed-member -- Performing
> Test C_COMPILER_UNDERSTANDS_-Wno-error=address-of-packed-member - Failed --
> Performing Test CXX_COMPILER_UNDERSTANDS_-Wno-error=address-of-packed-member
> -- Performing Test
> CXX_COMPILER_UNDERSTANDS_-Wno-error=address-of-packed-member - Failed --
> Performing Test C_COMPILER_UNDERSTANDS_-Wframe-larger-than=32768 --
> Performing Test C_COMPILER_UNDERSTANDS_-Wframe-larger-than=32768 - Success
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-Wframe-larger-than=32768 --
> Performing Test CXX_COMPILER_UNDERSTANDS_-Wframe-larger-than=32768 - Success
> -- Performing Test C_COMPILER_UNDERSTANDS_-Wstack-usage=32768 -- Performing
> Test C_COMPILER_UNDERSTANDS_-Wstack-usage=32768 - Success -- Performing Test
> CXX_COMPILER_UNDERSTANDS_-Wstack-usage=32768 -- Performing Test
> CXX_COMPILER_UNDERSTANDS_-Wstack-usage=32768 - Success -- Performing Test
> C_COMPILER_UNDERSTANDS_-Wlarger-than=524288 -- Performing Test
> C_COMPILER_UNDERSTANDS_-Wlarger-than=524288 - Success -- Performing Test
> CXX_COMPILER_UNDERSTANDS_-Wlarger-than=524288 -- Performing Test
> CXX_COMPILER_UNDERSTANDS_-Wlarger-than=524288 - Success -- Looking for
> external programs -- Found perl -- Found intltool-merge -- Found
> desktop-file-validate -- Found LLVM 3.9.1 -- Found clang compiler -
> /usr/bin/clang-3.9 -- Found clang opencl-c.h header in
> /usr/lib/llvm-3.9/lib/clang/3.9.1/include -- Will be able to test-compile
> OpenCL programs. Nice. -- Found jsonschema -- Found xsltproc -- Found
> xmllint -- All external programs found -- Found msgfmt to convert .po file.
> Translation enabled CMake Error at src/CMakeLists.txt:133 (message):   The
> compiler /usr/bin/c++ has no C++11 support.  Please use a different C++
> compiler.
> -- Configuring incomplete, errors occurred! See also
> "/home/aurelien/Softwares/darktable/build/CMakeFiles/CMakeOutput.log". See
> also "/home/aurelien/Softwares/darktable/build/CMakeFiles/CMakeError.log".
So what compiler is c++?
and which version

> I don't understand why C++11 is not recognized… Any idea ?
Have you tried  git clean -f -d -x?
(i.e. purge build dir)

> Thanks.
>
> --
>
> Aurélien PIERRE
> aurelienpierre.com
Roman.

> 
>
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] darktable performance

[Roman Lebedev]

On Fri, May 12, 2017 at 7:09 PM, Alexander Rabtchevich
 wrote:
> I know well what is Bayern pattern and how demosaicing works ;) . In
> previous discussion I was told the time spending was due raw denoise,

> Two opearations during regular jpg export do not use OpenCl -
> raw demosaic (or decompression) and applying of final gamma
Ah, well, "raw demosaic (or decompression)" sounds kind-of gibberish,
non-raw demosaic makes no sense, so i just assumed that you meant "raw denoise"
But regardless, amaze demosaic algo is also not implemented in opencl,
and to be honest, without prior knowledge about internals of the algo, and thus,
possibility of the implementation) i don't really expect it to be
implemented in opencl,
at least in any near future.

> not
> demosaic. And there is no raw denoise active settings in demosaic module,
> maybe except the AMaZe algorithm itself.
>
>
> With respect,
> Alexander Rabtchevich
Roman.

> Joel Brunetti wrote:
>>
>> Demosaic is the process of going from three pixels (one each for red,
>> green and blue) beside each other on the camera sensor to a single RGB
>> pixel.
>>
>> On 12 May 2017 at 09:44, Alexander Rabtchevich
>>  wrote:
>>>
>>> Could you correct me one more time - does "demosaic" mean raw denoise?
>>>
>>> [dev_pixelpipe] took 0.000 secs (0.000 CPU) initing base buffer [export]
>>> [dev_pixelpipe] took 0.040 secs (0.020 CPU) processed `raw black/white
>>> point' on GPU, blended on GPU [export]
>>> [dev_pixelpipe] took 0.006 secs (0.012 CPU) processed `white balance' on
>>> GPU, blended on GPU [export]
>>> [dev_pixelpipe] took 0.004 secs (0.008 CPU) processed `highlight
>>> reconstruction' on GPU, blended on GPU [export]
>>> [dev_pixelpipe] took 1.007 secs (3.816 CPU) processed `demosaic  ' on
>>> CPU,
>>> blended on CPU [export]
>>> [dev_pixelpipe] took 0.208 secs (0.000 CPU) processed `orientation' on
>>> GPU,
>>> blended on GPU [export]
>>> [dev_pixelpipe] took 0.014 secs (0.000 CPU) processed `base curve' on
>>> GPU,
>>> blended on GPU [export]
>>> [dev_pixelpipe] took 0.009 secs (0.000 CPU) processed `input color
>>> profile'
>>> on GPU, blended on GPU [export]
>>> [dev_pixelpipe] took 0.020 secs (0.000 CPU) processed `sharpen' on GPU,
>>> blended on GPU [export]
>>> [dev_pixelpipe] took 0.019 secs (0.004 CPU) processed `output color
>>> profile'
>>> on GPU, blended on GPU [export]
>>> [dev_pixelpipe] took 0.644 secs (0.356 CPU) processed `gamma' on CPU,
>>> blended on CPU [export]
>>>
>>> AMaZe settings are: color smoothing off, match greens disabled.
>>>
>>> With respect,
>>> Alexander Rabtchevich
>>>
>>>
>>>
>>>
>>> Ulrich Pegelow wrote:

 Am 12.05.2017 um 08:21 schrieb Alexander Rabtchevich:
>
> Hello
> I've installed a new graphics card with Radeon 580 chip (8Gb) and so
> examined darktable performance. Two opearations during regular jpg
> export do
> not use OpenCl - raw demosaic (or decompression) and applying of final
> gamma. Their common time equals or even prewails a whole bunch of all
> other
> operations. The OpenCl setting in GUI is - powerful graphics card. Is
> there
> a way to increase the performance? Darktable is from current git.


 Absolutely! You could just write the needed OpenCL processing code for
 raw
 denoise.

 Concerning gamma: this is the last module in the pixelpipe. Latest in
 that
 module we need all data been transferred back to CPU memory. The time
 that
 darktable reports to spend in this module is an artifact. The reason is
 that
 the GPU and the CPU run idepenently. The CPU code just registers the
 needed
 GPU calls and then waits until the GPU terminates. This waiting happens
 (among other places) in module gamma. If you need to see the real
 timings
 you could set opencl_async_pixelpipe=FALSE. This way darktable will wait
 for
 OpenCL processing to finish after each module.

 Ulrich


>
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] darktable performance

[Roman Lebedev]

On Fri, May 12, 2017 at 9:21 AM, Alexander Rabtchevich
 wrote:
> Hello
>
> I've installed a new graphics card with Radeon 580 chip (8Gb) and so
> examined darktable performance. Two opearations during regular jpg export do
> not use OpenCl -

>raw demosaic (or decompression)
I'm guessing you mean "raw denoise"
>and applying of final
> gamma.
Both of these module do not have opencl kernels, so they have to be
processed on CPU.
And for that, the data needs to be copied from GPU memory to CPU (and back)...

>Their common time equals or even prewails a whole bunch of all other
> operations. The OpenCl setting in GUI is - powerful graphics card. Is there
> a way to increase the performance? Darktable is from current git.
Basically only by implementing those respective opencl kernels
The gamma kernel would be trivial, now that the "pipe format callbacks" work has
landed last fall (https://github.com/darktable-org/darktable/pull/1253)

I wanted to do it, and I would do it, but (*still*, sigh) i have no opencl here.

> With respect,
> Alexander Rabtchevich
Roman.

> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] darktable on Ubuntu 17.04

[Roman Lebedev]

On Fri, May 5, 2017 at 1:35 PM, Heiko Bauke  wrote:
> Hi,
>
> recently some ui problems due to a newer gtk version in Ubuntu 17.04 have
> been reported on this list.  I wonder has this already been fixed in git
> master or should I wait upgrading to Ubuntu 17.04?
That is not dt bug, there is nothing to wait from us i'm afraid.
The solution is the same as the last few times this was asked:
darktable needs to be rebuilt against that gtk version. that needs to be either
done by the ubuntu, or by user. If the problem happens on a fresh clean install
with no PPA's, then i think someone eventually should report that to ubuntu.

Or, use debian.

> Regards,
>
> Heiko
Roman.

> --
> -- Number Crunch Blog @ https://www.numbercrunch.de
> --  Cluster Computing @ http://www.clustercomputing.de
> --   Professional @ https://www.mpi-hd.mpg.de/personalhomes/bauke
> --  Social Networking @ https://www.researchgate.net/profile/Heiko_Bauke
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Adaptative deconvolution

[Roman Lebedev]

Are there any actual use-cases for this algorithm, specifically in darktable?

I'd imagine 95+% of blurred images/images with motion blur
where that is not intentional, would be deleted and not processed..

Roman.

On Thu, Apr 27, 2017 at 1:06 PM, Aurélien PIERRE
 wrote:
> Sorry for the spam, but I have found a 2015 article which adresses some of
> the limits of the previous ones (with Matlab code) :
> http://www.cvg.unibe.ch/dperrone/logtv/index.html
>
> Aurélien PIERRE
> aurelienpierre.com
>
> 
>
> Le 2017-04-27 à 05:05, Aurélien PIERRE a écrit :
>
> I have found some other implementations of blind deconvolution which seem
> lighter. A Matlab example here :
> http://cs.nyu.edu/~dilip/research/blind-deconvolution/.
>
> Aurélien PIERRE
> aurelienpierre.com
>
> 
> Le 2017-04-27 à 04:50, Heiko Bauke a écrit :
>
> Hi,
>
> Am 27.04.2017 um 10:27 schrieb Aurélien PIERRE:
>
> I found a software (http://relaunch.piccureplus.com/) which goal is to
> apply adaptative deconvolution to pictures in order to remove blur and
> noise. The result is quite amazing, without halos.
>
> [...]
>
> looks very interesting.
>
> [...]
>
> I know
> some of the developpers here are PhD in physics and maths, maybe they
> could take a look.
>
>
> I just had a very quick look at the research paper.  This filter probably
> demands rather high computational resources, it needs to compute discrete
> Fourier transforms and to solve sparse linear systems. It might be too slow
> for a darktable-work flow.  I will test this filter soon.
>
>
> Heiko
>
>
>
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
>
>
>
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Failing in rawspeed for some NIKON 1J5

[Roman Lebedev]

On Tue, Apr 11, 2017 at 10:10 PM, Wolfgang Goetz  wrote:
> Hello,
>
> 17 of my NIKON 1J5 files are crashing darktable-generate-cache (adjusted 
> --min-imgid to proceed until finish)
>
> i uploaded as example nogo: 20151027-10431071-NIKON_1_J5.nef to 
> https://raw.pixls.us/
>
> checked on gentoo(the cache and dt itself) and macos(half-processed file) 
> with actual git version.
>
>
>
> darktable-generate-cache: 
> /data_b/portage/portage/media-gfx/darktable-/work/darktable-/src/external/rawspeed/src/librawspeed/io/BitStream.h:158:
>  rawspeed::uint32 rawspeed::BitStream Cache>::peekBitsNoFill(rawspeed::uint32) [with Tag = rawspeed::MSBBitPumpTag; 
> Cache = rawspeed::BitStreamCacheRightInLeftOut; rawspeed::uint32 = unsigned 
> int]: Assertion `nbits <= Cache::MaxGetBits && nbits <= cache.fillLevel' 
> failed.
> Aborted
So i have had a look.
Thanks, good sample.
Not sure yet how to fix it.
But at least it made me finally fix the HuffmanTable fuzzer, and it
finally found issues (including "this" one)

> kind regards
> Wolfgang
Roman.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Failing in rawspeed for some NIKON 1J5

[Roman Lebedev]

(resend, accidentally forgot to CC the list)

On Tue, Apr 11, 2017 at 10:10 PM, Wolfgang Goetz  wrote:
> Hello,
>
> 17 of my NIKON 1J5 files are crashing darktable-generate-cache (adjusted 
> --min-imgid to proceed until finish)
Hi.

> 17 of my NIKON 1J5 files are crashing darktable-generate-cache (adjusted 
> --min-imgid to proceed until finish)
So basically all the raws from the camera cause that?
Btw, the files are properly manually copied from camera, and not
modified afterwards?

> i uploaded as example nogo: 20151027-10431071-NIKON_1_J5.nef to 
> https://raw.pixls.us/
Thanks.
Do check, perhaps there are some other samples you might be able to provide :)

> checked on gentoo(the cache and dt itself) and macos(half-processed file) 
> with actual git version.
>
>
>
> darktable-generate-cache: 
> /data_b/portage/portage/media-gfx/darktable-/work/darktable-/src/external/rawspeed/src/librawspeed/io/BitStream.h:158:
>  rawspeed::uint32 rawspeed::BitStream Cache>::peekBitsNoFill(rawspeed::uint32) [with Tag = rawspeed::MSBBitPumpTag; 
> Cache = rawspeed::BitStreamCacheRightInLeftOut; rawspeed::uint32 = unsigned 
> int]: Assertion `nbits <= Cache::MaxGetBits && nbits <= cache.fillLevel' 
> failed.
> Aborted
>
>
>
>
> kind regards
> Wolfgang
Roman.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Anyone building from git master with Fedora's rpmbuild?

[Roman Lebedev]

(resend, accidentally forgot to CC the list)

On Wed, Apr 12, 2017 at 1:18 AM, Terry Duell  wrote:
> Hello Tobias,
>
> On Wed, 12 Apr 2017 07:07:04 +1000, Tobias Ellinghaus  wrote:
>
>> Am Dienstag, 11. April 2017, 14:40:54 CEST schrieb Terry Duell:
>>>
>>> Hello All,
>>> My recent builds (Fedora 25) from git master have been missing the
>>> basecurve module. It doesn't appear in the 'more modules' list and I'm at
>>
>>
>> Is there a file called "libbasecurve.so" in your package/getting
>> installed? If
>> yes, are there any error messages when starting dt from a shell?
>
>
> Yes, that lib is installed.
> Starting dt from a shell does indeed throw an error...
>
> [iop_load_module] failed to open operation `basecurve':
> /usr/lib64/darktable/plugins/libbasecurve.so: undefined symbol:
> exposure_increment
Thanks, fixed, and CI adjusted to catch such cases in the future.

> Any ideas as to whether this is code problem or a build error at my end?
The problem i guess is that you disabled -Werror.
Instead of some vague run-time problem, it would have been a compile failure.

> Cheers,
> --
> Regards,
> Terry Duell
Roman.

> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] All of a sudden, darktable Thread Seg faults

[Roman Lebedev]

On Sun, Apr 9, 2017 at 3:43 PM, Ulrich Pegelow
<ulrich.pege...@tongareva.de> wrote:
> Am 09.04.2017 um 09:31 schrieb Roman Lebedev:
>>
>> On Sun, Apr 9, 2017 at 9:59 AM, Ulrich Pegelow
>> <ulrich.pege...@tongareva.de> wrote:
>>>
>>> Am 08.04.2017 um 20:04 schrieb Roman Lebedev:
>>>>
>>>>
>>>> Well, that is *very* strange indeed.
>>>> If it *reliably* happens for you, then maybe you could also bisect this
>>>> within the submodule itself?
>>>>
>>>
>>> Very clear result:
>>
>> Aha, now that makes rather no sense.
>> It is likely caused by just one raw image, if you can find it, i'll
>> take it from here.
>>
>>> 7f087325d09e2b6d4ecc392f7aee44dd29fafe62 is the first bad commit
>>> commit 7f087325d09e2b6d4ecc392f7aee44dd29fafe62
>>> Author: Roman Lebedev <lebedev...@gmail.com>
>>> Date:   Sat Apr 1 13:11:57 2017 +0300
>>>
>>> ThrowException(): and how about this?
>>>
>>> :04 04 84dd635a545bf913c916bc075f152a6718f05b1b
>>> ba3c956bb4ffb0b8f54b55ac4aaaf879334f7327 M  src
>>
>> This commit was reverted in the very next commit, so what is the next
>> bad commit?
>>
>
> Looks like none of the following commits solves the issue.
>
> However, looking at the changes in question I found that the following patch
> in master brings darktable back to normal:
>
> diff --git a/src/librawspeed/common/RawspeedException.h
> b/src/librawspeed/common/RawspeedException.h
> index 692d3f9..b0ebee6 100644
> --- a/src/librawspeed/common/RawspeedException.h
> +++ b/src/librawspeed/common/RawspeedException.h
> @@ -32,7 +32,7 @@
>  namespace RawSpeed {
>
>  template 
> -[[noreturn]] static inline void __attribute__((noreturn, format(printf, 1,
> 2)))
> +[[noreturn]] void __attribute__((noreturn, format(printf, 1, 2)))
>  ThrowException(const char* fmt, ...) {
>static constexpr size_t bufSize = 8192;
>  #if defined(HAVE_THREAD_LOCAL)
>
> That means reverting the change from commit
> 7f087325d09e2b6d4ecc392f7aee44dd29fafe62 which has not yet been reverted in
> commit 0967e3c8a528cca0800cc5289cba5c212a385a6b.
>
> Don't ask me 
And, pushed.

> Ulrich
>
>
>
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] All of a sudden, darktable Thread Seg faults

[Roman Lebedev]

On Sun, Apr 9, 2017 at 3:43 PM, Ulrich Pegelow
<ulrich.pege...@tongareva.de> wrote:
> Am 09.04.2017 um 09:31 schrieb Roman Lebedev:
>>
>> On Sun, Apr 9, 2017 at 9:59 AM, Ulrich Pegelow
>> <ulrich.pege...@tongareva.de> wrote:
>>>
>>> Am 08.04.2017 um 20:04 schrieb Roman Lebedev:
>>>>
>>>>
>>>> Well, that is *very* strange indeed.
>>>> If it *reliably* happens for you, then maybe you could also bisect this
>>>> within the submodule itself?
>>>>
>>>
>>> Very clear result:
>>
>> Aha, now that makes rather no sense.
>> It is likely caused by just one raw image, if you can find it, i'll
>> take it from here.
>>
>>> 7f087325d09e2b6d4ecc392f7aee44dd29fafe62 is the first bad commit
>>> commit 7f087325d09e2b6d4ecc392f7aee44dd29fafe62
>>> Author: Roman Lebedev <lebedev...@gmail.com>
>>> Date:   Sat Apr 1 13:11:57 2017 +0300
>>>
>>> ThrowException(): and how about this?
>>>
>>> :04 04 84dd635a545bf913c916bc075f152a6718f05b1b
>>> ba3c956bb4ffb0b8f54b55ac4aaaf879334f7327 M  src
>>
>> This commit was reverted in the very next commit, so what is the next
>> bad commit?
>>
>
> Looks like none of the following commits solves the issue.
>
> However, looking at the changes in question I found that the following patch
> in master brings darktable back to normal:
>
> diff --git a/src/librawspeed/common/RawspeedException.h
> b/src/librawspeed/common/RawspeedException.h
> index 692d3f9..b0ebee6 100644
> --- a/src/librawspeed/common/RawspeedException.h
> +++ b/src/librawspeed/common/RawspeedException.h
> @@ -32,7 +32,7 @@
>  namespace RawSpeed {
>
>  template 
> -[[noreturn]] static inline void __attribute__((noreturn, format(printf, 1,
> 2)))
> +[[noreturn]] void __attribute__((noreturn, format(printf, 1, 2)))
>  ThrowException(const char* fmt, ...) {
>static constexpr size_t bufSize = 8192;
>  #if defined(HAVE_THREAD_LOCAL)
>
> That means reverting the change from commit
> 7f087325d09e2b6d4ecc392f7aee44dd29fafe62 which has not yet been reverted in
> commit 0967e3c8a528cca0800cc5289cba5c212a385a6b.
>
> Don't ask me 
Okay, thank you for debugging this :)
I'll try to push that later today.

> Ulrich
Roman.

> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] All of a sudden, darktable Thread Seg faults

[Roman Lebedev]

On Sat, Apr 8, 2017 at 6:23 PM, Ulrich Pegelow
<ulrich.pege...@tongareva.de> wrote:
> Strange things also happen here. All of a sudden darktable would hang during
> startup in the OpenCL init phase of my AMD card (catalyst driver).
>
> I bisected the issue and found this:

> 97085123a6c29bed86fc7795d527c95bd50a is the first bad commit
> commit 97085123a6c29bed86fc7795d527c95ccccbd50a
> Author: Roman Lebedev <lebedev...@gmail.com>
> Date:   Tue Apr 4 20:51:11 2017 +0300
>
> Rawspeed submodule update: some static analysis fixes.
Well, that is *very* strange indeed.
If it *reliably* happens for you, then maybe you could also bisect this
within the submodule itself?

And perhaps build with ASAN.

> :04 04 c3da68a8bc9ec1664348e969bae26540f76234c0
> 6a112acf0d814aa0eb4bd68f17d14f012ef94e4c M  src
>
>
> Quite surprising. Doesn't look like the commit is related to OpenCL but I
> can reproduce that before this commit all is good and after that darktable
> with AMD OpenCL doesn't start. Reverting that commit in master makes
> darktable start again.
>
> Ulrich
Roman.

> Am 05.04.2017 um 21:42 schrieb Roman Lebedev:
>>
>> On Wed, Apr 5, 2017 at 10:29 PM, Mark Heieis <mhei...@alois.ca> wrote:
>>>
>>> Hi There,
>>>
>>> Today, for some reason, darktable seg faults with the following. I used
>>> it
>>> yesterday and it worked fine. I may have updated the OS after my last use
>>> and could roll-back the update to check. Any thoughts?
>>>
>>> Linux copernicus 4.10.8-200.fc25.x86_64 #1 SMP Fri Mar 31 13:20:22 UTC
>>> 2017
>>> x86_64 x86_64 x86_64 GNU/Linux
>>>
>>> $ darktable
>>> [New LWP 2506]
>>> [New LWP 2507]
>>> [New LWP 2508]
>>> [New LWP 2509]
>>> [New LWP 2510]
>>> [New LWP 2511]
>>> [New LWP 2512]
>>> [New LWP 2513]
>>> [New LWP 2514]
>>> [New LWP 2515]
>>> [Thread debugging using libthread_db enabled]
>>> Using host libthread_db library "/lib64/libthread_db.so.1".
>>> 0x7f1b3b095fdb in waitpid () from /lib64/libpthread.so.0
>>> backtrace written to /tmp/darktable_bt_XVOKYY.txt
>>> Segmentation fault (core dumped)
>>>
>>> ~
>>>
>>> Core dump:
>>>
>>> this is darktable darktable-2.2.3-1.fc25 reporting a segfault:
>>>
>>> #0  0x7f1b3b095fdb in waitpid () at /lib64/libpthread.so.0
>>> #1  0x7f1b3f9ccc40 in _dt_sigsegv_handler () at
>>> /usr/bin/../lib64/darktable/libdarktable.so
>>> #2  0x7f1b3790b990 in  () at /lib64/libc.so.6
>>> #3  0x in  ()
>>> #4  0x7f1ae45dfb89 in  () at /lib64/libamdocl64.so
>>
>> So the issue *appears* to be in amd opencl blob.
>> You can disable opencl, that would get rid of the crash.
>>
>>> #5  0x7f1ae45e1afe in  () at /lib64/libamdocl64.so
>>> #6  0x7f1ae45d1b98 in  () at /lib64/libamdocl64.so
>>> #7  0x7f1ae42edf69 in  () at /lib64/libamdocl64.so
>>> #8  0x7f1ae42bc4d9 in  () at /lib64/libamdocl64.so
>>> #9  0x7f1ae42bc54f in  () at /lib64/libamdocl64.so
>>> #10 0x7f1ae42bd2c9 in  () at /lib64/libamdocl64.so
>>> #11 0x7f1ae42843d8 in  () at /lib64/libamdocl64.so
>>> #12 0x7f1ae42858c7 in  () at /lib64/libamdocl64.so
>>> #13 0x7f1ae4285a56 in  () at /lib64/libamdocl64.so
>>> #14 0x7f1ae424140e in  () at /lib64/libamdocl64.so
>>> #15 0x7f1ae425cc27 in  () at /lib64/libamdocl64.so
>>> #16 0x7f1ae422adbe in clIcdGetPlatformIDsKHR () at
>>> /lib64/libamdocl64.so
>>> #17 0x7f1b1c65676e in  () at /lib64/libOpenCL.so
>>> #18 0x7f1b1c658647 in  () at /lib64/libOpenCL.so
>>> #19 0x7f1b3b093ba9 in __pthread_once_slow () at
>>> /lib64/libpthread.so.0
>>> #20 0x7f1b1c656d31 in clGetPlatformIDs () at /lib64/libOpenCL.so
>>> #21 0x7f1b3f9da58b in dt_opencl_init () at
>>> /usr/bin/../lib64/darktable/libdarktable.so
>>> #22 0x7f1b3f9802be in dt_init () at
>>> /usr/bin/../lib64/darktable/libdarktable.so
>>> #23 0x560f0cb71b86 in main ()
>>>
>>> Thread 11 (Thread 0x7f1b1d05b700 (LWP 2515)):
>>> #0  0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at
>>> /lib64/libpthread.so.0
>>> #1  0x7f1b3f9e265f in dt_control_work_res () at
>>> /usr/bin/../lib64/darktable/libdarktable.so
>>> #2  0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0
>>> #3  0x7f1b379ddf7f in clone () at /lib64/libc.so.6

Re: [darktable-dev] All of a sudden, darktable Thread Seg faults

[Roman Lebedev]

On Wed, Apr 5, 2017 at 10:29 PM, Mark Heieis  wrote:
> Hi There,
>
> Today, for some reason, darktable seg faults with the following. I used it
> yesterday and it worked fine. I may have updated the OS after my last use
> and could roll-back the update to check. Any thoughts?
>
> Linux copernicus 4.10.8-200.fc25.x86_64 #1 SMP Fri Mar 31 13:20:22 UTC 2017
> x86_64 x86_64 x86_64 GNU/Linux
>
> $ darktable
> [New LWP 2506]
> [New LWP 2507]
> [New LWP 2508]
> [New LWP 2509]
> [New LWP 2510]
> [New LWP 2511]
> [New LWP 2512]
> [New LWP 2513]
> [New LWP 2514]
> [New LWP 2515]
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> 0x7f1b3b095fdb in waitpid () from /lib64/libpthread.so.0
> backtrace written to /tmp/darktable_bt_XVOKYY.txt
> Segmentation fault (core dumped)
>
> ~
>
> Core dump:
>
> this is darktable darktable-2.2.3-1.fc25 reporting a segfault:
>
> #0  0x7f1b3b095fdb in waitpid () at /lib64/libpthread.so.0
> #1  0x7f1b3f9ccc40 in _dt_sigsegv_handler () at
> /usr/bin/../lib64/darktable/libdarktable.so
> #2  0x7f1b3790b990 in  () at /lib64/libc.so.6
> #3  0x in  ()
> #4  0x7f1ae45dfb89 in  () at /lib64/libamdocl64.so
So the issue *appears* to be in amd opencl blob.
You can disable opencl, that would get rid of the crash.

> #5  0x7f1ae45e1afe in  () at /lib64/libamdocl64.so
> #6  0x7f1ae45d1b98 in  () at /lib64/libamdocl64.so
> #7  0x7f1ae42edf69 in  () at /lib64/libamdocl64.so
> #8  0x7f1ae42bc4d9 in  () at /lib64/libamdocl64.so
> #9  0x7f1ae42bc54f in  () at /lib64/libamdocl64.so
> #10 0x7f1ae42bd2c9 in  () at /lib64/libamdocl64.so
> #11 0x7f1ae42843d8 in  () at /lib64/libamdocl64.so
> #12 0x7f1ae42858c7 in  () at /lib64/libamdocl64.so
> #13 0x7f1ae4285a56 in  () at /lib64/libamdocl64.so
> #14 0x7f1ae424140e in  () at /lib64/libamdocl64.so
> #15 0x7f1ae425cc27 in  () at /lib64/libamdocl64.so
> #16 0x7f1ae422adbe in clIcdGetPlatformIDsKHR () at /lib64/libamdocl64.so
> #17 0x7f1b1c65676e in  () at /lib64/libOpenCL.so
> #18 0x7f1b1c658647 in  () at /lib64/libOpenCL.so
> #19 0x7f1b3b093ba9 in __pthread_once_slow () at /lib64/libpthread.so.0
> #20 0x7f1b1c656d31 in clGetPlatformIDs () at /lib64/libOpenCL.so
> #21 0x7f1b3f9da58b in dt_opencl_init () at
> /usr/bin/../lib64/darktable/libdarktable.so
> #22 0x7f1b3f9802be in dt_init () at
> /usr/bin/../lib64/darktable/libdarktable.so
> #23 0x560f0cb71b86 in main ()
>
> Thread 11 (Thread 0x7f1b1d05b700 (LWP 2515)):
> #0  0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at
> /lib64/libpthread.so.0
> #1  0x7f1b3f9e265f in dt_control_work_res () at
> /usr/bin/../lib64/darktable/libdarktable.so
> #2  0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0
> #3  0x7f1b379ddf7f in clone () at /lib64/libc.so.6
>
> Thread 10 (Thread 0x7f1b1d85c700 (LWP 2514)):
> #0  0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at
> /lib64/libpthread.so.0
> #1  0x7f1b3f9e265f in dt_control_work_res () at
> /usr/bin/../lib64/darktable/libdarktable.so
> #2  0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0
> #3  0x7f1b379ddf7f in clone () at /lib64/libc.so.6
>
> Thread 9 (Thread 0x7f1b1e05d700 (LWP 2513)):
> #0  0x7f1b379a281d in nanosleep () at /lib64/libc.so.6
> #1  0x7f1b379a276a in sleep () at /lib64/libc.so.6
> #2  0x7f1b3f9e228a in dt_control_worker_kicker () at
> /usr/bin/../lib64/darktable/libdarktable.so
> #3  0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0
> #4  0x7f1b379ddf7f in clone () at /lib64/libc.so.6
>
> Thread 8 (Thread 0x7f1b1e85e700 (LWP 2512)):
> #0  0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at
> /lib64/libpthread.so.0
> #1  0x7f1b3f9e38be in dt_control_work () at
> /usr/bin/../lib64/darktable/libdarktable.so
> #2  0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0
> #3  0x7f1b379ddf7f in clone () at /lib64/libc.so.6
>
> Thread 7 (Thread 0x7f1b1f05f700 (LWP 2511)):
> #0  0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at
> /lib64/libpthread.so.0
> #1  0x7f1b3f9e38be in dt_control_work () at
> /usr/bin/../lib64/darktable/libdarktable.so
> #2  0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0
> #3  0x7f1b379ddf7f in clone () at /lib64/libc.so.6
>
> Thread 6 (Thread 0x7f1b1705f700 (LWP 2510)):
> #0  0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at
> /lib64/libpthread.so.0
> #1  0x7f1b3f9e38be in dt_control_work () at
> /usr/bin/../lib64/darktable/libdarktable.so
> #2  0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0
> #3  0x7f1b379ddf7f in clone () at /lib64/libc.so.6
>
> Thread 5 (Thread 0x7f1b1f860700 (LWP 2509)):
> #0  0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at
> /lib64/libpthread.so.0
> #1  0x7f1b3f9e38be in dt_control_work () at
> /usr/bin/../lib64/darktable/libdarktable.so

Re: [darktable-dev] Please test darktable-2.2.x branch

[Roman Lebedev]

On Wed, Mar 29, 2017 at 9:58 PM, Heiko Bauke <heiko.ba...@mail.de> wrote:
> Hi,
>
> Am 28.03.2017 um 10:40 schrieb Roman Lebedev:
>>
>> I believe we are *getting ready* to roll out the next point release, 2.2.4
>
>
> compiled dt freshly from the darktable-2.2.x branch and found a strange run
> time behavior.   If I start dt and close the UI just a few seconds later the
> UI disappears immediately (as one would expect).  However, dt keeps running
> until the total wall-clock running time has reached exactly 1 minute.
How many worker threads did you set in preferences? 1?

That reminds me of cups printer detection running for 30s/1m,
occupying exactly one worker thread. Normally, that should also
result in thumbnails being 'stuck' - not generating, not updating, nothing.

> Heiko
Roman.

> --
> -- Number Crunch Blog @ https://www.numbercrunch.de
> --  Cluster Computing @ http://www.clustercomputing.de
> --   Professional @ https://www.mpi-hd.mpg.de/personalhomes/bauke
> --  Social Networking @ https://www.researchgate.net/profile/Heiko_Bauke
>
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] PSA: Does anyone still use gcc-4.8/4.9 ?

[Roman Lebedev]

On Tue, Mar 28, 2017 at 3:44 PM, Germano Massullo
<germano.massu...@gmail.com> wrote:
> Il 28/03/2017 14:04, Mark Feit ha scritto:
>> On 03/28/2017 04:57 AM, Roman Lebedev wrote:
>>> I want to bump gcc requirement up to GCC-5 soon,
>>>
>>> Thus, subj.
>>> If you do, please speak up now.
>>> PS: using outdated distro version is not an excuse.
>>
>> I'm not even a bit player in this but...
>>
>> This will put off anybody using EL7 or its derivatives because there
>> are ABI and library changes and no easy way to get GCC 5 installed
>> using the "usual" repositories (i.e., Base and EPEL).  Fedora has
>> already made the jump, but those changes aren't going to be in the
>> stable distro picture until EL8 happens.  Whether that makes EL7
>> outdated would, of course, be up for discussion.
Thank you for this feedback.

>> If EL8 drags out beyond production DT having the GCC 5 requirement, EL
>> users running the latest available
That is actually the very important point - running git master of some software
on supported Enterprise distribution. Does anyone here actually do that?

Otherwise, the version bump would only be of an importance for the new
software versions, and since EL does not seem to get any upgrades, i think
it does not matter at all. New distro version will contain newer gcc, and will
be able to update darktable.

That being said, dt is packaged for EL, right? Else this is all irrelevant.

>> won't have a way to use it other
>> than a VM with a distro that supports it.  I've done that a couple of
>> times out of necessity, but I/O is sluggish enough that I'd prefer not
>> to.

So right now the two 'blockers' to consider is RHEL7 and CentOS7

>> --Mark
Roman.

>> ___
>>
>> darktable developer mailing list
>> to unsubscribe send a mail to
>> darktable-dev+unsubscr...@lists.darktable.org
>>
>>
> As darktable maintainer for Fedora EPEL 7 (also known as EL7)[1] the
> repository that provides extra packages for CentOS / RHEL / Scientific
> Linux, I can say that the actual available GCC version is 4.8.5
>
> [1]: https://fedoraproject.org/wiki/EPEL/
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] PSA: Does anyone still use gcc-4.8/4.9 ?

[Roman Lebedev]

Hi!

I want to bump gcc requirement up to GCC-5 soon,
after upcoming debian release.
I need this for C++14 for rawspeed.

Thus, subj.
If you do, please speak up now.
PS: using outdated distro version is not an excuse.

Roman.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Please test darktable-2.2.x branch

[Roman Lebedev]

Hi all.

I believe we are *getting ready* to roll out the next point release, 2.2.4

Please do test it before it is released, (end of this week?)
so that the 2.2.2/2.2.3 does not happen again :)

Roman.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Darktable 2.2.X Plugin Pano Professional

[Roman Lebedev]

On Sun, Mar 26, 2017 at 10:38 PM, Holger Klemm
 wrote:
The subject/name is so click-bait-y :)
It is a lua script, and they are called scrips, not plugins.
In darktable, plugin might refer to the lib/iop/view, i.e. in general
something that needs to be actually compiled from sources.

Roman.

> Hello,
> here is the first beta version of the darktable plugin pano pro. The script
> does the same as hugin.lua, but is better integrated into darktable.
> Similar to enfuse pro you can use the GPU, exif data attach and a reimport the
> panorama image to the database.
>
> It's a beta testing version and may contain bugs! The plugin is only tested
> with dt 2.2.3
>
> Plugin image:
> http://www.multimedia4linux.de/images/darktable/plugins/pano_pro_2.1beta1.jpg
>
> Download:
> http://www.multimedia4linux.de/images/darktable/plugins/pano_pro-2.1beta1.tar
>
>
>
>
>
>
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Fuji Compressed RAW Files

[Roman Lebedev]

On Fri, Mar 17, 2017 at 12:30 AM, Uwe Müssel <uwe_mues...@web.de> wrote:
> 2017-03-16 21:50 GMT+01:00 Roman Lebedev <lebedev...@gmail.com>:
>>
>> Now, the important question: do you know if that code is noticeably
>> different from
>> the vanilla libraw/rawtherapee version? Does it have any
>> behavior-changing changes?
>> Like, producing different output for the same raw?
>
>
> The main diffrerence between this code and the  libraw/rawtherapee code is
> in reading the file. Libraw does it with fseek and fread into a local
> "small" buffer. In a first version I replaced this by memcpy operations. Now
> I use simple input.getData(...).

> The decompression algorithm itself is untouched. I even do not know how it
> is working in detail. I expect the raw the be equal.
Ok, good.

> There is some more cleanup to be done, e.g. remove obsolete fields.
Then please don't do that just yet.

>> Oh, and, please apply clang-format to decompressors/FujiDecompressor.*
>> and install clang-format git hook, so that the formatting is uniform.
> I  will do this on the next commit.
It probably makes sense to squash it into that first commit.

I think it may make sense for me to merge your work into a separate
branch (raf-compressed) of the repo first.

Did you try building rawspeed on it's own, or only as part of darktable?
Does it actually compile with all the current warning flags?
If not i'd just disable -Werror for now.

Roman.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Fuji Compressed RAW Files

[Roman Lebedev]

On Thu, Mar 16, 2017 at 11:30 PM, Uwe Müssel  wrote:
> Hello Roman,
Hi.

> I've cloned darktable-org/rawspeed and have started to ported the compressed
> RAF support. You can find it at https://github.com/muessel/rawspeed.

> Now I use the CFA from camaras.xml.
Cool :)

> I changed the copyright header: I took the standard one and inserted the
> people from libraw. Mabe there is missing a reference to the libraw project?
Looking at it again, i'm not sure what i was commenting about. So just keep
it as is i guess.

Now, the important question: do you know if that code is noticeably
different from
the vanilla libraw/rawtherapee version? Does it have any
behavior-changing changes?
Like, producing different output for the same raw?

The reason being, there is some kind of rudimentary regression testing
in rawspeed.
It may make sense for me to merge it somewhere in this current state
(with absolutely
minimal amount of changes) so that going forward, all the changes will
be test-able.

Oh, and, please apply clang-format to decompressors/FujiDecompressor.*
and install clang-format git hook, so that the formatting is uniform.

> Regards
>Uwe
Roman.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Darktable stopped working; symbol lookup error libdarktable.so

[Roman Lebedev]

On Thu, Mar 16, 2017 at 3:33 PM, Matthew Malthouse  wrote:
> Hi Roman,
>
> tl;dr  that worked.  Thank you.
Good :)

> I'm still baffled about what happened.
>
> Re-installing DT caused libexiv2-14 to be installed as a dependency and gave
> /usr/lib/x86_64-linux-gnu/libexiv2.so.14 etc.  No such files existed when I
> was looking before, although they obviously must have at some point and I
> assume that a prior install, subsequently damaged, was what dpkg.log was
> referring to.
>
> It's worrying that dpkg.log says that this was updated on Tuesday
>
> dpkg.log:2017-03-14 06:25:04 upgrade libexiv2-14:amd64 0.25-2.1
> 0.25-2.1ubuntu16.04.1
>
> but the only related files existed in /usr/local/lib.
>
> I can be confident that I didn't compile by hand, I almost never do these
> days and I think that trying to compile DT from source on Tuesday was the
> first time I'd done so on this particular machine  (started about 11:00, so
> hours after that entry in dpkg.log) in large part because I had to install
> the cmake tools to build the dependencies to build DT.
>
> I can only guess that some unrelated and dodgy package install did the
> breaking but have no clue what that might be.  Maybe I'll find out the next
> time I discover something that doesn't work.  :)
dpkg -S   is your friends here

> Cheers,
>
> Matthew
>
>
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Darktable stopped working; symbol lookup error libdarktable.so

[Roman Lebedev]

On Tue, Mar 14, 2017 at 11:45 PM, Matthew Malthouse
 wrote:
>> That is typical C++11 issue.
>> Please do make sure that both the dt and libexiv2 are installed from
>> official repo, not from some random PPA's
>
>
> Darktable as per the install page from
> http://ppa.launchpad.net/pmjdebruijn/darktable-release/ubuntu xenial main
>
> darktable is already the newest version (1:2.2.3-0pmjdebruijn1~xenial).
>
>>
>> Especially the exiv2.
>
>
> exiv2 is already the newest version (0.25-2.1ubuntu16.04.1).
> libexiv2-14 is already the newest version (0.25-2.1ubuntu16.04.1).
Please do show
$ ldd /path/to/darktable
and
$ ldd /path/to/libdarktable.so

> Nothing in /etc/apt suggests that they're coming from anywhere except the
> Ubuntu repository
>
>>
>> Also, do make sure that you do not have some self-compiled libexif2
>> somewhere, e.g. in /opt, or /usr/local
>
>
> No, nothing there.:(
>
> Matthew
>
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Darktable stopped working; symbol lookup error libdarktable.so

[Roman Lebedev]

On Tue, Mar 14, 2017 at 7:54 PM, Matthew Malthouse  wrote:
> Hi,
>
> I don't use Darktable that often and when I tried to this morning it...
> well, it just didn't.
>
> Machine *was* Ubuntu 14.04.LTS and has been upgraded to 16.04.LTS, now:
> 4.4.0-66-generic #87-Ubuntu SMP x86_64 GNU/Linux (Dual 4-core proc; 16Gib
> RAM).
>
> Darktable was installed when the OS was 14.04 and has been used subsequent
> to upgrade.
>
> The Errors
>
> From Syslog:
> Mar 14 11:30:42 nine gnome-session[2520]: (gnome-software:2721): As-WARNING
> **: failed to rescan: Failed to parse
> /usr/share/applications/darktable.desktop.dpkg-new file: cannot process file
> of type text/plain
> Mar 14 11:30:42 nine gnome-session[2520]: (gnome-software:2721): As-WARNING
> **: failed to rescan: Failed to parse
> /usr/share/applications/darktable.desktop file: cannot process file of type
> application/x-desktop
> Mar 14 11:30:46 nine gnome-session[2520]: (gnome-software:2721): As-WARNING
> **: failed to rescan: Failed to parse /usr/share/applications/bamf-2.index
> file: cannot process file of type text/plain
>
> Debug:
> ~$ /usr/bin/darktable -d all
> [memory] at startup
> [memory] max address space (vmpeak):  317332 kB
> [memory] cur address space (vmsize):  317332 kB
> [memory] max used memory   (vmhwm ):   20028 kB
> [memory] cur used memory   (vmrss ):   20028 kB
> /usr/bin/darktable: symbol lookup error:
> /usr/bin/../lib/x86_64-linux-gnu/darktable/libdarktable.so: undefined
> symbol:
> _ZN5Exiv213XmpProperties10registerNsERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES8_
That is typical C++11 issue.
Please do make sure that both the dt and libexiv2 are installed from
official repo, not from some random PPA's
Especially the exiv2.

Also, do make sure that you do not have some self-compiled libexif2
somewhere, e.g. in /opt, or /usr/local

> That file...
> ~#  file /usr/lib/x86_64-linux-gnu/darktable/libdarktable.so
> /usr/lib/x86_64-linux-gnu/darktable/libdarktable.so: ELF 64-bit LSB shared
> object, x86-64, version 1 (SYSV), dynamically linked,
> BuildID[sha1]=c0c8f07f10ed3c9928ea7b9b32caed116bd29acf, stripped
> ~# ls -l /usr/lib/x86_64-linux-gnu/darktable/libdarktable.so
> -rw-r--r-- 1 root root 2922920 Jan 31 21:12
> /usr/lib/x86_64-linux-gnu/darktable/libdarktable.so
>
>
> What I've done:  update Darktable;  purge Darktable, install Darktable from
> "deb http://ppa.launchpad.net/pmjdebruijn/darktable-release/ubuntu xenial
> main" — all with same errors
>
> Purged Darkable again and tried to build from source [this failed, another
> question for another time] installed again as above.  Still failed.
>
> Now I'm stumped.
>
> Matthew
Roman.

> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Fuji Compressed RAW Files

[Roman Lebedev]

On Sat, Mar 11, 2017 at 10:26 PM, Roman Lebedev <lebedev...@gmail.com> wrote:
> Yes, basically add this:
EDIT:

auto id = mRootIFD->getID();
const Camera* cam = meta->getCamera(id.make, id.model, "");
if (!cam)
  ThrowRDE("Couldn't find camera");
mRaw->cfa = cam->cfa;

Somewhere in the beginning.
I did not test, but it should be pretty much all that is needed.

>> Regards
>>Uwe
Roman.

>> ___
>> darktable developer mailing list to unsubscribe send a mail to
>> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Fuji Compressed RAW Files

[Roman Lebedev]

On Sat, Mar 11, 2017 at 9:59 PM, Uwe Müssel  wrote:
> Hello,
Hi, current rawspeed maintainer here.

> I've started to adapt the code for decoding fuji compressed raw files from
> libraw/rawtherapee to darktable. You can find the code on github
> https://github.com/muessel/darktable in the branch fuji_decompress.
Cool.

A few notes:
1. You are working on a completely wrong base.
It should be git develop branch of repo
https://github.com/darktable-org/rawspeed
2. The copyright header is obviously completely wrong in FujiDecompressor.
3. There has been substantial cleanup of rawspeed, and thus, such code
(FujiDecompressor)
would need to be rather seriously rewritten, before i would
consider merging it.

> It is currently working with raw files from my Fujifilm X-T2.
Nice!

It would be *much* better to have more direct line of communication,
i can be found in IRC in #darktable channel on Freenode.

> The algorithm depends on the CFA of the sensor which seems not to be set in
> the RawImage object at the stage of decoding the raw file. So I've
> implemented a hard coded version into the FujiDecompressor. My question is,
> is it possible to get the CFA from the camera.xml during or before  decoding
> the raw file?
Yes, basically add this:

const Camera* cam = meta->getCamera(id.make, id.model, "");
if (!cam)
  ThrowRDE("Couldn't find camera");
mRaw->cfa = cam->cfa;

Somewhere in the beginning.

> Regards
>Uwe
Roman.

> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] export to google photo

[Roman Lebedev]

On Thu, Feb 16, 2017 at 9:10 PM, Pascal Obry  wrote:
>
> A follow-up on this issue. I think the different transient issues we
> had week ago was due to Google deprecating part of the API. Lot of
> changes have been made!
>
> As of today it is not possible to create album from the API. That is
> the darktable export to Google Photo will always fail. It is the case
> for me and during investigation I've found that Google as removed the
> creation of album from the API (plus many other things, but well not
> used by darktable).

Is there any kind of announcement i wonder?
In facebook case, IIRC they only disabled album creation for old API,
but it is still possible with the new API version.

> Anyway, I'm prepare a PR to fix this:
>
> https://github.com/darktable-org/darktable/pull/1440
>
> The idea is to use the Drop Box (a special album) to upload pictures.
> This is supported. Of course it is still possible to upload pictures
> into existing albums.
>
> Regards,
>
> --
>   Pascal Obry /  Magny Les Hameaux (78)
>
>   The best way to travel is by means of imagination
>
>   http://www.obry.net
>
>   gpg --keyserver keys.gnupg.net --recv-key F949BD3B
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Darktable on Beignet

[Roman Lebedev]

On Thu, Feb 16, 2017 at 11:11 AM, yan.wang  wrote:
> Hi,
> I am Beignet devloper from Intel.
Hi.

> Just I found Beignet is pushed into the blacklist of darktable because
> of one bug.
> http://www.darktable.org/2016/12/darktable-2-2-0rc3-released/
> I want to fix it but I don't know how to reproduce it.
In this particular case, i blacklisted it because of
https://redmine.darktable.org/issues/11358

To reproduce, i guess you'd need
https://redmine.darktable.org/attachments/download/2799/CRW_9672.DNG
and https://redmine.darktable.org/attachments/download/2803/CRW_9672.DNG.xmp

Disable blacklist (echo "opencl_disable_drivers_blacklist=true >>
~/.config/darktable/darktablerc")
Start dt
Import image
Select it (highlight the image, click on it once)
In right sidepanel, in "History stack" module, click on "load sidecar
file", and select that XMP.

Maybe this particular issue is already fixed, maybe it is not.

> Who could help me?
> Thanks.
>
> 
> yan.wang
Roman.

> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Multiple white balances?

[Roman Lebedev]

On Tue, Feb 7, 2017 at 9:20 PM, Thomas Werzmirzowsky  wrote:
> Hello everybody,
>
> I was just wondering if there are any plans to add the feature of
> multiple white balances to darktable.
It was recently disscussed. Last consensus was that it may not work in our
pipeline too well, but can be done.
But first, sidepanel code needs to be brushed a little.

I started the changes, but did not finish them.

> Usually I'm watching lightroom tutorials online as there are not many
> for darktable and it seems to be a common thing
> to have multiple white balances. This seems to be used especially often
> for sunset/sunrise to have warmer tones around
> the sun/in the sky.
>
> I tried to reproduce that in darktable using "color correction" and
> "split toning" modules but didn't really succeed. Also having
> just another white balance module with a mask seems to be much easier.
>
> Thanks a lot for your feedback.
>
> Best regards
> Thomas
Roman.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] cannot compile dt from git

[Roman Lebedev]

On Thu, Feb 2, 2017 at 10:50 PM, Alexander Rabtchevich
 wrote:
> Hello
>
> An attempt to compile results in an error:
>
> /home/sasha/Install/darktable/src/common/imageio_rawspeed.cc: In function
> ‘uint32_t dt_rawspeed_crop_dcraw_filters(uint32_t, uint32_t, uint32_t)’:
> /home/sasha/Install/darktable/src/common/imageio_rawspeed.cc:109:10: error:
> ‘shiftDcrawFilter’ is not a member of ‘RawSpeed::ColorFilterArray’
>return ColorFilterArray::shiftDcrawFilter(filters, crop_x, crop_y);
>   ^
> [ 23%] Building C object
> src/CMakeFiles/lib_darktable.dir/control/jobs/film_jobs.c.o
> [ 25%] Building C object
> src/CMakeFiles/lib_darktable.dir/control/jobs/image_jobs.c.o
> src/CMakeFiles/lib_darktable.dir/build.make:940: recipe for target
> 'src/CMakeFiles/lib_darktable.dir/common/imageio_rawspeed.cc.o' failed
> make[2]: *** [src/CMakeFiles/lib_darktable.dir/common/imageio_rawspeed.cc.o]
> Error 1
>
> git submodules have been fetched with git pull --recurse-submodules
also do  $ git submodule update -f

> With respect,
> Alexander Rabtchevich
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Re: Unusual stability problem

[Roman Lebedev]

On Tue, Jan 31, 2017 at 7:58 AM, Dan Torop  wrote:
> Thank you for the report & the very helpful sample file.

> I'm mortified, though, that the bug made its way into 2.2.2.
Nah, it's just me continuing the tradition of breaking one(?)
stable point release per series. (this was 3rd time in three series)

one release (i think 1.6.x) had broken dt-cli
then there was nikon issue in 2.0.6
and now low-MP bayer problem in 2.2.2

Let's hope i won't break a second point release this time :)

> Dan
Roman.

> David Vincent-Jones  writes:
>
>> My problem appears to be fixed now ... thanks for the quick work
>>
>> David
>>
>> On 01/30/2017 09:31 AM, Ulrich Pegelow wrote:
>>
>>  Great, this seems to have fixed the issue for me!
>>
>>  Ulrich
>>
>>  Am 30.01.2017 um 09:45 schrieb johannes hanika:
>>
>>  thanks for providing the fix! seems correct to me, since the loop is y
>>  <= max and y+1 is accessed inside. i pushed this PR to master. let's
>>  see if it fixes it for everyone.
>>
>>  cheers,
>>  jo
>>
>>  ___
>>  darktable developer mailing list
>>  to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>>
>> ___ 
>> darktable developer mailing list to unsubscribe send a mail to
>> darktable-dev+unsubscr...@lists.darktable.org
>
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] cannot compile current git

[Roman Lebedev]

On Sat, Jan 28, 2017 at 4:41 PM, Moritz Moeller <virtualr...@gmail.com> wrote:
> On 28.1.17 12:06 , Roman Lebedev wrote:
> I did. Same error.
Fixed, thank you for reporting!

> .mm
Roman.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Re: Unusual stability problem

[Roman Lebedev]

On Sun, Jan 29, 2017 at 1:09 AM, Ulrich Pegelow
 wrote:
> Same here with current master on specific images with and without OpenCL. I
> have several images from one session, all have the same raw size. One image
> with an uncommon crop crashes whenever I open it in the darkroom.
Looks like the crash is in gtk / x?

> Ulrich
Roman.

> Am 28.01.2017 um 05:14 schrieb David Vincent-Jones:
>>
>> Apparently the problem still exists:
>>
>> Thread 74 "darktable" received signal SIGSEGV, Segmentation fault.
>> [Switching to Thread 0x7fff1cff9700 (LWP 28841)]
>> dt_iop_clip_and_zoom_mosaic_half_size_plain._omp_fn.1 ()
>> at
>>
>> /usr/src/debug/darktable-2.3.0+git309.0f2cfb2/src/develop/imageop_math.c:230
>>
>> Interesting that this is only occurring on my 16mp. Canon raw files and
>> I cannot reproduce on my more recent 16mp. raw Fuji files.
>>
>> This is the first time that I have worked on the Canon files since
>> installing OpenCL
>>
>> David
>>
>>
>
>
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org