Re: [darktable-dev] Scrolling in Collect Images

[Roman Lebedev]

On Fri, Nov 13, 2015 at 11:02 PM, David Vincent-Jones
 wrote:
> darktable 2.0+git1447190176.3c611df
> openSUSE 13.2 64 bit
>
> Scrolling appears to not work in the 'collect images' window.
http://redmine.darktable.org/issues/10653#note-1

That is intentional.

> The only way that I can get to the lower (more frequent) folders is by
> directly editing the top bar.
>
> 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] usermanual update

[Roman Lebedev]

On Tue, Oct 6, 2015 at 10:07 PM, Ulrich Pegelow
<ulrich.pege...@tongareva.de> wrote:
> Am 06.10.2015 um 20:11 schrieb Roman Lebedev:
>>>
>>>
>>> Not sure if I miss something here but I observe some issues.
>>>
>>> If I select one of the presets, let's say tungsten then I can adjust the
>>> finetuning parameter to let's say 8 Mired. Now if if I go to another
>>> preset
>>> like cloudy the image will stay as it was before. I first need to
>>> manually
>>> go back to 0 Mired until the change of the preset gets reflected. I would
>>> regard a change of the preset to take precedence over any finetuning and
>>> reset that value to zero automatically.
>>>
>>> BTW: I do not see any visible effect of finetuning. I checked with images
>>> from my Canon 5DII and IIRC in the past the effect was more pronounced.
>>
>> Those 2 issues are happening for the same camera, if yes, which?
>> But i guess it means, there is simply no finetuning data for that preset.
>
>
> I double checked. It affects images from my old Canon 40D. The images from
> my 5DII behave as they should, no problem there.
>
> Here is a 40D example image showing the issue:
> https://www.dropbox.com/s/pkg1dum8blk7bf2/IMG_2049.CR2?dl=0
Like i said, no finetuning data:
https://github.com/darktable-org/darktable/blob/afd5431011b717926af35004e00a163baf9d82aa/src/external/wb_presets.c#L830-L835

>
>
> 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

Darktable on windows. Was: Re: [darktable-dev] Darktable crashes on a SIGILL

[Roman Lebedev]

And here I thought dt windows bikeshedding was explained to
death[1][2] and over :(

The problem is *not* building under windows.
The problem is maintaining it.

What *all* the people trying to bring dt to windows have been doing so
far is called packaging,
at best. As an example, thus far, no one has actually talked to us
directly, did not try to
contribute windows-related fixes/changes for 1.6.x version back into darktable.

We are working on darktable in our free time, of pure fun and
interest. There is no money involved.
Thus, darktable, being available  for some bigger circle of/to more
users does not help *us* at ALL.

It *ONLY* hurts us:
1. More users => more bugreports, while amount of developers stays constant.
2. The more darktable is popular, the bigger the chances of next
person to use it being less
skilled in at least basic debugging than the average dt user before that.
That, unfortunately, even includes uploading
/tmp/darktable_bt_XX.txt... Not all users do that :(
3. !!! Every new big chunk of "market" is always a minefield at start,
e.g.: https://redmine.darktable.org/issues/10541
That bug is probably very simple, but no one of us uses a distribution
with musl libc, so no one can debug it,
so it stays there, dormant...
4. Also, did you know that on windows, our automatic backtrace
creation would not even work, so
even getting backtrace would be harder than usual?

Now, imagine, how much of those bugs will be from windows?
None of us uses windows, for various reasons, so we are of little help there.
Of course, if there is a VERY large demand, one can do it, but ONLY
for some money as paid builds.

Thus, before darktable can be made available to any new big "market",
there needs to be a person,
whom we trust to be capable in handling all of the aspects of
maintaining darktable there.

(For a normal UNIX/BSD/Linux distribution, package maintainer is an
obvious answer, in most cases.)

So, what exactly do we mean by a maintainer?
0. Be actively involved with darktable for some time. At least half a year.
That means:
*) Stick with us in IRC.
*) actually know the code.
*) actively examine bugreports, fix bugs.
1. Be reliable and trustworthy [over that time], and more importantly,
make us believe in that.

Once 1. and 2. are complete, there is some room to discuss possibility
of making official darktable windows port and becoming it's
maintainer.

IMPORTANT: ANY OTHER APPROACH TO DARKTABLE ON WINDOWS CAN AND WILL BE
CONSIDERED HOSTILE,
HAPPENING AGAINST OUR WILL AND ACTIVELY HURTING DARKTABLE PROJECT.

[1] 
https://www.darktable.org/2015/07/why-dont-you-provide-a-windows-build/comment-page-1/#comment-46412
[2] https://discuss.pixls.us/t/darktable-on-windows-parthas-build-thread/290

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

Re: [darktable-dev] Slow startup (thumbnails regenerated?) with 1:2.0.0-0pmjdebruijn1~trusty

[Roman Lebedev]

On Tue, Dec 29, 2015 at 9:47 PM, KOVÁCS István  wrote:
> Hi,
>
> I'm on Mint 17 and use Pascal's PPA. During my investigations, I:
> - upgraded already installed version 1.6.9 with 'aptitude upgrade'
> - when I saw there's this slow startup, I removed dt with 'aptitude
> purge darktable'
> - I moved my .config/darktable to .config/darktable_ (out of the way)
> - did the same for .cache/darktable
>
> I then re-imported a folder I had been working on, and waited until
> thumbnail generation was complete. I quit and started again, but
> 'loading' the 65 thumbnails takes about 40 seconds ('loading' is in
> quotation marks because I think the thumbs are being re-generated
> during that time - see logs).
Make sure that "enable disk backend for thumbnail cache" setting
in "core options" in preferences is on.

> If I launch my self-compiled version 2.0.0, it loads very quickly
> (opening the same lighttable view, using the same config, library and
> data directories).
> If I quit and re-launch the PPA version, it loads slowly again.
> The value of 'colour-managed thumbnails' setting does not influence
> this behaviour.
>
> 'darktable -d all' logs for both launches are available here:
> http://tech.kovacs-telekes.org/files/darktable-startup-slow/
Why do people keep sending those?

>
> Thanks,
> Kofa
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] Slow startup (thumbnails regenerated?) with 1:2.0.0-0pmjdebruijn1~trusty

[Roman Lebedev]

Oh, second thought, what is the value of "number of background threads"?
I bet it is set to 1?
Due to printer detection, you want to either have it set to 2, or
compile without printer support.

On Tue, Dec 29, 2015 at 10:43 PM, KOVÁCS István  wrote:
> Roman,
>
>> Make sure that "enable disk backend for thumbnail cache" setting
>> in "core options" in preferences is on.
>
> Thanks for the quick reply. The 'enable disk backend for thumbnail
> cache' preference is ON - and since both my own build and the PPA
> version use the same .config directory, their behaviour would have
> been identical, regardless of the preference.
>
>>> 'darktable -d all' logs for both launches are available here:
>>> http://tech.kovacs-telekes.org/files/darktable-startup-slow/
>> Why do people keep sending those?
>
> Well, I'm a software developer myself, and I find logs invaluable for
> remote diagnosis. If there were useless, why would developers add
> them?
>
> I'm confused about the log line
> '[image_cache] has 61826 entries'
> printed during start-up; listing .cache/darktable gives:
> /home/kofa/.cache/darktable/:
> cached_kernels_for_GeForceGTX650
> mipmaps-6ac0672dac6fe81d5e75505cc7fa15bfeed1acf8.d
>
> /home/kofa/.cache/darktable/cached_kernels_for_GeForceGTX650:
> [omitted for brevity]
>
> /home/kofa/.cache/darktable/mipmaps-6ac0672dac6fe81d5e75505cc7fa15bfeed1acf8.d:
> 1
>
> /home/kofa/.cache/darktable/mipmaps-6ac0672dac6fe81d5e75505cc7fa15bfeed1acf8.d/1:
> [thumbs of the 80 images on my lighttable]
>
> Thanks,
> Kofa
Roman.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] crop bug?

[Roman Lebedev]

On Sat, Jan 9, 2016 at 8:41 PM, Ivan Tarozzi  wrote:
> Hi all,
Hi.

> before opening a bug report  (and try to fix and PR) I prefere to ask
> you if the following behavior is actually a bug.
>
> I use  to set the rotation angle tracing a line with right-click mouse
> on the picture. Now I'm working on a set of pictures obtained shooting
> my old slide projector (ok, not a god result, but it works to see some
> old picture on tablet and tv).
>
> I use flip-vertical on crop module, but when I set rotation using
> right-click mouse on the picture I obtain a wrong angle (wrong rotation
> direction).
Tested, looks like a bug to me...
Again crop :(

>
> Is that a bug?  Can I submit a issue on redmine?
Sure, http://redmine.darktable.org/projects/darktable/issues/new

>
> Thanks
> Ivan
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] Slow startup (thumbnails regenerated?) with 1:2.0.0-0pmjdebruijn1~trusty

[Roman Lebedev]

On Tue, Dec 29, 2015 at 11:34 PM, KOVÁCS István <kovacs...@gmail.com> wrote:
> On 29 December 2015 at 21:04, Roman Lebedev <lebedev...@gmail.com> wrote:
>> Oh, second thought, what is the value of "number of background threads"?
>> I bet it is set to 1?
>
> Bingo! If set to 2, the PPA version loads quickly. It was set to one,
> and my compiled version lacks printing support:
> === build.log ===
> -- Could NOT find CUPS (missing:  CUPS_LIBRARY CUPS_INCLUDE_DIR)
> -- Print mode: disabled, please install CUPS dev package
> === build.log ===
>
> What's the better option on an old machine (8 years old Core2 Duo, 4 GB RAM):
> - roll my own (without printer support) and set 'number of background
> threads' to 1 to conserve resources
> - go with the PPA and set 'number of background threads' to 2 (if it's
> safe with such a low-end machine)
We do acknowledge that neither of the cases is optimal, so we will try
to fix it some other way in the future.

If you _really_ see that the performance is that much worse with 2
threads, i'd go with self-compile.

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

[darktable-dev] Anyone with 30-bit color depth?

[Roman Lebedev]

Hello, lists.

darktable's support for 30-bit color depth was again brought up in IRC
channel yesterday.

As far as i'm aware, none of us developers has the hardware (videocard
that supports
30-bit output + 30-bit monitor), so we have no means to test and
develop needed changes.

Traditional answer to the issue would be "not before someone donates
30-bit videocard +
30-bit wide-gamut display to one of developers".

However, is there anyone reading this lines, who
1. already has all of the 30-bit-enabled hardware AND
2. is running X in 30-bit color depth AND
3. uses darktable AND
4. has some basic debugging/development skills?

IF there is such a person, *MAYBE* we could make all the necessary changes and
test them with his/her help.

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

Re: [darktable-dev] darktable-generate-cache puzzled

[Roman Lebedev]

Thank you for reporting this, it should be fixed now in the following commit:

commit 0ae79c07257923457914f5e63e19355d7772c624
Author: Roman Lebedev <lebedev...@gmail.com>
Date:   Mon Jun 6 21:56:34 2016 +0300

Generate-cache: comparing signed and unsigned integers is bad

Fixes a bug introduced in previous commit.
min_mip is dt_mipmap_size_t, which is unsigned,
and k is signed. So when k becomes -1, it is
4294967295, which is bigger than any maximal
mipmap size (7), so we have issues...


Roman.

On Mon, Jun 6, 2016 at 9:07 PM, Wolfgang Goetz <wolfgang.zt...@web.de> wrote:
> Hi,
>
> actual git build has problems with darktable-generate-cache:
>
> strace -f -o dtgenc.str /usr/bin/darktable-generate-cache
> creating complete lighttable thumbnail cache
> creating cache directories
> creating cache directory 
> '/home/goetz/.cache/darktable/mipmaps-a4cd72ccd971fe7e3411548419df6506c774f32f.d/0'
> creating cache directory 
> '/home/goetz/.cache/darktable/mipmaps-a4cd72ccd971fe7e3411548419df6506c774f32f.d/1'
> creating cache directory 
> '/home/goetz/.cache/darktable/mipmaps-a4cd72ccd971fe7e3411548419df6506c774f32f.d/2'
> [..consuming 100% cpu, manually ^c after a while...]
>
>
> from above strace:
> 4407 
> access("/home/goetz/.cache/darktable/mipmaps-a4cd72ccd971fe7e3411548419df6506c774f32f.d/-69735/1.jpg",R_OK)
>  = -1 ENOENT (No such file or directory)
>
>
>
>
>
>
> check: older one is ok:
> commit 023110ecf102f37fe3e82a692a81e3478dc5995b
> Author: johannes hanika <hana...@gmail.com>
> Date:   Mon May 16 20:39:38 2016 +0200
>
>
> /opt/darktable/bin/darktable-generate-cache
> ...
> image 52803/52805 (100,00%)
> image 52804/52805 (100,00%)
> image 52805/52805 (100,00%)
> done
>
>
>
>
>
>
> kind regards
> Wolfgang
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Compile error in Ubuntu Xenial using osm-gps-map

[Roman Lebedev]

Have you tried something like this
$ cd darktable/build/ && rm -rf * && cmake ../ && make
already?

Which osm-gps-map version is that, specifically?

Roman.

On Mon, May 30, 2016 at 6:30 PM, Darrell Eifert  wrote:
> Hello --
>
> I just recently updated to Ubuntu Xenial and tried to compile the latest 
> version of Darktable from Git using both ./build.sh and cmake from the 
> appropriate directories. Both times the compiler got about 44% of the way 
> through, and then stopped with the following message:
>
> /home/administrator/darktable/src/views/map.c:284:13: error: static 
> declaration of ‘osm_gps_map_zoom_fit_bbox’ follows non-static declaration
>  static void osm_gps_map_zoom_fit_bbox(OsmGpsMap *map, float latitude1, float 
> l
>  ^
> In file included from /usr/include/osmgpsmap-1.0/osm-gps-map-layer.h:43:0,
>  from /usr/include/osmgpsmap-1.0/osm-gps-map.h:24,
>  from /home/administrator/darktable/src/views/view.h:29,
>  from /home/administrator/darktable/src/libs/lib.h:23,
>  from /home/administrator/darktable/src/control/control.h:33,
>  from /home/administrator/darktable/src/views/map.c:27:
> /usr/include/osmgpsmap-1.0/osm-gps-map-widget.h:88:17: note: previous 
> declaration of ‘osm_gps_map_zoom_fit_bbox’ was here
>  voidosm_gps_map_zoom_fit_bbox   (OsmGpsMap *map, 
> float
>  ^
> src/views/CMakeFiles/map.dir/build.make:62: recipe for target 
> 'src/views/CMakeFiles/map.dir/map.c.o' failed
> make[2]: *** [src/views/CMakeFiles/map.dir/map.c.o] Error 1
> CMakeFiles/Makefile2:1812: recipe for target 
> 'src/views/CMakeFiles/map.dir/all' failed
> make[1]: *** [src/views/CMakeFiles/map.dir/all] Error 2
> Makefile:149: recipe for target 'all' failed
> make: *** [all] Error 2
>
> -
>
> I've done a quick search for solutions, but haven't seen anything.  Thanks in 
> advance for ideas on a fix or workaround.
>
> -- Darrell
> ___
> 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] Manjaro XFCE compiling error

[Roman Lebedev]

On Wed, Jun 15, 2016 at 4:11 PM, João Horta  wrote:
> Pacotes (1) darktable-git-release.2.1.0.r1148.g3267c6b-1
>
> Tamanho Total Instalado: 13,92 MiB
> Tamanho de Atualização da Internet:   0,00 MiB
>
> :: Continuar a instalação? [S/n]
> (1/1) a verificar chaves no chaveiro   [##]
> 100%
> (1/1) a verificar integridade dos pacotes  [##]
> 100%
> (1/1) a carregar ficheiros dos pacotes [##]
> 100%
> (1/1) a verificar conflitos em ficheiros   [##]
> 100%
> erro: falhou ao submeter a transação (ficheiros em conflito)
> darktable-git: /usr/lib64 existe no sistema de ficheiros
> darktable-git: /usr/lib64/darktable/libdarktable.so existe no sistema de
> ficheiros
> darktable-git: /usr/lib64/darktable/plugins/imageio/format/libcopy.so existe
> no sistema de ficheiros
> darktable-git: /usr/lib64/darktable/plugins/imageio/format/libexr.so existe
> no sistema de ficheiros
> darktable-git: /usr/lib64/darktable/plugins/imageio/format/libj2k.so existe
> no sistema de ficheiros
> darktable-git: /usr/lib64/darktable/plugins/imageio/format/libjpeg.so existe
> no sistema de ficheiros
> darktable-git: /usr/lib64/darktable/plugins/imageio/format/libpdf.so existe
> no sistema de ficheiros
> darktable-git: /usr/lib64/darktable/plugins/imageio/format/libpfm.so existe
> no sistema de ficheiros
> darktable-git: /usr/lib64/darktable/plugins/imageio/format/libpng.so existe
> no sistema de ficheiros
> darktable-git: /usr/lib64/darktable/plugins/imageio/format/libppm.so existe
> no sistema de ficheiros
> darktable-git: /usr/lib64/darktable/plugins/imageio/format/libtiff.so existe
> no sistema de ficheiros
> darktable-git: /usr/lib64/darktable/plugins/imageio/format/libwebp.so existe
> no sistema de ficheiros
> darktable-git: /usr/lib64/darktable/plugins/imageio/storage/libdisk.so
> existe no sistema de ficheiros
> darktable-git: /usr/lib64/darktable/plugins/imageio/storage/libemail.so
> existe no sistema de ficheiros

Not everyone speaks !english :)

There were changes to the cmake build system, probably some
adjustments are needed.
Incomplete list:
https://github.com/darktable-org/darktable/pull/1039#issuecomment-225953306

>
> ...
> ...
> ...
> ...
> etc.etc...
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] No lua support with Fedora

[Roman Lebedev]

On Sun, Jan 10, 2016 at 10:47 PM, Colin Adams  wrote:
> I see.
>
> This is never going to get resolved, if Lua releases are not backwards
> compatible. But presumably I can compile in support for Lua 5.2? Do I just
> install Lua 5.2 from source on my system, and then rebuild darktable?
Or just build darktable and pass -DDONT_USE_INTERNAL_LUA=off to cmake.

>
> On 10 January 2016 at 19:32, Germano Massullo 
> wrote:
>>
>> Do an internet search in both fedora and darktable development list.
>> The problem has been discussed many times
>> http://www.kappit.com/img/pics/201412_1954_eegba_sm.jpg
>
>
>
> ___
> 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

[darktable-dev] Re: [darktable-devel] How to set the UI language in DT 2.0?

[Roman Lebedev]

YOU ARE USING OLD MAIL LIST !!!


On Sun, Feb 7, 2016 at 12:51 PM, Sven Claussner  wrote:
> Hi,
Hi.

>
> I'd like to set the UI language for DT 2.0.
> Trying to set LANG=C or with a country specific code failed.
> How can I achieve this?
$ echo "ui_last/gui_language=de" >> ~/.config/darktable/darktablerc && darktable

>
> Greetings
>
> Sven
Roman.

>
>
> 
> Sie interessieren sich für wunderschöne Malereien,
> Märchenbücher und Heimtextilien?
> Dann schauen Sie mal rein: http://www.unikate4you.de !
>
> --
>
>
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
> ___
> darktable-devel mailing list
> darktable-de...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/darktable-devel
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Some Questions on monochrome

[Roman Lebedev]

On Sat, Apr 9, 2016 at 12:23 AM, Helena Henkel  wrote:
> Hallo,
Hi.

> thank you for your good work on darktable.
>
> I have two questions:
>
> 1) Can you explain what in the demosaize module the method "passthrough
> (monochrome)" (in german "durchschleifen") is dedicated for?
It is for the cameras with Bayer sensor with color filter array _physically_
removed. I.e. physically scraped off, or physically deleted in some other way.

>I played
> with it and I like the look of it somehow, because it interpolates in a
> very clear and sharp way, but also somewhat vintage.
It is not intended to be used as a generic module to turn an image into
monochrome.

> But when I tried to
> export the image, it was still in color and not like I have seen in the
> preview.
> I suppose it is not meant for cameras with Bayer sensor technology, but
> still, could you make the export possible?
I do not follow. I suspect a user error, but i will check what could be wrong..

> 2) In the standard monochrome module, would it be possible to include
> some color picker tool which helps to choose the area on the color
> matrix where I want to filter my image?
Does that module not have blend menu enabled?
If it does, just set it to "drawn mask" and drawn the area of effect.
https://www.darktable.org/usermanual/ch03s02s05.html.php

> If these things are not possible, it doesn't matter, darktable is
> already a good tool. :)
Thank you :)

> Thanks a lot,
> Helena
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] Wrong colors in exported images when using split toning

[Roman Lebedev]

On Tue, Mar 22, 2016 at 11:31 PM, J. Liles  wrote:
> A little more information... Here are two screenshots showing the color
> picker results for the central area of the DNG and the PNG freshly exported
> from it:
>
> http://imgur.com/a/dnIxF
>
> The DNG shows an RGB value of 65,44,42, while the export shows a value of
> 58,46,42.
https://redmine.darktable.org/issues/10389
Color picker works in _display_ color profile, so you need to set
display color profile
to sRGB if you want to be able to somehow compare those values.
Also, splittoning is also applied in rgb colorspace, so in darkroom -
in display color space.

>
> Any ideas as to what could cause this discrepency?
>
> I repeated the same experiment on an image without split toning or any other
> modules active and the results also differ, so I no longer believe that the
> problem is specific to split-toning, although that did make it more
> noticeable.
>
> Here are the numbers for the image with no modules: 34,36,38 for the DNG and
> 36,33,42 for the PNG.
>
> FYI, I don't think I mentioned it before, but all of this this applies
> regardless of whether sRGB softproofing is enabled when viewing the DNG.
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 alternative to Markesteijn x-trans demosaic?

[Roman Lebedev]

On Mon, Mar 21, 2016 at 11:06 PM, Ingo Liebhardt
<ingo.liebha...@ziggo.nl> wrote:
> Hi Roman,
>
> A while ago, I asked if there’s maybe interest in a demosaic alternative for
> the Fuji x-trans sensor, next to the present alternatives VNG and
> Markesteijn.
>
> In the dropbox link below, you can find some sample images (always a variant
> with 3-pass Markesteijn and with an approach I was trying out), if you want
> to have e look (demosaic algorithm identified by file name).
> Especially the high-contrast edges of the buildings might be interesting to
> look at.
>
> In any case, my approach is also still very experimental, and I don’t know
> if there’s interest as such?
>
> If you’ve more questions, just let me know.
Nono, all that i did read and understood.

I was specifically referring to the word "marketable".

>
> Cheers,
> Ingo
Roman.

