Re: [darktable-dev] considerations to port the documentation to Docbook 5.x

[The Ritz]

On May 3, 2018 11:24:52 PM Andreas Schneider  wrote:

On Thursday, 3 May 2018 21:09:59 CEST KOVÁCS István wrote:
'Something more lightweight?'

restructedtext, which is what a lot of projects use to write documentation
e.g. using sphinx or pandoc.

+1. Use Spinx (which is based on ReST).
You can publish automatically on readthedocs from github.
This step, if taken though, S
suggests separating the docs from the code, repo wise.

.mm


P.S.: I would be available to help with conversion to Spinx/ReST, if that 
ever happens.



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

[darktable-dev] Re: [darktable-dev] DNG vs RAW → Lens and focus info

[The Ritz]

A bug in DTs metadata reader is not a good argument for your cause. ;)

On April 4, 2018 13:36:36 Tobias Ellinghaus  wrote:


Am Mittwoch, 4. April 2018, 13:15:39 CEST schrieb Timur Irikovich Davletshin:
> Hello everybody!
>
> Just decided to play with DNG converter and discovered problem related
> to lens data interpretation by DT (2.4.2).
>
> 1. NEF file loaded by DT applies correct lens parameters.
>Lens info shown by DT: Nikon AF-S DX Nikkor 18-55mm f/3.5-5.6G
> VR II
>
> 2. DNG file cannot apply it because wrong EXIF information is used
> (short lens name vs. full).
>Lens info shown by DT: 18.0-55.0 mm f/3.5-5.6
>
> 3. Focus information also is lost in DNG.

That's why we tell everyone to never convert to DNG.

Tobias

[...]




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

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

[The Ritz]

On June 20, 2017 18:34:27 Roman Lebedev  wrote:

On Tue, Jun 20, 2017 at 5:55 PM, Moritz Moeller  wrote:

On 20.6.17 11:43 , Tobias Ellinghaus wrote:
I'm using a local build with [...] Wolfgang Mader's
modern monochrome modules since about 4 months and wouldn't want to miss
either.
https://github.com/wmader/darktable/tree/color2gray

That was merged initially, currently resides as a preset in "color
look up table" module


This module has a parameter. How can this work with a single look up table???

.mm




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

Re: [darktable-dev] Content Aware Patch

[The Ritz]

I agree with Tobias. Judging from the video the implementation shown would 
be of limited use. I.e. this quality is not sufficient for any work I 
usually do that requires in-painting. Results with Photoshop's in painting 
tools usually get me there 90%. Meaning there is still manual work, even 
with an industry strength tool that has been through years of iterations 
and improvements.


In DT, what would be more useful for now would be if the spot removal tool 
was made content aware for e.g. low frequency luminance and/or color.
Basically, interpolate low frequency luminance or.color or both from the 
are surrounding area and high frequency detail from the source.


.mm


On May 1, 2017 13:52:53 Tobias Ellinghaus  wrote:


Am Sonntag, 30. April 2017, 15:34:19 CEST schrieb EI:

Hello Eugene,


Is there interest in having a content aware patch module in darktable? I
just finished one for Krita. Here's a demo: https://youtu.be/jI87VzDtkPY

I should be able to port it to darktable. Is anyone else working on
something similar already?


We are not aware of anyone working on something similar for darktable.
In the videos the quality of the result was a little mixed. While that isn't
that big of a deal for an image editor where you can clean the filled region up
afterwards it's a little harder for a program like darktable. However, I can
see it at least being useful for more robust spot removal, so having this as a
2nd mode in that module would be nice. And once it's in there you can still
use it to get rid of Trotzki. ;-)

One question about the algorithm you are using: Does it sample the whole image
for matching patches that are then cloned in, or is it just filling with a
gradient from the surrounding pixels? The samples seemed to indicate the
former but I'd like to be sure.


Eugene


Tobias



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

Re: [darktable-dev] Problems compiling darktable

[The Ritz]

git submodule update?

.mm


On April 26, 2017 07:02:17 Kevin  wrote:


Hi,

I'm having problems compiling darktable. This has been happening for some time
so is not just some recent change to the source.

Platform: Fedora 25, completely up-to-date.

The error is as follows:


[ 21%] Building CXX object src/CMakeFiles/lib_darktable.dir/common/
imageio_exr.cc.o
/home/kmg/photography/darktable/src/common/imageio_rawspeed.cc:51:76:
error: ‘RawImage’ has not been declared
 static dt_imageio_retval_t dt_imageio_open_rawspeed_sraw (dt_image_t *img,
RawImage r, dt_mipmap_buffer_t *buf);

^~~~
/home/kmg/photography/darktable/src/common/imageio_rawspeed.cc:52:8: error:
‘CameraMetaData’ does not name a type
 static CameraMetaData *meta = NULL;
