[darktable-user] Moving darktable database to another machine

[Bruce Williams]

Hi all,
I'm new to Linux and have spent the last 3 weeks getting my head around
darktable.
So far? Blown away! I love it.
My question though is this... At the moment, I'm running on an old laptop.
When I'm ready to bite the bullet and convert my main desktop machine over
to Linux (from win 7/64), is there a way to easily copy the database
across? Obviously, moving the image folders I'd easy enough, but I'm not
sure where the database lives.
Thanks in advance!


darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org

Re: [darktable-user] Moving darktable database to another machine

[Frank J.]

Am 18.09.2016 um 09:47 schrieb Bruce Williams:
> ...
> but I'm not sure where the database lives.

Hi,
on my Ubuntu-Linux the configurations are in

~/.config/darktable/

The Database: ~/.config/darktable/library.db

The Thumbnail-Cache in
 /~/.cache/darktable/
will be build new when first looking at a picture.

It is also possible to build all thumbs with a terminal-command:

$ darktable-generate-cache

--
Frank



darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org

[darktable-user] D200 "Image Comment" and Darktable

[James]

For years, I've had my Nikon D200 insert an Image Comment in each *.xmp
file that contains a makeshift copyright symbol along with my name and
phone number.

My phone number has changed several times so I wrote a simple bash script
that uses sed to exchange each of the old phone numbers with the current
one whenever they're found. The script runs well. I view any modified *.xmp
and clearly see that the phone numbers have been updated.

Problem is, when I view those photos in Darktable, the old number/s still
appear in the Metadata Editor as though nothing's been changed.

Does Darktable store this information in another location or it is a matter
of getting it to reread or refresh?

Jim Coleman
http://www.linkedin.com/in/jamescoleman
http://www.flickr.com/photos/jecoleman/sets



darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org

Re: [darktable-user] Moving darktable database to another machine

[Patrick Shanahan]

* Frank J.  [09-18-16 04:48]:
> Am 18.09.2016 um 09:47 schrieb Bruce Williams:
> > ...
> > but I'm not sure where the database lives.
> 
> Hi,
> on my Ubuntu-Linux the configurations are in
> 
> ~/.config/darktable/
> 
> The Database: ~/.config/darktable/library.db
> 
> The Thumbnail-Cache in
>  /~/.cache/darktable/
> will be build new when first looking at a picture.
> 
> It is also possible to build all thumbs with a terminal-command:
> 
> $ darktable-generate-cache

WARNING: if the path to the photos is different on your new box, you need
to remove those images from the database and import them from their new
location.  Probably would be easier to just begin anew and import from the
new locations into a new library if you have not created styles.

I suggest you also bring with you from ~/.config/darktable/: 
  darktablerc
  keyboardrc
  keyboardrc_default

-- 
(paka)Patrick Shanahan   Plainfield, Indiana, USA  @ptilopteri
http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri
http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2
Registered Linux User #207535@ http://linuxcounter.net

darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org

Re: [darktable-user] D200 "Image Comment" and Darktable

[Patrick Shanahan]

* James  [09-18-16 05:48]:
> For years, I've had my Nikon D200 insert an Image Comment in each *.xmp
> file that contains a makeshift copyright symbol along with my name and
> phone number.
> 
> My phone number has changed several times so I wrote a simple bash script
> that uses sed to exchange each of the old phone numbers with the current
> one whenever they're found. The script runs well. I view any modified *.xmp
> and clearly see that the phone numbers have been updated.
> 
> Problem is, when I view those photos in Darktable, the old number/s still
> appear in the Metadata Editor as though nothing's been changed.
> 
> Does Darktable store this information in another location or it is a matter
> of getting it to reread or refresh?

you need to tell dt to read the altered xmp files or it will report from
the data within ~/.config/darktable/library.db, which you have not
changed.

might be simpler to edit library.db with sqlitebrowser or sqliteman and
change the comment when to alter the xmp files.