> Am 21.03.2016 um 20:45 schrieb Roman Lebedev <lebedev...@gmail.com>:
>
> On Mon, Mar 21, 2016 at 10:40 PM, Ingo Liebhardt
> <ingo.liebha...@ziggo.nl> wrote:
>
> Hi Dan, and of course all potentially interested in x-trans demosaicing,
>
> In the meanwhile, I continued work on my algorithm and it’s now sufficiently
> stable that I can start -
> 1. documenting it, and
> 2. trying to make a branch off of
> marketable
>
> What is that thing people keep talking about?
>
> master, following your below
> suggestion.
>
> As you might have seen from yesterday’s mails, I’m trying to start getting
> accustomed to dark table’s code and to where to find what.
>
> If you’re interested, I prepared some sample images using the original
> Markesteijn and my approach (all tif, as they come out of dcraw, so beware
> of the large files):
> https://www.dropbox.com/sh/un1y11uimbqxjjk/AAD3L-Rs9-ztwyBIm4rnCzK-a?dl=0
>
> A couple of further notes:
> The algorithm itself is clear and succinct, no worries. Please don’t be
> deceived by the code, which doesn’t look succinct… It is plain OpenCL host
> code without any wrapper, and that is awfully verbose. Concerning the
> kernels, some also don’t look succinct, but that’s because I tried to use
> constants rather than the far more succinct calculation rules, already
> bearing performance in mind.
>
> Actually, I managed to reach a better quality in the meanwhile by not only
> interpolating horizontally and vertically, but also diagonally. This is
> something that you can only do with x-trans, so an advantage when compared
> to Bayer.
> Unfortunately it came with a performance penalty (no surprise), but I’m
> confident that there’s room for further performance improvement later on.
> Presently I’m back to around 13 seconds :-(
> I also dropped the iterative approach, as I could not guarantee convergence.
> Some images were even deteriorating with more than one iteration, others
> were barely improving. All in all not satisfactory, so the approach is now
> non-iterative: no loop.
>
> One other comment: I think that even now, darktable’s x-trans support is
> more than just experimental. Even many commercial raw converters have quite
> some difficulties with these x-trans files…
> Some commercial products try to hide these problems by quite a degree of
> softening, but they’re still there.
> You also might want to consider that even Bayer CFAs cause quite some moiré
> and false colour artifacts if they don’t have an AA filter.
> Doing some expectation management here ;-)
>
>
> Cheers,
> Ingo
>
> Roman.
>
>
>
> Am 15.02.2016 um 04:47 schrieb Dan Torop <d...@pnym.net>:
>
> Hi Ingo,
>
> Interesting to hear about the speed. That sounds promising. Here my
> not-that-spectacular laptop is running darktable's Markesteijn
> 1-pass/3-pass demosaic in approx. 1.4sec./3.8sec. respectively on the
> CPU for 16 MP images. But there's no reason to worry about optimization
> this early on. The code only got that fast after it was heavily worked
> over by Ingo Weyrich from the RawTherapee project. Ulrich Pegelow's
> recent OpenCL implementation of Markesteijn is now making a significant
> difference for those with the hardware.
>
> It strikes me that there are very few people out there with the
> mathematical knowledge and focus to craft a new demosaicing algorithm
> for a novel sensor. Well worth pursuing if you're one who can do this.
> The ideal algorithm would be succinct and clear, of course, but is that
> possible?
>
> If you're interested in darktable users testing it, one approach would
> be to make a branch off of darktable master and add your work as an
> alternative demosaic algorithm? This would give people in the dt
> community an easy route to test it. Though it could also build
> expectations for what is 

Re: [darktable-dev] Re: proposal : clipping iop replacement

[Roman Lebedev]

On Sun, Mar 27, 2016 at 11:02 PM, Torsten Bronger
 wrote:
> Hallöchen!
>
> AlicVB writes:
>
>> [...]
>>
>> 2 : Deprecate c, and rewrite their features in different iop(s) :
>>
>> 2.a : merge rotation and perspective inside lensfun () and do a
>> special iop for cropping only. It has the advantage to concentrate
>> all interpolation inside lensfun iop, we lost the actual c ui,
>> which works quite well from an user pov
>
> Just lurking, so maybe I'm missing context, but Lensfun has grown
> the ability to do perspective correction and rotation.  Thus, PC,
> rotation, anti-distortion, and anti-TCA could be done without
> leaving floating point space.  Moreover, Lensfun's auto-scaling
> would take all of them into account.
>
> Status of rotation and PC: Both are in master but in no release yet.
> Lensfun's PC is the most feature-rich as far as I can see (circles,
> fine-tuning parameter, see
> http://wilson.bronger.org/lensfun/perspective-correction.html) and
> covered with tests, but it doesn't have auto detection of lines or
> serious performance tests.
Yes, that is exactly what i am proposing to replace current c
features with. That is the best case solution in my opinion.

Caveat 1: "Both are in master but in no release yet."
So we will need to keep the same implementation in lens.c,
for those lf versions which did not have PC functionality.

Caveat 2: at first i was going to say that lf is currently a soft-dep,
but it is a hard-dep, so all good.

> Tschö,
> Torsten.
Roman.

>
> --
> Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.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] Re: latest darktable git & tarbal failed to build

[Roman Lebedev]

On Sun, Mar 20, 2016 at 9:40 PM, wim vandenbussche
 wrote:
>> especially libexif:
>> # cd /usr/local && find -name *libexif* -delete
>>
>> This looks very much like C++ ABI difference, i.e. darktable is being 
>> compiled
>> with new C++11 ABI, while that libexif2 is still compiled with old ABI.
>>
>> Roman.
>>
>
> I tried with the libexif - delete part but the error stays the same. when I
> do the build.sh. I also removed the build directory again but to no avail.
No clue then. Something on your particular install is broken.
Try to find out which exif2 is used, and why it does not build.

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 alternative to Markesteijn x-trans demosaic?

[Roman Lebedev]

On Mon, Mar 21, 2016 at 10:40 PM, Ingo Liebhardt
 wrote:
> Hi Dan, and of course all potentially interested in x-trans demosaicing,
>
> In the meanwhile, I continued work on my algorithm and it’s now sufficiently
> stable that I can start -
> 1. documenting it, and
> 2. trying to make a branch off of
> marketable
What is that thing people keep talking about?

> master, following your below
> suggestion.
>
> As you might have seen from yesterday’s mails, I’m trying to start getting
> accustomed to dark table’s code and to where to find what.
>
> If you’re interested, I prepared some sample images using the original
> Markesteijn and my approach (all tif, as they come out of dcraw, so beware
> of the large files):
> https://www.dropbox.com/sh/un1y11uimbqxjjk/AAD3L-Rs9-ztwyBIm4rnCzK-a?dl=0
>
> A couple of further notes:
> The algorithm itself is clear and succinct, no worries. Please don’t be
> deceived by the code, which doesn’t look succinct… It is plain OpenCL host
> code without any wrapper, and that is awfully verbose. Concerning the
> kernels, some also don’t look succinct, but that’s because I tried to use
> constants rather than the far more succinct calculation rules, already
> bearing performance in mind.
>
> Actually, I managed to reach a better quality in the meanwhile by not only
> interpolating horizontally and vertically, but also diagonally. This is
> something that you can only do with x-trans, so an advantage when compared
> to Bayer.
> Unfortunately it came with a performance penalty (no surprise), but I’m
> confident that there’s room for further performance improvement later on.
> Presently I’m back to around 13 seconds :-(
> I also dropped the iterative approach, as I could not guarantee convergence.
> Some images were even deteriorating with more than one iteration, others
> were barely improving. All in all not satisfactory, so the approach is now
> non-iterative: no loop.
>
> One other comment: I think that even now, darktable’s x-trans support is
> more than just experimental. Even many commercial raw converters have quite
> some difficulties with these x-trans files…
> Some commercial products try to hide these problems by quite a degree of
> softening, but they’re still there.
> You also might want to consider that even Bayer CFAs cause quite some moiré
> and false colour artifacts if they don’t have an AA filter.
> Doing some expectation management here ;-)
>
>
> Cheers,
> Ingo
Roman.

>
>
> Am 15.02.2016 um 04:47 schrieb Dan Torop :
>
> Hi Ingo,
>
> Interesting to hear about the speed. That sounds promising. Here my
> not-that-spectacular laptop is running darktable's Markesteijn
> 1-pass/3-pass demosaic in approx. 1.4sec./3.8sec. respectively on the
> CPU for 16 MP images. But there's no reason to worry about optimization
> this early on. The code only got that fast after it was heavily worked
> over by Ingo Weyrich from the RawTherapee project. Ulrich Pegelow's
> recent OpenCL implementation of Markesteijn is now making a significant
> difference for those with the hardware.
>
> It strikes me that there are very few people out there with the
> mathematical knowledge and focus to craft a new demosaicing algorithm
> for a novel sensor. Well worth pursuing if you're one who can do this.
> The ideal algorithm would be succinct and clear, of course, but is that
> possible?
>
> If you're interested in darktable users testing it, one approach would
> be to make a branch off of darktable master and add your work as an
> alternative demosaic algorithm? This would give people in the dt
> community an easy route to test it. Though it could also build
> expectations for what is already only "experimental" x-trans support in
> dt.
>
> As you write, despite the debatable virtues of x-trans, the cameras are
> fine enough that it has become worth the work to deal with the sensors.
> But so much knowledge and effort has gone into demosaicing Bayer sensors
> that is hard to imagine that comparably fast and good algorithms for
> x-trans anytime soon.
>
> It is striking to read the original patent application for the Bayer
> sensor (https://www.google.com/patents/US3971065) and see how it was
> envisioned to allow usable results from my very simple processing.
> X-Trans seems much more a fly-by-wire version of a sensor, requiring all
> sorts of intervention to produce decent output...
>
> Dan
>
>
>
> On Sun, Feb 14, 2016, at 01:04 PM, Ingo Liebhardt wrote:
>
> Hi Dan,
>
> To come back briefly on the profiling.
>
> After two passes there are indeed no further visible improvements in image
> quality.
>
> With two passes and some more minor tweaking I’m now at 7.6 seconds with my
> not too spectacular laptop hardware.
>
> I also tried DCI for red and blue reconstruction once the green is there,
> but it didn’t look good at all. More false colour artifacts.
>
> Cheers,
> Ingo
>
>
> Am 08.02.2016 um 23:52 schrieb Dan Torop :
>
> Hi Ingo,
>
> This 

Re: [darktable-dev] weird colours when using several color modules

[Roman Lebedev]

Hello all.

I expect this to be fixed by:

commit 8e859e9b890203eba7dae77bc9f61ab134c4d81e
Author: Roman Lebedev <lebedev...@gmail.com>
Date:   Fri May 20 19:54:20 2016 +0300

Rawprepare: properly adjust proper filters. AKA: adjust fresh filters once.

Fixes full pipe going all pink in certain situations, e.g. after sclaing
window.

Reported by Marc Cousin on darktable-dev list.

The root cause is the fact that we reuse pipe structure every time,
and don't recreate it from zero. So on the second run, it would
adjust already adjusted filters, cropping them second time,
and in case of irregular x-trans pattern, that has very high
chances to not work.


If it is still reproducible, please let me know.

Roman.

On Thu, May 19, 2016 at 8:36 PM, Roman Lebedev <lebedev...@gmail.com> wrote:
> On Thu, May 19, 2016 at 8:22 PM, David Vincent-Jones <david...@gmail.com> 
> wrote:
>> Simply moving dt from one display screen to another while open in the
>> darkroom mode was sufficient to bring on the magenta cast. dt was resized as
>> a part of the move.
> Awesome hint, rescaling dt window finally reproduces the issue every time.
> Thank you!
>
> I will try to look into that tomorrow...
>
>> David
> Roman.
>
>> On 05/18/2016 12:31 PM, Roman Lebedev wrote:
>>>
>>> On Wed, May 18, 2016 at 10:15 PM, David Vincent-Jones
>>> <david...@gmail.com> wrote:
>>>>
>>>> Not sure why I am getting that version information ... I am using the
>>>> OpenSUSE nightly build and it appears to me to include all of the latest
>>>> bells and whistles.
>>>
>>> Okay, which one specifically?
>>>
>>> https://build.opensuse.org/package/show/home:darix:darktable:master/darktable
>>> ?
>>>
>>>> I reported the result of $darktable --version which is the same that I
>>>> see
>>>> on the dt screen.
>>>
>>> Good. But that is broken and needs to be fixed.
>>> So we'd like to know who provides those nightly builds :)
>>>
>>>> David
>>>
>>> Roman.
>>>
>>>> On 05/18/2016 11:51 AM, Roman Lebedev wrote:
>>>>>
>>>>> On Wed, May 18, 2016 at 9:37 PM, David Vincent-Jones<david...@gmail.com>
>>>>> wrote:
>>>>>>>
>>>>>>> I am running on a fresh install ver:1.7.0.1463568662.d724dea
>>>>>
>>>>> Huh?
>>>>> How do you build darktable?
>>>>> It should be 2.1.0something
>>>>>
>>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] weird colours when using several color modules

[Roman Lebedev]

On Wed, May 18, 2016 at 10:15 PM, David Vincent-Jones
<david...@gmail.com> wrote:
> Not sure why I am getting that version information ... I am using the
> OpenSUSE nightly build and it appears to me to include all of the latest
> bells and whistles.
Okay, which one specifically?
https://build.opensuse.org/package/show/home:darix:darktable:master/darktable ?

> I reported the result of $darktable --version which is the same that I see
> on the dt screen.
Good. But that is broken and needs to be fixed.
So we'd like to know who provides those nightly builds :)

> David
Roman.

> On 05/18/2016 11:51 AM, Roman Lebedev wrote:
>>
>> On Wed, May 18, 2016 at 9:37 PM, David Vincent-Jones<david...@gmail.com>
>> wrote:
>>>
>>> >I am running on a fresh install ver:1.7.0.1463568662.d724dea
>>
>> Huh?
>> How do you build darktable?
>> It should be 2.1.0something
>>
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Re: PSA: OpenSUSE nightly builds have moved.

[Roman Lebedev]

On Wed, May 18, 2016 at 11:29 PM, David Vincent-Jones
<david...@gmail.com> wrote:
> The repos are not accepting this url currently ... maybe I need to be
> patient?
(i'm using debian, so it was impossible for me to change anything)

I guess, i should have linked this, but i fear the url is too long:
https://software.opensuse.org/download.html?project=home%3Adarix%3Adarktable%3Amaster=darktable

Otherwise, in the url i linked in the mail, are you trying to add it itself,
instead of one of the distro-specific links that is listed on that page?

> David
Roman.

> On 05/18/2016 01:23 PM, Roman Lebedev wrote:
>>
>> Hello all users of darktable on opensuse :)
>>
>>  From now on, the recommended repository for darktable nightly builds is
>> http://download.opensuse.org/repositories/home:/darix:/darktable:/master/
>>
>> https://www.darktable.org/install/#opensuse has been updated.
>>
>> Roman.
>>
>> On Wed, May 18, 2016 at 10:35 PM, David Vincent-Jones
>> <david...@gmail.com> wrote:
>>>
>>> This should tell all!!
>>>
>>> http://download.opensuse.org/repositories/home:/toganm:/photography/
>>>
>>> As referenced on the dt site.
>>>
>>> David
>>>
>>>
>>> On 05/18/2016 12:31 PM, Roman Lebedev wrote:
>>>>
>>>> On Wed, May 18, 2016 at 10:15 PM, David Vincent-Jones
>>>> <david...@gmail.com> wrote:
>>>>>
>>>>> Not sure why I am getting that version information ... I am using the
>>>>> OpenSUSE nightly build and it appears to me to include all of the
>>>>> latest
>>>>> bells and whistles.
>>>>
>>>> Okay, which one specifically?
>>>>
>>>>
>>>> https://build.opensuse.org/package/show/home:darix:darktable:master/darktable
>>>> ?
>>>>
>>>>> I reported the result of $darktable --version which is the same that I
>>>>> see
>>>>> on the dt screen.
>>>>
>>>> Good. But that is broken and needs to be fixed.
>>>> So we'd like to know who provides those nightly builds :)
>>>>
>>>>> David
>>>>
>>>> Roman.
>>>>
>>>>> On 05/18/2016 11:51 AM, Roman Lebedev wrote:
>>>>>>
>>>>>> On Wed, May 18, 2016 at 9:37 PM, David
>>>>>> Vincent-Jones<david...@gmail.com>
>>>>>> wrote:
>>>>>>>>
>>>>>>>> I am running on a fresh install ver:1.7.0.1463568662.d724dea
>>>>>>
>>>>>> Huh?
>>>>>> How do you build darktable?
>>>>>> It should be 2.1.0something
>>>>>>
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] PSA: OpenSUSE nightly builds have moved.

[Roman Lebedev]

Hello all users of darktable on opensuse :)

>From now on, the recommended repository for darktable nightly builds is
http://download.opensuse.org/repositories/home:/darix:/darktable:/master/

https://www.darktable.org/install/#opensuse has been updated.

Roman.

On Wed, May 18, 2016 at 10:35 PM, David Vincent-Jones
<david...@gmail.com> wrote:
> This should tell all!!
>
> http://download.opensuse.org/repositories/home:/toganm:/photography/
>
> As referenced on the dt site.
>
> David
>
>
> On 05/18/2016 12:31 PM, Roman Lebedev wrote:
>>
>> On Wed, May 18, 2016 at 10:15 PM, David Vincent-Jones
>> <david...@gmail.com> wrote:
>>>
>>> Not sure why I am getting that version information ... I am using the
>>> OpenSUSE nightly build and it appears to me to include all of the latest
>>> bells and whistles.
>>
>> Okay, which one specifically?
>>
>> https://build.opensuse.org/package/show/home:darix:darktable:master/darktable
>> ?
>>
>>> I reported the result of $darktable --version which is the same that I
>>> see
>>> on the dt screen.
>>
>> Good. But that is broken and needs to be fixed.
>> So we'd like to know who provides those nightly builds :)
>>
>>> David
>>
>> Roman.
>>
>>> On 05/18/2016 11:51 AM, Roman Lebedev wrote:
>>>>
>>>> On Wed, May 18, 2016 at 9:37 PM, David Vincent-Jones<david...@gmail.com>
>>>> wrote:
>>>>>>
>>>>>> I am running on a fresh install ver:1.7.0.1463568662.d724dea
>>>>
>>>> Huh?
>>>> How do you build darktable?
>>>> It should be 2.1.0something
>>>>
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Fujifilm X100 blackpoint issue

[Roman Lebedev]

On Tue, May 24, 2016 at 6:44 PM, J. Liles  wrote:
>
>
> On Tue, May 24, 2016 at 5:40 AM, johannes hanika  wrote:
>>
>> hi,
>>
>> the good news is your black levels look very uniform there, so no
>> change required.
>>
>> if you have a sample where these are actually different.. rawspeed
>> only supports a hardcoded amount of 4 black levels today. no big deal
>> changing it, but without a use case i don't think we should.
>>
>> cheers,
>>  jo
>>
>>
>
> In every one I've looked at, all the values have matched. At least with the
> X70 and the shooting modes I've tried.
>
> Indeed, locally I changed the == 4 to >= 4 when interpreting this tag in
> rawspeed's RafDecoder.cpp and that seemed to do the trick to get the first 4
> black levels into darktable.
Hm, and without this change, what values does the darktable receive?
Something very different?

>>
>> On Mon, May 23, 2016 at 8:36 PM, J. Liles  wrote:
>> > FYI this change does not help with the Fuji X70 black levels. Here's
>> > what
>> > the black level tag looks like for the X70 and other newer fuji cameras:
>> >
>> > Black Level : 1026 1026 1026 1026 1026 1026 1026
>> > 1026
>> > 1026 1026 1026 1026 1026 1026 1026 1026 1026 1026 1026 1026 1026 1026
>> > 1026
>> > 1026 1026 1026 1026 1026 1026 1026 1026 1026 1026 1026 1026 1026
>> >
>> >
>> > On Sun, May 15, 2016 at 10:27 AM, johannes hanika 
>> > wrote:
>> >>
>> >> see
>> >>
>> >> https://github.com/darktable-org/darktable/pull/1202
>> >>
>> >> j.
>> >>
>> >> On Mon, May 16, 2016 at 5:02 AM, Martijn Kruiten 
>> >> wrote:
>> >> > Yes, I thought it was amazing too. Thanks for looking into it!
>> >> >
>> >> > Op zo 15 mei 2016 om 17:40 schreef johannes hanika
>> >> > :
>> >> >>
>> >> >> oh, right. thanks for pointing that out. amazing what a difference
>> >> >> this small change makes. i shall look into pushing that into
>> >> >> rawspeed's camera.xml then.
>> >> >>
>> >> >> -j.
>> >> >>
>> >> >> On Mon, May 16, 2016 at 3:14 AM, Martijn Kruiten
>> >> >> 
>> >> >> wrote:
>> >> >> > Correction: it obviously varies with ISO /and/ some other
>> >> >> > variables.
>> >> >> >
>> >> >> > Op zo 15 mei 2016 om 17:10 schreef Martijn Kruiten
>> >> >> > :
>> >> >> >>
>> >> >> >> Your blackpoint was not the same as the value that was reported
>> >> >> >> in
>> >> >> >> the
>> >> >> >> Google Groups issue. I changed it to be the same and that fixed
>> >> >> >> it,
>> >> >> >> so
>> >> >> >> that's definitely where the issue is
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> (https://www.dropbox.com/s/d3h5uwwoj7xe4w7/DSCF3831-Darktable_blackpointfix.png?dl=0).
>> >> >> >>
>> >> >> >> Quote from the group:
>> >> >> >>
>> >> >> >> "Camconst.json cannot help with BL because it is not steady in
>> >> >> >> every
>> >> >> >> ISO
>> >> >> >> but varies depending on other settings (exposure time should be
>> >> >> >> one),
>> >> >> >> sensors temperature etc.
>> >> >> >>
>> >> >> >> I converted the samples provided (see forum link) to DNG and
>> >> >> >> there
>> >> >> >> one
>> >> >> >> can
>> >> >> >> see that while the first 3200ISO sample (DSC3831) has BL
>> >> >> >> 253-258-258-253 the
>> >> >> >> other two samples at 3200ISO have BL 251-260-260-251,
>> >> >> >> 251-263-263-250
>> >> >> >> (channel order is R-G1-G2-B) .."
>> >> >> >>
>> >> >> >> So the blackpoint varies with ISO and maybe some other variables
>> >> >> >> and
>> >> >> >> should be read out for each image independently.
>> >> >> >>
>> >> >> >> Regards,
>> >> >> >>
>> >> >> >> Martijn
>> >> >> >>
>> >> >> >> Op zo 15 mei 2016 om 16:43 schreef johannes hanika
>> >> >> >> :
>> >> >> >>>
>> >> >> >>> well, we're not using dcraw and the black point (as you can see
>> >> >> >>> in
>> >> >> >>> the
>> >> >> >>> screenshot) is the same as the one in the google groups issue
>> >> >> >>> you
>> >> >> >>> posted after the fix. possibly the black point is a red herring
>> >> >> >>> here.
>> >> >> >>>
>> >> >> >>> j.
>> >> >> >>>
>> >> >> >>> On Mon, May 16, 2016 at 2:32 AM, Martijn Kruiten
>> >> >> >>> 
>> >> >> >>> wrote:
>> >> >> >>> > Hi Johannes,
>> >> >> >>> >
>> >> >> >>> > I only pushed a few stops to exaggerate it. I'm seeing green
>> >> >> >>> > shadows
>> >> >> >>> > even in
>> >> >> >>> > well lit daylight ISO 1600 shots without exposure
>> >> >> >>> > compensation,
>> >> >> >>> > but
>> >> >> >>> > i
>> >> >> >>> > felt
>> >> >> >>> > this image could demonstrate it much better. Also, in your
>> >> >> >>> > screenshot
>> >> >> >>> > the
>> >> >> >>> > shadows are still green, just less obvious because they are
>> >> >> >>> > darker.
>> >> >> >>> > They are
>> >> >> >>> > not green in Adobe Camera Raw, DxO and Aperture and they
>> >> >> >>> > aren't
>> >> >> >>> > in
>> >> >> >>> > RawTherapee either, all at default settings, white balance as
>> 

