Re: [darktable-user] Scanning and EXIF information

2020-11-15 Thread Remco Viëtor
On dimanche 15 novembre 2020 21:52:02 CET Andrew Greig wrote:
> Thanks Stephane,
> 
> I have taken your warning on messing with RAW files on board. I can
> produce a text file with my information and store it with the RAW files.
> Is it possible to change the data exported to a jpg or png to reflect
> the settings for the images? And leave the RAW files untouched?

You could add the scanning info as a caption in darktable, it won't be stored 
in the raw file, but darktable will keep it in the database (and sidecar), and 
export it to the jpg/png.

Remco



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



[darktable-user] Ubuntu 20.04, OpenCL, DT3.2.1, Radeon HD5400

2020-11-15 Thread Šarūnas
On 11/15/20 3:28 PM, GianLuca Sarto wrote:
> thanks, Šarūnas,
> 
> I have two Darktable systems, based on Lenovo TS140, one with AMD, the
> other with Nvidia Quadro 400.
> Neither of the two manage OpenCL..
> 
> 0.039390 [opencl_init] found opencl runtime library 'libOpenCL'
> 0.039412 [opencl_init] opencl library 'libOpenCL' found on your system
> and loaded
> 0.042560 [opencl_init] found 1 platform
> 0.042582 [opencl_init] found 1 device
> 0.042727 [opencl_init] device 0 `Quadro 400' has sm_20 support.
> 0.042778 [opencl_init] discarding device 0 `Quadro 400' due to
> insufficient global memory (511MB).

Too small video memory for useful OpenCL.

> I would like to upgrade one of the two systems to a 4K display, so was
> already decided to purchase a new video card.
> 
> Is there a tested solution that works out of the box, or a list of DT
> OpenCL compliant cards for Linux?

I don't know whether such a list exists[1]. The more memory and more
parallel processing units (“GPU cores”) a video card has, the more
useful it will be for OpenCL processing. The useful minimum these days
might be 2GB, but I would look for 4GB and more.

“Out of the box” would probably only happen if you buy a computer from a
company that sells them configured with Linux. Whether you install AMD
or Nvidia GPU, there will be additional steps.

In case of AMD, Linux kernel already supports AMD cards with the open
source ‘amdgpu’ module, so that part will be “out of the box”. OpenCL
support will have to come from either 1) open source ROCm or 2)
proprietary AMDGPU-PRO.

In case of Nvidia, Linux kernel's ‘nouveau’ module will need to be
replaced with the proprietary ‘nv’ one from Nvidia, plus OpenCL part
from the same Nvidia. Ubuntu has them in standard repositories. One can
also use Nvidia repositories for perhaps slightly newer software.

Intel appears to have a completely open source system, but usable GPUs
are still to come.

-- 
Šarūnas Burdulis
math.dartmouth.edu/~sarunas

· https://useplaintext.email ·





OpenPGP_signature
Description: OpenPGP digital signature


Re: [darktable-user] Scanning and EXIF information

2020-11-15 Thread Andrew Greig

Thanks Stephane,

I have taken your warning on messing with RAW files on board. I can 
produce a text file with my information and store it with the RAW files. 
Is it possible to change the data exported to a jpg or png to reflect 
the settings for the images? And leave the RAW files untouched?


Gratefully

Andrew Greig

On 16/11/20 2:02 am, Stéphane Gourichon wrote:

Hi Greig,

You basically want to replace some EXIF information present in the raw 
file.


A number of people (including me) would strongly avoid ever modifying 
a raw file. These are full of dragons. First I would make a backup of 
the raw files for fear or any change triggering some wrong checksum 
somewhere and making other software (or the camera itself) refuse to 
do anything with it, claiming corruption. If any software claims to be 
able to perform changes, I would open a binary comparison of 
before/after to check what is the actual change. And keep the original 
raw files in a backup, indefinitely.



The situation is somehow similar to a more common one : camera clock 
was off and you need right times in EXIF after the facts. The typical 
case being: at some events (wedding, etc) several cameras were used, 
clock mismatch as always by minutes hours or days, making a mess of 
timeline order. Fortunately the case of adjusting time is somehow 
covered by darktable, which copies EXIF DateTimeOriginal to the XMP 
sidecar, as XML attribute of rdf:Description XML element like this : 
exif:DateTimeOriginal="2020:11:11 09:54:44" . Changing this line in 
the XMP while darktable is not running was enough for me to get 
correct datetime in Darktable and exported EXIF data, yay!


