Re: [Darktable-users] How to change modules auto-applied to raw files

> in "global settings" go to the rightest of the four tabs - there you can set default behaviour - theoretically. Thanks for the hint. The way to add one is actually though the module, as described here: http://www.darktable.org/usermanual/ch03s02s02.html.php The trouble is that thi

[Darktable-users] SOLVED: crop area methods

* Patrick Shanahan [11-06-14 16:00]: > * Tobias Ellinghaus [11-06-14 14:39]: > > Am Donnerstag, 6. November 2014, 09:18:25 schrieb Patrick Shanahan: > [...] > > > This is not correct as I apparently jumped the gun and used a package > > > prior to your change. Your change did remove the errant

Re: [Darktable-users] crop area methods

* Tobias Ellinghaus [11-06-14 14:39]: > Am Donnerstag, 6. November 2014, 09:18:25 schrieb Patrick Shanahan: [...] > > This is not correct as I apparently jumped the gun and used a package > > prior to your change. Your change did remove the errant condition of > > moving rather than resizing. B

Re: [Darktable-users] crop area methods

Am Donnerstag, 6. November 2014, 09:18:25 schrieb Patrick Shanahan: > * Patrick Shanahan [11-06-14 08:59]: > > * Tobias Ellinghaus [11-06-14 07:54]: > > > Am Donnerstag, 6. November 2014, 12:56:23 schrieb Tobias Ellinghaus: > > > > Am Mittwoch, 5. November 2014, 14:31:23 schrieb Patrick Shanahan:

Re: [Darktable-users] color zones - brilliant but flawed

I would send your mail to the development list for further discussion there -- ___ Darktable-users mailing list Darktable-users@lists.sourceforge.net https://lists.sourceforge.net

[Darktable-users] color zones - brilliant but flawed

Hi, I love the color zones adjustment tool, especially for scanning Kodachrome. However, I find the way to manipulate it with the control points a bit flawed: I'd expect the shape of the adjustment curve to be translation invariant - meaning that I can pick an arbitrary point on the x axis and s

Re: [Darktable-users] Darktable and Nvidia Optimus (again...)

2014-11-06 15:26 GMT+01:00 Patrick Shanahan : > * Hans Petter Birkeland [11-06-14 09:07]: > [...] > > And then I installed nvidia-modprobe, downloaded from > > http://packages.ubuntu.com/utopic/nvidia-modprobe. > > > > After a reboot this actually worked. But I am not completely happy with > > t

Re: [Darktable-users] crop area methods

* Patrick Shanahan [11-06-14 09:21]: [...] > This is not correct as I apparently jumped the gun and used a package > prior to your change. Your change did remove the errant condition of > moving rather than resizing. But now the crop selection ratio (1:2, 3:2, > ...) only maintain the intended

Re: [Darktable-users] Darktable and Nvidia Optimus (again...)

* Hans Petter Birkeland [11-06-14 09:07]: [...] > And then I installed nvidia-modprobe, downloaded from > http://packages.ubuntu.com/utopic/nvidia-modprobe. > > After a reboot this actually worked. But I am not completely happy with > the Nvidia-Prime way of doing things, having to switch card i

Re: [Darktable-users] crop area methods

Am Donnerstag, 6. November 2014, 08:57:48 schrieb Patrick Shanahan: > * Tobias Ellinghaus [11-06-14 07:54]: > > Am Donnerstag, 6. November 2014, 12:56:23 schrieb Tobias Ellinghaus: > > > Am Mittwoch, 5. November 2014, 14:31:23 schrieb Patrick Shanahan: > > > > currently: darktable-1.5.1415208636.

Re: [Darktable-users] crop area methods

* Patrick Shanahan [11-06-14 08:59]: > * Tobias Ellinghaus [11-06-14 07:54]: > > Am Donnerstag, 6. November 2014, 12:56:23 schrieb Tobias Ellinghaus: > > > Am Mittwoch, 5. November 2014, 14:31:23 schrieb Patrick Shanahan: > > > > currently: darktable-1.5.1415208636.739107a > > > > > > > > The c

Re: [Darktable-users] Darktable and Nvidia Optimus (again...)

Hi again! I posted a question in the Nvidia developer forums and was made aware of this thread on the Darktable list, which I had not found before. I

Re: [Darktable-users] crop area methods

* Tobias Ellinghaus [11-06-14 07:54]: > Am Donnerstag, 6. November 2014, 12:56:23 schrieb Tobias Ellinghaus: > > Am Mittwoch, 5. November 2014, 14:31:23 schrieb Patrick Shanahan: > > > currently: darktable-1.5.1415208636.739107a > > > > > > The crop module presently (and for as long as I can rem

Re: [Darktable-users] crop area methods

Am Donnerstag, 6. November 2014, 12:56:23 schrieb Tobias Ellinghaus: > Am Mittwoch, 5. November 2014, 14:31:23 schrieb Patrick Shanahan: > > currently: darktable-1.5.1415208636.739107a > > > > The crop module presently (and for as long as I can remember) has a border > > area utilized or provided

Re: [Darktable-users] crop area methods

Am Mittwoch, 5. November 2014, 14:31:23 schrieb Patrick Shanahan: > currently: darktable-1.5.1415208636.739107a > > The crop module presently (and for as long as I can remember) has a border > area utilized or provided for enlarging/reducing the on-screen crop area > but the very edge of the crop

Re: [Darktable-users] How to change modules auto-applied to raw files

Compared to your search expression %14-42mm F3.5-5.6 II R% the supported list shows "f/" instead of "F". On Thu, Nov 6, 2014, at 10:19 AM, Jamie Kitson wrote: > Sorry, I only just read the last line of your email saying that you > can set it manually, but not automatically. Do you mean when you

Re: [Darktable-users] How to change modules auto-applied to raw files

Sorry, I only just read the last line of your email saying that you can set it manually, but not automatically. Do you mean when you load a raw file, or when you switch the module on? Is your camera supported as well as your lens? I do notice that your description of the lens doesn't exactly match

Re: [Darktable-users] How to change modules auto-applied to raw files

> in "global settings" go to the rightest of the four tabs - there you can set default behaviour - theoretically. Thanks, I'll have a look. > > I'm struggling to get lens correction working for my Olympus - no success yet. > > exiftool says: >> Lens Type Olympus M.Z

Re: [Darktable-users] How to adjust a former module

Yes, go to the module you want to modify in the right panel and tweak it. The processing pipe order is driven by the modules on the right, from the bottom to the top, not by the history. Thus means that vignette is being applied after all the color modules for instance, regardless of when in time y