-- 
(paka)Patrick Shanahan   Plainfield, Indiana, USA  @ptilopteri
http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri
http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2
Registered Linux User #207535@ http://linuxcounter.net

darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org

Re: [darktable-user] Moving darktable database to another machine

[Bruce Williams]

OK,cool. I have no idea what the files do, but I'll keep this info handy
for when I do swap over. Thanks!

Cheers,
Bruce Williams
--
Mobile:  +61 41 250 6349

brucewilliamsphotography.com
shuttersincpodcast.com
sinelanguagepodcast.com
audio2u.com

e-mail  | Twitter  |
LinkedIn  | Facebook

--



On Sun, Sep 18, 2016 at 9:19 PM, Patrick Shanahan 
wrote:

> * Frank J.  [09-18-16 04:48]:
> > Am 18.09.2016 um 09:47 schrieb Bruce Williams:
> > > ...
> > > but I'm not sure where the database lives.
> >
> > Hi,
> > on my Ubuntu-Linux the configurations are in
> >
> > ~/.config/darktable/
> >
> > The Database: ~/.config/darktable/library.db
> >
> > The Thumbnail-Cache in
> >  /~/.cache/darktable/
> > will be build new when first looking at a picture.
> >
> > It is also possible to build all thumbs with a terminal-command:
> >
> > $ darktable-generate-cache
>
> WARNING: if the path to the photos is different on your new box, you need
> to remove those images from the database and import them from their new
> location.  Probably would be easier to just begin anew and import from the
> new locations into a new library if you have not created styles.
>
> I suggest you also bring with you from ~/.config/darktable/:
>   darktablerc
>   keyboardrc
>   keyboardrc_default
>
> --
> (paka)Patrick Shanahan   Plainfield, Indiana, USA  @ptilopteri
> http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri
> http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2
> Registered Linux User #207535@ http://linuxcounter.net
> 
> 
> darktable user mailing list
> to unsubscribe send a mail to darktable-user+unsubscribe@
> lists.darktable.org
>
>


darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org

Re: [darktable-user] Moving darktable database to another machine

[Tobias Ellinghaus]

Am Sonntag, 18. September 2016, 07:19:52 CEST schrieb Patrick Shanahan:
> * Frank J.  [09-18-16 04:48]:
> > Am 18.09.2016 um 09:47 schrieb Bruce Williams:
> > > ...
> > > but I'm not sure where the database lives.
> > 
> > Hi,
> > on my Ubuntu-Linux the configurations are in
> > 
> > ~/.config/darktable/
> > 
> > The Database: ~/.config/darktable/library.db
> > 
> > The Thumbnail-Cache in
> > 
> >  /~/.cache/darktable/
> > 
> > will be build new when first looking at a picture.
> > 
> > It is also possible to build all thumbs with a terminal-command:
> > 
> > $ darktable-generate-cache
> 
> WARNING: if the path to the photos is different on your new box, you need
> to remove those images from the database and import them from their new
> location.  Probably would be easier to just begin anew and import from the
> new locations into a new library if you have not created styles.

If the basic folder structure is the same and filenames didn't change you just 
have to point darktable to the new base by using the "folder" mode of the 
collect module on lighttable. You will see the folder being struck through. 
Right click and select the correct folder.

> I suggest you also bring with you from ~/.config/darktable/:
>   darktablerc
>   keyboardrc
>   keyboardrc_default

I'd just copy the whole ~/.config/darktable/ folder. Just to be sure.

Tobias

signature.asc
Description: This is a digitally signed message part.

Re: [darktable-user] D200 "Image Comment" and Darktable

[Tobias Ellinghaus]

Am Sonntag, 18. September 2016, 05:45:27 CEST schrieb James:
> For years, I've had my Nikon D200 insert an Image Comment in each *.xmp
> file that contains a makeshift copyright symbol along with my name and
> phone number.
> 
> My phone number has changed several times so I wrote a simple bash script
> that uses sed to exchange each of the old phone numbers with the current
> one whenever they're found. The script runs well. I view any modified *.xmp
> and clearly see that the phone numbers have been updated.
> 
> Problem is, when I view those photos in Darktable, the old number/s still
> appear in the Metadata Editor as though nothing's been changed.
> 
> Does Darktable store this information in another location or it is a matter
> of getting it to reread or refresh?