I checked the source code (current git master), and alas this is 
specific to DateTimeOriginal, darktable current code does not consider 
overriding EXIF metadata from the XMP file, other than DateTimeOriginal.


Would your need happen to me, I would either just ignore the problem 
and live with it, or modify darktable source code to save that data to 
XMP and read it back, then offer a Pull Request to the darktable team.


It may be possible to manually edit EXIF values in the database, but 
I'm not sure this can even work, and furthermore the current design of 
the database is fragile with respect to the locations of raw files. 
More concretely, whenever the raw file is moved, or happen to be 
stored on an external drive that is mounted at a different place, you 
would probably lose your customization. With the XMP sidecar, 
darktable would load it again in those cases.



Addendum: to handle comfortably the "several cameras with random time 
offsets take pictures of same events over a time range" case, I wrote 
a year ago a script to automatically adjust batches of pictures. It 
saved the day several times for me and I am considering publishing it 
as open-source. Anyone who reads this (even years after) please 
consider telling me if you're interested.



-- Stéphane



Le 15/11/2020 à 02.55, Andrew Greig a écrit :

Hi All,

I shot and developed a roll of B+W film, and I will scan it using my 
Canon EOS 5D iv with the EF 100mm f2.8 Macro lens. As I was shooting 
the roll of film I maintained a notebook where I wrote down the 
settings, what is the best way to substitute the info in the 
resulting .CR2 files with the info from my notes? I am really looking 
forward to loading these into Darktable/Negadoctor.


Thanks
Andrew Greig
 


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

Re: [darktable-user] Ubuntu 20.04, OpenCL, DT3.2.1, Radeon HD5400

2020-11-15 Thread GianLuca Sarto

thanks, Šarūnas,

I have two Darktable systems, based on Lenovo TS140, one with AMD, the 
other with Nvidia Quadro 400.

Neither of the two manage OpenCL..

0.039390 [opencl_init] found opencl runtime library 'libOpenCL'
0.039412 [opencl_init] opencl library 'libOpenCL' found on your system 
and loaded

0.042560 [opencl_init] found 1 platform
0.042582 [opencl_init] found 1 device
0.042727 [opencl_init] device 0 `Quadro 400' has sm_20 support.
0.042778 [opencl_init] discarding device 0 `Quadro 400' due to 
insufficient global memory (511MB).

0.042784 [opencl_init] no suitable devices found.
0.042788 [opencl_init] FINALLY: opencl is NOT AVAILABLE on this system.

I would like to upgrade one of the two systems to a 4K display, so was 
already decided to purchase a new video card.


Is there a tested solution that works out of the box, or a list of DT 
OpenCL compliant cards for Linux?




On 15/11/20 15:34, Šarūnas wrote:

On 11/14/20 3:41 PM, GianLuca Sarto wrote:

Hello All,

DT 3.2.1 here, running on Ubuntu 20.04, Radeon HD5400.

OpenCL should be working, however DT complains "could not get platforms"
(see below).

Support for Radeon HD5xxx may have ended with fglrx (Ubuntu 16.04?).

You may check what is currently supported,
by proprietary AMDGPU-PRO:
https://www.amd.com/en/support

by open source ROCm:
https://github.com/RadeonOpenCompute/ROCm#Hardware-and-Software-Support




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



Re: [darktable-user] Presettings

2020-11-15 Thread David Vincent-Jones
I am slowly picking mmy way through many of my images and reprocessing 
based on the-filmic-way . my finding was that there was often more 
elements than the basecurve that needed to be changed so I now simply 
make a duplicate and start-over with a number of presets. The big 
advantage of this duplication is that it does in the end allow me to 
really quantify the results of the new processing ... in many instances 
the 'look' is quite different and I elect to keep both versions.


David

On 2020-11-15 12:14 p.m., Terry Pinfold wrote:

Hi Peter,
   Jan's solution of creating a style would work. Another solution would be to set 
the preferences for "Scene referred"  processing and in the duplicate manager 
of lighttable create a 'virgin copy'. You can then delete the base curve version if it is 
no longer needed. Keep in mind that duplicate manager does not create another image but 
rather just another xmp file with processing instructions for scene referred.



From: Jan Ingwer Baer 
Sent: Monday, 16 November 2020 4:19 AM
To: darktable-user@lists.darktable.org 
Subject: Re: [darktable-user] Presettings

It would be more simple do to create a style that disable the basecurve
and enable filmic:

1. Open one of the pictures in the darkroom
2. disable basecurve
3. enable filmic
4. go back to lighttable
5. save style with (only) basecurve and filmic checked

