Re: [darktable-user] Will the next release of darktable support CR3 files?
Hi Terry, from a cursory glance, it seems like work on CR3 support is tracked in [1] and [2]. Looks like there's progress? Cheers Moritz [1] https://github.com/darktable-org/darktable/issues/2170 [2] https://github.com/darktable-org/rawspeed/issues/121 On Fri, Apr 30, 2021 at 2:25 AM Terry Pinfold wrote: > > I am just wondering if there is any confirmation on CR3 file support in > DT3.0. It would be such a shame if this support is not available. I have read > the online discussions about the issue and hope a resolution has been found. > > -- > > > > 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] darktable 3.4 released
Congratulations for another great release to you guys. Your commitment is super impressive and so are the results. On Thu, Dec 24, 2020 at 10:09 AM Pascal Obry wrote: > > We're proud to announce the new feature release of darktable, 3.4.0! > > The github release is here: > [ > https://github.com/darktable-org/darktable/releases/tag/release-3.4.0](https://github.com/darktable-org/darktable/releases/tag/release-3.4.0) > . > > As always, please don't use the autogenerated tarball provided by > github, but only our tar.xz. the checksums are: > > ``` > $ sha256sum darktable-3.4.0.tar.xz > 6dd3de1f5ea9f94af92838c0be5ff30fdaa599aa1d737dcb562f9e0b2b2dbdda > darktable-3.4.0.tar.xz > > $ sha256sum darktable-3.4.0.dmg > da72476993160d1cb2ff8e40c6bd402f1032884936a9eb818197c936d4b22a14 > darktable-3.4.0.dmg > > $ sha256sum darktable-3.4.0.exe > 29dee565292a4a72443874bb970663d46420f5a9ba74a5acfcb3251a48c86f7c > darktable-3.4.0.exe > ``` > > When updating from the currently stable 3.2.x series, please bear in > mind that your edits will be preserved during this process, but the new > library and configuration will not be usable with 3.2.x any more, so > you are strongly advised to take a backup first. > > Important note: to make sure that darktable can keep on supporting > the raw file format for your camera, *please* read [this post]( > https://discuss.pixls.us/t/raw-samples-wanted/5420?u=lebedevri) on > how/what raw samples you can contribute to ensure that we have the *full* > raw sample set for your camera under CC0 license! > > - Almost 2146 commits to darktable+rawspeed since 3.2 > - 700 pull requests handled > - 116 issues closed > > ## The Big Ones > > - The user manual is made available at the same time as the > release. Note that this user manual is also the last version as a > new project has taken over the lead on this. The goal is to have > an up-to-date user manual by using a simpler format > to write text for contributors. Feedback or contributions for the > new format are welcome at https://github.com/darktable-org/dtdocs. > > Current manual (multilingual): > > https://darktable.gitlab.io/doc/ > > New manual (English only): > > https://www.darktable.org/usermanual/en/ > > - The tethering view has been reworked and is now more stable. > > - The histogram is back on the tethering view (it was disabled in 3.2 > due to lack of time) > > - A new module grouping feature has been introduced. This makes the "more > modules" module > (at the bottom right of the darkroom) obsolete and this module has > therefore been removed. > > The module grouping feature allows users to create their own groups > of modules. A number of pre-defined module groups are included as presets > (default, minimal, scene-referred, display-referred, > all modules) as well as a new default module group tab layout (technical > / grading / effects), > which beter organizes the modules according to their purpose. > > - Module masking is now enhanced for use with scene-referred workflows. A > new masking implementation > has been added, with fully unbounded blending modes, which allows > parametric masking > either in linear RGB or in JzCzHz color spaces. A boost factor slider > has been > introduced in the masking GUI so that users may set thresholding > parameters above 100% > to mask pixels in HDR images. > > JzCzHz is derived from JzAzBz, which is a perceptual color space > developed > for HDR and published in 2017, with better properties than CIE Lab from > 1976, > allowing near-perfect hue linearity, for a robust hue/saturation masking. > A JzCzHz hue mask will produce the same output whether it is used > before input color profile, after output color profile, or anywhere > in-between, > providing an important consistency improvement over HSL masking. > > - A new color calibration module has been added as a full-featured hub for > color correction. > It was first intended as a scene-referred (unbounded) rewrite of the old > channel mixer, > allowing corrections of the color space, both for creative and > corrective purposes. > > Because channel mixing is how white balancing and chromatic adaptation > are implemented, color calibration also introduces robust chromatic > adaptation transforms, > Bradford (from ICC v4) and CAT16 (from CIECAM 2016), improving the color > rendition > of the white-balanced final image. The module provides a library of all > standard > CIE illuminants and two machine-learning illuminant detection > algorithms, using > different assumptions, for when no neutral colors can be sampled from > the image, > along with the traditional color-picker for manual sampling of neutral > colors. > > Color calibration internally implements gamut-mapping and gamut-clipping, > which attempts to preserve the hue and luminance of pixels while > avoiding imaginary and > out-of-gamut colors at the beginning of the pipeline, to improve the >
[darktable-user] Darktable database corruption leads to hanging lighttable
I currently have a reproducible hang in the lighttable. Version 3.2.1 of
darktable in Ubuntu 20.04. A possible workaround is described below.
- Open Darktable
- Images matching the filters last set are displayed
- Reset the collect module
- Darktable hangs
- Expected: All images are shown (and darktable does not hang)
Setting specific other filters in the collect module works fine, e.g. I can
open an individual previous film roll without any problem.
I suspected based on the logging (below) is that it's hanging whenever the
collect module matches a specific image (#4079) that's broken. I opened the
library.db in sqlitebrowser, and looked at the images table. There was
indeed no entry with id 4079, but the rows 4077 and 4080 referred to
group_id 4079. On a whim I changed the group_id of 4077 to 4077 etc.
Restarting darktable resulted in the same error but with a different id. In
fact the same inconsistency happened with a few more ids, I "fixed" them
with the same approach and after that, the bug did not trigger anymore.
Here's a screenshot of (a backup of) the corrupted db:
https://imgur.com/a/m7UdD9W
The first 8 ids are affected. I have to wonder what happened to image 4079,
4084, etc. Or worse, maybe other images (db rows) are missing, but don't
trigger a crash because they are not part of a group...
Cheers
Moritz
strace spams the following line over and over again:
clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=0, tv_nsec=5000},
0x7fff9515da80) = 0
Last couple of lines of darktable -d all, of which only
[image_cache_allocate] failed to open image 4079 from database: no more
rows available
stands out:
130,233841 [sql] /usr/src/packages/BUILD/src/common/image_cache.c:39,
function dt_image_cache_allocate(): prepare "SELECT id, group_id, film_id,
width, height, filename, maker, model, lens, exposure, aperture, iso,
focal_length, datetime_taken, flags, crop, orientation, focus_distance,
raw_parameters, longitude, latitude, altitude, color_matrix, colorspace,
version, raw_black, raw_maximum, aspect_ratio, exposure_bias,
import_timestamp, change_timestamp, export_timestamp, print_timestamp FROM
main.images WHERE id = ?1"
[image_cache_allocate] failed to open image 4079 from database: no more
rows available
130,234003 [sql] /usr/src/packages/BUILD/src/dtgtk/thumbnail.c:104,
function _image_update_group_tooltip(): prepare "SELECT id, version,
filename FROM main.images WHERE group_id = ?1"
130,234087 [sql] /usr/src/packages/BUILD/src/common/image.c:222, function
dt_image_full_path(): prepare "SELECT folder || '/' || filename FROM
main.images i, main.film_rolls f WHERE i.film_id = f.id and i.id = ?1"
130,234162 [sql] /usr/src/packages/BUILD/src/common/image.c:250, function
_image_local_copy_full_path(): prepare "SELECT folder || '/' || filename
FROM main.images i, main.film_rolls f WHERE i.film_id = f.id AND i.id = ?1"
130,234348 [sql] /usr/src/packages/BUILD/src/common/history.c:1488,
function dt_history_hash_get_status(): prepare "SELECT CASE WHEN
basic_hash == current_hash THEN 1 WHEN auto_hash == current_hash THEN 2
WHEN (basic_hash IS NULL OR current_hash != basic_hash) AND
(auto_hash IS NULL OR current_hash != auto_hash) THEN 4 ELSE 1 END AS
status FROM main.history_hash WHERE imgid = 4077"
130,234421 [sql] /usr/src/packages/BUILD/src/common/history.c:858, function
dt_history_get_items_as_string(): prepare "SELECT operation, enabled,
multi_name FROM main.history WHERE imgid=?1 ORDER BY num DESC"
130,235337 [sql] /usr/src/packages/BUILD/src/common/image_cache.c:39,
function dt_image_cache_allocate(): prepare "SELECT id, group_id, film_id,
width, height, filename, maker, model, lens, exposure, aperture, iso,
focal_length, datetime_taken, flags, crop, orientation, focus_distance,
raw_parameters, longitude, latitude, altitude, color_matrix, colorspace,
version, raw_black, raw_maximum, aspect_ratio, exposure_bias,
import_timestamp, change_timestamp, export_timestamp, print_timestamp FROM
main.images WHERE id = ?1"
130,235487 [sql] /usr/src/packages/BUILD/src/common/history.c:1488,
function dt_history_hash_get_status(): prepare "SELECT CASE WHEN
basic_hash == current_hash THEN 1 WHEN auto_hash == current_hash THEN 2
WHEN (basic_hash IS NULL OR current_hash != basic_hash) AND
(auto_hash IS NULL OR current_hash != auto_hash) THEN 4 ELSE 1 END AS
status FROM main.history_hash WHERE imgid = 4080"
130,235984 [sql] /usr/src/packages/BUILD/src/common/history.c:858, function
dt_history_get_items_as_string(): prepare "SELECT operation, enabled,
multi_name FROM main.history WHERE imgid=?1 ORDER BY num DESC"
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Making Adjustment(s) with Mouse Wheel
Not only that, but you can set up hotkeys for many settings in the preferences. Holding the key while scrolling the wheel will modify the parameter, without (!) having to select the respective module. E.g. here I've set up the hotkey E for exposure correction: https://imgur.com/a/jWRRDy2 Using the wheel while holding E will increase or decrease the exposure value in the basic adjustments module. So really you can make the mouse wheel do pretty much anything. Moritz On Fri, Sep 25, 2020 at 9:29 PM Jason Polak wrote: > > When I put the mouse arrow over the slider, the mouse wheel scrolls the > slider. For the tone equalizer, you can put the crosshair directly over > the image and scroll to adjust the tone category defined by the location > of the crosshair. > > Jason > > On 25/09/2020 14.39, J. Verreault wrote: > > Hi all, > > Am I able to make adjustment(s) in modules that has slider(s) with the > > mouse wheel and if so how..? > > Am using a Logitech MX Master mouse on ArcoLinux with latest DT version > > > > Thanks > > > > -- > > You don't know what you have until you need it. > > > > > > 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 mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Darkroom image visible under Lighttable thumnails
I was affected by this as well. Crossposting what I wrote on Github: Switching to a different theme fixed the issue. I had made some HiDPI theming tweaks in the previous version (which may be superflous now). I removed my `themes` folder (in `~/.config/darktable`), and now the default darktable theme does not exhibit the issue anymore either. Cheers Moritz On Wed, Aug 12, 2020 at 9:52 AM Kneops wrote: > Thanks for the link :) > > > > Op 12-08-2020 om 09:45 schreef KOVÁCS István: > > On Wed, 12 Aug 2020 at 09:42, Kneops wrote: > >> I just installed 3.2.1 and now when I switch back from an image in > >> Darkroom to Lighttable, the Darkroom image is still visible under the > >> thumbnails. Is that how it is supposed to work? > > > > I think an issue has been opened for that: > > https://github.com/darktable-org/darktable/issues/5922 > > > > Kofa > > > > > 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 mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
[darktable-user] Re: Export to Clipboard
Ok, I cobbled together a lua script that calls an external tool. There
were already scripts doing something similar, but they attempt to copy
back the result from the external program back to Darktable, which is
not applicable for my use case.
This also makes the script much shorter and very easy to understand.
It should be easily adaptable for anyone who wants to "export"
individual files to an external command.
In my case, the external command is `ffmpeg -i {FILENAME} -f apng - |
xclip -selection clipboard -target image/png`. Xclip to get data into
the clipboard, and ffmpeg to quickly convert anything to png (which
many applications seem to prefer as a clipboard data type). I could
also have limited the exporter to PNG, but then I'd have to remember
to switch back when I want to export to filesystem.
Cheers
Moritz
On Sat, Apr 18, 2020 at 4:16 PM Moritz wrote:
>
> Hello all,
>
> sometimes I just want to quickly share an image via copy/paste. Is
> there any way to export an (individual) image to the clipboard? I kind
> of hoped pressing Ctrl-C would do the job, but no. Currently I'm using
> the system screenshot tool to (roughly) select the image as rendered
> in the Darktable, which is quite a clutch. But it's much quicker than
> exporting to file system and opening the file in an editor that can
> interact with the clipboard.
>
> Seems like something a LUA script would be able to do, but I don't
> know how to write images to clipboard using LUA. I guess I could call
> an external tool, but that's very system-specific and it's non-obvious
> which external tool to use[1].
>
> Thanks
> Moritz
>
> [1]
> https://superuser.com/questions/301851/how-to-copy-a-picture-to-clipboard-from-command-line-in-linux
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org-- title of external tool, used for UI actions
local title = "clipboard"
-- the external tool that will be called (once per image)
-- {FILENAME} is replaced by the filename, {MIME} by the selected format's mime type
local external_tool = "ffmpeg -i {FILENAME} -f apng - | xclip -selection clipboard -target image/png"
-- if you have more than one instance of this lua, you need to increment this number so that DT can tell them apart
local number = "1"
local dt = require "darktable"
local df = require "lib/dtutils.file"
local dtsys = require "lib/dtutils.system"
local function exportSingle(storage, image, format, filename, number, total, high_quality, extra_data)
filename = df.sanitize_filename(filename)
local command = external_tool
command = string.gsub(command, "{FILENAME}", filename)
command = string.gsub(command, "{MIME}", format.mime)
local retval = dtsys.external_command(command)
dt.print_log("return value " .. retval .. " for " .. command)
if retval ~= 0 then
dt.print("could not run external command " .. title)
else
dt.print(string.format("exported image %i/%i to " .. title, number, total))
end
end
dt.register_storage("export_external_" .. number, title, exportSingle, nil, nil, nil, nil)
[darktable-user] Export to Clipboard
Hello all, sometimes I just want to quickly share an image via copy/paste. Is there any way to export an (individual) image to the clipboard? I kind of hoped pressing Ctrl-C would do the job, but no. Currently I'm using the system screenshot tool to (roughly) select the image as rendered in the Darktable, which is quite a clutch. But it's much quicker than exporting to file system and opening the file in an editor that can interact with the clipboard. Seems like something a LUA script would be able to do, but I don't know how to write images to clipboard using LUA. I guess I could call an external tool, but that's very system-specific and it's non-obvious which external tool to use[1]. Thanks Moritz [1] https://superuser.com/questions/301851/how-to-copy-a-picture-to-clipboard-from-command-line-in-linux darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] 3.0
FWIW, there's an alternative repository that contains 3.0: http://ubuntuhandbook.org/index.php/2019/12/install-darktable-3-0-0-ubuntu-18-04-19-10/ On Tue, Jan 7, 2020 at 3:02 AM Michael wrote: > > So I'm thinking I want to compile 3.0 (getting tired of waiting for > pascal to update his ppa). So I'm lost I went to Github and dl the > zip but now what do I do? The instructions say: > > Easy way > > ./build.sh --prefix /opt/darktable --build-type Release > > What about the existing darktable installation? Will it be overwritten > or else do I need to do anything? Should I rename a copy of 2.6.3 to > an old directory? > > > -- > :-)~MIKE~(-: > > 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] Darktable 3.0 looks great, but my fonts are far too large...
I had the same problem, but it's easily fixed by using the new CSS theming engine. In my case (Ubuntu 19.10, Ubuntu Handbook PPA binary) the default (system-wide) themes were installed under /usr/share/darktable/themes. You can probably edit the file in-place (as root), but it's cleaner to copy everything to you user directory under ~/.config/darktable/themes. The file darktable.css is the root theme which needs to be modified. It's all very straightforward and human-readable. I replaced all lines of type font-size with custom values (1em -> 10pt worked out for me, smaller em-values did not). There may be a better way to do it globally. I'll attach my darktable.css. Note that if you want one of the other themes (e.g. elegant), you'll need to copy those to your user dir as well, since they'll refer to the darktable.css in the user dir. When in doubt, just copy all of them. The new themes are picked up by darktable without having to restart. Unless you rename the files, you'll have duplicates in the GUI options dialog; but note that if you rename e.g. darktable.css you will need to adjust the reference in the other files. Modifications to the themes are also picked up without restarting, just by switching to another theme and back. So it's very easy to do a bit of trial and error. On a sidenote, in 4k resolution the improvement in UI latency is almost eery. Great work. Cheers Moritz On Sat, Dec 28, 2019 at 10:24 PM Shane Simmons wrote: > > I just installed DT 3.0 from the unofficial Ubuntu Handbook PPA, the other > day, but the issue I have is that the fonts are much too large on my 4K > monitor, and I've tried adjusting the screen_dpi_overwrite setting in > darktablerc, to no avail. In fact it doesn't even seem > seem to work anymore. My monitor is an ASUS PB287Q, with a screen area of > 621x341mm, to give an idea of the scale of these fonts (I reduced this image > to half-size - 1920x1024) -- > > > I need to reduce the overall UI scaling, or fonts, by about half, to get a > reasonable scaling here. How do I do that? The old method of editing the > darktablerc file to fit the screen resolution doesn't work anymore (And what > gives with this anyway?) > > Any ideas? As is it is now, the program is almost unusable with these > oversized fonts. Also, I am running Kubuntu 19.10, on a Ryzen 7 2700X, with > a GTX 1080 Ti, if it matters. > > -- Shane > > "Understanding is a three-edged sword." -- Kosh Naranek > > > 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 /* This file is part of darktable, copyright (c) 2019 Aurélien Pierre. darktable is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. darktable is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with darktable. If not, see <http://www.gnu.org/licenses/>. */ /* This has been tested with GTK 3.24 on Gnome */ /* Perceptually uniform grey gradient */ /* grey_00 = pure black is forbidden for visual assessment */ @define-color grey_00 #00; @define-color grey_05 #11; @define-color grey_10 #1b1b1b; @define-color grey_15 #262626; @define-color grey_20 #303030; @define-color grey_25 #3b3b3b; @define-color grey_30 #474747; @define-color grey_35 #525252; @define-color grey_40 #5e5e5e; @define-color grey_45 #6a6a6a; @define-color grey_50 #77; @define-color grey_55 #848484; @define-color grey_60 #919191; @define-color grey_65 #9e9e9e; @define-color grey_70 #ababab; @define-color grey_75 #b9b9b9; @define-color grey_80 #c6c6c6; @define-color grey_85 #d4d4d4; @define-color grey_90 #e2e2e2; @define-color grey_95 #f1f1f1; @define-color grey_100 #ff; /* grey_100 = pure white is forbidden for visual assessment */ /* General rules : * keep just enough contrast in the UI to make text readable, but not too much to avoid distractions from the picture, * avoid sharp and unnecessary details for the same reason (shadows, borders, colors, fancy bits). Use plain shapes and flat design. * keep 50 % distance between background and foreground colors for active controls * keep 30 % distance between background and foreground colors for labels and info * keep 10