darktable caches these things in a database. Try enabling "look for updated 
xmp files in startup" in the core tab of the preferences. Theoretically that 
should make darktable notice when XMP files changed behind its back and offer 
to re-read them.

> Jim Coleman
> http://www.linkedin.com/in/jamescoleman
> http://www.flickr.com/photos/jecoleman/sets
> 
> 
> 
> darktable user mailing list
> to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org



signature.asc
Description: This is a digitally signed message part.

Re: [darktable-user] D200 "Image Comment" and Darktable

[James]

Thanks.

After enabling and restarting Darktable, I'm presented with a long list of
nef and jpg files. There's a 'select all' button and options to reload
selected xmp files and over write selected xmps.

Aside from the fact that there are no xmps in the list, Darktable crashes
if I 'select all' and chose the reload option.

James Coleman
http://www.linkedin.com/in/jamescoleman
http://www.flickr.com/photos/jecoleman/sets

On Sep 18, 2016 11:21 AM, "Tobias Ellinghaus"  wrote:

> Am Sonntag, 18. September 2016, 05:45:27 CEST schrieb James:
> > For years, I've had my Nikon D200 insert an Image Comment in each *.xmp
> > file that contains a makeshift copyright symbol along with my name and
> > phone number.
> >
> > My phone number has changed several times so I wrote a simple bash script
> > that uses sed to exchange each of the old phone numbers with the current
> > one whenever they're found. The script runs well. I view any modified
> *.xmp
> > and clearly see that the phone numbers have been updated.
> >
> > Problem is, when I view those photos in Darktable, the old number/s still
> > appear in the Metadata Editor as though nothing's been changed.
> >
> > Does Darktable store this information in another location or it is a
> matter
> > of getting it to reread or refresh?
>
> darktable caches these things in a database. Try enabling "look for updated
> xmp files in startup" in the core tab of the preferences. Theoretically
> that
> should make darktable notice when XMP files changed behind its back and
> offer
> to re-read them.
>
> > Jim Coleman
> > http://www.linkedin.com/in/jamescoleman
> > http://www.flickr.com/photos/jecoleman/sets
> > 
> >
> > 
> 
> > darktable user mailing list
> > to unsubscribe send a mail to darktable-user+unsubscribe@
> lists.darktable.org
>
>


darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org

Re: [darktable-user] D200 "Image Comment" and Darktable

[Tobias Ellinghaus]

Am Sonntag, 18. September 2016, 11:42:57 CEST schrieb James:
> Thanks.
> 
> After enabling and restarting Darktable, I'm presented with a long list of
> nef and jpg files. There's a 'select all' button and options to reload
> selected xmp files and over write selected xmps.
> 
> Aside from the fact that there are no xmps in the list,

Maybe we should show the XMP filename, too.

> Darktable crashes
> if I 'select all' and chose the reload option.

Could you provide a backtrace? If you are lucky darktable might have written 
one to /tmp/darktable_bt_*.txt.

