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

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

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

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

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

On 29 December 2015 at 21:04, Roman Lebedev 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: ===

Re: [darktable-dev] Re: Micro Four Thirds Lens Correction

I think this is the relevant source code: https://github.com/Beep6581/RawTherapee/blob/master/rtengine/calc_distort.cc ___ darktable developer mailing list to unsubscribe send a mail to

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

You can copy exif from original raw to jpeg using exiv2. Since your jpeg will probably have been correctly rotated by the orientation module, you'll need to clear the 'rotation needed' flag using jhead -norot; you can then regenerate the thumbnail using jhead -rgt . Kofa On 28 November 2016 at

Re: [darktable-dev] OpenCL does not work after Nvidia driver upgrade to 384.90

Thanks for the quick reply. My issue seems to be different: the first module gets compiled. I've tried the workaround, anyway, but it failed: == eagle ~ # cd /usr/lib/x86_64-linux-gnu eagle x86_64-linux-gnu # ls nvidia/current/libnvidia-ptxjitcompiler.so.1<-- this was the original file linked

Re: [darktable-dev] OpenCL does not work after Nvidia driver upgrade to 384.90

Hi Bob, It gives me hope :) Could you please check the link to my logs, and send me the output of the commands on your system? E.g. dpkg. I installed the driver using the driver manager app; is that all you did, too, or did you need to add any package manually? Thanks, István On 18 Dec 2017

Re: [darktable-dev] OpenCL does not work after Nvidia driver upgrade to 384.90

Thanks, Bob. I have now removed all extra packages and reconfigured the remaining ones; the result is more free disk space, but no improvement in darktable. One thing I see is that your nvidia packages are of version 384.90-0ubuntu0.16.04.1, while mine are 384.90-0ubuntu0.16.04.2. I'll try a

Re: [darktable-dev] OpenCL does not work after Nvidia driver upgrade to 384.90

On 19 December 2017 at 07:05, KOVÁCS István <k...@kovacs-telekes.org> wrote: > Could you please try one more thing for me? Run the command > ls -l /usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.1 > and paste its output here. > > (I did not have that file; I needed to li

Re: [darktable-dev] OpenCL does not work after Nvidia driver upgrade to 384.90

Hello All, I seems I posted the wrong logs - I guess it was too early in the morning for me. Here are the correct ones: clinfo output: http://tech.kovacs-telekes.org/files/darktable-opencl-nvidia384.90/clinfo.log darktable -d opencl output:

Re: [darktable-dev] OpenCL does not work after Nvidia driver upgrade to 384.90

at 07:09, Bob Tregilus <v2g...@gmail.com> wrote: > > > On Mon, Dec 18, 2017 at 10:06 PM, KOVÁCS István <k...@kovacs-telekes.org> > wrote: >> >> On 19 December 2017 at 07:05, KOVÁCS István <k...@kovacs-telekes.org> >> wrote: >> > Could you ple

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

'Something more lightweight?' What about Github pages and https://github.com/yakivmospan/github-wikito-converter 'allows you to generate HTML & PDF documentation from your Github wiki or any other markdown-based wiki.' > >

Re: [darktable-dev] OpenCL does not work after Nvidia driver upgrade to 384.90

enCL (Open Computing Language) header files Kofa On 19 December 2017 at 09:07, Bob Tregilus <v2g...@gmail.com> wrote: > > > > > On Mon, Dec 18, 2017 at 11:30 PM, KOVÁCS István <k...@kovacs-telekes.org> > wrote: >> >> Update: I've gone through all the modules, m

[darktable-dev] Fwd: Colour zones - bug or works as intended?

Hello, Sorry about cross-posting, I did not get any reaction on the users' list. [Some typos fixed below.] I find the way colour zones behaves surprising. To demonstrate, I've shared a set of images (raw + screenshots) here: http://tech.kovacs-telekes.org/files/dt-colour-zones/ orig.jpg: I

[darktable-dev] Grey theme

on light background). I mostly edit at night, in a quite dark room, with a 'warm-white' LED desk lap illuminating the white wall behind the monitor. Thanks in advance, Kofa -- Forwarded message - From: KOVÁCS István Date: Sun, 17 Feb 2019 22:38 Subject: Grey theme To: Darktable Users

Re: [darktable-dev] Grey theme