Re: [darktable-dev] Darktable 2.0.5

[Roman Lebedev]

On Tue, May 24, 2016 at 8:46 PM, Jefferson Ferreira
 wrote:
> Hi,
>
> I have three questions to make:
>
> 1. I would like to know if the next version of darktable will bring the new
> modules Liquify and Perspective ?
2.2.0

> 2. I would like to know if the darktable developers are working in some
> tool/module that make the same work as the "Plugins -> Color Equalizer" of
> the AfterShot (or LightZone) ?
I don't think anyone is working on anything like that.

> The module "Color Zone" should do the same
> task, but is much more difficult to catch the same result and so fast ...
>
> 3. The lua-widget ( separator ) could contain a line to separate the
> elements ? Exists a elements "list box" in lua api ?
>
> Thanks in advance.
>
>
> --
> Jefferson Ferreira
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] Another git compilation problem

[Roman Lebedev]

On Sun, May 1, 2016 at 2:10 PM, Alexander Rabtchevich
 wrote:
> Hello
>
> Here is the result of the recent attempt. The processor is AMD Phenom 1075T.
>
> Linking C shared module libclipping.so
> In file included from
> /home/sasha/Install/darktable/build/src/iop/introspection_colorchecker.c:33:0:
> /home/sasha/Install/darktable/src/iop/colorchecker.c:262:0: error: ignoring
> #pragma omp declare [-Werror=unknown-pragmas]
>  #pragma omp declare simd
>  ^
> /home/sasha/Install/darktable/src/iop/colorchecker.c: In function ‘process’:
> /home/sasha/Install/darktable/src/iop/colorchecker.c:305:0: error: ignoring
> #pragma omp simd [-Werror=unknown-pragmas]
>  #pragma omp simd
>  ^
> Linking C shared module libcacorrect.so
> cc1: all warnings being treated as errors
Fixed, thanks.
But you really should think about updating your compiler.

FIXME: or should we just depend on gcc-4.9+ in cmake?

> 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] Problem with lens correction and multiple lenses

[Roman Lebedev]

On Thu, May 5, 2016 at 12:43 AM, Graeme Leese  wrote:
> Hi,
Hi.

> I'm having a problem with the lens correction module where more than one
> lens in the database matches the exif data. The GUI gives a menu to choose
> between the different matches but the correction data used is always the
> same.
Hm, can you provide the sample raw with this situation?

> When a lens is chosen from the menu only its name is saved into the params,
> and when the params are committed the first matching lens is always used.
> This gives the same result regardless of which menu item is chosen since the
> lenses all have the same name.  Storing the selected lens in the params
> makes the selection work but breaks introspection (presumably related to
> storing parameters in the database?)
>
> I'd be happy to contribute a patch if someone can suggest a direction for
> the fix, or I can provide more details on how to reproduce the problem if it
> would help.
Which version of darktable are you using?

> Thanks,
> Graeme
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 lens correction and multiple lenses

[Roman Lebedev]

On Fri, May 6, 2016 at 12:30 AM, Graeme Leese <gnl...@gmail.com> wrote:

> [Apologies, Roman, if you've received this twice.]
>
> On 5 May 2016 at 11:57, Roman Lebedev <lebedev...@gmail.com> wrote:
>
>> On Thu, May 5, 2016 at 12:43 AM, Graeme Leese <gnl...@gmail.com> wrote:
>> > I'm having a problem with the lens correction module where more than one
>> > lens in the database matches the exif data. The GUI gives a menu to
>> choose
>> > between the different matches but the correction data used is always the
>> > same.
>> Hm, can you provide the sample raw with this situation?
>>
>
> Sure. Sample raw is attached (via Google Drive, I hope), but I think that
> any with a similar exif lens tag would show the issue.
>
> Which version of darktable are you using?
>>
>
> I tested it on 2.0.3 and
>


> on the HEAD from git
>
I love it when people mis-apply non-git terminology to git :)
I guess you meant git master?

in the last few days (I'm afraid that workspace is on a different machine
> so I don't have the commit sha to hand). I was also using the version of
> lensfun from Pascal's darktable-unstable PPA -- I'm not sure if the last
> released version has multiple profiles for this lens.
>
Hm, i did not look into that yet, but i would have thought
that https://github.com/darktable-org/darktable/pull/1059 fixed just that...


> Thanks,
> Graeme
>
Roman.


> ​
>  IMG_5388.CR2
> <https://drive.google.com/file/d/0B5KRSUptAIc0NjJReFg3UmZnd28/view?usp=drive_web>
>

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

Re: [darktable-dev] Re: sRGB internal color profile

[Roman Lebedev]

On Sun, May 8, 2016 at 4:54 PM, jmsarat  wrote:
> Hi Matthias,
>
> With a clean $HOME/.config/darktable, the option lcms2 is deactivated by
> default

>therefore the export function use lcms1-1.19.
Where from are you getting this?
I do not think dt ever used lcms1.

> The resulting image
> does not have defect in the blue shade but if the lcms2 option is activated
> then the problem appears.
>
> I tried with a fresh DT 2.0.4 compiled on Mageia 5 with lcms2-2.7 and with
> the latest dev version 2.1.0+1082~g6e50d7a. The problem is there with both
> versions.
>
> Jean-Marc
Roman.

>
>
>
> Le 08/05/2016 à 13:09, Matthias Bodenbinder a écrit :
>>
>> Hi Jean-Marc,
>>
>> I can not reproduce your JPG output. Not even with your xmp file. I am
>> using DT 2.0.4, self compiled.
>>
>> Have you tried with a different user resp. with a clean
>> $HOME/.config/darktable ?
>>
>> Matthias
>>
>>
>> Am 08.05.2016 um 12:35 schrieb jmsarat:
>>>
>>> Hi Jo,
>>>
>>> With this clean xmp : https://1fichier.com/?rd1q8touto
>>>
>>> I obtain this image : https://1fichier.com/?3uqu4ijx0g
>>>
>>> No style on export and using the image parameters for color profile
>>> (sRGB(web))  and rendering intent (perceptual).
>>>
>>> The raw image is there  : https://1fichier.com/?5n9xbgf9ej
>>>
>>> The problem is visible in the blue shade but could be present in other
>>> colors.
>>>
>>> Jean-Marc
>>>
>>> Le 08/05/2016 à 08:26, johannes hanika a écrit :

 heya,

 this is what it looks like for me:

 https://jo.dreggn.org/img_0001.jpg

 much like your not broken reference image?

 do you apply any styles on export maybe? if you have an exported jpg i
 could check the history stack in the xmp stored in that one..

 cheers,
jo



 On Sat, May 7, 2016 at 4:42 AM, jmsarat  wrote:
>
> Bonjour Johannes,
>
> The problem occurs when exporting an image and using the internal sRGB
> color
> profile. The problem disappear if I select another sRGB color profile
> (Sony
> sRGB or RT sRGB).
> As the source is a sony arw raw image, I do not specify a particular
> icc
> profile and use the standard matrix. I tried sony dcp profiles for
> A6000
> converted to icc but if the result is different the problem has been
> moved
> to other places in the blue shades.
> Attached the xmp corresponding to the image. This is a simplified xmp
> with
> the minimal options that create the problem in blue shades.
> The arw file is there : https://1fichier.com/?8khnco34cy
>
> darktable version 2.1.0+1080~gfedb40
>
> Jean-marc
>
>
>
>
> Le 27/04/2016 à 15:06, johannes hanika a écrit :
>>
>> heya,
>>
>> i can't reproduce. is there anything else? can you share an .xmp
>> sidecar file so we can precisely reproduce your steps? and just to
>> double check: you are talking export, not display, right? so it can't
>> be a display profile issue. are you using any particular icc profile
>> as input colour space?
>>
>> -jo
>>
>> On Wed, Apr 27, 2016 at 2:06 PM, Moritz Moeller
>> 
>> wrote:
>>>
>>> On 25/04/16 12:43, jmsarat wrote:

 [...] lower image
 result with an external profile (Sony Corp sRGB). [...]
>>>
>>>
>>> Can you share the source of the Sony profile?
>>>
>>> I have some images that have always shown exactly the artifacts you
>>> documented and which I could never develop through DT therefore. I
>>> thought
>>> it was some module inside DT causing this. If it is as simple as
>>> changing
>>> the profile, that would be really awesome.
>>>
>>> .mm
>>>
>>>
>>>
>>>
>>> ___
>>> 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
>>
>>
>
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable 

Re: [darktable-dev] error during building current git on 14.04

[Roman Lebedev]

Yes, we understand that version bumps are troublemakers at times...

On Thu, Jul 28, 2016 at 10:20 AM, Josep V. Moragues <jose...@arrakis.es> wrote:
>
>
> El 27/07/16 a les 13:02, Roman Lebedev ha escrit:
>
>> Yes, darktable git master now requires gtk3 3.14+ to build.
>> The 3.14 was chosen because even debian stable has that version.
>>
>> That is not a bug.
>> This was intentional.
>> Therefore this will not be fixed.
>
> I understand the reasons to match Darktable's build requirements with
> current stable distributions (Debian stable, Ubuntu 16.04) and I am not
> trying to convince the developers to change that.
>
> But currently there is a reason that makes me stick with Ubuntu 14.04
> for photo work: the AMD Catalyst binary driver. This driver is disabled
> in 16.04. And the AMDGPU Pro that will replace it (only for GCN based
> AMD cards) is not still available.
I'm also in this situation (no more fglrx and no amdgpu yet, Radeon 7970HD)

> I need the AMD closed source graphics driver because, as far as I know,
> the open source radeon driver does not allow using the 12 bit LUT
> present on AMD cards. And this is needed to acurately profile a monitor
> (using ArgyllCMS or DispcalGUI), without banding artifacts.
Hm, where did you read that?
Also, if it really is the case, is this issue already reported against
open source radeon driver?

(and, does argyll actually produce > 8bit vcgt? because if it does not,
the issue is bogus)

TBN i don't really believe there is any banding even with 8-bit bit depth..

> No AMD propietary driver for Ubuntu 16.04 means also no OpenCL
> acceleration for Darktable ... but my main concern is the LUT color depth.
>
> I expect this situation will get solved by the time Darktable 2.2 will
> be released. My current card is a Radeon R7 250, that is a low-end card,
> but I like it because is a fanless design, it matches well my silent
> self built computer. It is GCN 1.0, and AMD has announced AMDGPU support
> for it, but only with the 4.8 Linux kernel, i.e. Ubuntu 16.10. We will
> see. If this do not allow me to use 12 bit LUT, i will have to stick
> with Ubuntu 14.04 and Darktable 2.0.x. Or to buy a new card.
>
> Josep V. Moragues
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 Phase One P65+

[Roman Lebedev]

On Sat, Jul 23, 2016 at 2:08 AM, Marco Sala <_c...@libero.it> wrote:
> Hello there!
Hi.

> I have a Phase One P65+ digital back.
>
> In DT is not yet supported ("unknown format" error), and also in the list of
> cameras supported by dcraw is unreported. However dcraw develops its files,
> though not officially supported, and the results are very good, often better
> than CP1 and LR.
https://www.darktable.org/resources/camera-support/ is the only relevant list
of supported cameras. (We do not use dcraw for loading)

> Is possible to implement the support for DT?
Maybe yes.
https://www.darktable.org/2012/10/whats-involved-with-adding-support-for-new-cameras/
https://redmine.darktable.org/projects/darktable/issues/new tracker =
"camera support"

> Many thanks,
>
> --
>   Marco Sala
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 during building current git on 14.04

[Roman Lebedev]

On Wed, Jul 27, 2016 at 1:47 PM, Nazarii Vitak  wrote:
> Hi everyone,
>
> I tried to update the darktable through git. The command ./build.sh ended up
> in error.
> Last lines from terminal:
> "CMake Error at
> /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:108
> (message):
>   Could NOT find GTK3 (missing: VERSION_OK) (Required is at least version
>   "3.14")
> Call Stack (most recent call first):
>   /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:315
> (_FPHSA_FAILURE_MESSAGE)
>   cmake/modules/FindGTK3.cmake:58 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
>   src/CMakeLists.txt:146 (find_package)
>
>
> -- Configuring incomplete, errors occurred!
> "
> As I understand it requires gtk3 >3.14, but I have found that installation
> of gtk3 3.14 brokes unity. The only way is to upgrade the system, but I
> usually do this when xx.04.2 LTS appears. Could it possibly be fixed to
> build darktable at 14.04.
> I have attached ~/darktable/build/CMakeFiles/CMakeOutput.log and
> ~/darktable/build/CMakeFiles/CMakeError.log.
Yes, darktable git master now requires gtk3 3.14+ to build.
The 3.14 was chosen because even debian stable has that version.

That is not a bug.
This was intentional.
Therefore this will not be fixed.

The solution is:
*). Either use stable darktable version (2.0.x), which still requires 3.10+
*) or keep using the git master at the moment just before gtk version
requirement was bumped
   Do note that it will no longer be considered a build of "git
master", and is perhaps more
   riskier than using the actual "git master".
*) Or update gtk, possibly by updating the system to something newer.

LTS is only about the packages present in said LTS release, it has
nothing to do whatsoever
with the choices about version requirement made by the developers of
the software...

Also see "[darktable-user] Compiling last git master failed because of
GTK-3 outdated" thread.

> If you need more information let me know how I can gather this information
> and I try to obtain it.
>
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] saving user-selected lens for the lens correction module

[Roman Lebedev]

On Tue, Jul 19, 2016 at 9:32 AM, Corey  wrote:
> Hi,
Hi.

> I love darktable, but the lens I use the most is never recognized by
> automatically by the lens correction module. The result is that I have to
> manually select my lens for every photo, which not particularly enjoyable.
But why is it not automatically recognized?
Which lens? Which lensfun version?
Better upload sample raw file with that lens.

> I thought this problem could be solved if the user's lens selection was
> stored. That is, darktable could store the mapping from "camera+lens exif
> string" to "camera+lens lensfun string" whenever the user selects a lens
> explicitly. This could then be looked up if the lensfun search fails.
>
> I've attached a patch file that implements this in a pretty simple way. It
> seems to work for me (but I haven't done extensive testing).
>
> The same thing could be done for the camera too, of course.
>
> I'm curious to see what people think.
>
> - Corey
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-dev] Re: [Lensfun-users] Canon PowerShot SD1100/IXUS 80

[Roman Lebedev]

Hi.

On Mon, Jul 4, 2016 at 7:31 PM, Jonathan Niehof  wrote:
> In short, the attached snippet contains full (distortion + TCA +
> vignetting) lens information for the Canon Powershot SD1100 IS/IXUS
> 80.
>
> Caveats: the distortion information is from the existing IXUS 80
> information in the database. I added TCA and vignetting data to the
> IXUS 80 and copied it to the SD1100. This is the older database format
> since I'm still running lensfun 0.2.8 (Ubuntu 15.10) and wanted to
> make sure it worked with my current darktable. This camera doesn't
> have an adjustable aperture, but an ND8 filter; when the filter is in,
> the camera reports the "effective" aperture in the EXIF data, i.e. an
> aperture that would give the same brightness. I'm assuming the ND
> filter doesn't affect the vignetting or TCA.
>
> The very long:
>
> I shot with CHDK to DNG 1.3 raws. This is supposed to embed the
> badpixels.bin data (bad pixels reported from the camera firmware) into
> DNG opcodes so it can be removed by the raw converter; however, I
> found a lot of obvious dead pixels (e.g. cyan blotches) in the dcraw
> converted raws. I pulled the CHDK-generated badpixels.bin and parsed
> it into the format that dcraw uses for its -P option. I converted all
> vignetting images with no interpolation ("dcraw -v -t 0 -4 -o 0 -M -D
> foo.DNG") and checked the pgm for zero-value (totally dead) pixels.
> All the vignetting images gave identical results, which I merged with
> the badpixels.bin list, and then edited calibrate.py to add the
> appropriate -P option to all dcraw calls. Python code for all this is
> available.
>
> I made a lenses.txt file with the distortion from the existing IXUS80
> in lensfun.xml, but with a changed first line: "Canon PowerShot SD1100
> IS: Canon, canonSD100IS, 5.9". I edited line 169 of calibrate.py to
> default to "Canon PowerShot SD1100 IS" (matching the exif) instead of
> "Standard".
>
> For TCA, I made several attempts with buildings before giving up. I
> bought two black-and-white checkered tablecloths on Amazon, 137x274cm,
> and hung them up. I set up a tripod about 6-7m away. Because at the
> shorter focal lengths the pattern didn't fill the frame, I did five
> shots: one with the pattern in each corner (filling as much of the
> frame as possible) and one with the camera brought closer (about 4m
> for the shortest focal length) so the pattern filled the frame. At
> longer focal lengths (filling the frame), I took a couple of exposures
> with slight movements of the camera between to get some differences. I
> shot at ISO 80 (base), exposure on automatic, auto focus, with a 2sec
> timer to avoid vibrations from pressing the shutter button. I shot at
> all six. All exposure were without the ND filter (although I didn't
> force that.)
>
> I ran calibrate.py against all the images with a one-, two-, and
> three-parameter fits. For each focal length, I parsed the .tca file
> and plotted distortion vs. radius (r and b) for all images, looking
> for reasonable agreement between the images. I took the mean of
> parameters for all images at each focal length to plot parameter as a
> function of focal length, looking for smooth variation with focal
> length. (Code available.) The three-parameter (bcv) fit has poor
> agreement between images and noisy variation with focal length. At the
> shorter focal lengths, the two-parameter (b and v) was clearly very
> good. The images taken closer in were clear outliers and I threw them
> out. At longer focal length, neither one- nor two-parameter had
> perfect agreemnt, but the two- had better, and in all cases the
> deviation from no correction was larger than the difference between
> the images. So I used the means of the two-parameter fits.
>
> I shot vignetting images against a white ceiling about 2m from the
> camera, mounted on a tripod facing up. A lamp was positioned right
> next to the tripod and emitting from just above lens level, to avoid
> camera shadow. I sandwiched a sheet of Rosco #216 white diffusion gel
> between the lens below and glass above (two pieces, a sort of
> "floating picture frame" that I had handy.) Focus distance was set at
> maximum: I did not bring an image at infinity to focus. Again 80ISO,
> auto exposure, 2sec timer, no ND filter. I shot all focal lengths,
> then rotated the camera and gel so that the relationship between
> ceiling, camera, and gel were all different (lamp and ceiling remained
> in the same orientation) before shooting another set.
>
> Using gnuplot output from calibrate.py, I verifying vignetting images
> were generally smooth (and threw out two other sets of vignetting
> photos where I tried a different approach to holding the gel, which
> had obvious defects.) The two images for each focal length provided
> very similar outputs.
>
> For the XML, I copied the IXUS 80 verbatim (both camera and lens),
> then changed model tag to match Exif.Image.Model (which is the same as
> 

Re: [darktable-dev] Usermanual update for 2.2

[Roman Lebedev]

On Sat, Jul 23, 2016 at 11:52 AM, Ulrich Pegelow
 wrote:
> Dear all,
>
> I'd like to start an update of the usermanual to make it ready for 2.2.
>
> Let's begin by compiling a list of required changes. From my side following
> comes to mind and I added a proposal of whom might take care. Please and
> your proposals.
>
> * new module color check lut [Jo?]

> * new binary darktable-chart [Jo?]
That was Tobias

> * new module liquify [Pascal?]
> * new module perspective correction [Ulrich]
> * various improvements for x-trans sensors [Dan?]
> * the "other" dropdown box [Tobias?]
> * new preferences tab for Lua options [Jeremy?]
> * updates to the collection module [Aldric?]
> * correction of outdated issues and factual errors [Roman?]
I guess this is mostly about proofreading?
> * general style and proofreading [Ulrich]
> * .

What about marking the code samples that is in manuals (e.g. lua api)
as non-translatable?
(I have asked that last year)

> My idea is to start working now. Maybe we can have text for the new features
> complete by early September and have everything ready with all proofreading
> etc. by mid October.
>
> 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] Issue with D800 RAW, wrong pixels on right of image

[Roman Lebedev]

On Wed, Aug 17, 2016 at 5:40 PM, Pascal Obry <pas...@obry.net> wrote:
>
> I have updated to master this morning and I have found that my non-
> cropped RAW images from my Nikon D800 have some bad columns on the
> right border of the images. That is, 5 or so right most columns are
> only garbage.
>
> I have tracked down this issue to recent work on the RAW nikon support
> (not surprising).
>
> After some tweaking around I have been able to get clean images by
> doing the following:
>
> 1. revert:
>
> $ git revert 73820d803d0c71fe1e26336be95ce1190fb46f24
>
> <<<
> commit 73820d803d0c71fe1e26336be95ce1190fb46f24
> Author: Roman Lebedev <lebedev...@gmail.com>
> Date:   Mon Aug 15 19:34:54 2016 +0300
>
> Rawspeed: NefDecoder: stop providing the rope for users to hang 
> themselves.
>
> This is basically the same problem as with Rw2Decoder.
>
> It looks like all the nikon cameras has different modes -
> 14-bit compressed, 12-bit compressed,
> 14-bit uncompressed, 12-bit uncompressed.
>
> And the problem here is that 14-bit and 12-bit have different white 
> levels.
>
> Since NefDecoder::checkSupportInternal() just silently fallbacks
> to the generic entry, if present (with mode=""),
> this has result in silently-garbled images.
>
> Let's not do that.
>>>>
>
> 2. reverting camera.xml to the version from this commit:
>
> $ git show 
> 73820d803d0c71fe1e26336be95ce1190fb46f24:src/external/rawspeed/data/cameras.xml
>  > src/external/rawspeed/data/cameras.xml
>
> Hope this helps. Let me know if I can provide some more information.
Yes, please provide that very raw file. (or any other raw file, but
shoot with the same settings, particularly bitness (12/14)  and
compression)

I really did not expect those changes to affect crop...

> Thanks,
>
> --
>   Pascal Obry /  Magny Les Hameaux (78)
Roman.

>   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] Issue with D800 RAW, wrong pixels on right of image

[Roman Lebedev]

On Wed, Aug 17, 2016 at 6:17 PM, Pascal Obry <pas...@obry.net> wrote:
> Roman,
>
>> Yes, please provide that very raw file. (or any other raw file, but
>> shoot with the same settings, particularly bitness (12/14)  and
>> compression)
>
> Here you can download an image which exhibit the issue:
>
> https://we.tl/fSD9r4iQAc
>
> Thanks!
And now fixed:

commit ed0b518e31ff298251c2543ccd3ae9403297466d
Author: Roman Lebedev <lebedev...@gmail.com>
Date:   Wed Aug 17 19:33:40 2016 +0300

Rawspeed: Nikon: fixup crop for D800{,E} 14bit-compressed

Was erroneously set to that value in
53af22a7d8b255f386bf1c012c2202d3324d3c75

Reported by Pascal Obry.


I must say, this was very lucky report, i made this mistake only in
D800 and D800E.

(assuming the script i used to diff is not broken)

> --
>   Pascal Obry /  Magny Les Hameaux (78)
Roman.

>   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] Issue with D800 RAW, wrong pixels on right of image

[Roman Lebedev]

