into the issue some more - I know nothing about how
the dt code is structured?
Regards
Dusenberg
On 27/07/2023 11:46, Guillermo Rozas wrote:
Hi,
sorry for the late reply, I was a bit busy. Yes, pixls.us
<http://pixls.us> will probably give you more 'developer eyes' to
check the problem. It's pr
I have posted this on pixls.us now it is back up.
Dusenberg
On 26/07/2023 20:39, Dusenberg wrote:
Guillermo
Since my last post, I have extracted data from the dt db image table
for the image and versions concerned from three backup instances of
the dt database going back 3 years:
a) 2020
ensure
images with the same filename are permitted and can be handled, it seems
the 'duplicate image' functionality does not recognise this potential.
Regards
Dusenberg
On 26/07/2023 09:59, Dusenberg wrote:
Guillermo,
Answers to your questions:
a) xmp's are named '__<$VERSION>.RAWextension.xm
isting xmp for the previous version 3. Also all xmp files in that
group new have new modified dates - 24 July 2023, when I created the
new duplicate
Also I didn't mention that the NIK_1413 RAW and duplicates are in a
single group.
Thanks for your time.
Dusenberg
On 26/07/2023 03:41, Guillermo
Hi Guillermo
Yes the original and all duplicates were in the database before making
the new duplicate.
Regards
Dusenberg
On 25/07/2023 15:03, Guillermo Rozas wrote:
Hi,
were the original and all the duplicates present in the database
before making the duplicate?
Regards,
Guillermo
On Tue
Originally posted to darktable-dev list in error.
dt 4.2.1 (OBS), Linux Mint 21,Ubuntu 22.04 jammy
I have an image from March 2020 developed in darktable. I went back to
it today to try another edit on it (its a monochrome rendition that I
just can't get 'right').
However, today when I created
I had same problem with a Tokina AT-X 24-70mm f/2.8
PRO FX on D810. I got the answer here https://dev.exiv2.org/projects/exiv2/wiki/Lens_Recognition_in_Exiv2_v026_(and_later)/
The solution needs exiv2 0.26+, which at the time meant it
wouldn't work on
Re your [ASIDE]: I recently built a similarly spec'd
photo workstation with Ryzen 3900x 12-core, 32Gb 3200Mhz DDR4,
Radeon RX 5500XT 8Gb DDR6 GPU, 2 x NVMe M2 SSD, on an ASRock X570
Phantom Gaming 4 - all PCIe4 - running OpenSUSE Leap 15.1. It
ABSOLUTELY FLIES!!
Anyone know how to display the date/time of the last
edit on an image in DT? I like to go back over my edits and tweak
them, so I have a lot of versions, and it isn't always the biggest
version number which was edited last. So being able to see when I
last
I had the same problem on my Nikon when I bought a
Tokina 24-70mm F2.8 AT-X Pro for it. The issue is that the camera
doesn't recognise the foreign lens and so does not populate the
necessary exif fields with the lens data. It's not a Darktable
issue.
version 3
Last year I edited a group of raw images and created a focus
stacked final output of them. One of the edits was to make the
after-sunset sky pinker. I did this using Color Balance in HSL and
changing the Highlights hue and saturation. I had to
Hi
Over last few months I've finally created a style which I can
apply to all my landscape shots and which produces what I think
are excellent images which usually need little or no manual
attention. A big thanks to all the developers - DT is a great
Hajo - thanks. I had no idea such an app existed.
I'll look into it.
Cheers
Dusenberg
On 03/09/2019 08:18, HaJo Schatz wrote:
"Loose integration", to me in Linux, could mean a
2nd window which has buttons such
as a
temporary fix I'll manually add the version number on export
rather than use $(VERSION), and then work out a more reliable
method for the longer term.
Regards
Dusenberg
On 29/08/2019 10:31, Michael Fritze
wrote
Thanks Hajo
My first thought on your suggestion is the revision control system
would need integrating with darktable somehow.
I'll think on this a while.
Dusenberg
On 28/08/2019 05:09, HaJo Schatz wrote
Hi
I'm fairly new to darktable, but have set up a reasonable
workflow, and feel I'm producing good outputs. However I do
have a problem with file management caused by DT version
numbering which I hope someone can help me with as
wrote:
On jeudi 14 février 2019 12:23:03 CET Dusenberg wrote:
I have just been puzzling over the 'pink highlight' problem on several raws
I recently shot (not HDR), all of which have blown highlights caused by a
camera operator silly error :) I recently created a custom style for
I have just been puzzling over the 'pink highlight'
problem on several raws I recently shot (not HDR), all of which
have blown highlights caused by a camera operator silly error :) I recently created a custom style
for my camera and I thought that was something to
On 26/01/2019 20:03, Normand Fortier wrote:
So far, my understanding is this.
DT works in LAB color space. Most modules work in that space ("The
local color pickers run in the color space of the individual module,
which is usually L"; see also
19 matches
Mail list logo
