Thank you! So easy. It was already fixed. Just needed another git pull.
Am 16.06.19 um 23:50 schrieb Axel Gerber:
>
> See this:
> https://github.com/darktable-org/darktable/issues/2725
>
> Von meinem Mobiltelefon gesendet
>
Am 15.09.18 um 10:30 schrieb Matthias Andree:
> Are you looking at stripped files, or what does "size" print? Are
Here is what "size" is saying:
clang binaries:
4# size *
textdata bss dec hex filename
2233 672 82913 b61 darktable
975972400 48
Am 13.09.18 um 07:38 schrieb Matthias Bodenbinder:
> export CC=/usr/bin/clang
> export CXX=/usr/bin/clang++
> INSTALL_PREFIX_DEFAULT="/opt/darktable-clang"
>
This is working now. I had to remove the build directory after editing build.sh
I have the following package
Am 14.09.18 um 10:15 schrieb johannes hanika:
> hi,
>
> clang needs libomp-dev, not libgomp which gcc uses. i assume you have
> that installed?
There is no such package in manjaro. I have openmp 6.0.1-1 with these files
install
/usr/include/omp.h
/usr/include/ompt.h
/usr/lib/libiomp5.so
Am 13.09.18 um 15:58 schrieb sturmflut:
> Hi all,
>
> IIRC this has something to do with clang not linking against libatomic
> by default, but GCC doing so.
>
> regards,
> Simon
And how to I make this happen with clang?
Am 13.09.18 um 07:38 schrieb Matthias Bodenbinder:
> I assume I am missing some significant compiler options for clang. But dont
> know what that is.
> Can somebody help me with that and tell me what I need to do to make the
> clang binary faster?
I found these messages with c
Hi,
now that google announced that they are using clang for compiling chrome I
wanted to give it a try with DT. I was mainly interested to see what the
performance impact is for the DT binary when using clang.
I simply edited build.sh like this to use clang:
export CC=/usr/bin/clang
export
Hi
I want to play around with noise profile for my Canon G9X MkII to verify if
issue #11928 is really related to the noise profile
(https://redmine.darktable.org/issues/11928 )
But I am struggling with the instructions:
https://www.darktable.org/2012/12/profiling-sensor-and-photon-noise/
I
I created bug report for this issue: https://redmine.darktable.org/issues/11928
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Am 10.01.2018 um 20:56 schrieb Matthias Bodenbinder:
> Hi,
>
> I see weird colored pixel when using profiled denoise with non-local means
> and blend mode HSV-Lightness. Just using blend mode Lightness is fine. Please
> see the attached screenshot. The corresponding RAW is he
Am 08.12.2017 um 10:31 schrieb Roman Lebedev:
>> I found that RAW from Canon Powershot G9X Mark II are not supported although
>> the camera is listed as supported:
>> http://www.darktable.org/resources/camera-support/
> Hmm, now that i actually look at the release notes, the camera is
>
Hi,
since I did not get feedback on the user list I try it here.
I found that RAW from Canon Powershot G9X Mark II are not supported although
the camera is listed as supported:
http://www.darktable.org/resources/camera-support/
I am using DT 2.2.5 on Manjaro Linux. I am testing with this RAW
Hello,
I just want to bring to your attention that there is a new translation engine
available which translates much, much better than anything google or Microsoft
are doing: https://www.deepl.com/translator
May be it is a good idea to use this engine to translate the englisch
documentation
FYI
The performance difference DT self-compiled vs. distributions binary package
has been confirmed for debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855359
Not sure about other distros. But could be similar.
Matthias
Am 17.02.2017 um 06:57 schrieb Matthias Bodenbinder:
> Am 16.02.2017 um 23:27 schrieb Tobias Ellinghaus:
>
>> Neither module was changed between those two releases. Did you compile both
>> versions yourself and are you sure that the compile flags are identical?
>>
Am 16.02.2017 um 23:27 schrieb Tobias Ellinghaus:
> Neither module was changed between those two releases. Did you compile both
> versions yourself and are you sure that the compile flags are identical?
>
>> Good job! Thank you!
>>
>> Matthias
>
I compiled 2.2.3 myself and took 2.2.1 from
Hi,
since I have a new CPU and mainboard I did a lot of benchmarking. What I am
basically doing is executing
darktable-cli bench.SRW test.jpg --core -d perf -d opencl
I got bench.SRW and bench.SRW.xmp somewhere from a darktable group.
Anyhow, I am comparing the DT processing times shown in
Am 05.02.2017 um 15:37 schrieb johannes hanika:
> hi,
>
> how much do you trust your numbers? they look very weird to me. such a
> speedup sounds more like one is running single threaded :)
>
> did you run it a couple of times one after the other? to rule out disk
> prefetching etc? using the
Am 05.02.2017 um 15:37 schrieb johannes hanika:
> hi,
>
> how much do you trust your numbers? they look very weird to me. such a
> speedup sounds more like one is running single threaded :)
>
> did you run it a couple of times one after the other? to rule out disk
> prefetching etc? using the
Hi,
I have upgraded my PC to newest chipset and CPU: Kaby Lake, Z270 with i7-7700K.
Out of curiosity I did a kernel benchmark. Comparing darktable performance with
kernel 3.16.0-4-amd64 and 4.9.0-1-amd64. I use the following command to run
darktable:
darktable-cli test.CR2 test.jpg --core -d
It is working now. Here is what I did:
I just upgraded to exvi2 0.25 from debian testing and elimitated all packages
associated with version 0.24:
39# dpkg -l | grep exiv
ii exiv2 0.25-3
amd64
Am 03.01.2017 um 17:31 schrieb c...@0n0e.com:
> On 01/03/2017 03:22 AM, Matthias Bodenbinder wrote:
>> Hello,
>>
>> I am running Mint LMDE and can not easily install exiv2 0.25 from testing
>> because it has too many dependencies.
>> I compiled version 0.25 by
Hello,
I am running Mint LMDE and can not easily install exiv2 0.25 from testing
because it has too many dependencies.
I compiled version 0.25 by myself and installed it in /home/software/exiv2. In
parallel I still have the default exiv2 version 0.24.
How can I tell my self compiled darktable
Many many thanks to the developers. What a Christmas present!
Matthias
Am 24.12.2016 um 17:50 schrieb Tobias Ellinghaus:
> we're proud to finally announce the new feature release of darktable, 2.2.0!
>
> the github release is here: https://github.com/darktable-org/darktable/
>
Am 08.12.2016 um 20:58 schrieb Tobias Ellinghaus:
> I just installed Ubuntu in a VM, installed Gnome Shell and darktable from the
> PPA. Everything is working normal for me.
May be this is something Timur can test on his PC as well. If it is working for
him in a VM he just needs to do the diff
Am 28.05.2016 um 18:55 schrieb Tobias Ellinghaus:
> Please file a bug report
https://redmine.darktable.org/issues/11039
___
darktable developer mailing list
to unsubscribe send a mail to
Am 24.05.2016 um 07:18 schrieb Matthias Bodenbinder:
> I will do more testing the next days.
After a few more tests it is clear that I can not change the basecurve preset
"test" after it is created. This is true not only for the format value, but
also for the filter when it shou
Am 23.05.2016 um 15:14 schrieb Tobias Ellinghaus:
> Just to reiterate:
> - Which of those presets gets applied?
>
> - When editing that preset, is any change done to the auto-apply settings
> remembered? Maybe even try restarting darktable (that shouldn't matter, but
> who knows what edge
Am 20.05.2016 um 12:10 schrieb Tobias Ellinghaus:
> echo 'select name, format, autoapply from presets where
> operation="basecurve";' | sqlite3 ~/.config/darktable/library.db
meine Canon 6D|2|1
test|7|0
Reinhards Sony RX100M3|2|1
kubischer Spline|2|0
neutral|2|0
Canon EOS-artig|2|1
Canon
Am 19.05.2016 um 19:30 schrieb Matthias Bodenbinder:
> Am 19.05.2016 um 19:03 schrieb Tobias Ellinghaus:
>> and finally those where format is "7", i.e., every image:
>>
>>>> meine Canon 6D|basecurve|7
>>>> Eizo FS2331|colorout|7
>>>>
Am 19.05.2016 um 19:03 schrieb Tobias Ellinghaus:
> and finally those where format is "7", i.e., every image:
>
>> > meine Canon 6D|basecurve|7
>> > Eizo FS2331|colorout|7
>> > Fuji X100|colorin|7
>> > Schärfen aus|sharpen|7
>> > Sony DSC-RX100M3|lens|7
>> > Reinhards Sony RX100M3|basecurve|7
>>
Am 18.05.2016 um 21:08 schrieb Tobias Ellinghaus:
>>> Please open src/libs/metadata_view.c in a text editor and make sure that
>>> SHOW_FLAGS is defined as 1 (around line 39). Then recompile/install and
>>> check the image information of the PNG. There should be a line "Flags"
>>> now. What does
Am 18.05.2016 um 11:05 schrieb Tobias Ellinghaus:
> Am Mittwoch, 18. Mai 2016, 08:05:35 schrieb Matthias Bodenbinder:
>> Am 17.05.2016 um 22:44 schrieb Matthias Bodenbinder:
>>> Am 17.05.2016 um 10:36 schrieb Tobias Ellinghaus:
>>>> Am Samstag, 14. Mai 2016, 15:34:4
Am 08.05.2016 um 15:54 schrieb jmsarat:
> Hi Matthias,
>
> With a clean $HOME/.config/darktable, the option lcms2 is deactivated by
> default therefore the export function use lcms1-1.19. The resulting image
> does not have defect in the blue shade but if the lcms2 option is activated
> then
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 :
Am 07.03.2016 um 16:38 schrieb Matthias Bodenbinder:
> Hi,
>
> I just had a weird experience during playing around with DT 2.0.2. I have
> white balance presets in the darkroom which I can neither select, update or
> delete anymore.
>
> Here is what I did:
> prerequi
Hi,
I just had a weird experience during playing around with DT 2.0.2. I have white
balance presets in the darkroom which I can neither select, update or delete
anymore.
Here is what I did:
prerequisite: I have an existing preset for white balance called "temp". I use
this to temporarily save
Am 28.01.2016 um 07:45 schrieb Matthias Bodenbinder:
> I just found that this already was a bug report with DT version 1.2! Status
> changed from Triaged to Fixed over 1 year ago.
>
> "exported TIFF missing ImageLength field, incompatible with ImageMagick
> iden
Hi,
I started to experiment with focus stacking with enfuse, which needs the hugin
tools for aligning the pictures. Therefore I exported 16 bit TIF from DT. But
when I use these TIF with align_image_stack from hugin tools or in gimp I am
getting these warnings:
align_image_stack:
39 matches
Mail list logo