On Wed, Aug 17, 2016 at 6:17 PM, Pascal Obry  wrote:
> Roman,
>
>> Yes, please provide that very raw file. (or any other raw file, but
>> shoot with the same settings, particularly bitness (12/14)  and
>> compression)
>
> Here you can download an image which exhibit the issue:
>
> https://we.tl/fSD9r4iQAc
Thank you for catching and reporting this issue this soon!
Reproduced.

I'll try to come up with a tool to catch other issues like this that i
added in that commit...

>
> Thanks!
Roman.

> --
>   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] 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] 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 current git

[Roman Lebedev]

On Sat, Jan 28, 2017 at 1:57 PM, Moritz Moeller  wrote:
> I also have an issue. But it's a different one:
>
> [  6%] Building CXX object
> src/external/rawspeed/src/librawspeed/CMakeFiles/rawspeed.dir/decoders/DngDecoderSlices.cpp.o
> /Users/moeller/code/darktable/src/external/rawspeed/src/librawspeed/decoders/DngDecoderSlices.cpp:435:31:
> error: no matching function for call to
>   'jpeg_read_header'
> if (JPEG_HEADER_OK != jpeg_read_header(, true))
>   ^~~~
> /opt/local/include/jpeglib.h:1039:13: note: candidate function not viable:
> no known conversion from 'bool' to 'boolean' for 2nd argument
> EXTERN(int) jpeg_read_header JPP((j_decompress_ptr cinfo,
> ^
> 1 error generated.
>
>
> I am currently building on the monochrome branch. I did
Tht branch is long merged into master and gone.
*Please* try building master directly.

> git pull
> git merge origin/master
> git submodule update
I'd also try   git submodule update -f
And maybe git clean -f -d -x, both in darktable/ and in src/external/rawspeed

>
> .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] 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:
>>
>> *Please* try building master directly.

> I did. Same error.
Okay, so the old bug creeped back in. Should be easy to fix.
Remind me, which libjpeg do you have? the -turbo or the usual one?
Also, OSX?

> .mm
Roman.
___
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 1:44 PM, Alexander Rabtchevich
 wrote:
> Thank you, it did help.

> > $ git submodule update
> Should it be done each time git pull is made?
Yes it should be.

> The output of git pull usually says: submodule rawspeed updated...
Updated, but not checked-out.

> With respect,
> Alexander Rabtchevich
>
>
>> $ git submodule update
>>
>> did it for me.
>>
>> Christian
>>
>>
>
> ___
> 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 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

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] 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] 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] Can't compile last git pull source (08/Sep/2016)

[Roman Lebedev]

My first guess would be - need newer version of pugixml
It does work for me with debian sid's version - 1.7-2

On Thu, Sep 8, 2016 at 1:10 PM, André Felipe Carvalho
 wrote:
> Hello,
>
> After git pulling the code this morning, I can't compile dt. What am I doing
> wrong?
>
>
> [ 31%] Building C object
> src/CMakeFiles/lib_darktable.dir/control/crawler.c.o
> [ 31%] Building C object src/CMakeFiles/lib_darktable.dir/control/jobs.c.o
> [ 31%] Building C object
> src/CMakeFiles/lib_darktable.dir/control/jobs/control_jobs.c.o
> /home/andre/compilar/darktable/src/common/exif.cc: In function ‘GList*
> read_history_v1(const char*)’:
> /home/andre/compilar/darktable/src/common/exif.cc:1714:37: error: ‘class
> pugi::xml_document’ has no member named ‘select_node’
>pugi::xpath_node modversion =
> doc.select_node("//darktable:history_modversion
>  ^
> /home/andre/compilar/darktable/src/common/exif.cc:1715:34: error: ‘class
> pugi::xml_document’ has no member named ‘select_node’
>pugi::xpath_node enabled =
> doc.select_node("//darktable:history_enabled/rdf:S
>   ^
> /home/andre/compilar/darktable/src/common/exif.cc:1716:36: error: ‘class
> pugi::xml_document’ has no member named ‘select_node’
>pugi::xpath_node operation =
> doc.select_node("//darktable:history_operation/r
> ^
> /home/andre/compilar/darktable/src/common/exif.cc:1717:33: error: ‘class
> pugi::xml_document’ has no member named ‘select_node’
>pugi::xpath_node params =
> doc.select_node("//darktable:history_params/rdf:Seq
>  ^
> /home/andre/compilar/darktable/src/common/exif.cc:1718:41: error: ‘class
> pugi::xml_document’ has no member named ‘select_node’
>pugi::xpath_node blendop_params =
> doc.select_node("//darktable:blendop_params
>  ^
> /home/andre/compilar/darktable/src/common/exif.cc:1719:42: error: ‘class
> pugi::xml_document’ has no member named ‘select_node’
>pugi::xpath_node blendop_version =
> doc.select_node("//darktable:blendop_versi
>   ^
> /home/andre/compilar/darktable/src/common/exif.cc:1720:41: error: ‘class
> pugi::xml_document’ has no member named ‘select_node’
>pugi::xpath_node multi_priority =
> doc.select_node("//darktable:multi_priority
>  ^
> /home/andre/compilar/darktable/src/common/exif.cc:1721:37: error: ‘class
> pugi::xml_document’ has no member named ‘select_node’
>pugi::xpath_node multi_name =
> doc.select_node("//darktable:multi_name/rdf:Seq
>  ^
> [ 32%] [ 32%] Building C object
> src/CMakeFiles/lib_darktable.dir/control/jobs/develop_jobs.c.o
> Building C object
> src/CMakeFiles/lib_darktable.dir/control/jobs/film_jobs.c.o
> [ 32%] Building C object
> src/CMakeFiles/lib_darktable.dir/control/jobs/image_jobs.c.o
> src/CMakeFiles/lib_darktable.dir/build.make:415: recipe for target
> 'src/CMakeFiles/lib_darktable.dir/common/exif.cc.o' failed
> make[2]: *** [src/CMakeFiles/lib_darktable.dir/common/exif.cc.o] Error 1
> make[2]: ** Esperando que outros processos terminem.
> CMakeFiles/Makefile2:1366: recipe for target
> 'src/CMakeFiles/lib_darktable.dir/all' failed
> make[1]: *** [src/CMakeFiles/lib_darktable.dir/all] Error 2
> Makefile:136: recipe for target 'all' failed
> make: *** [all] Error 2
>
>
> --
> André Felipe
Roman.

> https://www.flickr.com/photos/andrefelipecarvalho/
>
> ___
> 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 CRW Files

[Roman Lebedev]

What is the problem?

On Thu, Sep 8, 2016 at 9:39 PM, Tim Rolph  wrote:
> Hello, Who do I need to speak to to get help resolving a problem with Canon
> CRW files in Darktable? Is it Darktable developers or Rawspeed developers?
>
> Kind Regards,
>
> Tim Rolph.
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] How to get profiled denoise data incorporated into Darktable?

[Roman Lebedev]

On Fri, Sep 9, 2016 at 2:34 AM, Pete Hall <p...@hallcircus.net> wrote:
> Hello Roman
>
> Sorry to get in at the end here, but I have a tarball that's been
> getting ignored for quite a while too.Would you please tell me the
> actual uri I need in order to  create an issue in redmine?
Tracker = "Camera Support"
Subject = "Noise profile: ${Camera maker} ${Camera model}"
https://redmine.darktable.org/projects/darktable/issues/new

> I know it's
> not your issue, and I'm glad you are trying to help,

> but it would be
> really great if this info were actually published with the instructions.
> This is way more difficult than it needs to be and certainly not
> efficient.
It is, yes. But the noise profile review throughput is severely limited too...

> Does anyone actually own new hardware support? That's how it
> would be done in a normal business. Might work for DT as well...
Did not parse that.

> Thanks
>
> Pete Hall
Roman.

> On 09/08/2016 05:40 PM, Terry Duell wrote:
>> Hello Roman,
>>
>> On Thu, 08 Sep 2016 20:17:27 +1000, Roman Lebedev
>> <lebedev...@gmail.com> wrote:
>>
>>> On Thu, Sep 8, 2016 at 9:29 AM, Terry Duell <tdu...@iinet.net.au> wrote:
>>>> Hello All,
>>>> For those who have seen the post below but ignored it, sorry to keep
>>>> harping
>>>> on this subject, but having generated the data and made it
>>>> available, it
>>>> would be nice to get just one response.
>>>> I thought I was following the guidelines in making the data
>>>> available this
>>>> way, but if not, please point me in the right direction so we can have
>>>> profiled denoise support built-in for the K-1.
>>
>>> Seemingly-best way is to create new issue in redmine (camera support),
>>> attach the tarball, and just wait...
>>>
>>
>> Thanks.
>>
>> Cheers,
>
> --
> Pete Hall
> p...@hallcircus.net
> 608-290-0731
>
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] spot WB hangs dt

[Roman Lebedev]

Yes, spot wb (and color picking for invert iop) are broken for raw
images in git master.

Roman.

On Mon, Sep 26, 2016 at 7:33 PM, Alexander Rabtchevich
 wrote:
> Hello
>
> Spot white balance hangs darktable from the current git.
>
> 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] Issue with Tamron lens

[Roman Lebedev]

On Tue, Oct 4, 2016 at 4:42 PM, Maurizio Paglia  wrote:
> Hi all,
> my Tamron SP AF 17-50mm F/2.8 XR Di II VC LD Aspherical (IF) is not
> recognized inside darktable

> but I have to select manually Tamron SP AF 17-50mm f/2.8 XR Di II VC LD 
> Aspherical (IF).

On http://lensfun.sourceforge.net/lenslist/ i only see the following lens:
Tamron SP AF 17-50mm f/2.8 XR Di II LD Aspherical (IF)

Which is not "Tamron SP AF 17-50mm f/2.8 XR Di II VC LD Aspherical (IF)"
('VC' is missing)

> The only difference is F/2.8 (uppercase while in dt list is lowercase).
> I got in touch with Lensfun people but they told me Lensfun does not look at
> upper/lower case.
> Could it be a darktable issue?
> Thanks,
> Maurizio
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] spot WB hangs dt

[Roman Lebedev]

Spot white balance, and invert colorpicker should be now functioning
properly in git master.

Roman.

On Mon, Sep 26, 2016 at 7:33 PM, Alexander Rabtchevich
 wrote:
> Hello
>
> Spot white balance hangs darktable from the current git.
>
> 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] Unable to Select All During Camera Import

[Roman Lebedev]

On Thu, Oct 6, 2016 at 10:51 PM, Gareth Williams
 wrote:
> Hi,
>
> If I connect my camera (Nikon D5500, if that's relevant) to my laptop and
> start Darktable, I have the option to 'import from camera'.  When I click on
> this a dialog appears and lists all the images stored on my camera.
> However, I cannot select all the images (Ctrl-A) on Darktable v2.0.6 running
> on Arch Linux.
>
> I had an old install of Fedora 23 on a partition, so I rebooted into that
> and can successfully select all image. The version of Darktable on Fedora 23
> is 1.6.?.
>
> Next, I updated Fedora 23 to Fedora 24, which also has Darktable v2.0.6 and
> this displays the same issue as Darktable 2.0.6 on Arch Linux - I cannot use
> Ctrl-A to select all images.
>
> Is this a known problem with v2.0.6?
It is a known problem with GTK+.
https://redmine.darktable.org/issues/11159

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

Re: [darktable-dev] Nikon 1 V1

[Roman Lebedev]

Hi.

On Sat, Sep 17, 2016 at 2:04 PM, Robert William Hutton
 wrote:
> On 17/09/16 20:48, Prof. Dr. Stefan Schmidt wrote:
>>
>> Last week my Kubuntu 16.04 crashed and I had to do a complete new setup
>> of the whole system. By that chance I also upgraded from dt 2.04 to 2.0.6.
>>
>> Since that I cannot open my Nikon 1v1 raw files (*.NEF).
>>
>> I am desperate sitting on 800 new pictures from our summer holiday
>
>
> Hi Stefan,
>
> Not sure why your camera isn't supported any more,
It was fixed later on https://redmine.darktable.org/issues/11137

> I'll leave that to an actual dev to comment on.

The root cause is: nikon can write up to 4 different raw formats:
14bit compressed, 14bit uncompressed, 12bit compressed, 12bit uncompressed.

Unsurprisingly, 12-bit and 14-bit have different white levels.
Additionally, old code assumed that "*-compressed" always have a fixed
whitelevels of (2^bitness)-1), i.e. 4095 or 16383.

For that reason, many nikon cameras in cameras.xml had completely
arbitrary whitelevel specified,
which resulted in wrong image => either way too bright (if 12bit wl
was specified, and image is from 14bit-uncompressed)
or too dark and with purple highlights (if 14bit wl was specified, and
image is from 12bit-uncompressed)
or with just purple highlights (all other cases, e.g. "*-compressed").

And no one noticed that ^ it was completely and utterly broken.

So when i finally did notice that, i had zero options other than just
disable all the nikon cameras
for which we do not have proper whitelevel information, and then add
the support back
on per-camera case once someone provides all the necessary samples.

This is the script that gives the list of broken (and disabled in git
master) nikon cameras:
https://github.com/darktable-org/darktable/blob/master/tools/rawspeed-check-nikon-modes.rb

If your camera is in that output, one needs to provide samples to redmine
(but do check for duplicates first!)

> However, since you mention that you're desperate,
> you could build from source.  The general instructions are here:
>
> https://redmine.darktable.org/projects/darktable/wiki/Building_darktable_20#General-build-instructions
>
> And how to install the dependencies for your system here:
>
> https://redmine.darktable.org/projects/darktable/wiki/Building_darktable_20#Ubuntu-1604
>
> To get the older version (2.0.4 in your case) you would do:
>
> git checkout release-2.0.4
> rm -rf build
> ./build.sh
>
> rather than using the latest version (2.0.6).
>
> Then you would install:
>
> cd "./build"; sudo make install
>
> And run the version you just installed:
>
> /opt/darktable/bin/darktable
>
> You have to run it this way to avoid using the version installed by your
> operating system.
>
> HTH,
>
> Rob
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 for windows

[Roman Lebedev]

(spoiler: i have read only the mail subject.)

Is this Battlestar Galactica or something? :)
"All this has happened before, and all of it will happen again."

https://www.mail-archive.com/darktable-dev%40lists.darktable.org/msg00344.html

Please do actually read what is written there, and do understand it.
There is absolutely nothing to add to that mail.
And nothing has changed since it was written, all and every point still applies.

Roman.

On Mon, Oct 3, 2016 at 9:56 PM, Jan Ingwer Baer  wrote:
> Hi,
>
> i have done some work to build darktable for windows. Now i can build it
> (without maps and lua) on windows and first test show no problems. I have
> done this in first for my private use. But i share this, so other can test
> and use it. At this time it is only for developres, and not ready for
> end-users.
>
> I hope that i can find enough other interested developers who can help to
> test and stabilize it.
>
> You find my changes i the branch 'darktable-2.0.x-win' in my github fork
> 'https://github.com/jibaer/darktable.git'.
>
> While building the windows version i have found some issues in the
> darktable-source:
>
> - In common/film.c function film_recursive_get_files() there is a mistake in
> the call to function g_build_filename(). It is called with the same
> parameters as g_build_pathname(), but according to the glib manual it does
> not need the first parameter (G_DIR_SEPARATOR_S). Under windows this will
> produce an invalid filename with a leading slash (like /c:/user/...). Under
> *ix this no problem because it will simple double the leading slash of an
> absolute path what the os ignores.
>
> - In common/darktable.c function strip_semicolons_from_keymap() there is
> only a test for the result of fgetc() !=eof. But on mingw this doesnt work,
> and it must test for feof() ==0. Without the test for feof() the result is
> an infinite loop...
>
> - With gcc 6.x the search-path for include-files is very important and the
> includes  and  will not work if the default search order for
> the system-include-directorys is changed. Because the cmake-files insert
> some include-paths with the system-attributes they change the
> default-search-order and the build will fail with the error : file
>  not found. On my mingw-build i have found a solution in an edit
> to src/CMakeLists.txt that avoids to do use the system-attribute while
> adding the include-path for PThreads.
>
> I hope you will accept my contribution and dont take it hostile. And with
> the help from more developers some day there will be an official version of
> darktable for windows. To use another raw-photo application is not an
> alternative because DT has at least two outstanding features:
> - The profile-based noise-reduction is really great
> - The mask feature is also really great
>
> Greetings from Berlin
>
> Jan Ingwer Baer
> ___
> 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 for windows

[Roman Lebedev]

How do i politely put it?
Because we are sick and tired of this topic.

This is my last mail on the subject.

On Mon, Oct 3, 2016 at 11:50 PM, Jan Ingwer Baer <jib...@web.de> wrote:
> Hi Roman,
>
> why do you react so harsh? I think this is not the right way. My work on the
> windows version is a try to get enough people  to do the windows work. I
> know that i am not the only one who wants to work on this.

> No wonder that other people run away from this project after a short time if
> they get such a hostile reaction. Better read my mail complete and think
> again. If you had read my mail, you would know that your reference to your
> mail from december 2015 is at least partly wrong.
Like i said, i did not read your mail at all. So no need to re-read.

> I dont try to do some packaging of an darktable windows version. I have put
> all my work to a public github-repo (see my mail). So the core-team can view
> my changes and can merge them to the main repo. I have some things that i've
> found in the source written in my mail. So i try my best to contribute.
>
> How can i met your requirements for contributing to darktable if i not use
> linux or mac-os? The only way for me to be actively involved in darktable is
> to do it on windows. That is what i try.
>
> Greetings
>
> Jan
>
>
> Am 03.10.2016 um 21:48 schrieb Roman Lebedev:
>>
>> (spoiler: i have read only the mail subject.)
>>
>> Is this Battlestar Galactica or something? :)
>> "All this has happened before, and all of it will happen again."
>>
>>
>> https://www.mail-archive.com/darktable-dev%40lists.darktable.org/msg00344.html
>>
>> Please do actually read what is written there, and do understand it.
>> There is absolutely nothing to add to that mail.
>> And nothing has changed since it was written, all and every point still
>> applies.
>>
>> Roman.
>>
>> On Mon, Oct 3, 2016 at 9:56 PM, Jan Ingwer Baer <jib...@web.de> wrote:
>>>
>>> Hi,
>>>
>>> i have done some work to build darktable for windows. Now i can build it
>>> (without maps and lua) on windows and first test show no problems. I have
>>> done this in first for my private use. But i share this, so other can
>>> test
>>> and use it. At this time it is only for developres, and not ready for
>>> end-users.
>>>
>>> I hope that i can find enough other interested developers who can help to
>>> test and stabilize it.
>>>
>>> You find my changes i the branch 'darktable-2.0.x-win' in my github fork
>>> 'https://github.com/jibaer/darktable.git'.
>>>
>>> While building the windows version i have found some issues in the
>>> darktable-source:
>>>
>>> - In common/film.c function film_recursive_get_files() there is a mistake
>>> in
>>> the call to function g_build_filename(). It is called with the same
>>> parameters as g_build_pathname(), but according to the glib manual it
>>> does
>>> not need the first parameter (G_DIR_SEPARATOR_S). Under windows this will
>>> produce an invalid filename with a leading slash (like /c:/user/...).
>>> Under
>>> *ix this no problem because it will simple double the leading slash of an
>>> absolute path what the os ignores.
>>>
>>> - In common/darktable.c function strip_semicolons_from_keymap() there is
>>> only a test for the result of fgetc() !=eof. But on mingw this doesnt
>>> work,
>>> and it must test for feof() ==0. Without the test for feof() the result
>>> is
>>> an infinite loop...
>>>
>>> - With gcc 6.x the search-path for include-files is very important and
>>> the
>>> includes  and  will not work if the default search order
>>> for
>>> the system-include-directorys is changed. Because the cmake-files insert
>>> some include-paths with the system-attributes they change the
>>> default-search-order and the build will fail with the error : file
>>>  not found. On my mingw-build i have found a solution in an
>>> edit
>>> to src/CMakeLists.txt that avoids to do use the system-attribute while
>>> adding the include-path for PThreads.
>>>
>>> I hope you will accept my contribution and dont take it hostile. And with
>>> the help from more developers some day there will be an official version
>>> of
>>> darktable for windows. To use another raw-photo application is not an
>>> alternative because DT has at least two outstanding features:
>>> - The profile-based noise-reduction is really great
>>> - The mask feature is also really great
>>>
>>> Greetings from Berlin
>>>
>>> Jan Ingwer Baer
>>>
>>> ___
>>> 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] Exif data imports but does not export: .RAW files on git2 camera

[Roman Lebedev]

On Tue, Sep 27, 2016 at 7:01 AM, Christian Gunning  wrote:
> Hello all,
Hi.

> I'm new to darktable, and my experiences have been great.  Thanks so much
> for the excellent tool. Note - I'm using 2.0.6 on debian.
>
> I've been testing the raw capabilities of a Git2 camera
> (www.gitup.com/home/12-gitup-git2-action-camera-pro-packing.html, Sony Exmor
> IMX206 16MP sensor, Novatek 96660 chip). So far, darktable is the only linux
> tool that will even recognize and read this camera's raw files (dcraw et al
> don't).
:)

> The images import fine,

>and the "Image Information" panel show full, correct EXIF info.
Huuh, for raw images from that camera?