Now you can apply the saved style to every picture where you want change
'display referred' to 'scene referred'

regards
Jan

On 15-Nov-20 16:49, Peter Schlaufer wrote:

Hello to all

I need some help:
A few months ago, I imported some 25'000 pictures in dt 3.2 with the setting "display 
referred" meaning that the basecurve is autoapplied. I found out now that most of these 
pictures have far to dark dark shadows, sometimes to an extreme extent. Some of them I reedited 
with filmic with much better results which as far as I am aware that would be the setting 
"scene referred".
Question:
Is it now possible to delete these pictures and reimport them with the setting 
"scene referred“, will the editing be overwritten when newly importing them?

Kind regards
Peter Schlaufer
Landenbergstrasse 19
CH-6005 Luzern
pe...@schlaufer.ch 







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



University of Tasmania Electronic Communications Policy (December, 2014).
This email is confidential, and is for the intended recipient only. Access, 
disclosure, copying, distribution, or reliance on any of it by anyone outside 
the intended recipient organisation is prohibited and may be a criminal 
offence. Please delete if obtained in error and email confirmation to the 
sender. The views expressed in this email are not necessarily the views of the 
University of Tasmania, unless clearly intended otherwise.


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

Re: [darktable-user] Presettings

2020-11-15 Thread Terry Pinfold
Hi Peter,
  Jan's solution of creating a style would work. Another solution would be 
to set the preferences for "Scene referred"  processing and in the duplicate 
manager of lighttable create a 'virgin copy'. You can then delete the base 
curve version if it is no longer needed. Keep in mind that duplicate manager 
does not create another image but rather just another xmp file with processing 
instructions for scene referred.



From: Jan Ingwer Baer 
Sent: Monday, 16 November 2020 4:19 AM
To: darktable-user@lists.darktable.org 
Subject: Re: [darktable-user] Presettings

It would be more simple do to create a style that disable the basecurve
and enable filmic:

1. Open one of the pictures in the darkroom
2. disable basecurve
3. enable filmic
4. go back to lighttable
5. save style with (only) basecurve and filmic checked

Now you can apply the saved style to every picture where you want change
'display referred' to 'scene referred'

regards
Jan

On 15-Nov-20 16:49, Peter Schlaufer wrote:
> Hello to all
>
> I need some help:
> A few months ago, I imported some 25'000 pictures in dt 3.2 with the setting 
> "display referred" meaning that the basecurve is autoapplied. I found out now 
> that most of these pictures have far to dark dark shadows, sometimes to an 
> extreme extent. Some of them I reedited with filmic with much better results 
> which as far as I am aware that would be the setting "scene referred".
> Question:
> Is it now possible to delete these pictures and reimport them with the 
> setting "scene referred“, will the editing be overwritten when newly 
> importing them?
>
> Kind regards
> Peter Schlaufer
> Landenbergstrasse 19
> CH-6005 Luzern
> pe...@schlaufer.ch 
>
>
>
>
>
>
> 
> 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



University of Tasmania Electronic Communications Policy (December, 2014).
This email is confidential, and is for the intended recipient only. Access, 
disclosure, copying, distribution, or reliance on any of it by anyone outside 
the intended recipient organisation is prohibited and may be a criminal 
offence. Please delete if obtained in error and email confirmation to the 
sender. The views expressed in this email are not necessarily the views of the 
University of Tasmania, unless clearly intended otherwise.


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



[darktable-user] Lens correction not working

2020-11-15 Thread t_drei

Hi,

Lens correction doesn't work anymore for my Sony RX10M4.

In earlier versions of darktable, the camera was recognized and lens
correction (geometry) worked just fine. Now, there's no recognition of
the camera, and I cannot choose it from the list (my other two cameras
are still there, e.g. Sony RX100M3, but the RX 10s are missing).

I use darktable 3.2.1 / Ubuntu; as I'm only a happy user of darktable
(no IT expert), I didn't change any part of the installation.

Any suggestion what I could do?

Best regards, Regina



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



Re: [darktable-user] Scanning and EXIF information

2020-11-15 Thread William Ferguson
Another way to handle the scans is import them into darktable, then update
the EXIF data in the database.  There is a lua script to adjust or set time
for an image or set of images called, appropriately enough, adjust_time.
It's located at https://github.com/wpferguson/extra-dt-lua-scripts.

On Sun, Nov 15, 2020 at 10:10 AM Stéphane Gourichon <
stephane_darkta...@gourichon.org> wrote:

