[darktable-user] Re: Darktable 3.0 looks great, but my fonts are far too large...

Am 28.12.19 um 22:12 schrieb Shane Simmons: > I just installed DT 3.0 from the unofficial Ubuntu Handbook PPA, the other > day, but the issue I have is that the fonts are much too large on my 4K > monitor, and I've tried adjusting the /screen_dpi_overwrite /setting in > darktablerc, to no

[darktable-user] Re: GFX card recommendations

Am 16.09.19 um 07:57 schrieb Matthias Bodenbinder: > I am using NVIDIA cards since decades. Very nice. > I can not understand the NVIDIA bashing I read every now and then. I used > NVIDIA cards with debian, Mint and now Manjaro without issue. > > The GTX 1050 Ti have

[darktable-user] Re: GFX card recommendations

I am using NVIDIA cards since decades. Very nice. I can not understand the NVIDIA bashing I read every now and then. I used NVIDIA cards with debian, Mint and now Manjaro without issue. The GTX 1050 Ti have the best price-for-performance from my point of view. Very good opencl performance with

[darktable-user] Re: OpenCL error starting dt

Am 17.08.19 um 03:29 schrieb I. Ivanov: > Hi Jack, > > Can I ask for clarification please? openCL on Intel CPU is black listed > *regardless of the GPU* (Nvidia / Radeon) or this affects only the build > in Intel GPU (that is integrated on the processor)? > > Thank you, > > B > There is some

[darktable-user] gtk image viewer honouring xmp sidecar files