> James Coleman
> http://www.linkedin.com/in/jamescoleman
> http://www.flickr.com/photos/jecoleman/sets
> 
> On Sep 18, 2016 11:21 AM, "Tobias Ellinghaus"  wrote:
> > Am Sonntag, 18. September 2016, 05:45:27 CEST schrieb James:
> > > For years, I've had my Nikon D200 insert an Image Comment in each *.xmp
> > > file that contains a makeshift copyright symbol along with my name and
> > > phone number.
> > > 
> > > My phone number has changed several times so I wrote a simple bash
> > > script
> > > that uses sed to exchange each of the old phone numbers with the current
> > > one whenever they're found. The script runs well. I view any modified
> > 
> > *.xmp
> > 
> > > and clearly see that the phone numbers have been updated.
> > > 
> > > Problem is, when I view those photos in Darktable, the old number/s
> > > still
> > > appear in the Metadata Editor as though nothing's been changed.
> > > 
> > > Does Darktable store this information in another location or it is a
> > 
> > matter
> > 
> > > of getting it to reread or refresh?
> > 
> > darktable caches these things in a database. Try enabling "look for
> > updated
> > xmp files in startup" in the core tab of the preferences. Theoretically
> > that
> > should make darktable notice when XMP files changed behind its back and
> > offer
> > to re-read them.
> > 
> > > Jim Coleman
> > > http://www.linkedin.com/in/jamescoleman
> > > http://www.flickr.com/photos/jecoleman/sets
> > > 
> > > 
> > > 
> > 
> > 
> > 
> > > darktable user mailing list
> > > to unsubscribe send a mail to darktable-user+unsubscribe@
> > 
> > lists.darktable.org
> 
> 
> darktable user mailing list
> to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org



signature.asc
Description: This is a digitally signed message part.

Re: [darktable-user] D200 "Image Comment" and Darktable

[James]

I can, indeed. There were several.

/tmp ->
 01:32 PM Sun Sep 18$ cat darktable_bt_0ZXSNY.txt
this is darktable 2.1.pre+git1546.07ed916-1.1 reporting a segfault:

#0  0x7f2547033469 in waitpid () at /lib64/libpthread.so.0
#1  0x7f25472cbda0 in  () at /usr/bin/../lib64/darktable/libdarktable.so
#2  0x7f2546cb2120 in  () at /lib64/libc.so.6
#3  0x7f2541f0ae06 in pugi::xml_node_iterator::operator++() () at
/usr/lib64/libpugixml.so.1
#4  0x7f2541f0ae22 in pugi::xml_node_iterator::operator++(int) () at
/usr/lib64/libpugixml.so.1
#5  0x7f25472df2de in dt_exif_xmp_read () at
/usr/bin/../lib64/darktable/libdarktable.so
#6  0x7f25472ecef8 in dt_history_load_and_apply () at
/usr/bin/../lib64/darktable/libdarktable.so
#7  0x7f2547325188 in  () at /usr/bin/../lib64/darktable/libdarktable.so
#8  0x7f2544eaf0a7 in  () at /usr/lib64/libgobject-2.0.so.0
#9  0x7f2544ec73d8 in g_signal_emit_valist () at
/usr/lib64/libgobject-2.0.so.0
#10 0x7f2544ec8022 in g_signal_emit () at /usr/lib64/libgobject-2.0.so.0
#11 0x7f25461cca7d in  () at /usr/lib64/libgtk-3.so.0
#12 0x7f25461ccac3 in  () at /usr/lib64/libgtk-3.so.0
#13 0x7f2544eaee78 in g_closure_invoke () at
/usr/lib64/libgobject-2.0.so.0
#14 0x7f2544ebf8b7 in  () at /usr/lib64/libgobject-2.0.so.0
#15 0x7f2544ec7d68 in g_signal_emit_valist () at
/usr/lib64/libgobject-2.0.so.0
#16 0x7f2544ec8022 in g_signal_emit () at /usr/lib64/libgobject-2.0.so.0
#17 0x7f25461cab10 in  () at /usr/lib64/libgtk-3.so.0
#18 0x7f253cdd7cd6 in ffi_call_unix64 () at /usr/lib64/libffi.so.4
#19 0x7f253cdd7729 in ffi_call () at /usr/lib64/libffi.so.4
#20 0x7f2544eafb15 in g_cclosure_marshal_generic_va () at
/usr/lib64/libgobject-2.0.so.0
#21 0x7f2544eaf0a7 in  () at /usr/lib64/libgobject-2.0.so.0
#22 0x7f2544ec73d8 in g_signal_emit_valist () at
/usr/lib64/libgobject-2.0.so.0
#23 0x7f2544ec8022 in g_signal_emit () at /usr/lib64/libgobject-2.0.so.0
#24 0x7f254626abbe in  () at /usr/lib64/libgtk-3.so.0
#25 0x7f2544eb1cd0 in g_cclosure_marshal_VOID__BOXEDv () at
/usr/lib64/libgobject-2.0.so.0
#26 0x7f2544eaf0a7 in  () at /usr/lib64/libgobject-2.0.so.0
#27 0x7f2544ec73d8 in g_signal_emit_valist () at
/usr/lib64/libgobject-2.0.so.0
#28 0x7f2544ec8022 in g_signal_emit () at /usr/lib64/libgobject-2.0.so.0
#29 0x7f254626829e in  () at /usr/lib64/libgtk-3.so.0
#30 0x7f2546269598 in  () at /usr/lib64/libgtk-3.so.0
#31 0x7f254626c017 in  () at /usr/lib64/libgtk-3.so.0
#32 0x7f2546240bbb in gtk_event_controller_handle_event () at
/usr/lib64/libgtk-3.so.0
#33 0x7f25463cf7fd in  () at /usr/lib64/libgtk-3.so.0
#34 0x7f25462ac45e in  () at /usr/lib64/libgtk-3.so.0
#35 0x7f2544eaf0a7 in  () at /usr/lib64/libgobject-2.0.so.0
#36 0x7f2544ec73d8 in g_signal_emit_valist () at
/usr/lib64/libgobject-2.0.so.0
#37 0x7f2544ec8022 in g_signal_emit () at /usr/lib64/libgobject-2.0.so.0
#38 0x7f25463d2e8c in  () at /usr/lib64/libgtk-3.so.0
#39 0x7f25462a9f7c in  () at /usr/lib64/libgtk-3.so.0
#40 0x7f25462ab9c7 in gtk_main_do_event () at /usr/lib64/libgtk-3.so.0
#41 0x7f2545e53e02 in  () at /usr/lib64/libgdk-3.so.0
#42 0x7f25469baa04 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#43 0x7f25469bac48 in  () at /usr/lib64/libglib-2.0.so.0
#44 0x7f25469baf0a in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0
#45 0x7f25462aacf5 in gtk_main () at /usr/lib64/libgtk-3.so.0
#46 0x7f25473a7b9b in dt_gui_gtk_run () at
/usr/bin/../lib64/darktable/libdarktable.so
#47 0x004008ba in main ()