> Hi Greig,
>
> You basically want to replace some EXIF information present in the raw
> file.
>
> A number of people (including me) would strongly avoid ever modifying a
> raw file. These are full of dragons. First I would make a backup of the
> raw files for fear or any change triggering some wrong checksum
> somewhere and making other software (or the camera itself) refuse to do
> anything with it, claiming corruption. If any software claims to be able
> to perform changes, I would open a binary comparison of before/after to
> check what is the actual change. And keep the original raw files in a
> backup, indefinitely.
>
>
> The situation is somehow similar to a more common one : camera clock was
> off and you need right times in EXIF after the facts. The typical case
> being: at some events (wedding, etc) several cameras were used, clock
> mismatch as always by minutes hours or days, making a mess of timeline
> order. Fortunately the case of adjusting time is somehow covered by
> darktable, which copies EXIF DateTimeOriginal to the XMP sidecar, as XML
> attribute of rdf:Description XML element like this :
> exif:DateTimeOriginal="2020:11:11 09:54:44" . Changing this line in the
> XMP while darktable is not running was enough for me to get correct
> datetime in Darktable and exported EXIF data, yay!
>
> I checked the source code (current git master), and alas this is
> specific to DateTimeOriginal, darktable current code does not consider
> overriding EXIF metadata from the XMP file, other than DateTimeOriginal.
>
> Would your need happen to me, I would either just ignore the problem and
> live with it, or modify darktable source code to save that data to XMP
> and read it back, then offer a Pull Request to the darktable team.
>
> It may be possible to manually edit EXIF values in the database, but I'm
> not sure this can even work, and furthermore the current design of the
> database is fragile with respect to the locations of raw files. More
> concretely, whenever the raw file is moved, or happen to be stored on an
> external drive that is mounted at a different place, you would probably
> lose your customization. With the XMP sidecar, darktable would load it
> again in those cases.
>
>
> Addendum: to handle comfortably the "several cameras with random time
> offsets take pictures of same events over a time range" case, I wrote a
> year ago a script to automatically adjust batches of pictures. It saved
> the day several times for me and I am considering publishing it as
> open-source. Anyone who reads this (even years after) please consider
> telling me if you're interested.
>
>
> -- Stéphane
>
>
>
> Le 15/11/2020 à 02.55, Andrew Greig a écrit :
> > Hi All,
> >
> > I shot and developed a roll of B+W film, and I will scan it using my
> > Canon EOS 5D iv with the EF 100mm f2.8 Macro lens. As I was shooting
> > the roll of film I maintained a notebook where I wrote down the
> > settings, what is the best way to substitute the info in the resulting
> > .CR2 files with the info from my notes? I am really looking forward to
> > loading these into Darktable/Negadoctor.
> >
> > Thanks
> > Andrew Greig
> >
> 
>
> >
> > darktable user mailing list
> > to unsubscribe send a mail to
> > darktable-user+unsubscr...@lists.darktable.org
> >
> --
> Stéphane Gourichon
>
>
> 
> 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



Re: [darktable-user] Ubuntu 20.04, OpenCL, DT3.2.1, Radeon HD5400

2020-11-15 Thread Šarūnas
On 11/14/20 3:41 PM, GianLuca Sarto wrote:
> Hello All,
> 
> DT 3.2.1 here, running on Ubuntu 20.04, Radeon HD5400.
> 
> OpenCL should be working, however DT complains "could not get platforms"
> (see below).

Support for Radeon HD5xxx may have ended with fglrx (Ubuntu 16.04?).

You may check what is currently supported,
by proprietary AMDGPU-PRO:
https://www.amd.com/en/support

by open source ROCm:
https://github.com/RadeonOpenCompute/ROCm#Hardware-and-Software-Support

-- 
Šarūnas Burdulis
math.dartmouth.edu/~sarunas

· https://useplaintext.email ·



OpenPGP_signature
Description: OpenPGP digital signature


Re: [darktable-user] Presettings

2020-11-15 Thread Jan Ingwer Baer

It would be more simple do to create a style that disable the basecurve
and enable filmic:

1. Open one of the pictures in the darkroom
2. disable basecurve
3. enable filmic
4. go back to lighttable
5. save style with (only) basecurve and filmic checked

Now you can apply the saved style to every picture where you want change
'display referred' to 'scene referred'

regards
Jan

On 15-Nov-20 16:49, Peter Schlaufer wrote:

Hello to all