Hi, I am using darktable while my wife uses digikam. Both apps are compatible with regard to xmp files and star ratings. In digikam she can see the start ratings I am setting in darktable while in darktable I can see the start ratings my wife setting with digikam (I have to reimport the images

[darktable-user] Re: OpenCL on Manjaro

I have it working and no cuda packages installed: lib32-nvidia-utils 1:415.18-1 linux414-nvidia 1:415.18-3 linux419-nvidia 1:415.18-3 mhwd-nvidia 1:415.18-1 mhwd-nvidia-340xx 340.107-1 mhwd-nvidia-390xx 390.87-1 nvidia-utils 1:415.18-1 opencl-nvidia 1:415.18-1 Am 03.12.18 um 19:42 schrieb David

[darktable-user] Re: showing wrong lens

Am 03.07.2018 um 05:31 schrieb jys: > Exiv2 (not exiftool) provides a lens mapping method for that, described here: > > > http://dev.exiv2.org/projects/exiv2/wiki/Lens_Recognition_in_Exiv2_v026_(and_later)/ Indeed, that did the trick. I created a file ~/.exiv2 with the following content:

[darktable-user] showing wrong lens

Hi, I have a Tamron 90 mm macro lens. exiftool shows two different lenses for the same picture: 10# exiftool IMG_4527.CR2 | grep -i lens Lens Type : Canon EF 100mm f/2.8L Macro IS USM Lens Drive No AF: Focus search on Lens Info : 90mm

[darktable-user] Re: opencl memory issue with GUI vs. commandline

Am 25.05.2018 um 14:35 schrieb Peter McD: > Is there a rule of thumb for headroom settings? Very good question. Specifically because I do not see a performance difference between opencl_memory_headroom=1000 and opencl_memory_headroom=400. The pipeline processing always takes the same time

[darktable-user] Re: opencl memory issue with GUI vs. commandline

Hello Ulrich, I did more testing around starting / stopping DT. This alone increase the GPU memory consumption continuously by 30 MiB per start/stop activity. It starts with 107 MiB at the beginning and ends at 271 MiB after five start/stop cylces. This is with gnome-shell. I did the same

[darktable-user] Re: opencl memory issue with GUI vs. commandline

Am 25.05.2018 um 07:10 schrieb Ulrich Pegelow: > Am 25.05.2018 um 06:21 schrieb Matthias Bodenbinder: >> But for me the issue is more: Why does it work with >> opencl_memory_headroom=400 for the first couple of cycles and then I get the >> issue. Then

[darktable-user] Re: opencl memory issue with GUI vs. commandline

Am 24.05.2018 um 21:51 schrieb Ulrich Pegelow: > Am 24.05.2018 um 18:15 schrieb Matthias Bodenbinder: >> Am 24.05.2018 um 17:43 schrieb Matthias Bodenbinder: >>> 37,787315 [opencl_summary_statistics] device 'GeForce GTX 1050 Ti' (0): >>> peak memory usage 380

[darktable-user] Re: opencl memory issue with GUI vs. commandline

Am 24.05.2018 um 17:43 schrieb Matthias Bodenbinder: > Am 24.05.2018 um 16:02 schrieb Ulrich Pegelow: >> Am 24.05.2018 um 14:10 schrieb Matthias Bodenbinder: >>> Can it be that the DT GUI is not releasing all the GPU memory and then the >>> commandline

[darktable-user] Re: opencl memory issue with GUI vs. commandline

Am 24.05.2018 um 16:02 schrieb Ulrich Pegelow: > Am 24.05.2018 um 14:10 schrieb Matthias Bodenbinder: >> Can it be that the DT GUI is not releasing all the GPU memory and then the >> commandline fails? And the worst thing is that the system is not recovering >> from that

[darktable-user] Re: opencl memory issue with GUI vs. commandline

Am 24.05.2018 um 14:10 schrieb Matthias Bodenbinder: > 3# ll bench.SRW *.CR2 > -rw-r--r-- 1 matthias matthias 20453024 17. Jan 2017 bench.SRW > -rw-r--r--+ 1 matthias matthias 67127952 16. Feb 2017 RAW_CANON_EOS_5DS.CR2 bench.SRW can be downloaded here: http://www.mirada.ch/bench.S

[darktable-user] opencl memory issue with GUI vs. commandline

Hi, I have a weird opencl memory issue. I just got a new NVIDIA GFX 1050 Ti and wanted to do some benchmarking. I typically use the benchmarking which has been described several times here in this group as well. I run darktable-cli bench.SRW test.jpg --core -d perf -d opencl and see how

[darktable-user] Re: darktable not setting creator

rtist.  I'm speculating that > the 20D has an Artist field in the EXIF data and the G9 doesn't.  You could > check for the artist field with exiftool. > > > Bill > > On Thu, Apr 26, 2018 at 11:45 AM, Matthias Bodenbinder > <matth...@bodenbinder.de <mailto:matth...@bo

[darktable-user] Re: darktable not setting creator

Am 26.04.2018 um 11:31 schrieb Tobias Ellinghaus: > Am Dienstag, 24. April 2018, 07:06:38 CEST schrieb Matthias Bodenbinder: >> Am 23.04.2018 um 07:50 schrieb Matthias Bodenbinder: >>> Am 22.04.2018 um 12:26 schrieb Tobias Ellinghaus: >>>> Am Sonntag, 22. April 2018,

[darktable-user] Re: darktable not setting creator

Am 23.04.2018 um 07:50 schrieb Matthias Bodenbinder: > Am 22.04.2018 um 12:26 schrieb Tobias Ellinghaus: >> Am Sonntag, 22. April 2018, 09:09:09 CEST schrieb Matthias Bodenbinder: >>> Am 22.04.2018 um 09:01 schrieb Matthias Bodenbinder: >>>> Hi, >>>>

[darktable-user] Re: darktable not setting creator

Am 22.04.2018 um 12:26 schrieb Tobias Ellinghaus: > Am Sonntag, 22. April 2018, 09:09:09 CEST schrieb Matthias Bodenbinder: >> Am 22.04.2018 um 09:01 schrieb Matthias Bodenbinder: >>> Hi, >>> >>> I just realized that since this year darktable is not setting th

[darktable-user] Re: darktable not setting creator

Am 22.04.2018 um 12:26 schrieb Tobias Ellinghaus: > Am Sonntag, 22. April 2018, 09:09:09 CEST schrieb Matthias Bodenbinder: >> Am 22.04.2018 um 09:01 schrieb Matthias Bodenbinder: >>> Hi, >>> >>> I just realized that since this year darktable is not setting th

[darktable-user] Re: darktable not setting creator

Am 22.04.2018 um 09:01 schrieb Matthias Bodenbinder: > Hi, > > I just realized that since this year darktable is not setting the default > "creator" for imported pictures anymore. I have set my name in the "creator > to be applied when importing" field. And

[darktable-user] darktable not setting creator

Hi, I just realized that since this year darktable is not setting the default "creator" for imported pictures anymore. I have set my name in the "creator to be applied when importing" field. And I actually never changed that. How can I debug this? Matthias

[darktable-user] denoise weakness

Hi, I take the latest postings about denoise issues as an opportunity to ask a few questions. I am a long term DT user. I have spend hours creating my own denoise profiles with several instances of profiled denoise in wavelet and local means. But when comparing with rawtherapee or lightroom I

[darktable-user] Re: CPU Recommendations

Am 07.02.2018 um 03:12 schrieb Michael Rasmussen: > On Tue, 6 Feb 2018 17:52:48 -0800 > Scott wrote: > >> [default_process_tiling_opencl_ptp] couldn't run process_cl() for >> module 'atrous' in tiling mode: 0 >> [opencl_pixelpipe] could not run module 'atrous' on gpu.

[darktable-user] Re: CPU Recommendations

Am 06.02.2018 um 16:41 schrieb Jean-Luc Lacroix: > CPU i7-4790K > GPU GeForce GTX 970 (1664 CUDA cores, 4 GB) > RAM 24 GB > > $ wget http://www.mirada.ch/bench.SRW > $ wget http://www.mirada.ch/bench.SRW.xmp > > $ darktable-cli bench.SRW test.jpg --core --disable-opencl -d perf pixel

[darktable-user] Re: CPU Recommendations

Am 04.02.2018 um 23:38 schrieb Robert Bieber: > Oh yeah, I'm just talking about the price of the CPU, not the whole PC. I'm > planning on doing all out on RAM and solid state drives as well. I guess GPU > might be of some concern as well, how has GPU processing in dark table on > Linux been

[darktable-user] Re: Problem when I open raw files to edit on DARKTABLE

When I open the CR2 it pretty much looks like the JPG you provided. So I can not reproduce your issue. Which basecurve is applied in your DT? Matthias Am 31.01.2018 um 16:31 schrieb Diego Queres: > Hi!  > > I liked Darktable a lot. I'm learning a lot from it, to edit my last photos > and I

[darktable-user] Re: cannot exit DT when webdav file transfer is ongoing

Ellinghaus: > Am Sonntag, 28. Januar 2018, 13:13:20 CET schrieb Matthias Bodenbinder: >> I did an strace and found that DT is trying to stat a DCIM folder in the >> cloud: >> >> 4969 stat("/mnt/magentacloud/DCIM", >> 4969 stat("/mnt/magentacloud/dci

[darktable-user] cannot exit DT when webdav file transfer is ongoing

Hi I found the following odd behaviour of DT. While a am transfering a file to my magentacloud via webdav, I can not exit DT. Instead the GUI is telling me that DT is not responding and if I want to wait or terminate forcefully. If I wait, DT terminates after the webdav file transfer is

[darktable-user] Re: Color Lookup Tables

Am 06.01.2018 um 11:51 schrieb Jean-Luc Coulon (f5ibh): > Hi, > > But all the links on the site are dead. > I've found somewhere the link of the blog. > But I dont know where the files are and if there still are available... > > Regards > > Jean-Luc They are on github:

[darktable-user] Re: darktable and gimp 2.9

Am 04.01.2018 um 19:08 schrieb Matthias Bodenbinder: > Am 04.01.2018 um 18:59 schrieb François Patte: >> Bonjour, >> >> I just tried to experiment gimp 2.9 (development version): openning a >> raw file opens darktable and once you have finish to treat your photo in >

[darktable-user] Re: darktable and gimp 2.9

Am 04.01.2018 um 18:59 schrieb François Patte: > Bonjour, > > I just tried to experiment gimp 2.9 (development version): openning a > raw file opens darktable and once you have finish to treat your photo in > darktable, closing darktable imports the photo in gimp... Ok. > > But the result I had

[darktable-user] PTI patch impact on DT performance = 0,5 %

Hi, the new kernel 4.14.11 comes with the PTI patches. There are reports which indicate that these patches can have a severe performance impact (e.g. https://www.phoronix.com/scan.php?page=article=linux-415-x86pti=1) I did some benchmarks with DT. I am using Manjaro with latest kernel

[darktable-user] Re: order in which modules are applied

Am 28.12.2017 um 11:35 schrieb FK: > Am 27.12.2017 um 22:41 schrieb Matthias Bodenbinder: >> But my initial question is more from a theoretical point of view. I am >> just curious about the algorithm so to speak. Does it make a >> difference if denoise profile, wavele

[darktable-user] Re: order in which modules are applied

Am 27.12.2017 um 19:09 schrieb Roman Lebedev: > On Wed, Dec 27, 2017 at 9:00 PM, Matthias Bodenbinder > <matth...@bodenbinder.de> wrote: >> Hi, >> >> I know that the modules are applied in a fixed order. So my questions is >> about several instances of th

[darktable-user] order in which modules are applied

Hi, I know that the modules are applied in a fixed order. So my questions is about several instances of the same module. Specifically profiled denoise. I have the following scenario: I apply the profiled denoise module 3 times. All three blended "uniformly" but with a differen blend mode:

[darktable-user] Re: 16bit PNG in 2.4.0-rc2

Am 22.12.2017 um 23:12 schrieb Matthias Bodenbinder: > Hi, > > I just played a little bit with the rc2. I exported 16bit PNG but got 8bit > according to gimp-2.9.8. I checked with TIF an TIF is fine except for some > picture showing artefacts with 16bit TIF. DT at leats creat

[darktable-user] 16bit PNG in 2.4.0-rc2

Hi, I just played a little bit with the rc2. I exported 16bit PNG but got 8bit according to gimp-2.9.8. I checked with TIF an TIF is fine except for some picture showing artefacts with 16bit TIF. DT at leats creates a 16bit TIFF and a 32bit Fließkomma TIF as well (according to gimp 2.9.8.

[darktable-user] Re: How would you do this in Darktable

This looks fairly easy unless I am missing something. 1.) process the photo such that the cat looks good. 2.) apply monochrom module 2.) overexpose the surroundigs of the cat. (separate exposure layer with mask) Matthias Am 09.12.2017 um 06:31 schrieb Johann Spies: > Apologies. I forgot about

[darktable-user] Re: Canon Powershot G9X Mark II

Am 07.12.2017 um 07:50 schrieb Matthias Bodenbinder: > Hi, > > I have ordered a Canon Powershot G9X Mark II. In the meantime I checked RAW > files from this Camera with DT and it is not working :-( > > I used this RAW file for my test: > http://www.imaging-resource.c

[darktable-user] Canon Powershot G9X Mark II

Hi, I have ordered a Canon Powershot G9X Mark II. In the meantime I checked RAW files from this Camera with DT and it is not working :-( I used this RAW file for my test: http://www.imaging-resource.com/PRODS/canon-g9x-ii/YIMG_0850-FLASH-ON.CR2.HTM DT says: Color Matrix not found DT says:

[darktable-user] Re: Darktable seems to reboot my system.

Distros like Mint or Manjaro come with memtest86+ installed. It is part of the grub boot menu. Just select the memtest86 entry during boot. Matthias Am 06.11.2017 um 02:55 schrieb Michael: > oh  it is an iso! > > On Sun, Nov 5, 2017 at 8:25 PM, Patrick Shanahan

[darktable-user] Re: moving ratings from old db to new db

Am 03.03.2017 um 18:53 schrieb Tobias Ellinghaus: > Just grouping of images and date/time offsets applied in the geolocation > module. Everything else (including ratings) are in the XMPs. Well, and > presets > and styles of course (the latter are backed up to the disk though) if you > nuked

[darktable-user] moving ratings from old db to new db

Hi, i had to move my pictures to a different folder. I reimported the pictures with DT. The old folder is gone so I had to run purge_non_existing_images.sh to get rid of all entries pointing to the old folder. But with this exercise I lost all star ratings and probably other settings as well

[darktable-user] Re: what graphics card to get?

Am 17.01.2017 um 12:47 schrieb matth...@bodenbinder.de: > Am 2017-01-17 8:21, schrieb Colin Adams: > >> >> How do you arrive at that figure? >> > I did a lot of testing. ;-) > > For your reference: Here is the thread I started in 2014: >

[darktable-user] Re: issue with detecting canon EF16-35mm f/4L IS USM

Am 03.01.2017 um 10:34 schrieb Tobias Ellinghaus: > Am Dienstag, 3. Januar 2017, 00:13:15 CET schrieb Matthias Bodenbinder: >> I am pretty sure that this is related to my self compiled binaries in >> conjunction with exvi2 0.24 which does not include the Canon 16-35 mm f/4L. >>

[darktable-user] Re: issue with detecting canon EF16-35mm f/4L IS USM

export LD_LIBRARY_PATH=/home/software/exiv2/lib But that did not do the trick. Matthias Am 02.01.2017 um 18:35 schrieb Matthias Bodenbinder: > Hello, > > I just relaized that I have an issue with DT detecting the above mentioned > Canon lens. > > Photos taken until December 201

[darktable-user] issue with detecting canon EF16-35mm f/4L IS USM

Hello, I just relaized that I have an issue with DT detecting the above mentioned Canon lens. Photos taken until December 2014 show the correct exif and the proper lens in the correction modul. Starting in Jan 2015 (sorry, I do not use that lens very often and do not pay attention a lot to

[darktable-user] Re: Strange artifacts

Am 22.12.2016 um 08:40 schrieb Matthias Bodenbinder: > I just did a quick check with rawtherapee. It shows the same artefacts. > Matthias And I checked with Aftershot Pro 2.4.0.119: It shows also the same artefacts. Matthias > > Am 21.12.2016 um 23:23 schrieb Lorenzo Bossi: >&

[darktable-user] Re: exporting jpegs: 'quality %'

Am 18.12.2016 um 07:26 schrieb Tim Rolph: > Hi I Just ran a test to compare the same image on PS and dt and PS 10 was > equal to 91 in dt and PS 6 was equal to dt 70. > This was just one image tested but the file sizes came out the same. > Hope this helps. > > Tim. If that is the case the math

[darktable-user] Re: magic-lantern dual-iso feature

-11-29 23:44, johannes hanika wrote: >> >> what's the compile error? >> >> -jo >> >> On Wed, Nov 30, 2016 at 7:35 PM, Matthias Bodenbinder >> <matth...@bodenbinder.de> wrote: >> >> Hi, >> >> I want to give magic-lantern a try and

[darktable-user] magic-lantern dual-iso feature

Hi, I want to give magic-lantern a try and test the dual-iso feature. But unfortunatly I can not get cr2hdr compiled. And I dont know how to handle the dual-iso files in DT without cr2hdr. Does somebody know of a download link for a cr2hdr binary? Kind Regards Matthias PS I am using DT