Thread 12 (Thread 0x7f253780a700 (LWP 17939)):
#0  0x7f254703003f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f2547326e06 in  () at /usr/bin/../lib64/darktable/libdarktable.so
#2  0x7f254702c0a4 in start_thread () at /lib64/libpthread.so.0
#3  0x7f2546d61cbd in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7f2537009700 (LWP 17940)):
#0  0x7f254703003f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f2547326e06 in  () at /usr/bin/../lib64/darktable/libdarktable.so
#2  0x7f254702c0a4 in start_thread () at /lib64/libpthread.so.0
#3  0x7f2546d61cbd in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7f2536808700 (LWP 17941)):
#0  0x7f2546d33d8d in nanosleep () at /lib64/libc.so.6
#1  0x7f2546d33c24 in sleep () at /lib64/libc.so.6
#2  0x7f2547325fca in  () at /usr/bin/../lib64/darktable/libdarktable.so
#3  0x7f254702c0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f2546d61cbd in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7f2536007700 (LWP 17942)):
#0  0x7f254703003f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f254732638e in  () at /usr/bin/../lib64/darktable/libdarktable.so
#2  0x7f254702c0a4 in start_thread () at /lib64/libpthread.so.0
#3  0x7f2546d61cbd in clone () at /lib64/libc.so.6