> Exported jpegs, however, lack all EXIF info, and I get the
> following error (on the commandline that started the GUI):
>
> [exiv2] /media/2016_0924_215133_001.RAW: /media/2016_0924_215133_001.RAW:
> The file contains data of an unknown image type
> [xmp_attach] /tmp/2016_0924_215133_001.jpg: caught exiv2 exception
> '/media/2016_0924_215133_001.RAW: The file contains data of an unknown image
> type'
> [export_job] exported to `/tmp/2016_0924_215133_001.jpg'
Anyway long story short.
I have access to that camera too, and i was the one to add support for
this camera into
darktable.

And i can tell you that those raw images have no metadata whatsoever.
They are just plain sensor dump. No EXIF. Not even your usual TIFF tags.
The only data stored in raw file is the sensor readout.

For metadata, the only approach i envision is shooting JPG+RAW, and manually
storing JPG metadata into .RAW.xmp sidecar via exiv2 / exiftool.

I have just tried to come up with such a script, but failed.
Maybe others will succeed :)

> I've also  imported and then exported jpegs from this camera without any
> issues. I've included an example .RAW and (unprocessed) exported .jpg here:
> https://keybase.pub/xian/darktable/
>
> This is a fairly low priority for me, but I thought I'd pass the information
> along.
>
> Best,
> Christian
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: Fuji X-T2 noise profiles finalized

[Roman Lebedev]

On Thu, Oct 27, 2016 at 6:16 PM, J. Liles <malnour...@gmail.com> wrote:
> Just a reminder, my ICC profiles for the X-Trans I, II and III (also in
> X-T2) last mentioned in the post "Camera color profiles for FujiFilm X-Pro1
> and X-Pro2" also still waiting to be included.

Not really. We do not provide any camera ICC profiles.

We do have /some/ custom matrices.
But nowadays, same as with custom camera base/tone curves, we do not merge
new ones.
2 main reasons:
1. no knowledge to check whether they are valid.
2. no one wants to/has time to  look at them.

Roman.

> I'd be happy to make the patch myself but I don't know how the ICC profiles
> are converted into the numerical format embedded in the C code.
>
> FYI, I've confirmed the accuracy of my X-Trans III profile (made with the
> X-Pro2) with the new X-T2 visually, but the season for shooting charts is
> over where I live.
>
>
>
>
>
> On Thu, Oct 27, 2016 at 8:01 AM, Roman Lebedev <lebedev...@gmail.com> wrote:
>>
>> On Thu, Oct 27, 2016 at 5:53 PM, Sascha Oleszczuk <soleszc...@gmail.com>
>> wrote:
>> > Thx for release 2.0.7.
>> > It seams my noiseprofiles for fuji X-T2 and the white balance settings
>> > from
>> > another user are not part of 2.0.7.
>>
>> > Not sure if the team hasn't more time to put it in or if it was
>> > overlooked.
>> The problem here is the shortage of free time for the person who
>> currently reviews them.
>> Eventually, all the backlog will be handled...
>>
>> > Does it help to place a pull requets in github.
>> >
>> > Kind regards
>> > Sascha
>> Roman.
>>
>> > 2016-10-01 22:27 GMT+02:00 Sascha Oleszczuk <soleszc...@gmail.com>:
>> >>
>> >> Hi All,
>> >>
>> >> I have finalized and added the Fuji X-T2 noise profiles to the
>> >> follwoing
>> >> case:
>> >> https://redmine.darktable.org/issues/11151
>> >>
>> >> Best regards
>> >> Sascha
>> >
>> >
>> >
>> >
>> > ___
>> > 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 compiling

[Roman Lebedev]

Try now.

On Fri, Oct 28, 2016 at 12:07 AM, Michel Leblond
 wrote:
> I always delete build directory before compiling. I use gcc GNU 5.4.0.
>
> Michel.
>
>
> Le 27/10/2016 à 22:59, Tobias Ellinghaus a écrit :
>
> All of that looks good at first sight. It might take until tomorrow to find
> the
> issue.
>
> Tobias
>
> PS: Please send your answers to the list so others can come up with
> solutions,
> too.
>
> Am Donnerstag, 27. Oktober 2016, 21:54:13 CEST schrieb João Horta:
>
> i use this script for upgrade dev versions of darktable:
>
> #!/bin/sh
> #
> cd $HOME/darktable
> rm -rf build
> git pull
> ./build.sh --prefix /usr
> #./build.sh
> cd ./build && sudo make install
>
> 2016-10-27 21:52 GMT+01:00 João Horta :
>
> Building directory:  /home/jmhorta/darktable/build
> Installation prefix: /usr
> Build type:  RelWithDebInfo
> Build generator: Unix Makefiles
> Build tasks: 2
>
>
> -- The CXX compiler identification is GNU 5.4.0
> -- The C compiler identification is GNU 5.4.0
> -- Check for working CXX compiler: /usr/bin/c++
> -- Check for working CXX compiler: /usr/bin/c++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Performing Test _MSSE2
> -- Performing Test _MSSE2 - Success
> -- Building SSE2-optimized codepaths: ON
> -- Check if the system is big endian
> -- Searching 16 bit integer
> -- Looking for sys/types.h
> -- Looking for sys/types.h - found
> -- Looking for stdint.h
> -- Looking for stdint.h - found
> -- Looking for stddef.h
> -- Looking for stddef.h - found
> -- Check size of unsigned short
> -- Check size of unsigned short - done
> -- Using unsigned short
> -- Check if the system is big endian - little endian
> -- Found little endian system. Good.
> -- Performing Test IS_SUPPORTED_PLATFORM
> -- Performing Test IS_SUPPORTED_PLATFORM - Success
> -- Is the target platform supported: 1
> -- multiarch triplet detected: x86_64-linux-gnu
> -- Performing Test C_COMPILER_UNDERSTANDS_-Wall
> -- Performing Test C_COMPILER_UNDERSTANDS_-Wall - Success
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-Wall
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-Wall - Success
> -- Performing Test C_COMPILER_UNDERSTANDS_-fno-strict-aliasing
> -- Performing Test C_COMPILER_UNDERSTANDS_-fno-strict-aliasing - Success
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-fno-strict-aliasing
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-fno-strict-aliasing - Success
> -- Performing Test C_COMPILER_UNDERSTANDS_-Wformat
> -- Performing Test C_COMPILER_UNDERSTANDS_-Wformat - Success
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-Wformat
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-Wformat - Success
> -- Performing Test C_COMPILER_UNDERSTANDS_-Wformat-security
> -- Performing Test C_COMPILER_UNDERSTANDS_-Wformat-security - Success
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-Wformat-security
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-Wformat-security - Success
> -- Performing Test C_COMPILER_UNDERSTANDS_-Wshadow
> -- Performing Test C_COMPILER_UNDERSTANDS_-Wshadow - Success
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-Wshadow
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-Wshadow - Success
> -- Performing Test C_COMPILER_UNDERSTANDS_-Wtype-limits
> -- Performing Test C_COMPILER_UNDERSTANDS_-Wtype-limits - Success
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-Wtype-limits
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-Wtype-limits - Success
> -- Performing Test C_COMPILER_UNDERSTANDS_-Wvla
> -- Performing Test C_COMPILER_UNDERSTANDS_-Wvla - Success
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-Wvla
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-Wvla - Success
> -- Performing Test C_COMPILER_UNDERSTANDS_-Wold-style-declaration
> -- Performing Test C_COMPILER_UNDERSTANDS_-Wold-style-declaration -
> Success
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-Wold-style-declaration
> -- Performing Test CXX_COMPILER_UNDERSTANDS_-Wold-style-declaration -
> Failed
> -- 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
> -- 

Re: [darktable-dev] Gaussian Display Error

[Roman Lebedev]

Does all of you expirience the problem with X-Trans sensor?
Or with Bayer too?

For x-trans: https://redmine.darktable.org/issues/11272
For bayer need reproducer.
Hint: you can run darktable as  `darktable -d nan`  and look for
"Module xyz outputs NaNs!" in the console output."

Roman.

On Sun, Oct 30, 2016 at 11:21 AM, David Vincent-Jones
 wrote:
> I opened dt (with gdb) using an image that showed the problem yesterday and
> it was still apparent at start up ... I switched several times between
> gaussian and bilateral and the problem was clearly indicated; the 2
> locations blacked-out and reapeared with the change.
>
> Nothing unusual in the gdb listing.
>
> Tried to adjust memory settings (8 gb on this machine) ... no change.
>
> 2.1.pre+git2000.f63e5ce-1.1 Opensuse 42.1
>
>
> On 10/29/2016 10:59 AM, Patrick Shanahan wrote:
>>
>> * David Vincent-Jones  [10-29-16 12:33]:
>>>
>>> I find that if gaussian curve is used either with shad/high or lowpass
>>> the
>>> display of the histogram is lost also the top-left overall image.
>>>
>>> I first noticed this with shad/high and found the situation was corrected
>>> when I switched to bilateral filter.
>>
>> seems also to happen with perspective correction on 19c3415, but not all
>> the time, and is still active/usable to adjust exposure.  it also will
>> reappear when accessing some other modules.
>>
>
> ___
> 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] Gaussian Display Error

[Roman Lebedev]

On Sun, Oct 30, 2016 at 3:28 PM, David Vincent-Jones <david...@gmail.com> wrote:
> Yes, this is an x-trans raw file 
I'm mostly asking, can anyone reproduce this with bayer raw?

> and yes NaNs are in console output as
> below:
>
> [dev_pixelpipe] module `lowpass' outputs NaNs! [preview]
> [dev_pixelpipe] module `lowpass' min: (0.00; -128.00; -128.00)
> max: (100.00; 128.00; 128.00) [preview]
> [dev_pixelpipe] module `output color profile' outputs NaNs! [preview]
> [dev_pixelpipe] module `output color profile' min: (0.00; 0.00;
> 0.00) max: (1.329883; 1.130938; 1.493263) [preview]
> [dev_pixelpipe] module `velvia' outputs NaNs! [preview]
> [dev_pixelpipe] module `velvia' min: (0.00; 0.00; 0.00) max:
> (1.00; 1.00; 1.00) [preview][dev_pixelpipe] module `lowpass'
> outputs NaNs! [preview]
> [dev_pixelpipe] module `lowpass' min: (0.00; -128.00; -128.00)
> max: (100.00; 128.00; 128.00) [preview]
> [dev_pixelpipe] module `output color profile' outputs NaNs! [preview]
> [dev_pixelpipe] module `output color profile' min: (0.00; 0.00;
> 0.00) max: (1.329883; 1.130938; 1.493263) [preview]
> [dev_pixelpipe] module `velvia' outputs NaNs! [preview]
> [dev_pixelpipe] module `velvia' min: (0.00; 0.00; 0.00) max:
> (1.000000; 1.00; 1.00) [preview]
>
>
>
> On 10/30/2016 01:53 AM, Roman Lebedev wrote:
>>
>> Does all of you expirience the problem with X-Trans sensor?
>> Or with Bayer too?
>>
>> For x-trans: https://redmine.darktable.org/issues/11272
>> For bayer need reproducer.
>> Hint: you can run darktable as  `darktable -d nan`  and look for
>> "Module xyz outputs NaNs!" in the console output."
>>
>> Roman.
>>
>> On Sun, Oct 30, 2016 at 11:21 AM, David Vincent-Jones
>> <david...@gmail.com> wrote:
>>>
>>> I opened dt (with gdb) using an image that showed the problem yesterday
>>> and
>>> it was still apparent at start up ... I switched several times between
>>> gaussian and bilateral and the problem was clearly indicated; the 2
>>> locations blacked-out and reapeared with the change.
>>>
>>> Nothing unusual in the gdb listing.
>>>
>>> Tried to adjust memory settings (8 gb on this machine) ... no change.
>>>
>>> 2.1.pre+git2000.f63e5ce-1.1 Opensuse 42.1
>>>
>>>
>>> On 10/29/2016 10:59 AM, Patrick Shanahan wrote:
>>>>
>>>> * David Vincent-Jones <david...@gmail.com> [10-29-16 12:33]:
>>>>>
>>>>> I find that if gaussian curve is used either with shad/high or lowpass
>>>>> the
>>>>> display of the histogram is lost also the top-left overall image.
>>>>>
>>>>> I first noticed this with shad/high and found the situation was
>>>>> corrected
>>>>> when I switched to bilateral filter.
>>>>
>>>> seems also to happen with perspective correction on 19c3415, but not all
>>>> the time, and is still active/usable to adjust exposure.  it also will
>>>> reappear when accessing some other modules.
>>>>
>>>
>>> ___
>>> 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] extract_wb ruby script doesn't work for Fuji X-TRANS RAF

[Roman Lebedev]

On Tue, Nov 8, 2016 at 5:53 PM, Sascha Oleszczuk <soleszc...@gmail.com> wrote:
> Hi Roman,
>
> attached the updated script.
Oh, you modified the extract_wb from darktable-2.0.x branch?
Did you check beforehand whether the version in master branch works
for RAF's already?

> Sorry to mess up the pull request. First time that I used github.
> Next time I need to deep dive in github before creating a request.
>
> The Fuji X-T2 wb settings are listed below and attached to the case
> https://redmine.darktable.org/issues/11174
>
> { "Fujifilm", "X-T2", Daylight, 0, { 1.877483, 1, 1.940397, 0 } },
> { "Fujifilm", "X-T2", Cloudy, 0, { 2.086093, 1, 1.672185, 0 } },
> { "Fujifilm", "X-T2", DaylightFluorescent, 0, { 2.360927, 1, 1.668874, 0 }
> },
> { "Fujifilm", "X-T2", DayWhiteFluorescent, 0, { 1.976821, 1, 2.05298, 0 } },
> { "Fujifilm", "X-T2", WhiteFluorescent, 0, { 1.86755, 1, 2.639073, 0 } },
> { "Fujifilm", "X-T2", Incandescent, 0, { 1.248344, 1, 2.907285, 0 } },
> { "Fujifilm", "X-T2", Underwater, 0, { 1.877483, 1, 1.940397, 0 } },
>
>
> Thx in advance and sorry again
> Sascha
Roman.

> 2016-11-07 16:56 GMT+01:00 Roman Lebedev <lebedev...@gmail.com>:
>>
>> On Mon, Nov 7, 2016 at 6:32 PM, Sascha Oleszczuk <soleszc...@gmail.com>
>> wrote:
>> > Hi Roman,
>> >
>> > I did. What is the best way to share the updated extract_wb script?
>> Best - commit and create pullrequest on github.
>>
>> Other than that, anything that works for you, you could even just
>> attach it email.
>>
>> > Thx
>> > Sascha
>> Roman.
>>
>> > 2016-11-06 12:33 GMT+01:00 Roman Lebedev <lebedev...@gmail.com>:
>> >>
>> >> On Sun, Nov 6, 2016 at 1:16 AM, Sascha Oleszczuk <soleszc...@gmail.com>
>> >> wrote:
>> >> > The new extract_wb ruby script can't export the wb settings from my
>> >> > fuji
>> >> > X-T2 RAF files.
>> >> > I get only the following message:
>> >> > ERROR: Couldn't figure out preset values, sorry
>> >> >
>> >> > I tried the extract_wb from darktable 2.0.6 and 2.0.7 both will not
>> >> > work.
>> >> >
>> >> > Tests with my old Canon 7D files succeed.
>> >> > Looks like the script is not supporting Fuji RAF files.
>> >> >
>> >> > I tried as well X-Pro2 RAF files - same effect.
>> >> > In both cases I used uncompressed RAWs.
>> >> >
>> >> > Any hint?
>> >>
>> >> Look what old perl based script does, and possibly attempt to
>> >> modify extract_wb to be able to do the same :)
>> >>
>> >> > Sascha
>> >> 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] extract_wb ruby script doesn't work for Fuji X-TRANS RAF

[Roman Lebedev]

On Sun, Nov 6, 2016 at 1:16 AM, Sascha Oleszczuk  wrote:
> The new extract_wb ruby script can't export the wb settings from my fuji
> X-T2 RAF files.
> I get only the following message:
> ERROR: Couldn't figure out preset values, sorry
>
> I tried the extract_wb from darktable 2.0.6 and 2.0.7 both will not work.
>
> Tests with my old Canon 7D files succeed.
> Looks like the script is not supporting Fuji RAF files.
>
> I tried as well X-Pro2 RAF files - same effect.
> In both cases I used uncompressed RAWs.
>
> Any hint?

Look what old perl based script does, and possibly attempt to
modify extract_wb to be able to do the same :)

> Sascha
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] Cygwin

[Roman Lebedev]

On Sun, Nov 6, 2016 at 10:55 AM, Phil Rosenberg  wrote:
> Hi
> Up front I will say I have read your policy on Windows and totally
> agree. I also work on an open source project and supporting many OSs
> is tough and usually requires at least a couple of developers willing
> to use and test the code as it develops.
>
> So with that in mind you are free to tell me that you cannot help me
> with building on Cygwin, however I'm very close to completing the
> build and I have made notes on how to get the build running which I am
> happy to share If that is useful to you.

Please start talking to peterbud and Jan Ingwer NOW.
https://github.com/darktable-org/darktable/pull/1327

Spreading effort will only negatively help.

> In case you can help, my issue is that during the make all step of the
> build I am getting this error
>
> Scanning dependencies of target darktable.appdata_file
> [ 99%] Generating darktable.appdata.xml
> Merging translations into
> /home/phil/usr/src/darktable/build/data/darktable.appdata.xml.
> CREATED /home/phil/usr/src/darktable/build/data/darktable.appdata.xml
> /home/phil/usr/src/darktable/build/data/darktable.appdata.xml: FAILED:
> • tag-missing   :  is not present
> Validation of files failed
> make[2]: *** [data/CMakeFiles/darktable.appdata_file.dir/build.make:89:
> data/darktable.appdata.xml] Error 1
> make[2]: *** Deleting file 'data/darktable.appdata.xml'
> make[1]: *** [CMakeFiles/Makefile2:6870:
> data/CMakeFiles/darktable.appdata_file.dir/all] Error 2
> make: *** [Makefile:139: all] Error 2

That is appstream-util bug.

> I presume this is an xml tag that is missing from somewhere, but I
> can't work out which file it is missing from to look at fixing it. I'm
> not so good with makefiles.
>
> I'm building from the git repo if that helps. Currently at commit
> d62c69e36ab428e37df0ae6b57e704bc9178d0b0
>
> Thanks in advance
>
> Phil
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] extract_wb ruby script doesn't work for Fuji X-TRANS RAF

[Roman Lebedev]

On Tue, Nov 8, 2016 at 5:53 PM, Sascha Oleszczuk <soleszc...@gmail.com> wrote:
> Hi Roman,

> attached the updated script.
OK!
It took some doing, but i was able to port it to the git master...
For future reference, please do understand that git master is the only
thing that matters, changes are done *only* in git master, and then
(optionally) picked to stable branch.

> Sorry to mess up the pull request. First time that I used github.
> Next time I need to deep dive in github before creating a request.
Yes, please do learn git, it is a very important tool :)

> The Fuji X-T2 wb settings are listed below and attached to the case
> https://redmine.darktable.org/issues/11174
>
> { "Fujifilm", "X-T2", Daylight, 0, { 1.877483, 1, 1.940397, 0 } },
> { "Fujifilm", "X-T2", Cloudy, 0, { 2.086093, 1, 1.672185, 0 } },
> { "Fujifilm", "X-T2", DaylightFluorescent, 0, { 2.360927, 1, 1.668874, 0 }
> },
> { "Fujifilm", "X-T2", DayWhiteFluorescent, 0, { 1.976821, 1, 2.05298, 0 } },
> { "Fujifilm", "X-T2", WhiteFluorescent, 0, { 1.86755, 1, 2.639073, 0 } },
> { "Fujifilm", "X-T2", Incandescent, 0, { 1.248344, 1, 2.907285, 0 } },
> { "Fujifilm", "X-T2", Underwater, 0, { 1.877483, 1, 1.940397, 0 } },
>
>
> Thx in advance and sorry again
Thank *you*.

> Sascha
Roman.

> 2016-11-07 16:56 GMT+01:00 Roman Lebedev <lebedev...@gmail.com>:
>>
>> On Mon, Nov 7, 2016 at 6:32 PM, Sascha Oleszczuk <soleszc...@gmail.com>
>> wrote:
>> > Hi Roman,
>> >
>> > I did. What is the best way to share the updated extract_wb script?
>> Best - commit and create pullrequest on github.
>>
>> Other than that, anything that works for you, you could even just
>> attach it email.
>>
>> > Thx
>> > Sascha
>> Roman.
>>
>> > 2016-11-06 12:33 GMT+01:00 Roman Lebedev <lebedev...@gmail.com>:
>> >>
>> >> On Sun, Nov 6, 2016 at 1:16 AM, Sascha Oleszczuk <soleszc...@gmail.com>
>> >> wrote:
>> >> > The new extract_wb ruby script can't export the wb settings from my
>> >> > fuji
>> >> > X-T2 RAF files.
>> >> > I get only the following message:
>> >> > ERROR: Couldn't figure out preset values, sorry
>> >> >
>> >> > I tried the extract_wb from darktable 2.0.6 and 2.0.7 both will not
>> >> > work.
>> >> >
>> >> > Tests with my old Canon 7D files succeed.
>> >> > Looks like the script is not supporting Fuji RAF files.
>> >> >
>> >> > I tried as well X-Pro2 RAF files - same effect.
>> >> > In both cases I used uncompressed RAWs.
>> >> >
>> >> > Any hint?
>> >>
>> >> Look what old perl based script does, and possibly attempt to
>> >> modify extract_wb to be able to do the same :)
>> >>
>> >> > Sascha
>> >> 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] extract_wb ruby script doesn't work for Fuji X-TRANS RAF

[Roman Lebedev]

On Mon, Nov 7, 2016 at 6:32 PM, Sascha Oleszczuk <soleszc...@gmail.com> wrote:
> Hi Roman,
>
> I did. What is the best way to share the updated extract_wb script?
Best - commit and create pullrequest on github.

Other than that, anything that works for you, you could even just
attach it email.

> Thx
> Sascha
Roman.

> 2016-11-06 12:33 GMT+01:00 Roman Lebedev <lebedev...@gmail.com>:
>>
>> On Sun, Nov 6, 2016 at 1:16 AM, Sascha Oleszczuk <soleszc...@gmail.com>
>> wrote:
>> > The new extract_wb ruby script can't export the wb settings from my fuji
>> > X-T2 RAF files.
>> > I get only the following message:
>> > ERROR: Couldn't figure out preset values, sorry
>> >
>> > I tried the extract_wb from darktable 2.0.6 and 2.0.7 both will not
>> > work.
>> >
>> > Tests with my old Canon 7D files succeed.
>> > Looks like the script is not supporting Fuji RAF files.
>> >
>> > I tried as well X-Pro2 RAF files - same effect.
>> > In both cases I used uncompressed RAWs.
>> >
>> > Any hint?
>>
>> Look what old perl based script does, and possibly attempt to
>> modify extract_wb to be able to do the same :)
>>
>> > Sascha
>> 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] Cannot build Darktable release-2.0.6 on Mac OS X 10.12 (Sierra)

[Roman Lebedev]

 *** 
> [src/external/rawspeed/CMakeFiles/rawspeed.dir/RawSpeed/DngDecoderSlices.cpp.o]
>  Error 1
> make[1]: *** [src/external/rawspeed/CMakeFiles/rawspeed.dir/all] Error 2
> make: *** [all] Error 2

Could you please try the attached patch and let me know whether it helps?

> Maybe some library is missing. Voilà a selection of what I have installed 
> using MacPorts base version 2.3.4:
>
> $ port echo installed | grep -i -E "saxon|xml|xslt“
>
> docbook-xml-4.1.2  @5.0_1
> docbook-xml-4.2@5.0_1
> docbook-xml-4.3@5.0_1
> docbook-xml-4.4@5.0_1
> docbook-xml-4.5@5.0_1
> docbook-xml-5.0@5.0_1
> libxml2@2.9.4_0
> libxslt@1.1.29_1
> p5.24-xml-parser   @2.440.0_0
> pugixml@1.7_0
> saxon  @9.5.1.1_0
> xmlcatmgr  @2.2_1
>
>
>
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

From f2206f863b05f250b11c17638dff640035ff99e6 Mon Sep 17 00:00:00 2001
From: Roman Lebedev <lebedev...@gmail.com>
Date: Tue, 18 Oct 2016 10:30:06 +0300
Subject: [PATCH] Rawspeed: common.h: C++: true/false are not 1/0

---
 src/external/rawspeed/RawSpeed/Common.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/external/rawspeed/RawSpeed/Common.h b/src/external/rawspeed/RawSpeed/Common.h
index 8e444bf..b515350 100644
--- a/src/external/rawspeed/RawSpeed/Common.h
+++ b/src/external/rawspeed/RawSpeed/Common.h
@@ -58,10 +58,10 @@ typedef char* LPCWSTR;
 #endif // __unix__
 
 #ifndef TRUE
-#define TRUE 1
+#define TRUE true
 #endif
 #ifndef FALSE
-#define FALSE 0
+#define FALSE false
 #endif
 
 #define get2BE(data,pos) ushort16)(data)[pos]) << 8) | \
-- 
2.9.3

Re: [darktable-dev] Shadows/Highlights Problem

[Roman Lebedev]

On Wed, Oct 12, 2016 at 11:06 PM, David Vincent-Jones
 wrote:
> When S/H is used with gaussian param ... both the histogram and the top left
> (small) image go blank.
> I have also found on some occasions that the main image also blanks out.
> This does not occur if bilateral-filter is selected.
> darktable 2.1.pre+git1806.5b5c954-1.1
That is old.
Please try with current git master.

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] PSA: ATTENTION NIKON OWNERS !!!

[Roman Lebedev]

On Fri, Oct 14, 2016 at 10:45 PM, Wolfgang Goetz <wolfgang.zt...@web.de> wrote:
> Roman Lebedev wrote:
>
>> Hi all.
>
> Hello dev's,
>
> please find attached some thoughts about the planned deprecation.
>
>
>
>> This mail is primarily targeted to all the owners of Nikon cameras.
>
> bunch of them in the last decade, actually two.
>
>
>> As you may have seen, an issue with white level for some
>> nikon cameras (or so i thought) was discovered by me:
>> https://www.mail-archive.com/darktable-dev@lists.darktable.org/msg01196.html
>>
>
> great. really!
>
>
>
>> In the meantime i have adjusted white levels for all the cameras i
>> could find samples for.
>
> great. thx a lot.
>
>
>> But unfortunately, for some cameras i was unable to find samples.
>> Below, you will find a list of all the cameras for which i need
>> samples.
>>
>> IMPORTANT: if you see your camera in that list, it is imperative for
>> you to provide
>> a sample set, or else your camera will not be supported in next
>> darktable release!
>>
> [...]
>
> sigh.
Doing that in a point release was a bad move, i do not deny that.
I guess my excuse was that i did not expected to see *so much*
issues.

I'm **cautiously optimistic** that we may get all or most cameras
off the list before .7

BTW, the current version of the list:

NIKON COOLPIX P6000
NIKON COOLPIX P7000
NIKON CORPORATION COOLPIX A
NIKON CORPORATION NIKON 1 AW1
NIKON CORPORATION NIKON 1 J4
NIKON CORPORATION NIKON D100
NIKON CORPORATION NIKON D1H
NIKON CORPORATION NIKON D3S
NIKON CORPORATION NIKON D3X
NIKON CORPORATION NIKON D5
NIKON CORPORATION NIKON Df
NIKON E5400
NIKON E5700
NIKON E8400
NIKON E8800


Just 16 cameras left, and there are 8 unhandled issues with samples in redmine..

BTW, special thanks to Stefan Schöfegger for helping me go through
that backlog!.

Roman.

> meanwhile...
> found D70 is on the way.
> hope the best for others.
>
>
>
>
>
>
> kind regards
> Wolfgang
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] can't find libintl while building and no Internationalization as a result

[Roman Lebedev]

On Sun, Oct 23, 2016 at 10:56 PM, shlomi braitbart <sbraitb...@gmail.com> wrote:
> Sorry but I didn't understand what you mean by "remove build dir first"
> Do I need to change something in the build.sh script?
No:

$ cd /home/shlomi/darktable2/darktable/
$ rm -rf build/
$ ./build.sh

> On Sun, Oct 23, 2016 at 10:47 PM, Roman Lebedev <lebedev...@gmail.com>
> wrote:
>>
>> On Sun, Oct 23, 2016 at 10:43 PM, shlomi braitbart <sbraitb...@gmail.com>
>> wrote:
>> > Sure.
>> > Please find the attached txt file for the cmake output.
>> > hope a txt file is okay.
>> Better :)
>> Now, remove build dir first so that we can actually see all the cmake
>> output.
>>
>> > thanks
>> > Shlomi
>> Roman.
>>
>> > On Sun, Oct 23, 2016 at 5:28 PM, Roman Lebedev <lebedev...@gmail.com>
>> > wrote:
>> >>
>> >> Please do show the whole cmake output.
>> >>
>> >> On Sun, Oct 23, 2016 at 5:17 PM, shlomi braitbart
>> >> <sbraitb...@gmail.com>
>> >> wrote:
>> >> > Hello.
>> >> > I maintain the Hebrew translation and I noticed the changes I made
>> >> > are
>> >> > not
>> >> > implemented after building dt.
>> >> > Looking at the terminal build messages I see the following message:
>> >> > -- Internationalization: Disabled (libintl not found)
>> >> > I checked and I seem to have "libintl-perl" & " libintl-xs-perl"
>> >> > installed.
>> >> > Am I missing something?
>> >> > System is Debian Jessie
>> >> > Darktable master branch
>> >> >
>> >> > To build I run:
>> >> >
>> >> > cd build/
>> >> > make clean
>> >> > cd ..
>> >> > ./build.sh
>> >> > cd build
>> >> > sudo make install
>> >> >
>> >> > please advise
>> >> >
>> >> > thanks
>> >> > Shlomi
>> >> >
>> >> >
>> >> >
>> >> > ___
>> >> > 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 find libintl while building and no Internationalization as a result

[Roman Lebedev]

On Sun, Oct 23, 2016 at 10:43 PM, shlomi braitbart <sbraitb...@gmail.com> wrote:
> Sure.
> Please find the attached txt file for the cmake output.
> hope a txt file is okay.
Better :)
Now, remove build dir first so that we can actually see all the cmake output.

> thanks
> Shlomi
Roman.

> On Sun, Oct 23, 2016 at 5:28 PM, Roman Lebedev <lebedev...@gmail.com> wrote:
>>
>> Please do show the whole cmake output.
>>
>> On Sun, Oct 23, 2016 at 5:17 PM, shlomi braitbart <sbraitb...@gmail.com>
>> wrote:
>> > Hello.
>> > I maintain the Hebrew translation and I noticed the changes I made are
>> > not
>> > implemented after building dt.
>> > Looking at the terminal build messages I see the following message:
>> > -- Internationalization: Disabled (libintl not found)
>> > I checked and I seem to have "libintl-perl" & " libintl-xs-perl"
>> > installed.
>> > Am I missing something?
>> > System is Debian Jessie
>> > Darktable master branch
>> >
>> > To build I run:
>> >
>> > cd build/
>> > make clean
>> > cd ..
>> > ./build.sh
>> > cd build
>> > sudo make install
>> >
>> > please advise
>> >
>> > thanks
>> > Shlomi
>> >
>> >
>> > ___
>> > 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] Re: PSA: ATTENTION NIKON OWNERS !!! LAST CALL

[Roman Lebedev]

Ok, some more samples were provided.
we are down to final 4 missing cameras:

Here is the current up-to-date list of the cameras, samples
from which are still wanted:

NIKON E8400, need one any raw
NIKON E8800, need one any raw
NIKON CORPORATION NIKON D3X, need three (at least one) 12bit samples
with different compressions
NIKON CORPORATION NIKON Df, need three (at least one) 12bit samples
with different compressions

Thank you everyone who submitted samples!
Special thanks to Stefan Schöfegger.

We will *probably* release 2.0.7 soon.
Better get these samples now.

Roman.

On Thu, Oct 13, 2016 at 8:51 PM, Roman Lebedev <lebedev...@gmail.com> wrote:
> Okay, some samples were provided, a few cameras got off the list.
> But not all.
>
> Here is the current up-to-date list of the cameras, samples
> from which are still wanted:
>
> NIKON COOLPIX P6000
> NIKON COOLPIX P7000
> NIKON COOLPIX P7100
> NIKON CORPORATION COOLPIX A
> NIKON CORPORATION NIKON 1 AW1
> NIKON CORPORATION NIKON 1 J4
> NIKON CORPORATION NIKON 1 S2
> NIKON CORPORATION NIKON D1
> NIKON CORPORATION NIKON D100
> NIKON CORPORATION NIKON D1H
> NIKON CORPORATION NIKON D3100
> NIKON CORPORATION NIKON D3S
> NIKON CORPORATION NIKON D3X
> NIKON CORPORATION NIKON D5
> NIKON CORPORATION NIKON D70
> NIKON CORPORATION NIKON D70s
> NIKON CORPORATION NIKON Df
> NIKON E5400
> NIKON E5700
> NIKON E8400
> NIKON E8800
>
> IMPORTANT: if you see your camera in that list, it is imperative for
> you to provide a sample set, or else your camera
> will not be supported in next darktable release!
>
> We are thinking about doing 2.0.7 in a couple weeks.
> Better get these samples now.
>
> Roman.
>
> On Fri, Oct 7, 2016 at 4:00 PM, Roman Lebedev <lebedev...@gmail.com> wrote:
>> Hi all.
>>
>> This mail is primarily targeted to all the owners of Nikon cameras.
>>
>> As you may have seen, an issue with white level for some
>> nikon cameras (or so i thought) was discovered by me:
>> https://www.mail-archive.com/darktable-dev@lists.darktable.org/msg01196.html
>>
>> In the meantime i have adjusted white levels for all the cameras i
>> could find samples for.
>> But unfortunately, for some cameras i was unable to find samples.
>>
>> Below, you will find a list of all the cameras for which i need samples.
>>
>> IMPORTANT: if you see your camera in that list, it is imperative for
>> you to provide
>> a sample set, or else your camera will not be supported in next
>> darktable release!
>>
>> NIKON COOLPIX P6000
>> NIKON COOLPIX P7000
>> NIKON COOLPIX P7100
>> NIKON CORPORATION COOLPIX A
>> NIKON CORPORATION NIKON 1 AW1
>> NIKON CORPORATION NIKON 1 J4
>> NIKON CORPORATION NIKON 1 S2
>> NIKON CORPORATION NIKON D1
>> NIKON CORPORATION NIKON D100
>> NIKON CORPORATION NIKON D1H
>> NIKON CORPORATION NIKON D1X
>> NIKON CORPORATION NIKON D3
>> NIKON CORPORATION NIKON D3100
>> NIKON CORPORATION NIKON D3S
>> NIKON CORPORATION NIKON D3X
>> NIKON CORPORATION NIKON D5
>> NIKON CORPORATION NIKON D5100
>> NIKON CORPORATION NIKON D5200
>> NIKON CORPORATION NIKON D70
>> NIKON CORPORATION NIKON D700
>> NIKON CORPORATION NIKON D70s
>> NIKON CORPORATION NIKON Df
>> NIKON E5400
>> NIKON E5700
>> NIKON E8400
>> NIKON E8800
>>
>> (that is an auto-generated list, fresh version of the list can be
>> acquired by running
>> https://github.com/darktable-org/darktable/blob/master/tools/rawspeed-check-nikon-modes.rb)
>>
>> Now, which samples do i need?
>>
>> Each nikon camera has several settings:
>> 1. Raw file bitness; can be 14bit and 12bit, not all cameras have that 
>> setting.
>> 2. Raw file compression; can be compressed, losslessly compressed and
>> uncompressed. not all cameras have every option.
>>
>> I need one sample per each combination.
>> I.e. for different cameras that can be from just one sample, up to 6
>> samples on the newest cameras.
>>
>> Content of the sample does not matter, you could even put body cap on.
>>
>> After taking samples, head to https://redmine.darktable.org/issues
>> check that the samples for that camera was not already provided,
>> open new issue
>> https://redmine.darktable.org/projects/darktable/issues/new
>> Tracker = "Camera support"
>> Subject = "${Camera maker} ${Camera model} raw support"
>>
>> And attach samples.
>> If you can not attach samples (e.g. filesize), upload them somewhere,
>> and attach a link to samples.
>>
>> (Also, it is a very good idea to also check whether rawsamples.ch has
>> sample for your camera, and send them samples too)
>>
>> Roman.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] can't find libintl while building and no Internationalization as a result

[Roman Lebedev]

Please do show the whole cmake output.

On Sun, Oct 23, 2016 at 5:17 PM, shlomi braitbart  wrote:
> Hello.
> I maintain the Hebrew translation and I noticed the changes I made are not
> implemented after building dt.
> Looking at the terminal build messages I see the following message:
> -- Internationalization: Disabled (libintl not found)
> I checked and I seem to have "libintl-perl" & " libintl-xs-perl" installed.
> Am I missing something?
> System is Debian Jessie
> Darktable master branch
>
> To build I run:
>
> cd build/
> make clean
> cd ..
> ./build.sh
> cd build
> sudo make install
>
> please advise
>
> thanks
> Shlomi
>
> ___
> 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] Feature Request

[Roman Lebedev]

On Tue, Oct 18, 2016 at 10:01 PM, Tim Rolph  wrote:
> Hi All, would it be possible to add an option for auto raw white point
> calculation?
No. Because that would be selfish.
If it really is an issue, you need to report it:
https://redmine.darktable.org/projects/darktable/issues/new
And do attach one raw per every iso level.
That way it could be fixed for everyone :)

> At the moment the raw white point for CRW files is set at 4000, I
> believe this is because of Adobe DNG creator reports this! I find that the
> required white point can vary between 1000 and 9000 depending on the
> individual image!

> I also have just checked how Rawtherapee handles highlight reconstruction and
> it seem at least on the few images I have checked to produce better
> results.:-(
That statement is too generic.
Which darktable version, which highlight reconstruction mode?
Which rt's highlight reconstruction mode?

But i can tell you that dt's highlight reconstruction mode LCh got much better
in git master compared to 2.0.x

> Regards,
>
> Tim
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 find libintl while building and no Internationalization as a result

[Roman Lebedev]

On Tue, Oct 25, 2016 at 5:28 PM, shlomi braitbart <sbraitb...@gmail.com> wrote:
> Okay here is what I got:
>
> shlomi@avia:~/darktable2/darktable$ git pull --tags
> Already up-to-date.
> shlomi@avia:~/darktable2/darktable$ git pull --tags upstream
> remote: Counting objects: 50, done.
> remote: Compressing objects: 100% (50/50), done.
> remote: Total 50 (delta 17), reused 0 (delta 0), pack-reused 0
> Unpacking objects: 100% (50/50), done.
> From https://github.com/darktable-org/darktable
>961f311..6d3a382  master -> upstream/master
> It doesn't make sense to pull all tags; you probably meant:
>   git fetch --tags

Err, i indeed meant  $ git fetch --tags
:)

> shlomi@avia:~/darktable2/darktable$ git fetch upstream
> shlomi@avia:~/darktable2/darktable$ ./build.sh > ../cmake_output29.txt
> -- multiarch triplet detected: x86_64-linux-gnu
> -- Checking for -march=native support
> Missing fop
> Can NOT build Lua API documentation
> /home/shlomi/darktable2/darktable/src/external/rawspeed/data/cameras.xml
> validates
> Validation of files failed
> make[2]: *** [data/darktable.appdata.xml] Error 1
> make[1]: *** [data/CMakeFiles/darktable.appdata_file.dir/all] Error 2
> make[1]: *** Waiting for unfinished jobs
> make: *** [all] Error 2
>
> the cmake output is attached.
> Seems the same to me.
>
>
> On Tue, Oct 25, 2016 at 5:19 PM, Roman Lebedev <lebedev...@gmail.com> wrote:
>>
>> try
>>
>> git pull --tags
>> git pull --tags upstream
>> git fetch upstream
>>
>> On Tue, Oct 25, 2016 at 5:11 PM, shlomi braitbart <sbraitb...@gmail.com>
>> wrote:
>> > Still getting the
>> > Already up-to-date
>> > message with no change of number:
>> >
>> > git describe
>> > release-0.9.3-13734-ge493501
>> > git status
>> > On branch master
>> > Your branch is ahead of 'origin/master' by 3 commits.
>> >   (use "git push" to publish your local commits)
>> > Untracked files:
>> >   (use "git add ..." to include in what will be committed)
>> >
>> > po/he.mo
>> >
>> > nothing added to commit but untracked files present (use "git add" to
>> > track)
>> >
>> >
>> >
>> > On Tue, Oct 25, 2016 at 12:33 PM, Tobias Ellinghaus <m...@houz.org> wrote:
>> >>
>> >> Am Montag, 24. Oktober 2016, 20:06:23 CEST schrieb shlomi braitbart:
>> >> > git describe
>> >> > release-0.9.3-13734-ge493501
>> >>
>> >> That looks good. Does a "git pull" bring you any updates now? And
>> >> change
>> >> the
>> >> 13734 to 13738 or something like that?
>> >>
>> >> > git status
>> >> > On branch master
>> >> > Your branch is ahead of 'origin/master' by 3 commits.
>> >> >   (use "git push" to publish your local commits)
>> >> > Untracked files:
>> >> >   (use "git add ..." to include in what will be committed)
>> >> >
>> >> > po/he.mo
>> >> >
>> >> > nothing added to commit but untracked files present (use "git add" to
>> >> > track)
>> >> >
>> >> > Shlomi
>> >> >
>> >> > On Mon, Oct 24, 2016 at 7:27 PM, Tobias Ellinghaus <m...@houz.org>
>> >> > wrote:
>> >> > > Am Montag, 24. Oktober 2016, 15:58:32 CEST schrieb shlomi
>> >> > > braitbart:
>> >> > > > When I do
>> >> > > > $ git pull
>> >> > > > I am getting:
>> >> > > > $ Already up-to-date.
>> >> > >
>> >> > > That sounds odd as I pushed changes before I wrote my last mail.
>> >> > >
>> >> > > What is the output of
>> >> > >
>> >> > > cd /home/shlomi/darktable2/darktable/
>> >> > > git describe
>> >> > > git status
>> >> > >
>> >> > > > (I am on the master branch)
>> >> > > > Trying to build result in an error same as before (attached file)
>> >> > > > I also attache CMakeCache.txt
>> >> > >
>> >> > > Tobias
>> >> > >
>> >> > > [...]
>> >> >
>> >> >
>> >> >
>> >> > ___
>> >> > 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] can't find libintl while building and no Internationalization as a result

[Roman Lebedev]

try

git pull --tags
git pull --tags upstream
git fetch upstream

On Tue, Oct 25, 2016 at 5:11 PM, shlomi braitbart  wrote:
> Still getting the
> Already up-to-date
> message with no change of number:
>
> git describe
> release-0.9.3-13734-ge493501
> git status
> On branch master
> Your branch is ahead of 'origin/master' by 3 commits.
>   (use "git push" to publish your local commits)
> Untracked files:
>   (use "git add ..." to include in what will be committed)
>
> po/he.mo
>
> nothing added to commit but untracked files present (use "git add" to track)
>
>
>
> On Tue, Oct 25, 2016 at 12:33 PM, Tobias Ellinghaus  wrote:
>>
>> Am Montag, 24. Oktober 2016, 20:06:23 CEST schrieb shlomi braitbart:
>> > git describe
>> > release-0.9.3-13734-ge493501
>>
>> That looks good. Does a "git pull" bring you any updates now? And change
>> the
>> 13734 to 13738 or something like that?
>>
>> > git status
>> > On branch master
>> > Your branch is ahead of 'origin/master' by 3 commits.
>> >   (use "git push" to publish your local commits)
>> > Untracked files:
>> >   (use "git add ..." to include in what will be committed)
>> >
>> > po/he.mo
>> >
>> > nothing added to commit but untracked files present (use "git add" to
>> > track)
>> >
>> > Shlomi
>> >
>> > On Mon, Oct 24, 2016 at 7:27 PM, Tobias Ellinghaus  wrote:
>> > > Am Montag, 24. Oktober 2016, 15:58:32 CEST schrieb shlomi braitbart:
>> > > > When I do
>> > > > $ git pull
>> > > > I am getting:
>> > > > $ Already up-to-date.
>> > >
>> > > That sounds odd as I pushed changes before I wrote my last mail.
>> > >
>> > > What is the output of
>> > >
>> > > cd /home/shlomi/darktable2/darktable/
>> > > git describe
>> > > git status
>> > >
>> > > > (I am on the master branch)
>> > > > Trying to build result in an error same as before (attached file)
>> > > > I also attache CMakeCache.txt
>> > >
>> > > Tobias
>> > >
>> > > [...]
>> >
>> >
>> > ___
>> > 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] can't find libintl while building and no Internationalization as a result

[Roman Lebedev]

Version string: 2.1.0+2014~ge493501

Better :)

On Tue, Oct 25, 2016 at 6:13 PM, shlomi braitbart <sbraitb...@gmail.com> wrote:
> So if I understood correctly:
> shlomi@avia:~/darktable2/darktable$ git fetch --tags
> shlomi@avia:~/darktable2/darktable$ git fetch --tags upstream
> shlomi@avia:~/darktable2/darktable$ git fetch upstream
> shlomi@avia:~/darktable2/darktable$ ./build.sh > ../cmake_output30.txt
> -- multiarch triplet detected: x86_64-linux-gnu
> -- Checking for -march=native support
> Missing fop
> Can NOT build Lua API documentation
> /home/shlomi/darktable2/darktable/src/external/rawspeed/data/cameras.xml
> validates
> Validation of files failed
> make[2]: *** [data/darktable.appdata.xml] Error 1
> make[1]: *** [data/CMakeFiles/darktable.appdata_file.dir/all] Error 2
> make[1]: *** Waiting for unfinished jobs
> make: *** [all] Error 2
>
> attached is the cmake output
>
>
> On Tue, Oct 25, 2016 at 5:49 PM, Roman Lebedev <lebedev...@gmail.com> wrote:
>>
>> On Tue, Oct 25, 2016 at 5:28 PM, shlomi braitbart <sbraitb...@gmail.com>
>> wrote:
>> > Okay here is what I got:
>> >
>> > shlomi@avia:~/darktable2/darktable$ git pull --tags
>> > Already up-to-date.
>> > shlomi@avia:~/darktable2/darktable$ git pull --tags upstream
>> > remote: Counting objects: 50, done.
>> > remote: Compressing objects: 100% (50/50), done.
>> > remote: Total 50 (delta 17), reused 0 (delta 0), pack-reused 0
>> > Unpacking objects: 100% (50/50), done.
>> > From https://github.com/darktable-org/darktable
>> >961f311..6d3a382  master -> upstream/master
>> > It doesn't make sense to pull all tags; you probably meant:
>> >   git fetch --tags
>>
>> Err, i indeed meant  $ git fetch --tags
>> :)
>>
>> > shlomi@avia:~/darktable2/darktable$ git fetch upstream
>> > shlomi@avia:~/darktable2/darktable$ ./build.sh > ../cmake_output29.txt
>> > -- multiarch triplet detected: x86_64-linux-gnu
>> > -- Checking for -march=native support
>> > Missing fop
>> > Can NOT build Lua API documentation
>> > /home/shlomi/darktable2/darktable/src/external/rawspeed/data/cameras.xml
>> > validates
>> > Validation of files failed
>> > make[2]: *** [data/darktable.appdata.xml] Error 1
>> > make[1]: *** [data/CMakeFiles/darktable.appdata_file.dir/all] Error 2
>> > make[1]: *** Waiting for unfinished jobs
>> > make: *** [all] Error 2
>> >
>> > the cmake output is attached.
>> > Seems the same to me.
>> >
>> >
>> > On Tue, Oct 25, 2016 at 5:19 PM, Roman Lebedev <lebedev...@gmail.com>
>> > wrote:
>> >>
>> >> try
>> >>
>> >> git pull --tags
>> >> git pull --tags upstream
>> >> git fetch upstream
>> >>
>> >> On Tue, Oct 25, 2016 at 5:11 PM, shlomi braitbart
>> >> <sbraitb...@gmail.com>
>> >> wrote:
>> >> > Still getting the
>> >> > Already up-to-date
>> >> > message with no change of number:
>> >> >
>> >> > git describe
>> >> > release-0.9.3-13734-ge493501
>> >> > git status
>> >> > On branch master
>> >> > Your branch is ahead of 'origin/master' by 3 commits.
>> >> >   (use "git push" to publish your local commits)
>> >> > Untracked files:
>> >> >   (use "git add ..." to include in what will be committed)
>> >> >
>> >> > po/he.mo
>> >> >
>> >> > nothing added to commit but untracked files present (use "git add" to
>> >> > track)
>> >> >
>> >> >
>> >> >
>> >> > On Tue, Oct 25, 2016 at 12:33 PM, Tobias Ellinghaus <m...@houz.org>
>> >> > wrote:
>> >> >>
>> >> >> Am Montag, 24. Oktober 2016, 20:06:23 CEST schrieb shlomi braitbart:
>> >> >> > git describe
>> >> >> > release-0.9.3-13734-ge493501
>> >> >>
>> >> >> That looks good. Does a "git pull" bring you any updates now? And
>> >> >> change
>> >> >> the
>> >> >> 13734 to 13738 or something like that?
>> >> >>
>> >> >> > git status
>> >> >> > On branch master
>> >> >> > Your bra

Re: [darktable-dev] Problem with lualib

[Roman Lebedev]

Missing information: darktable version?

On Thu, Oct 20, 2016 at 4:15 PM, Jefferson Ferreira
 wrote:
> Hi,
>
> I wrote an example in darktable/luarc that shows a strange error when I
> open/close the "export selected" module:
>
> ERROR in lualib, couldn't find a container, this should never happen
>
> The source of luarc is this:
>
> dt = require "darktable"
> dt.register_lib(
>   "test",
>   "test",
>   true,
>   false,
>   { [dt.gui.views.lighttable] = {"DT_UI_CONTAINER_PANEL_RIGHT_CENTER", 500}
> },
>   dt.new_widget("label") {
> label = "just a name"
>   },
>   nil,
>   nil
> )
>
> Thanks in advance.
>
> --
> Jefferson Ferreira
>
> ___
> 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-RX100 V RAW support

[Roman Lebedev]

On Sat, Nov 12, 2016 at 9:12 PM, Jason Long
 wrote:
> I am running darktable-2.0.7-1 which doesn't seem to support the Sony
> DSC-RX100 V RAW format.
>
> Any idea when this might be available?
Generic answer:
Probably not before someone actually reports it with a sample to
https://redmine.darktable.org/projects/darktable/issues/new

> ___
> 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 from Lua

[Roman Lebedev]

On Mon, Nov 14, 2016 at 4:53 PM, Pascal Obry  wrote:
> Hello Lua experts!
>
> I want to create a Lib (a bit like the Enfuse one in the lua-script
> repo) but I need to first export the RAW file as say TIF. Is there a
> way to export a set of RAW from Lua?

> I tried calling darktable-cli on command line, but as expected this
> does not work because of the db locking.
Hm, but dt-cli does not need db. So i think the fact that it tries to lock
the db is a bug. Please open new issue about this.

> Any idea?
>
> Thanks,
>
> --
>   Pascal Obry /  Magny Les Hameaux (78)
Roman.

>   The best way to travel is by means of imagination
>
>   http://photos.obry.net
>   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] Exotic builds: MacOS Homebrew, Gentoo

[Roman Lebedev]

OSX builds for darktable added to travis-ci.

On Fri, Nov 18, 2016 at 10:08 PM, Wolfgang Goetz  wrote:
> Folks, Roman for prctl..
>
> since a while dt compiles on MacOS/Homebrew ...until...
>
> src/common/system_signal_handling.c includes unconditional 
>
> quick fix is to //.. the #include
>
> (--> 2.2.0rc0+99~gca4ee4e-dirty OK)
>
>
>
>
>
>
> The other not so funny story is Gentoo build:
>
> horribly broken since a long time.
>
> is there anyone working on =media-gfx/darktable- ** (?)
> is it worth spending time on it?
> git source builds are ok.
>
> one has to un-use graphicsmagick anyway because someone is thinking that
> imagemagick and graphicsmagick are not to be installed on the same system.
> never seen that on any other system.
> really kind of ###.
>
>
> [blocks B  ] media-gfx/graphicsmagick[imagemagick] 
> ("media-gfx/graphicsmagick[imagemagick]" is blocking 
> media-gfx/imagemagick-6.9.6.2)
> [blocks B  ] media-gfx/imagemagick ("media-gfx/imagemagick" is blocking 
> media-gfx/graphicsmagick-1.3.25)
>
>  * Error: The above package list contains packages which cannot be
>  * installed at the same time on the same system.
>
>
>
>
> Good news: sci-geosciences/osm-gps-map is finally available in ~1.1.0
>
>
>
>
> kind regards
> Wolfgang
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Thumbnails in exported photos?

[Roman Lebedev]

On Mon, Nov 28, 2016 at 11:43 PM, François Tissandier
 wrote:
> Pity, such an app is very useful for me, I need to use an old Java app to be
> able to do that for the moment.
>
> Is it something we can suggest as a feature to add in darkroom ?
https://redmine.darktable.org/projects/darktable/issues/new

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

Re: [darktable-dev] String freeze for the upcoming 2.2 series

[Roman Lebedev]

On Mon, Nov 28, 2016 at 8:38 PM, Maurizio  wrote:
> Hi!
> So I enter the build directory with
> cd build
> and start the usermanual build
> make update-usermanual-it
>
> This is the result:
> pdating usermanual template
> I/O error : Attempt to load network entity http://docbook.sourceforge.net/
> release/xsl/current/profiling/profile.xsl
> warning: failed to load external entity "http://docbook.sourceforge.net/
> release/xsl/current/profiling/profile.xsl"
> compilation error: file ../xsl/darktable_profile.xsl line 3 element import
> xsl:import : unable to load http://docbook.sourceforge.net/release/xsl/
> current/profiling/profile.xsl
> doc/usermanual/po/CMakeFiles/update-template.dir/build.make:61: set di
> istruzioni per l'obiettivo "doc/usermanual/po/darktable-usermanual.pot" non
> riuscito

You need some more packages for that.
Here is all the usermanual deps (* as far as i know *), for debian:
https://github.com/darktable-org/darktable/blob/acd182e2510cbba18374b137dca8fecc3bd3c582/Dockerfile#L84-L86

> make[3]: *** [doc/usermanual/po/darktable-usermanual.pot] Errore 5
> CMakeFiles/Makefile2:8774: set di istruzioni per l'obiettivo "doc/usermanual/
> po/CMakeFiles/update-template.dir/all" non riuscito
> make[2]: *** [doc/usermanual/po/CMakeFiles/update-template.dir/all] Errore 2
> CMakeFiles/Makefile2:8717: set di istruzioni per l'obiettivo "doc/usermanual/
> po/CMakeFiles/update-usermanual-it.dir/rule" non riuscito
> make[1]: *** [doc/usermanual/po/CMakeFiles/update-usermanual-it.dir/rule]
> Errore 2
> Makefile:2953: set di istruzioni per l'obiettivo "update-usermanual-it" non
> riuscito
> make: *** [update-usermanual-it] Errore 2
>
>
> In data lunedì 28 novembre 2016 12:21:11 CET, Tobias Ellinghaus ha scritto:
>> Am Montag, 28. November 2016, 11:15:02 CET schrieb Maurizio Paglia:
>> > Ciao Tobias,
>> > I received a lot of errors running build.sh as root: running it as a
>> > normal
>> > user showed a couple of missing dependencies, installed, and now build
>> > runs
>> > smoothly.
>> > After that:
>> > cd build
>> > and then
>> > make update-usermanual-it
>> > again a lot of errors... it seems cannot download some files from outside,
>> > maybe a firewall matter.
>> > I will check again soon and re-try.
>>
>> Please show those errors. Updating the .po file shouldn't download anything.
>> If it does then it's a bug in our build system. Probably some part that
>> checks validity of the files.
>>
>> > Thank you,
>> > Maurizio
>>
>> Tobias
>>
>> > 2016-11-28 10:40 GMT+01:00 Tobias Ellinghaus :
>> > > Am Montag, 28. November 2016, 07:15:37 CET schrieb Maurizio:
>> > > > Hi,
>> > >
>> > > Hi.
>> > >
>> > > > dt build now works till the end (I always run build.sh) but cannot
>> > > > find
>> > >
>> > > Good. Did you change anything? I am curious to know what was causing
>> > > this.
>> > >
>> > > > saxon so - I guess - I cannot compile manuals.
>> > > > The exact error is:
>> > > >
>> > > > -- No saxon XSLT processor and/or no docbook saxon extension library
>> > >
>> > > found.
>> > >
>> > > > Xslt processor saxon not found. HTML usermanual will be built with
>> > >
>> > > xsltproc;
>> > >
>> > > > expect usermanual with inconsistent screenshot and image dimensions.
>> > > >
>> > > > But saxon is duly installed...
>> > > > Actually I recevie also an error for Java
>> > > >
>> > > > -- Could NOT find Java (missing:  Java_JAR_EXECUTABLE
>> > >
>> > > Java_JAVAC_EXECUTABLE
>> > >
>> > > > Java_JAVAH_EXECUTABLE Java_JAVADOC_EXECUTABLE) (found version
>> > >
>> > > "1.8.0.101")
>> > >
>> > > > while Java is installed and working...
>> > >
>> > > You only need saxon when building the HTML version of the manual for the
>> > > website. You can just ignore that.
>> > >
>> > > > Maurizio
>> > >
>> > > Tobias
>> > >
>> > > > In data domenica 27 novembre 2016 21:03:20 CET, Tobias Ellinghaus ha
>> > >
>> > > scritto:
>> > > > > Am Sonntag, 27. November 2016, 16:51:10 CET schrieb Maurizio:
>> > > > > > Hi all,
>> > > > >
>> > > > > Hi.
>> > > > >
>> > > > > > seems I cannot compile dt nomore on OpenSuse Leap 42.2
>> > > > > >
>> > > > > > I receive the following message:
>> > > > > >  git/darktable/src/common/dbus.c: In function
>> > >
>> > > ‘dbus_lua_call_finished’:
>> > > > > > git/darktable/src/common/dbus.c:64:16: error: ‘LUA_OK’ undeclared
>> > >
>> > > (first
>> > >
>> > > > > > use in this function)
>> > > > > >
>> > > > > >if(result == LUA_OK)
>> > > > > >
>> > > > > > ^
>> > > > > >
>> > > > > > git/darktable/src/common/dbus.c:64:16: note: each undeclared
>> > >
>> > > identifier
>> > >
>> > > > > > is
>> > > > > > reported only once for each function it appears in
>> > > > > > src/CMakeFiles/lib_darktable.dir/build.make:436: set di istruzioni
>> > >
>> > > per
>> > >
>> > > > > > l'obiettivo "src/CMakeFiles/lib_darktable.dir/common/dbus.c.o" non
>> > > > > > riuscito
>> > > > > > gmake[2]: *** [src/CMakeFiles/lib_darktable.dir/common/dbus.c.o]
>> > >
>> 

Re: [darktable-dev] Exotic builds: MacOS Homebrew, Gentoo

[Roman Lebedev]

On Fri, Nov 18, 2016 at 10:08 PM, Wolfgang Goetz  wrote:
> Folks, Roman for prctl..
>
> since a while dt compiles on MacOS/Homebrew ...until...
>
> src/common/system_signal_handling.c includes unconditional 
>
> quick fix is to //.. the #include
>
> (--> 2.2.0rc0+99~gca4ee4e-dirty OK)
Not many people are running dt on osx.
Thanks for report, fixed.

PS: would be awesome to figure travis build for osx.
But travis provides brew and not ports, and i'm not sure brew
has all the deps.


>
>
>
>
>
> The other not so funny story is Gentoo build:
>
> horribly broken since a long time.
>
> is there anyone working on =media-gfx/darktable- ** (?)
> is it worth spending time on it?
> git source builds are ok.
>
> one has to un-use graphicsmagick anyway because someone is thinking that
> imagemagick and graphicsmagick are not to be installed on the same system.
> never seen that on any other system.
> really kind of ###.
>
>
> [blocks B  ] media-gfx/graphicsmagick[imagemagick] 
> ("media-gfx/graphicsmagick[imagemagick]" is blocking 
> media-gfx/imagemagick-6.9.6.2)
> [blocks B  ] media-gfx/imagemagick ("media-gfx/imagemagick" is blocking 
> media-gfx/graphicsmagick-1.3.25)
>
>  * Error: The above package list contains packages which cannot be
>  * installed at the same time on the same system.
>
>
>
>
> Good news: sci-geosciences/osm-gps-map is finally available in ~1.1.0
>
>
>
>
> kind regards
> Wolfgang
Roman.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Exotic builds: MacOS Homebrew, Gentoo

[Roman Lebedev]

On Mon, Nov 21, 2016 at 1:01 AM, Wolfgang Goetz <wolfgang.zt...@web.de> wrote:
> Roman Lebedev wrote:
>
>> On Fri, Nov 18, 2016 at 10:08 PM, Wolfgang Goetz
>> <wolfgang.zt...@web.de> wrote:
>> > Folks, Roman for prctl..
> [...]
>> Not many people are running dt on osx.
>> Thanks for report, fixed.
>
> Great, thankyou!
>
>
>> PS: would be awesome to figure travis build for osx.
>> But travis provides brew and not ports, and i'm not sure brew
>> has all the deps.
>>

> brew: *it has*, Homebrew _is_ brew: http://brew.sh
> ports? i didnt install macports again because it screwed up itself on my old 
> Macbook several times
>
>
> simply clone/pull dt, run build.sh as usual. (do a rm -rf build if build.sh 
> breaks)
> my installed brew packages at end of this mail
Good to know.

> Fullscreen mode is OK. (Normal window is slightly larger than my MacBook's 
> retina screen)

> i took a short look on travis-ci.. NICE!
> unfortunately travis is not dealing with forked repositories. (i found only 
> my own ones catched up by travis)
For travis, there is no difference whether the repo is a clone/fork or not.
The procedure to enable travis-ci for a github repo is exactly the same.
I know it for a fact because i have already tried enabling it for my
dt repo fork.

> anyway...
>
> https://docs.travis-ci.com/user/multi-os/
> https://docs.travis-ci.com/user/osx-ci-environment/
> https://docs.travis-ci.com/user/ci-environment/
>
>
> just a start on https://lint.travis-ci.org/ using dt's  .travis.yml
> ..more work to do with matrix and conditionals to separate linux-docker and 
> osx parts.
>
>
> OUTPUT OF CHECK:* osx_image is experimental and might be removed in 
> the future
>
> ---
> language: generic
> os:
>   - linux
>   - osx
>
> osx_image: xcode8.1
>
> before_install:
>   - if [[ "$TRAVIS_OS_NAME" == "linux" ]];then docker pull 
> darktable/darktable; fi
>   - if [[ "$TRAVIS_OS_NAME" == "osx" ]]; then brew update ; fi
>   - if [[ "$TRAVIS_OS_NAME" == "osx" ]]; then brew install gtk+3 gphoto2 
> openexr lensfun librsvg json-glib pugixml ;fi
>
...
>
> $ brew list
> ack gdbmhdf5  
>   little-cms  qscintilla2
> ansible gdk-pixbuf  
> hicolor-icon-theme  little-cms2 qt
> aptly   geeqie  icu4c 
>   lua qt5
> arpack  gettext ilmbase   
>   metis   readline
> arping  ghc imagemagick   
>   mpfrsdl2
> atk ghostscript intltool  
>   octave  sdl2_image
> autoconfgit isl   
>   openexr shared-mime-info
> automakegl2ps   jpeg  
>   openssl sip
> boost   glewjson-glib 
>   openssl@1.1 sqlite
> cairo   gliblame  
>   packer  stow
> cmake   glpklensfun   
>   pandoc  suite-sparse
> curlgmp libcroco  
>   pango   szip
> elixir  gnu-getopt  libepoxy  
>   paralleltbb
> epstool gnu-sed libexif   
>   pcretexinfo
> erlang  gnuplot libffi
>   pixman  tin
> exiftoolgo  libgphoto2
>   pkg-config  transfig
> exiv2   gobject-introspection   libmpc
>   plotutils   veclibfort
> fbida   gource  libnet

Re: [darktable-dev] Re: Fuji X-T2 noise profiles finalized

[Roman Lebedev]

On Thu, Oct 27, 2016 at 5:53 PM, Sascha Oleszczuk  wrote:
> Thx for release 2.0.7.
> It seams my noiseprofiles for fuji X-T2 and the white balance settings from
> another user are not part of 2.0.7.

> Not sure if the team hasn't more time to put it in or if it was overlooked.
The problem here is the shortage of free time for the person who
currently reviews them.
Eventually, all the backlog will be handled...

> Does it help to place a pull requets in github.
>
> Kind regards
> Sascha
Roman.

> 2016-10-01 22:27 GMT+02:00 Sascha Oleszczuk :
>>
>> Hi All,
>>
>> I have finalized and added the Fuji X-T2 noise profiles to the follwoing
>> case:
>> https://redmine.darktable.org/issues/11151
>>
>> Best regards
>> Sascha
>
>
>
> ___
> 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 compiling

[Roman Lebedev]

On Fri, Oct 28, 2016 at 6:07 AM, Michel Leblond
 wrote:
> After the modifications made by Roman I now have two errors:
>
> In file included from /home/michel/Logiciels/DT_ML/src/common/opencl.h:39:0,
>  from /home/michel/Logiciels/DT_ML/src/develop/imageop.h:37,
>  from
> /home/michel/Logiciels/DT_ML/src/iop/amaze_demosaic_RT.cc:28:
> /home/michel/Logiciels/DT_ML/src/control/conf.h: In function ‘int
> dt_conf_get_int(const char*)’:
> /home/michel/Logiciels/DT_ML/src/control/conf.h:146:21: error: ‘isnan’ was
> not declared in this scope
>if(isnan(new_value)) new_value = 0.0;
>  ^
> /home/michel/Logiciels/DT_ML/src/control/conf.h:146:21: note: suggested
> alternative:
> In file included from /usr/include/c++/5/random:38:0,
>  from /usr/include/c++/5/bits/stl_algo.h:66,
>  from /usr/include/c++/5/algorithm:62,
>  from
> /home/michel/Logiciels/DT_ML/src/iop/amaze_demosaic_RT.cc:21:
> /usr/include/c++/5/cmath:641:5: note:   ‘std::isnan’
>  isnan(_Tp __x)
>  ^
> In file included from /home/michel/Logiciels/DT_ML/src/common/opencl.h:39:0,
>  from /home/michel/Logiciels/DT_ML/src/develop/imageop.h:37,
>  from
> /home/michel/Logiciels/DT_ML/src/iop/amaze_demosaic_RT.cc:28:
> /home/michel/Logiciels/DT_ML/src/control/conf.h: In function ‘int64_t
> dt_conf_get_int64(const char*)’:
> /home/michel/Logiciels/DT_ML/src/control/conf.h:161:21: error: ‘isnan’ was
> not declared in this scope
>if(isnan(new_value)) new_value = 0.0;
>  ^
> /home/michel/Logiciels/DT_ML/src/control/conf.h:161:21: note: suggested
> alternative:
> In file included from /usr/include/c++/5/random:38:0,
>  from /usr/include/c++/5/bits/stl_algo.h:66,
>  from /usr/include/c++/5/algorithm:62,
>  from
> /home/michel/Logiciels/DT_ML/src/iop/amaze_demosaic_RT.cc:21:
> /usr/include/c++/5/cmath:641:5: note:   ‘std::isnan’
>  isnan(_Tp __x)
>  ^
> In file included from /home/michel/Logiciels/DT_ML/src/common/opencl.h:39:0,
>  from /home/michel/Logiciels/DT_ML/src/develop/imageop.h:37,
>  from
> /home/michel/Logiciels/DT_ML/src/iop/amaze_demosaic_RT.cc:28:
> /home/michel/Logiciels/DT_ML/src/control/conf.h: In function ‘float
> dt_conf_get_float(const char*)’:
> /home/michel/Logiciels/DT_ML/src/control/conf.h:176:15: error: ‘isnan’ was
> not declared in this scope
>if(isnan(val)) val = 0.0;
>^
> /home/michel/Logiciels/DT_ML/src/control/conf.h:176:15: note: suggested
> alternative:
> In file included from /usr/include/c++/5/random:38:0,
>  from /usr/include/c++/5/bits/stl_algo.h:66,
>  from /usr/include/c++/5/algorithm:62,
>  from
> /home/michel/Logiciels/DT_ML/src/iop/amaze_demosaic_RT.cc:21:
> /usr/include/c++/5/cmath:641:5: note:   ‘std::isnan’
>  isnan(_Tp __x)
>  ^
> [100%] Building C object
> src/chart/CMakeFiles/darktable-chart.dir/tonecurve.c.o
> [100%] Built target darktable-generate-cache
> src/iop/CMakeFiles/demosaic.dir/build.make:91 : la recette pour la cible «
> src/iop/CMakeFiles/demosaic.dir/amaze_demosaic_RT.cc.o » a échouée
> make[2]: *** [src/iop/CMakeFiles/demosaic.dir/amaze_demosaic_RT.cc.o] Erreur
> 1
> CMakeFiles/Makefile2:6165 : la recette pour la cible «
> src/iop/CMakeFiles/demosaic.dir/all » a échouée
> make[1]: *** [src/iop/CMakeFiles/demosaic.dir/all] Erreur 2
> make[1]: *** Attente des tâches non terminées
> [100%] Built target darktable-cli
> [100%] Built target darktable-viewer
> [100%] Linking C executable darktable-chart
> [100%] Built target darktable-chart
> Makefile:149 : la recette pour la cible « all » a échouée
> make: *** [all] Erreur 2
Ok, try once more...

> Le 27/10/2016 à 22:34, João Horta a écrit :
>
> [ 92%] Building CXX object
> src/iop/CMakeFiles/demosaic.dir/amaze_demosaic_RT.cc.o
> In file included from /usr/include/x86_64-linux-gnu/c++/5/bits/gthr.h:148:0,
>  from /usr/include/c++/5/ext/atomicity.h:35,
>  from /usr/include/c++/5/bits/basic_string.h:39,
>  from /usr/include/c++/5/string:52,
>  from /usr/include/c++/5/random:40,
>  from /usr/include/c++/5/bits/stl_algo.h:66,
>  from /usr/include/c++/5/algorithm:62,
>  from
> /home/jmhorta/darktable/src/iop/amaze_demosaic_RT.cc:37:
> /usr/include/x86_64-linux-gnu/c++/5/bits/gthr-default.h:105:9: error:
> attempt to use poisoned "pthread_create"
>  __gthrw(pthread_create)
>  ^
> /usr/include/x86_64-linux-gnu/c++/5/bits/gthr-default.h:662:19: error:
> attempt to use poisoned "pthread_create"
>return __gthrw_(pthread_create) (__threadid, NULL, __func, __args);
>^
> In file included from /usr/include/c++/5/ext/string_conversions.h:43:0,
>  from 

Re: [darktable-dev] Re: crash on exporting a file

[Roman Lebedev]

Looks like a crash in lensfun.
Judging by tiling involved, i'd guess out-of-memory?

Roman.

On Mon, Oct 31, 2016 at 12:50 AM, João Horta  wrote:
> /tmp/darktable_bt_D4NDQY.txt
>
>
>
> 2016-10-30 21:46 GMT+00:00 João Horta :
>>
>> Darktable-git 2.1.0+2119 g50ebe5a
>>
>>
>> jmhorta@Ubuntu1604:~$ darktable
>>
>> (darktable:11094): Gtk-WARNING **: gtk_disable_setlocale() must be called
>> before gtk_init()
>> [New LWP 11095]
>> [New LWP 11096]
>> [New LWP 11097]
>> [New LWP 11098]
>> [New LWP 11099]
>> [New LWP 11100]
>> [New LWP 11101]
>> [New LWP 11102]
>> [New LWP 11107]
>> [New LWP 11108]
>> [New LWP 0]
>> [New LWP 1]
>> [Thread debugging using libthread_db enabled]
>> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
>> 0x7f9ca984db5d in poll () at ../sysdeps/unix/syscall-template.S:84
>> 84 ../sysdeps/unix/syscall-template.S: No such file or directory.
>> backtrace written to /tmp/darktable_bt_D4NDQY.txt
>> Falha de segmentação
>> jmhorta@Ubuntu1604:~$
>
>
>
> ___
> 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] Re: [darktable-user] Re: PSA: ATTENTION NIKON OWNERS !!! LAST CALL

[Roman Lebedev]

On Thu, Oct 13, 2016 at 10:55 PM, 12li...@gadz.org <12li...@gadz.org> wrote:
>  Hello Roman,
Hi.

> I just opened a camera support tracker on redmine for D70.
>
> I check available settings in my D70, no options for raw file compression,
> nor raw file bitness so I provided a one sample.
Ok.

> I cross checked your list against what is available on raw samples.ch, and
> what is proposed in manuals :
>
> D70S : "NEF (RAW) : compressed 12-bit" in manual, one file on raw samples.ch
> D1 : " Storage Compression: JPEG baseline-compliant (approximate compression
> ratios 1:4, 1:8, 1:16); uncompressed files recorded as YCbCr-TIFF (8-bit),
> RGB-TIFF (8-bit), or RAW data (12-bit)"
> D3100 : seems to have only 1 option, 12-bit, no info on compression, 1 file
> available on rawsamples.ch
> P6000 & P7000 & P7100 : seems to have only one option far raw, and 1 sample
> per camera available on rawsamples.ch
> coolpix P5700 : only one raw option in the manual, one file on rawsamples.ch
> coolpix P5400 : only TIFF described in the manual, but one NEF on
> rawsamples.ch
> nikon 1S2 : 12 bit compressed as per the manual, one file available on
> rawsamples.ch
Hmm, nice! Not sure why those got missed.

> less luck on those cases :
> D100 gives 2 options : NEF (Raw) and Comp. NEF (Raw) only 12bit, only 1 file
> on rawsamples.ch
> D1X gives 2 options : NEF (Raw) and Comp. NEF (Raw) only 12bit, only 1 file
> on rawsamples.ch
> D3 : 12 and 14 bit, lossless compression, lossy compression and no
> compression, only 1 file on rawsamples.ch
> D3X : 12 and 14 bit, lossless compression, lossy compression and no
> compression, only 1 file on rawsamples.ch
> Df : 12 and 14 bit, lossless compression, lossy compression and no
> compression, only 1 file on rawsamples.ch
> D5 NIKON E8400 & NIKON E8800 & coolpix A & AW1 & 1J2 : no files on
> rawsamples.ch
Well, **so far** the whitelevels only differ between the 14bit and
12bit, but not
between different raw compression methods, so it may be ok..

> do you need tickets to be opened for the previous availables files on
> rawsamples.ch ?
Yes, please.

> regards,
>
> Thomas
Roman.

> On 13 October 2016 at 19:51, Roman Lebedev <lebedev...@gmail.com> wrote:
>>
>> Okay, some samples were provided, a few cameras got off the list.
>> But not all.
>>
>> Here is the current up-to-date list of the cameras, samples
>> from which are still wanted:
>>
>> NIKON COOLPIX P6000
>> NIKON COOLPIX P7000
>> NIKON COOLPIX P7100
>> NIKON CORPORATION COOLPIX A
>> NIKON CORPORATION NIKON 1 AW1
>> NIKON CORPORATION NIKON 1 J4
>> NIKON CORPORATION NIKON 1 S2
>> NIKON CORPORATION NIKON D1
>> NIKON CORPORATION NIKON D100
>> NIKON CORPORATION NIKON D1H
>> NIKON CORPORATION NIKON D3100
>> NIKON CORPORATION NIKON D3S
>> NIKON CORPORATION NIKON D3X
>> NIKON CORPORATION NIKON D5
>> NIKON CORPORATION NIKON D70
>> NIKON CORPORATION NIKON D70s
>> NIKON CORPORATION NIKON Df
>> NIKON E5400
>> NIKON E5700
>> NIKON E8400
>> NIKON E8800
>>
>> IMPORTANT: if you see your camera in that list, it is imperative for
>> you to provide a sample set, or else your camera
>> will not be supported in next darktable release!
>>
>> We are thinking about doing 2.0.7 in a couple weeks.
>> Better get these samples now.
>>
>> Roman.
>>
>> On Fri, Oct 7, 2016 at 4:00 PM, Roman Lebedev <lebedev...@gmail.com>
>> wrote:
>> > Hi all.
>> >
>> > This mail is primarily targeted to all the owners of Nikon cameras.
>> >
>> > As you may have seen, an issue with white level for some
>> > nikon cameras (or so i thought) was discovered by me:
>> >
>> > https://www.mail-archive.com/darktable-dev@lists.darktable.org/msg01196.html
>> >
>> > In the meantime i have adjusted white levels for all the cameras i
>> > could find samples for.
>> > But unfortunately, for some cameras i was unable to find samples.
>> >
>> > Below, you will find a list of all the cameras for which i need samples.
>> >
>> > IMPORTANT: if you see your camera in that list, it is imperative for
>> > you to provide
>> > a sample set, or else your camera will not be supported in next
>> > darktable release!
>> >
>> > NIKON COOLPIX P6000
>> > NIKON COOLPIX P7000
>> > NIKON COOLPIX P7100
>> > NIKON CORPORATION COOLPIX A
>> > NIKON CORPORATION NIKON 1 AW1
>> > NIKON CORPORATION NIKON 1 J4
>> > NIKON CORPORATION NIKON 1 S2
>> > NIKON

Re: [darktable-dev] Panasonic GX80/85

[Roman Lebedev]

On Fri, Dec 9, 2016 at 3:08 PM, PD Dr. Stefan Schmidt
 wrote:
> Hi,
Hi.

> although the panasonic GX80/85 was included in 2.0.7

> I cannot find a noise profile.
That is because no one has created it yet / no one opened an issue on
redmine with profile.

https://www.darktable.org/2012/12/profiling-sensor-and-photon-noise/

> Also the camera is not on the list in the lens correction module.
Lensfun issue.

> Stefan
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] One week left to update translations

[Roman Lebedev]

On Thu, Dec 15, 2016 at 4:51 PM, Nazarii Vitak  wrote:
> Hi everyone,
>
> Could anyone check if the uk translation was updated.
https://github.com/darktable-org/darktable/commits/master/po/uk.po
Last change was on Dec 6, 2014, so no, not up-to-date.

> Thanks in advance.
>
> Nazarii.
Roman.

> On 14 December 2016 at 19:22, Tobias Ellinghaus  wrote:
>>
>> Hello translators,
>>
>> as you know we are in string freeze and about to release version 2.2.0.
>> You
>> have one week left to update your translations to a somewhat high
>> percentage.
>> As in the past we will again drop all translations that are below a to be
>> determined threshold.
>>
>> The current state looks like this:
>>
>> af: 77 translated messages, 56 fuzzy translations, 2083 untranslated
>> messages.
>> ca: 2216 translated messages.
>> cs: 2140 translated messages, 57 fuzzy translations, 19 untranslated
>> messages.
>> da: 2144 translated messages, 56 fuzzy translations, 16 untranslated
>> messages.
>> de: 2213 translated messages, 3 fuzzy translations.
>> el: 1978 translated messages, 131 fuzzy translations, 107 untranslated
>> messages.
>> es: 2147 translated messages, 55 fuzzy translations, 14 untranslated
>> messages.
>> fi: 483 translated messages, 911 fuzzy translations, 822 untranslated
>> messages.
>> fr: 2215 translated messages, 1 untranslated message.
>> gl: 321 translated messages, 894 fuzzy translations, 1001 untranslated
>> messages.
>> he: 2216 translated messages.
>> hu: 2164 translated messages, 40 fuzzy translations, 12 untranslated
>> messages.
>> it: 1999 translated messages, 136 fuzzy translations, 81 untranslated
>> messages.
>> ja: 2216 translated messages.
>> nl: 2211 translated messages, 5 fuzzy translations.
>> pl: 2189 translated messages, 3 fuzzy translations, 24 untranslated
>> messages.
>> pt_BR: 1647 translated messages, 310 fuzzy translations, 259 untranslated
>> messages.
>> pt_PT: 1598 translated messages, 340 fuzzy translations, 278 untranslated
>> messages.
>> ro: 562 translated messages, 859 fuzzy translations, 795 untranslated
>> messages.
>> ru: 1940 translated messages, 147 fuzzy translations, 129 untranslated
>> messages.
>> sk: 2068 translated messages, 101 fuzzy translations, 47 untranslated
>> messages.
>> sl: 2115 translated messages, 79 fuzzy translations, 22 untranslated
>> messages.
>> sq: 1738 translated messages, 265 fuzzy translations, 213 untranslated
>> messages.
>> sv: 2139 translated messages, 56 fuzzy translations, 21 untranslated
>> messages.
>> th: 428 translated messages, 295 fuzzy translations, 1493 untranslated
>> messages.
>> uk: 1755 translated messages, 265 fuzzy translations, 196 untranslated
>> messages.
>> zh_CN: 1231 translated messages, 585 fuzzy translations, 400 untranslated
>> messages.
>>
>> Thank you in advance for your help
>> Tobias
>
>
>
> ___
> 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-chart 2.2 rc2 not running

[Roman Lebedev]

On Sat, Dec 17, 2016 at 12:51 AM, Aurélien PIERRE
 wrote:
> That's strange, they were all exported the same way through DT 2.2rc2
Did you set output color space to lab?

output colour space to Lab (set the secret option in darktablerc:
allow_lab_output=true)


> Aurélien PIERRE
> aurelienpierre.com
>
> 
> Le 16/12/2016 à 08:56, Tobias Ellinghaus a écrit :
>
> Am Donnerstag, 15. Dezember 2016, 00:12:32 CET schrieb Aurélien PIERRE:
>
> Ok this folder contains 3 pfm pictures tested (from Nikon D810 and
> D5300) :
> https://www.dropbox.com/sh/pk8dwdu3pwmc9w6/AADUJsTBlQiR4pE7advNFqEMa?dl=0
>
> - calibration.pfm seems to be RGB instead of Lab.
> - calibration-D810.pfm is all black (only 0 Bytes in the image data, I
> checked
> with a hex editor)
> - calibration-D5300.pfm puzzles me. When looking at it as an RGB image the
> false colors look like a Lab image, however even darktable proper shows only
> a
> black image when setting the input profile to Lab. How exactly did you
> create
> that file?
>
> *Aurélien PIERRE*
> aurelienpierre.com 
>
> Tobias
>
> [...]
>
>
>
> ___
> 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 from subrepo doesn't find camera

[Roman Lebedev]

On Thu, Jan 12, 2017 at 12:31 PM, Moritz Moeller <virtualr...@gmail.com> wrote:
> On 6.1.17 17:33 , Roman Lebedev wrote:
>>>
>>> Note that I always convert all my original raws from the camera (.ARW) to
>>> DNGs and have done so from the beginning.
>>
>> Ah, well, i sure hope that you keep original ARW around :)
>
>
> No, I don't. I do not see a reason for it.
It is more or less the same deal as with editing raw files. (and yes,
that applies
to dng too). There are all sorts of fields, makernotes specific to camera
manufacturer. It is likely that converting to dng tosses half of these
out of the window.
But it's your data that is potentially getting damaged...

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

Re: [darktable-dev] Bottom buttons right click

[Roman Lebedev]

Worksforme.
Also, you can left-click and hold for a few sec, and the same popup will appear.

On Tue, Dec 6, 2016 at 1:19 PM, Timur Irikovich Davletshin
 wrote:
> Exactly, it is nearly impossible to right-click to change settings of
> over/under expose (all buttons, see screenshot). Left-click works
> perfectly but right click doesn't work. Sometimes it takes 10 or 20
> times to right-click for menu to appear. Other applications' right-
> click works as usual so it is not a mouse problem.
>
> On Tue, 2016-12-06 at 11:10 +0100, Tobias Ellinghaus wrote:
>> Am Dienstag, 6. Dezember 2016, 09:35:58 CET schrieb Timur Irikovich
>> Davletshin:
>> >
>> > Hello!
>> >
>> > I prefer to use shortcuts to toggle over/under exposed indication
>> > and
>> > don't use right click to change 2% settings but today I have
>> > discovered
>> > that it is nearly impossible to right-click those buttons (all of
>> > them). I clicked like 20 times and only 2 times I was able to see
>> > menu.
>> What do you mean, it's impossible to right click? In how far is right
>> clicking
>> different from left clicking?
>>
>> >
>> > System: Ubuntu 16.04/x64/DT2.2rc2 from unstable PPA
>> >
>> > Thanks in advance.
>> Tobias
> ___
> 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] Re: [darktable-user] darktable 2.2.0rc2 released

[Roman Lebedev]

On Mon, Dec 5, 2016 at 12:36 AM, Matthieu Moy
 wrote:
> Hi,
Hi

> I'm in the process of writing an article about dt 2.2 
> (https://linuxfr.org/redaction/news/darktable-2-2-0), and I have a few 
> questions about the release notes:
>
> - Original Message -

>> - In Highlight reconstruction module, the mode LCh reconstruction was
>> completely rewritten, and is no longer useless!
>
> What does this rewrite brings? My experience is that the "reconstruct color" 
> is too buggy to be usable in many cases, but I have good experience with LCh 
> reconstruction, so I wouldn't have called it "useless" before the rewrite.
"LCh reconstruction" was pure garbage in all the cases (all the
images) i had tried using it, before rewrite.
If you never noticed that, then the rewrite should be unnoticeable for you :)

As for "reconstruct color", yeah, it is buggy. It works for small
overexposed areas, but not large-ones.
if time permits, i plan on working on proper highlight inpainting module...

>> - Support running on platforms other than x86 (64bit little-endian, currently
>> ARM64 only) (https://www.darktable.org/2016/04/running-on-non-x86-platforms/)
>
> Are there plans particular use-case in mind in the roadmap? I suppose running 
> on a Raspberry Pi is fun for geeks, but not very helpful in practice given 
> the limited RAM and processing power of the device. Can user start dreaming 
> about an Android version for example?
No, but maybe some interesting aarch64-based HW will appear in future?

>> - darktable is now happy to use smaller stack sizes (no less than 256Kb).
>> That should allow using musl libc
>
> Same question here: are there concrete benefits for users?
Less crashy, in extreme cases (the max stack size is usually bound to
8Mb even for 64bit glibc, if one tries to use more stack (e.g. via
VLA), it segfaults).

> Just wondering (and looking for something to write in the article), but in 
> any case, it's cool to see dt more portable.
>
>> - Nicer web gallery exporter -- now touch friendly!
>
> Is there a public demo that I could link to anywhere?

>> - Filter-out some useless EXIF tags when exporting, helps keep EXIF size
>> under
>> ~64Kb
>
> What happens if one crosses this limit?

> Or just drop some EXIF data arbitrarily?
Not arbitrarily,
https://github.com/darktable-org/darktable/blob/08f232f24890f52da951a6f29b9559c6f01637a5/src/common/exif.cc#L1164-L1179
https://github.com/darktable-org/darktable/blob/08f232f24890f52da951a6f29b9559c6f01637a5/src/common/exif.cc#L1192-L1249

> Would the export fail?
These tags are dropped first, before trying to store EXIF.
If even after that the EXIF size is >64kb, then the image will have no metadata.
But it is a rare case, and it should be much rarer now.

>
>> - Drop darktable-viewer tool in favor of slideshow view
>
> Is there any user-visible change (other than not having darktable-viewer as a 
> command)?
>
> Is there a way to get the slideshow from the command-line?
>
> Thanks,
>
> --
> Matthieu Moy
Roman.

> http://www-verimag.imag.fr/~moy/
> 
> darktable user mailing list
> to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: quick fix for brew build on Sierra /XCode8 (was: [darktable-dev] Warning: git master now uses rawspeed as submodule !)

[Roman Lebedev]

On Wed, Jan 4, 2017 at 10:20 AM,  <para...@paraf.in> wrote:
> Changes to cmake files is probably the culprit - rawspeed now doesn't inherit 
> CFLAGS from darktable and so is missing include path for libjpeg.

But from where did darktable get that jpeg include path? From user?
rawspeed does look for jpeg:
https://github.com/darktable-org/rawspeed/blob/c42c358973b40a266f41de62e06a09a8d309c289/RawSpeed/CMakeLists.txt#L26-L27

> P.S.
> About switching from stable to master branch and back - there're also issues 
> with cherry-picking commits for some reason. We need to come up with correct 
> and clean way of branch checkout… Maybe git clean is needed…
Yeah, it will be a painful expirience. At least it will end one way or
another once 2.4 is out.

Roman.

>> On 4 Jan 2017, at 05:05, Wolfgang Goetz <wolfgang.zt...@web.de> wrote:
>>
>> Roman Lebedev wrote:
>>
>>> On Tue, Jan 3, 2017 at 1:46 AM, Wolfgang Goetz
>>> <wolfgang.zt...@web.de> wrote:
>>>> MacOS/brew broken:
>>>> ...
>>>> [  2%] Building CXX object
>>>> src/external/rawspeed/RawSpeed/CMakeFiles/rawspeed.dir/ArwDecoder.cpp.o
>>>> In file included
>>>> from 
>>>> /Users/wolfganggoetz/repos/darktable/src/external/rawspeed/RawSpeed/ArwDecoder.cpp:1:
>>>>  
>>>> /Users/wolfganggoetz/repos/darktable/src/external/rawspeed/RawSpeed/StdAfx.h:97:10:
>>>> fatal error: 'jpeglib.h' file not found #include "jpeglib.h" ^
>>>> 1 error generated.
>>> Hmm, you do have jpeg or jpeg-turbo formula installed?
>>
>>
>>
>>> Because travis-ci osx builds do not fail, e.g.
>>> https://travis-ci.org/darktable-org/rawspeed/jobs/188323509
>>
>>
>>
>> to make it short:  
>> http://stackoverflow.com/questions/14525898/cmake-doesnt-set-xcodes-user-include-path
>>
>> not sure if it's the right place, looks more like sledgehammer:
>>
>>
>> diff --git a/CMakeLists.txt b/CMakeLists.txt
>> index 6b7a1530f..d8e57008b 100644
>> --- a/CMakeLists.txt
>> +++ b/CMakeLists.txt
>> @@ -32,7 +32,7 @@ endif()
>> IF(DEFINED DT_FORCE_CXX_COMPILER)
>>   set(CMAKE_CXX_COMPILER ${DT_FORCE_CXX_COMPILER})
>> endif()
>> -
>> +include_directories(/usr/local/include)
>> include(CheckCCompilerFlag)
>> include(TestBigEndian)
>>
>>
>>
>> build OK, dt 2.3.0+142 running :-)
>>
>>
>>
>> kind regards
>> Wolfgang
>>
>>
>>
>>
>>
>>
>> the long way:
>>
>>
>> travis is cool.
>> attention: default is OSX 10.11/XCode 7.3.1
>>
>> i'm on real hardware more like osx_image: xcode8.2
>> exact:macOS Sierra Version 10.12.2, XCode Version 8.2.1 (not avail in travis)
>>
>>
>>
>> brew is cool. (in darktable: 'brew bundle' for dependencies, atm just 
>> updating to gcc-6.3.0, this will take some time!)
>>
>> tags/release-2.2.1 build is ok.
>>
>> /usr/local/include/jpeglib.h exists.
>>
>> playing around with CC and CXX environments doesnt help. (fun to see gcc-6 
>> as CC and clang as CXX)
>>
>> sandboxing: same error
>> export PATH=.:$PATH
>> brew bundle exec build.sh
>>
>>
>>
>>
>>
>>
>>
>> VERBOSE=1
>>
>>
>> with submodule:
>>
>> [  3%] Building CXX object 
>> src/external/rawspeed/RawSpeed/CMakeFiles/rawspeed.dir/ArwDecoder.cpp.o
>> cd /Users/wolfganggoetz/repos/darktable/build/src/external/rawspeed/RawSpeed 
>> && 
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
>>-DDEBUG -DGDK_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED 
>> -DGTK_DISABLE_SINGLE_INCLUDES -DOS_OBJECT_USE_OBJC=0 -D_XOPEN_SOURCE=700 
>> -D__GDK_KEYSYMS_COMPAT_H__ -isystem 
>> /usr/local/Cellar/pugixml/1.8.1/include/pugixml-1.8  -D_DARWIN_C_SOURCE 
>> -Wall -fno-strict-aliasing -Wformat -Wformat-security -Wshadow -Wtype-limits 
>> -Wvla -Wno-error=varargs -Wframe-larger-than=32768 -Wlarger-than=524288 
>> -std=c++11 -fno-strict-aliasing -Wall -fno-strict-aliasing -Wformat 
>> -Wformat-security -Wshadow -Wtype-limits -Wvla -Wno-error=varargs 
>> -Wframe-larger-than=32768 -Wlarger-than=524288 -O2 -g -DNDEBUG -O2 -isysroot 
>> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk
>>  -fPIC   -march=native -g3 -ggdb3 -o 
>> CMakeFiles/rawspeed.dir/ArwDecoder.cpp.o -c 
>> /Users/wolfganggoetz/repos/darktable/src/external/rawspeed/RawSpeed/ArwDecoder.cpp
>> In file 

Re: [darktable-dev] Warning: git master now uses rawspeed as submodule !

[Roman Lebedev]

On Tue, Jan 3, 2017 at 2:07 AM, Terry Duell  wrote:
> On Tue, 03 Jan 2017 09:46:23 +1100, Wolfgang Goetz 
> wrote:
>
>> Terry Duell wrote:
>
>
> [snip]
>
>>> Well that seems to have buggered things up :-)
>>> I suspect that the above commands might not be right...attempting to
>>> build results in a message that src/external/rawspeed has no
>>> CMakeLists.txt, and in fact it is an empty dir.
>>> Hopefully, someone who does know how to do this can educate us poor
>>> ignorant sods real soon.
>>>
>>> Cheers,
>>
>>
>>
>> Greetings,
>> this wfm:
>>
>> git pull
>> git submodule init
>> git submodule update
>
>
> That does the trick...but the build still fails here for another reason.
> Fedora 25 is still on LLVM 3.8.0 but 3.9 is now required.
It is not *required*. It is optional.
It is used to test-compile opencl kernels. That is all.

> Thanks for your help.
>
> 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] Warning: git master now uses rawspeed as submodule !

[Roman Lebedev]

On Tue, Jan 3, 2017 at 1:46 AM, Wolfgang Goetz  wrote:
> MacOS/brew broken:
> ...
> [  2%] Building CXX object
> src/external/rawspeed/RawSpeed/CMakeFiles/rawspeed.dir/ArwDecoder.cpp.o
> In file included
> from 
> /Users/wolfganggoetz/repos/darktable/src/external/rawspeed/RawSpeed/ArwDecoder.cpp:1:
>  
> /Users/wolfganggoetz/repos/darktable/src/external/rawspeed/RawSpeed/StdAfx.h:97:10:
> fatal error: 'jpeglib.h' file not found #include "jpeglib.h" ^
> 1 error generated.
Hmm, you do have jpeg or jpeg-turbo formula installed?
Because travis-ci osx builds do not fail, e.g.
https://travis-ci.org/darktable-org/rawspeed/jobs/188323509

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