Hi Aurélien, Thanks for the response. My editing is not critical, as I just post online, but now I'd like to print some photos. I'll first print one batch and see how they turn out (whether too dark etc.), and may re-edit accordingly. István On Tue, 26 Feb 2019, 02:50 Aurélien Pierre, wrote:

Re: Fwd: [darktable-dev] Pushing ISO (ISO invarience)

In the comments, they do mention using another instance of exposure. However, since they gave darktable a total of 20 minutes (and did not ask someone who has actually used it), they may have forgotten about base curves, which also influence brightness. ---

Re: [darktable-dev] Duplicate manager deletes all versions?

On Sun, 10 Mar 2019 at 14:48, Patrick Shanahan wrote: > > Sometimes (I have been unable to find out under what circumstances) > > clicking [x] in the duplicate manager deletes all versions of the > > file. > > Redmine: https://redmine.darktable.org/issues/12623 > > I cannot duplicate your

Re: [darktable-dev] Duplicate manager deletes all versions?

> > nor can I select more that one duplicate image at a time. NB: I'm not *selecting* anything. I click the x next to one of the duplicates. As shown on the screenshot, a popup appears, asking whether to delete N files, where N is the number of versions (duplicates). This is what I do:

Re: [darktable-dev] Duplicate manager deletes all versions?

Patrick, Thanks for the feedback. I'm trying to understand what's going on - please see below. On Sun, 10 Mar 2019 at 22:20, Patrick Shanahan wrote: > as I said, I do not see that. I cannot delete files within darkroom mode > or within duplicate module, selected or not. Do you mean there's no

[darktable-dev] Duplicate manager deletes all versions?

Hi, Sometimes (I have been unable to find out under what circumstances) clicking [x] in the duplicate manager deletes all versions of the file. Here's a screenshot; if I clicked 'Yes', it'd actually remove the raw file and all three sidecars.

Re: [darktable-dev] implementation question: remove all unused modules

On Thu, 13 Jun 2019 at 16:12, Aurélien Pierre wrote: > [of highlights reconstruction and white balance] until someone is able to > tell me what the use case for having them disabled is One use case is the workaround for the issue discussed here:

Re: [darktable-dev] Error message

On Thu, 1 Aug 2019, 20:56 Julian Rickards, wrote: > I've been getting the following error > > 'tiling failed for module "atrous", image may be garbled' > I think this belongs to the user list, but anyway: read the manual, and look for tiling. More specifically:

Re: [darktable-dev] Error message

On Fri, 2 Aug 2019, 03:44 Julian Rickards, wrote: > My laptop has non-expandable 4GB RAM > I'll just deal with the error message as it comes up > Why risk image corruption? I also use darktable with 4GB of RAM. If I were you, I'd try the instructions for 32-bit systems (even though you're

[darktable-dev] Increased memory requirements?

Hi, I think it's a user's question, but quite technical and with the dev version, so I'm posting it here. I've been using darktable since the 1.x days, maybe longer. I have an ancient Core2 Duo machine with just 4 GB of RAM and an NVidia GTX 650 with 2 GB onboard. For that reason, I have used the

[darktable-dev] Drag-and-drop to change module order

Hi, I've seen Aurélien Pierre's video about filmic and tone EQ; there, he used the mouse to reorder modules on the active modules tab. I can only use the 'multiple instances' menu's move up/down options; for me, click+drag just opens/closes the module (so the click takes effect, the drag is

Re: [darktable-dev] Increased memory requirements?

On Sat, 9 Nov 2019 at 21:28, Aurélien Pierre wrote: > atrous (contrast equalizer) is quite heavy on hardware and needs a lot of > memory to store the intermediate wavelets scales. I remember having the same > issue on my previous laptop (GPU Nvidia 635M, 2 GB too) with certain updates > of the

Re: [darktable-dev] Increased memory requirements?

Andreas, Thanks for the suggestion. I got a used NVidia 1060 with 6 GB of RAM for ~CHF 140, and it flies. I may get an AMD Ryzen 2600 with 16 GB RAM as the next step. Kofa On Sun, 10 Nov 2019 at 12:37, Andreas Schneider wrote: > You don't really need a beast. AMD RX560 with 4GB of RAM cost

[darktable-dev] filmic RGB presets

Hi, I'm on darktable 1a11ea71 compiled using build.sh; OS is Kubuntu 19.04. I started with a reasonably exposed landscape, and tried applying the 'outdoors' setting as a starting point (that, and 'bright outdoors', often worked well for me in 'classic' filmic in darktable 2.6.2). WIth the

[darktable-dev] Filmic RGB - switching 'preserve chroma' setting changes the curve

Hi, I don't know if this is how it's supposed to behave, but I suspect it is not: switching 'preserve chroma' to 'RGB power norm' drastically altered the curve. Switching back to any of the other settings (including to 'no') restored the original curve; selecting 'RGB power norm' altered it

Re: [darktable-dev] Filmic RGB - switching 'preserve chroma' setting changes the curve

Hi, On Fri, 25 Oct 2019, 07:31 Axel Gerber, wrote: > Before you installed a new dt 2.7 version, did you clean the installation > folder or just swiped it over? If the latter, try to clean and reinstall > Please keep the discussion on the list. Thanks for the suggestion. I did not remove the

Re: [darktable-dev] filmic RGB presets

; > Cheers, > > Aurélien. > > Le 16/10/2019 à 10:34, KOVÁCS István a écrit : > > Hi, > > I'm on darktable 1a11ea71 compiled using build.sh; OS is Kubuntu 19.04. > > I started with a reasonably exposed landscape, and tried applying the > 'outdoors' setting as a star

Re: [darktable-dev] Contributing a simple change

Hi, First: I've changed the subject (we're no longer discussing 'cannot open database', right?). > how do I contribute small bits to Darktable (preferably without cloning > the codebase and using git)? > > I have 1 line for the noise*json and a few WB presets for a camera to give. Second:

Re: [darktable-dev] Parametric Yellow mask

On Wed, 15 Jan 2020, 20:26 August Schwerdfeger, wrote: > I think that just means your parametric mask's parameters are set such > that it is not actually applying to any part of the image > Or opacity is 0. (Doesn't this belong to the users list, though?) Kofa

[darktable-dev] Compilation failure

Hi, Building from master (569b31) on Ubuntu 20.04 and the following build script: cd ~/darktable git clean -d -f -x git submodule init git submodule update git pull --rebase --recurse-submodules ./build.sh --disable-lua --disable-camera --disable-flickr --disable-kwallet --disable-libsecret

Re: [darktable-dev] dt build from git crashes on Ubuntu 20

git clean -d -f -x ; git pull --rebase --recurse-submodules This will remove generated files, then update from git. ___ darktable developer mailing list to unsubscribe send a mail to

Re: [darktable-dev] Personal copy of darktable

On Mon, 12 Oct 2020 at 18:04, Postmaster wrote: > is it possible to have your own copy of darktable without installing > pgm/libraries outside of your account? I assume you're under Linux. There are 'all-in-one' application packages that ship both the software and the libraries (AppImage,

Re: [darktable-dev] Bug in shape selection at large pictures?

On Fri, 9 Oct 2020 at 20:22, Frank Huebner wrote: > I used the retouch module on a large picture (10165 x 4018). It did not > work as expected. At normal size pictures (16 Mpix) it worked as > expected. This sounds like an issue I have logged, though mine had nothing to do with size of the

Re: [darktable-dev] Not flashing a blank space when loading an image?