Thread 8 (T

[darktable-user] Bug report

[Henkka]

In latest MacOS version 2.0.6, if I try to type value, forex. into 
exposure module, it does not work. It does not work on any module.


Tested on El Capitan 10.11.6



darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org

Re: [darktable-user] D200 "Image Comment" and Darktable

[Tobias Ellinghaus]

Am Sonntag, 18. September 2016, 13:32:08 CEST schrieb James:
> I can, indeed. There were several.

Thanks. It seems your version of darktable is stripped (lacking debug 
information). Could you try to install those and try to crash darktable again, 
then send the newly created backtrace?

> /tmp ->
>  01:32 PM Sun Sep 18$ cat darktable_bt_0ZXSNY.txt
> this is darktable 2.1.pre+git1546.07ed916-1.1 reporting a segfault:
> 
> #0  0x7f2547033469 in waitpid () at /lib64/libpthread.so.0
> #1  0x7f25472cbda0 in  () at /usr/bin/../lib64/darktable/libdarktable.so
> #2  0x7f2546cb2120 in  () at /lib64/libc.so.6 #3
>  0x7f2541f0ae06 in pugi::xml_node_iterator::operator++() () at
> /usr/lib64/libpugixml.so.1
> #4  0x7f2541f0ae22 in pugi::xml_node_iterator::operator++(int) () at
> /usr/lib64/libpugixml.so.1
> #5  0x7f25472df2de in dt_exif_xmp_read () at
> /usr/bin/../lib64/darktable/libdarktable.so

Without being sure where the crash is happening this might indicate a broken 
XMP file.

[...]

Tobias

PS: I am subscribed to the list, just answering there is enough. No need for 
personal copies.

signature.asc
Description: This is a digitally signed message part.

Re: [darktable-user] Bug report

[Tobias Ellinghaus]

Am Sonntag, 18. September 2016, 20:39:00 CEST schrieb Henkka:
> In latest MacOS version 2.0.6, if I try to type value, forex. into
> exposure module, it does not work. It does not work on any module.
> 
> Tested on El Capitan 10.11.6

That is a known problem with the OSX packages. From what I heard it might help 
to move the mouse out of the popup and back in or something like that.

Tobias

signature.asc
Description: This is a digitally signed message part.

Re: [darktable-user] open CL 2.0.6

[Ulrich Pegelow]

Hi,

the issue should now be fixed in master and in darktable-2.0.x branch.

Ulrich

darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org

Re: [darktable-user] Bug report

[Rafa García]

There's a problem with GTK+ in Mac OS X that broke almost all the UI in Mac
OS X.

You can work by changing values with the mouse not key numbers (be careful
it changes image ratings instead).

If you can work all with mouse you can do it as workaround else latest
version working was Darktable 2.0.4.


Regards

PS: I'm going to compile dartable (master branch) during this week and try
to find some help/fix with GTK+ team via IRC.


2016-09-18 20:52 GMT+02:00 Tobias Ellinghaus :

> Am Sonntag, 18. September 2016, 20:39:00 CEST schrieb Henkka:
> > In latest MacOS version 2.0.6, if I try to type value, forex. into
> > exposure module, it does not work. It does not work on any module.
> >
> > Tested on El Capitan 10.11.6
>
> That is a known problem with the OSX packages. From what I heard it might
> help
> to move the mouse out of the popup and back in or something like that.
>
> Tobias


darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org

[darktable-user] local contrast v contrast brightness saturation v clarity/equalizer

[darktable]

Hi,

I'm on DT 2.0.6.

What the difference between:

* local contrast
* contrast brightness saturation
* clarity/equalizer

-- 
sknahT

vyS

darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org

Re: [darktable-user] local contrast v contrast brightness saturation v clarity/equalizer

[KOVÁCS István]

Hi,

Contrast from contrast/brightness/saturation is global contrast, a kind of
tone-curve adjustment (steeper in the midtones range, flatter in highlights
and shadows). Local contrast boosts differences from a local average (a
grey spot on black background becomes brighter; the same grey spot on white
background becomes darker). Equalizer is a super-adjustable version on
local contrast, where you can set the boost for all detail levels at once.
Please read the manual.

Kofa

On 19 Sep 2016 05:38,  wrote:

Hi,

I'm on DT 2.0.6.

What the difference between:

* local contrast
* contrast brightness saturation
* clarity/equalizer

--
sknahT

vyS

darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org


darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org