I need some help:
A few months ago, I imported some 25'000 pictures in dt 3.2 with the setting "display 
referred" meaning that the basecurve is autoapplied. I found out now that most of these 
pictures have far to dark dark shadows, sometimes to an extreme extent. Some of them I reedited 
with filmic with much better results which as far as I am aware that would be the setting 
"scene referred".
Question:
Is it now possible to delete these pictures and reimport them with the setting 
"scene referred“, will the editing be overwritten when newly importing them?

Kind regards
Peter Schlaufer
Landenbergstrasse 19
CH-6005 Luzern
pe...@schlaufer.ch 







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



[darktable-user] IPTC Metadata Export

2020-11-15 Thread Ralf Kerkhoff

Hi,
just wondering how to manage this:
I would like to export the Image creation time within the IPTC section 
of the Metadata.

Darktable provides the "Tag":
Iptc.Application2.TimeCreated
in the Export Metadata section.
But what would be the correct formula for this?
Any hints are welcome
Ralf
--

Mit freundlichen Grüßen
Ralf Kerkhoff

https://www.ralf-kerkhoff.de 
https://www.tiere-beschuetzen.de 



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

[darktable-user] Presettings

2020-11-15 Thread Peter Schlaufer
Hello to all

I need some help:
A few months ago, I imported some 25'000 pictures in dt 3.2 with the setting 
"display referred" meaning that the basecurve is autoapplied. I found out now 
that most of these pictures have far to dark dark shadows, sometimes to an 
extreme extent. Some of them I reedited with filmic with much better results 
which as far as I am aware that would be the setting "scene referred".
Question:
Is it now possible to delete these pictures and reimport them with the setting 
"scene referred“, will the editing be overwritten when newly importing them?

Kind regards
Peter Schlaufer
Landenbergstrasse 19
CH-6005 Luzern
pe...@schlaufer.ch 







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



Re: [darktable-user] Scanning and EXIF information

2020-11-15 Thread Stéphane Gourichon

Hi Greig,

You basically want to replace some EXIF information present in the raw file.

A number of people (including me) would strongly avoid ever modifying a 
raw file. These are full of dragons. First I would make a backup of the 
raw files for fear or any change triggering some wrong checksum 
somewhere and making other software (or the camera itself) refuse to do 
anything with it, claiming corruption. If any software claims to be able 
to perform changes, I would open a binary comparison of before/after to 
check what is the actual change. And keep the original raw files in a 
backup, indefinitely.



The situation is somehow similar to a more common one : camera clock was 
off and you need right times in EXIF after the facts. The typical case 
being: at some events (wedding, etc) several cameras were used, clock 
mismatch as always by minutes hours or days, making a mess of timeline 
order. Fortunately the case of adjusting time is somehow covered by 
darktable, which copies EXIF DateTimeOriginal to the XMP sidecar, as XML 
attribute of rdf:Description XML element like this : 
exif:DateTimeOriginal="2020:11:11 09:54:44" . Changing this line in the 
XMP while darktable is not running was enough for me to get correct 
datetime in Darktable and exported EXIF data, yay!


I checked the source code (current git master), and alas this is 
specific to DateTimeOriginal, darktable current code does not consider 
overriding EXIF metadata from the XMP file, other than DateTimeOriginal.


Would your need happen to me, I would either just ignore the problem and 
live with it, or modify darktable source code to save that data to XMP 
and read it back, then offer a Pull Request to the darktable team.


It may be possible to manually edit EXIF values in the database, but I'm 
not sure this can even work, and furthermore the current design of the 
database is fragile with respect to the locations of raw files. More 
concretely, whenever the raw file is moved, or happen to be stored on an 
external drive that is mounted at a different place, you would probably 
lose your customization. With the XMP sidecar, darktable would load it 
again in those cases.



Addendum: to handle comfortably the "several cameras with random time 
offsets take pictures of same events over a time range" case, I wrote a 
year ago a script to automatically adjust batches of pictures. It saved 
the day several times for me and I am considering publishing it as 
open-source. Anyone who reads this (even years after) please consider 
telling me if you're interested.



-- Stéphane



Le 15/11/2020 à 02.55, Andrew Greig a écrit :

Hi All,

I shot and developed a roll of B+W film, and I will scan it using my 
Canon EOS 5D iv with the EF 100mm f2.8 Macro lens. As I was shooting 
the roll of film I maintained a notebook where I wrote down the 
settings, what is the best way to substitute the info in the resulting 
.CR2 files with the info from my notes? I am really looking forward to 
loading these into Darktable/Negadoctor.


Thanks
Andrew Greig
 


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



--
Stéphane Gourichon


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