On Sat, 10 Oct 2020 at 23:38, wrote: > I tried searching for the 'Culling Mode' and found this resource > (https://discuss.pixls.us/t/help-with-culling-mode-in-darktable/12296 > sorry but searching the official documentation didn't work without > javascript). I discovered that a user can > hold

Re: [darktable-dev] Left/right arrow keys to move between photos in Darkroom

On Tue, 6 Oct 2020 at 16:07, wrote: > Using left/right arrow keys to move between photos in Darkroom would be the > most intuitive. [...] > I discovered (in another ticket) that spacebar and backspace perform these > functions by default Feel free the reassign them. Also, you don't need to

Re: [darktable-dev] Upgrade from 3.0.2 to 3.2.1 destroys order of modules

On Thu, 13 Aug 2020 at 08:34, Andreas Herold wrote: > I decided to summarize everything from now on in every mail. > Additonally I have constructed an example, that shows my problem in a more > dramatic way. I think it'd be great if you opened a github issue with the same content and examples:

Re: [darktable-dev] Upgrade from 3.0.2 to 3.2.1 destroys order of modules

On Wed, 12 Aug 2020 at 21:09, Richard Hobday wrote: > You might benefit from changing the settings in: > Preferences/processing/auto apply pixel workflow defaults > this should allow you to the revert to the legacy pipe order. I thought that setting changes which modules get auto-applied (base

Re: [darktable-dev] Reporting two Bugs - that may be related

On Tue, 14 Jul 2020 at 10:22, Ramnarayan.K wrote: > Please do advise if there is an official PPA for ensuring the latest and > safest updates. A bit disappointed that the Mint / Ubuntu repos are not > linked to the latest stable versions. https://www.darktable.org/install/ -> OBS

[darktable-dev] Resources for beginners / newcomers

Dear All, There have been a number of questions from newcomers, which is, on one hand, great (means user base of darktable is growing), but it also means that people on this list keep answering the same questions. Therefore, I'd like to suggest a number of resources: - the darktable manual:

Re: [darktable-dev] Change request for copying editing steps without crop module

On Tue, 8 Dec 2020 at 07:30, Dennis Gräser wrote: > Copying editing steps is very helpful, especially with similarly exposed > images. > However, by default the crop module is always copied as well. This doesn't > make much sense, since a cropping has to be done by hand again and again >

Re: [darktable-dev] Meaning of one of the strings

"following modules are deprecated because they have internal design mistakes " "that can't be solved and alternatives that solve them.\n" "they will be removed for new edits in next release." I'd actually re-phrase that (but I'm not a native speaker): for me, the 'have' at the beginning of the

[darktable-dev] Extremely bad performance (Windows 10, darktable 3.2.1)

Hi, This is just to let you know that a member has reported extremely bad performance on pixls.us. The most time-consuming modules ran up to a 1000 times(!) slower than on my old Core2 Duo machine. The performance comparison can be found here:

[darktable-dev] Re: Extremely bad performance (Windows 10, darktable 3.2.1)

On Mon, 2 Nov 2020 at 20:18, KOVÁCS István wrote: > This is just to let you know that a member has reported extremely bad > performance on pixls.us. The most time-consuming modules ran up to a > 1000 times(!) slower than on my old Core2 Duo machine. This has been resolved: I did not

Re: [darktable-dev] Bug (lighttable, custom sort order): moving images inverts the order of moved images

Just a bit of background for Patrick's commands. There are at least two reasons your build won't match the one built from a fresh copy of the code on Github: - you have local modifications (the command 'git status' (without the quotes) should list the files differing from the baseline; 'git

Re: [darktable-dev] Issue with moving the crop box

Hello, You use a very old version of darktable, 3.0.1. Please try to reproduce with the current stable version, 3.4.1.1. If still reproducible, please file a bug, uploading the image, the xmp file, a screenshot showing what you see in the darkroom, and the exported image for comparison.

Re: [darktable-dev] News about darktable 3.6

I think you forgot to mention the automated parameterisation of filmic and tone equaliser, and the AI-powered selection of the chroma-preservation mode. ___ darktable developer mailing list to unsubscribe send a mail to

Re: [darktable-dev] Bug : dt git master exports in wrong order

> always the same dilemma for me with creating a github account... So I hope > someone will take pity... I think you should not abuse the developers' time to raise issues on your behalf, expecting them to do something that you feel violates privacy (even if they were already foolish enough to

Re: RV: [darktable-dev] CAN NOT OPEN FOLDERS

It has just occurred to me: have you tried disabling OpenCL before importing photos? A bad graphics driver could cause the issue you experience (processing hanging indefinitely). It can be toggled in settings, see here: https://darktable.gitlab.io/doc/es/cpugpumemory.html So, again, start with a

Re: RV: [darktable-dev] CAN NOT OPEN FOLDERS

Hello, I honestly think this thread should be on the users' list, not on the devs'. BTW, Susana, there's a lively forum at discuss.pixls.us, where it's much easier to share screenshots, for example. With that out of the way: removing (uninstalling) darktable only removes the program, but does not

Re: [darktable-dev] Histogram not visible 3.4 Win 10

I see it's not 3.4, but 3.4.1.1 (the latest). It's important, because 3.4.1 was broken, and 3.4 also had problems. Deleting and reinstalling does not remove/fix potentially broken configuration and database files. If you want helpful responses, please provide more info, e.g. have you ever had

Re: RV: [darktable-dev] CAN NOT OPEN FOLDERS

Note that today I installed darktable on a Windows laptop just to see if I can help with the issue. I ran it with darktable -d all but got absolutely no output on the console (Windows 10). That is not how it behaves on Linux. BTW, the invocation would need the 'bin' subdirectory and the name of