^~
/home/kmg/photography/darktable/src/common/imageio_rawspeed.cc: In function
‘void dt_rawspeed_load_meta()’:
/home/kmg/photography/darktable/src/common/imageio_rawspeed.cc:56:6: error:
‘meta’ was not declared in this scope
   if(meta == NULL)
  ^~~~
/home/kmg/photography/darktable/src/common/imageio_rawspeed.cc:65:18:
error: expected type-specifier before ‘CameraMetaData’
   meta = new CameraMetaData(camfile);
  ^~
... plus many more

The start of the build is as follows:

warning: unknown feature 'gnome-keyring'
warning: unknown feature 'openmap'
Darktable build script

Building directory:  /home/kmg/photography/darktable/build
Installation prefix: /usr/local
Build type:  RelWithDebInfo
Build generator: Unix Makefiles
Build tasks: 8


-- Building SSE2-optimized codepaths: ON
-- Found little endian system. Good.
-- Is the target platform supported: 1
-- Performing Test C_COMPILER_UNDERSTANDS_-Wno-error=varargs
-- Performing Test C_COMPILER_UNDERSTANDS_-Wno-error=varargs - Success
-- Performing Test CXX_COMPILER_UNDERSTANDS_-Wno-error=varargs
-- Performing Test CXX_COMPILER_UNDERSTANDS_-Wno-error=varargs - Success
-- Performing Test C_COMPILER_UNDERSTANDS_-Wno-error=address-of-packed-
member
-- Performing Test C_COMPILER_UNDERSTANDS_-Wno-error=address-of-packed-
member - Failed
-- Performing Test CXX_COMPILER_UNDERSTANDS_-Wno-error=address-of-packed-
member
-- Performing Test CXX_COMPILER_UNDERSTANDS_-Wno-error=address-of-packed-
member - Failed
-- Performing Test C_COMPILER_UNDERSTANDS_-Wframe-larger-than=32768
-- Performing Test C_COMPILER_UNDERSTANDS_-Wframe-larger-than=32768 -
Success
-- Performing Test CXX_COMPILER_UNDERSTANDS_-Wframe-larger-than=32768
-- Performing Test CXX_COMPILER_UNDERSTANDS_-Wframe-larger-than=32768 -
Success
-- Performing Test C_COMPILER_UNDERSTANDS_-Wstack-usage=32768
-- Performing Test C_COMPILER_UNDERSTANDS_-Wstack-usage=32768 - Success
-- Performing Test CXX_COMPILER_UNDERSTANDS_-Wstack-usage=32768
-- Performing Test CXX_COMPILER_UNDERSTANDS_-Wstack-usage=32768 -
Success
-- Performing Test C_COMPILER_UNDERSTANDS_-Wlarger-than=524288
-- Performing Test C_COMPILER_UNDERSTANDS_-Wlarger-than=524288 - Success
-- Performing Test CXX_COMPILER_UNDERSTANDS_-Wlarger-than=524288
-- Performing Test CXX_COMPILER_UNDERSTANDS_-Wlarger-than=524288 -
Success
-- Looking for external programs
-- Found perl
-- Found intltool-merge
-- Found desktop-file-validate
-- Found LLVM 3.9.1
-- Found clang compiler - /usr/bin/clang-3.9
CMake Warning at CMakeLists.txt:356 (message):
  Could not find clang opencl-c.h header include dir


CMake Warning at CMakeLists.txt:357 (message):
  Test-compilation of OpenCL programs can not be done.


-- Test-compilation of OpenCL programs is disabled.
-- Missing jsonschema, problems in noiseprofiles.json might go unnoticed
-- Found xsltproc
-- Found xmllint
-- All external programs found
-- Found msgfmt to convert .po file. Translation enabled
-- Checking for -march=native support
-- Checking for -march=native support - works
-- Checking for -std=c++11 support
-- Checking for -std=c++11 support - works
-- Looking for PThreads
-- Looking for PThreads - found
-- Looking for OpenMP
-- Looking for OpenMP - found
-- Looking for pugixml
-- Found Pugixml 1.80
-- Looking for pugixml - found (system)
-- Looking for JPEG
-- Looking for JPEG - found
-- Looking for ZLIB
-- Looking for ZLIB - found (system)
-- Looking for xmllint tool
-- Looking for xmllint tool - found
-- Found Glib 2.50.3
-- Found LibXml2: /usr/lib64/libxml2.so (found suitable version "2.9.3",
minimum required is "2.6")
-- Checking for one of the modules 'libsoup-2.2;libsoup2'
-- Found GIO
-- Found LibXml2: /usr/lib64/libxml2.so (found version "2.9.3")
-- Found Sqlite3 3.14.2
-- Found JsonGlib
-- Found OpenJPEG
-- Found GraphicsMagick
-- Does the compiler support __builtin_cpu_supports(): 1
-- Checking for -march=native support
-- Checking for one of the modules 'lua53;lua5.3;lua-5.3;lua'
-- Lua support: System library for lua 5.3 not found (to use darktable's
version use -DDONT_USE_INTERNAL_LUA=Off)
--