Re: [darktable-user] darktable-users list, fewer postings?
Styles and preferences is not the same as standards. On Sun, Apr 23, 2023, 16:23 Patrick Shanahan wrote: > * Terry Pinfold [04-23-23 18:23]: > > Totally agree with you Patrick. My email server posted incorrectly for > this > > list and it caused great offence to people here so I moved on to a forum > > where I was more welcomed. > > Have a nice day and keep up the good work supporting DT users. > > > > > > On Mon, 24 Apr 2023 at 08:16, Patrick Shanahan > wrote: > > > > > * Terry Pinfold [04-23-23 17:49]: > > > > On Sun, 23 Apr 2023 at 21:03, Peter McD wrote: > > > > > > > > > Am 23.04.23 um 12:29 schrieb Michael Below: > > > > > > Am Sonntag, dem 23.04.2023 um 12:21 +0200 schrieb Peter McD: > > > > > >> So where are the postings of other users? > > > > > > > > > > > > Many people moved to the pixls.us forum: > > > > > > https://discuss.pixls.us/c/software/darktable/19 > > > > > > > > > > > > Cheers > > > > > > Michael > > > > > > > > > > > > > > > > > > > > > darktable user mailing list > > > > > > to unsubscribe send a mail to > > > > > darktable-user+unsubscr...@lists.darktable.org > > > > > > > > > > > > > > > > Thanks > > > > > Peter > > > > > > > > > > > > > > > > > > > darktable user mailing list > > > > > to unsubscribe send a mail to > > > > > darktable-user+unsubscr...@lists.darktable.org > > > > > > > > > > > > > > > > > > -- > > > > I stopped posting to this list because people complained about my > posts > > > > being top posting or bottom posting or something else which I found > very > > > > petty. They also complained if I forgot to remove my email > signature. So > > > if > > > > I was going to have problems meeting their "net etiquette" I would > move > > > > onto another forum which is pixels.us. I have found the pixls.us > forum > > > much > > > > more friendly and tolerant. > > > > > > > > > > yes, much easier to change horses than to attempt to follow accepted > > > standards. > > > > > > -- > > > (paka)Patrick Shanahan Plainfield, Indiana, USA > @ptilopteri > > > http://en.opensuse.orgopenSUSE Community Member > facebook/ptilopteri > > > Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet > oftc > > > > > > > > > > darktable user mailing list > > > to unsubscribe send a mail to > > > darktable-user+unsubscr...@lists.darktable.org > > > > > > > > > > -- > > > > > and you do not hold your students to any standards? > > -- > (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri > http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri > Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc > > > 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] exif info not in shot
Export preferences (hamburger menu in the export module). Juan On Mon, Sep 26, 2022 at 7:37 AM Jason Polak wrote: > Hey List, > > I'm using Darktable 4.0.0. When I export my images the EXIF information > isn't in them any more...is there an option somewhere to turn this back on? > I can't seem to find it. > > Thanks > Jason > > > 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] Open/Close Behavior of darkroom Left Hand Modules
On Sun, Feb 21, 2021 at 7:34 PM Patrick Shanahan wrote: > in the configuration, "gear wheel" icon > select darkroom and look at the lower half "modules" > the third item "expand a single processing module at a time" > you apparently have it selected. > I do not. > > On my installation (dt 3.4.1/Ubuntu) that setting only affects the processing modules (right-hand side). OP's problem seems to be with the left-hand side. Juan darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] DT 3.4 no longer has zone system module (gone!)
On Mon, Jan 4, 2021 at 10:00 PM KOVÁCS István
wrote:
> On Tue, 5 Jan 2021 at 00:18, Tanya Riseman
> wrote:
>
> > You are supposed to use the tone equalizer module instead of the zone
> system module now. According to the manual, zone system is deprecated.
> >
> > The zone system is pretty easy for beginners to pick up.
> > The tone equalizer is much harder to get up to speed with. It lacks a 2D
> zone image.
> > It only has crosshairs that correspond to a hard to understand contrast
> mask, not the zone.
>
> The zone system was just one of the ways to define a tone curve. The
> resulting curve was applied at the pixel level (all pixels with a
> given value were affected the same way, without taking their
> surroundings into account). To replicate the same behaviour, you don't
> need the mask: select the 'simple tone curve' preset from the tone
> equalizer (this disables masking),
More precisely, choose 'no' in preserve details (in the masking tab), which
doesn't disable the mask but disables *smoothing* of the mask ("effect is
the same as using normal tone curves", according to the manual).
Juan
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] My Fuji Raws turn dark
Could be this: https://www.mail-archive.com/darktable-user@lists.darktable.org/msg10006.html On Wed, Oct 28, 2020 at 12:33 PM Rudi wrote: > Darktable 3.2.1 MX Linux 19 > > I shoot RAW + JPEG. Since switching to MX Linux and reinstalling > Darktable the raws of my Fuji turn dark (although not always but many > times) as if the exposure was lowered with at least 1 stop. The > histogram also shows the darkened picture. > > I do not have that problem with Rawtherapee. > > Does somebody has a clue what is happening? > > Thank you > > Rudi > > > > > 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] [PSA] [README] darktable 3.2.1 bug when importing RAW + JPEG
Also, you may avoid the bug if you set preferences->lighttable->don't use embedded preview JPEG. Juan On Wed, Sep 23, 2020 at 12:02 PM jys wrote: > This is just a heads-up for anyone who imports RAW + JPEG file pairs... > there is a bug in darktable 3.2.1 which can result in the input color > profile of the RAW image being set to sRGB (or other JPEG profiles?) under > some circumstances. The bug has been fixed in current master, and is > discussed here: > > https://github.com/darktable-org/darktable/issues/6202 > > If you find that the RAW file in a RAW + JPEG pair shows incorrect dark > colors, this is probably the cause. Setting the input color profile back to > "standard" (or whatever you normally use) will correct the problem. > > -- > jys > > > 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] Bug: raw images (inconsistently) get wrong input color profile
Ah, good to know, thanks. On Wed, Sep 23, 2020 at 11:51 AM jys wrote: > Yep, this has been reported and is fixed in current master: > > https://github.com/darktable-org/darktable/issues/6202 > > There probably should have been a PSA about it on the list, since it's > likely to affect quite a few people... > > On Wed, Sep 23, 2020, at 11:26, Juan Navarro wrote: > > Hi all. I'll report this in github, but it would be great to know if it > > happens to anybody else. > > > > When importing raw and jpeg files together some (usually most) of my > > raw files wind up with the sRGB input profile. To reproduce: > > - preferences->import: make sure "ignore JPEG images..." is unset > > - preferences->lighttable: make sure "don't use embedded preview > > JPEG..." is unset > > > > Download the 4 files in http://nandu.world/darktable/input_profile_bug/ > > to a directory, and import that directory. In most of my tries I get > > one (not always the same) of the raw files with the wrong input > > profile. Symptoms look like a concurrency bug to me, although I'm still > > unfamiliar with the code. > > > > This is with darktable 3.2.1 on an ubuntu 20.04 system. > > > > Thanks, > > > > Juan > > > 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] Bug: raw images (inconsistently) get wrong input color profile
Hi all. I'll report this in github, but it would be great to know if it happens to anybody else. When importing raw and jpeg files together some (usually most) of my raw files wind up with the sRGB input profile. To reproduce: - preferences->import: make sure "ignore JPEG images..." is unset - preferences->lighttable: make sure "don't use embedded preview JPEG..." is unset Download the 4 files in http://nandu.world/darktable/input_profile_bug/ to a directory, and import that directory. In most of my tries I get one (not always the same) of the raw files with the wrong input profile. Symptoms look like a concurrency bug to me, although I'm still unfamiliar with the code. This is with darktable 3.2.1 on an ubuntu 20.04 system. Thanks, Juan darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] darktable 3.2.1 released
"- Updated user manual is coming soon™" (7th paragraph of the announcement). Juan On Mon, Aug 10, 2020 at 12:57 PM Mikael Ståldal wrote: > Is there an updated user manual for 3.2? > > > > On 2020-08-10 09:38, Pascal Obry wrote: > > > > We're proud to announce the new feature release of darktable, 3.2.1! > > > > Note that 3.2.0 has been skipped due to last minute bug fixes. > > > > The github release is here: [ > https://github.com/darktable-org/darktable/releases/tag/release-3.2.1](https://github.com/darktable-org/darktable/releases/tag/release-3.2.1) > . > > > > As always, please don't use the autogenerated tarball provided by > > github, but only our tar.xz. the checksums are: > > > > ``` > > $ sha256sum darktable-3.2.1.tar.xz > > 6e3683ea88dc0a0271be7eca4fd594b9e46b1b7194847825a8d0a0c12bdeb90c > > darktable-3.2.1.tar.xz > > $ sha256sum darktable-3.2.1.dmg > > 292b8327fdc2bd6346994d52f904e0d89078100c91eec2a7c6982f71f8dd24ca > > darktable-3.2.1.dmg > > $ sha256sum darktable-3.2.1.exe > > 7d21442aa31a627428cf9e56c85ecb4e985b544ea950d98b54ed0a6f123ad6d3 > > darktable-3.2.1.exe > > ``` > > > > When updating from the current stable 3.0.x series, please bear in > > mind that your edits will be preserved during the upgrade, but the new > > library and configuration files are not backward compatible; they're > > not usable with 3.0.x, so > > making a backup is strongly advised. > > > > Important note: to make sure that darktable can keep supporting > > the raw file format from 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 2700 commits to darktable+rawspeed since 3.0 > > - 790 pull requests handled > > - 92 issues closed > > - Updated user manual is coming soon™ > > > > ## The Big Ones > > > > - The *lighttable* view has been rewritten and the filmstrip reworked, > > resulting in large performance gains, especially when using the > > zoomable lighttable view. The culling view has also been rewritten from > > scratch. Operations are smooth at any screen resolution up to 8k. > > > >Many types of overlay are now possible on lighttable thumbs. > >Different overlay information can be selected depending on the thumb > >size on the lighttable. The different sizes can be set in the > >preferences, so we can have no overlay at all for small thumbs and > >full overlay when large thumbs are displayed. This is fully > >configurable. > > > >Likewise, the tooltip information when hovering the thumbs can be > >activated/deactivated based on the thumbs size. > > > > - The lighttable modules have improved user interaction: buttons are > >highlighted only when the context makes the action possible. > > > > - A complete overhaul of the CSS has been done. This gives > >darktable a professional look. This continues > >the goal to make every single aspect of the UI themable using CSS. > > > > - The Color Picker and > >Location modules are updated to better fit into the new UI, and > >most of the icons have been altered so as to be more > >visually balanced. > > > > - The preference dialog has been fully reviewed and reorganized to > >propose a better look and require less > >scrolling. It is also possible to add some CSS rules directly into > >the preference dialog to tweak darktable's look as well as > >to directly control the font size and DPI values from the general > >preference tab. > > > >A search field has been added to the shortcuts tab to help you find > >the keyboard shortcut you want to customize. > > > > - The new negadoctor module has been added to help inverting negative > >films. > > > > - A new histogram display called RGB Parade has been added. At the > >same time the histogram module height can now be adjusted with > >Ctrl+Scroll. > > > > - The metadata feature has been made generic internally and has new > >features. The user can now select the information they want to see > >in the metadata editor. This selection is automatically mirrored in > >the collection and image information modules. > > > >Along with a new "notes" field, all the fields are multiline > >Ctrl+Enter, sizable Ctrl+Scroll and can be set > >as private (not exported). Metadata collection filters have an entry > >"not defined". At import time it is possible to choose not to import > >some metadata. > > > > - Image change detection has been made more reliable. This affects the > >lighttable thumbnails change symbol and history collection filter, > >which is now more accurate. In darkroom navigation, this avoids the > >need to recalculate an image and save the xmp file when there is > >no change. > > > > - A new down-sampling preference has been introduced for faster > >response in
Re: [darktable-user] Can "hover" in the lighttable be turned off?
On Sun, Jun 28, 2020 at 9:26 AM Patrick Shanahan wrote: > * Juan Navarro [06-28-20 12:17]: > > > > > > The "hoover" has been present in dt as long as I can remember, at least > > > 2012/2013 when I started using. The image below the mouse pointer is > the > > > "active" image, in all screens in dt. > > > > > > > > > At least the "ungroup" action doesn't apply to the hovered-over image, > but > > the selected one. There might be more. > > > > > > > > > > Changing an action with that much history would really cause a lot of > > > confusion. > > > > > > > Tom was asking for an option to disable this behaviour for those of us > who > > dislike it. I personally find it very confusing, annoying, and even with > > data-loss potential, so I'd welcome a way to disable it. Things get > > particularly confusing in darkroom view, where you have the image you are > > working on, the selected one, and the hovered-over one: which of the 3 > > images will ctrl-E apply to? What about ctrl-shift-C? > > the image below the mouse pointer is the "active" image. > Then you'd be surprised that ctrl-E does not apply to that one. darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Can "hover" in the lighttable be turned off?
> > The "hoover" has been present in dt as long as I can remember, at least > 2012/2013 when I started using. The image below the mouse pointer is the > "active" image, in all screens in dt. > At least the "ungroup" action doesn't apply to the hovered-over image, but the selected one. There might be more. > > Changing an action with that much history would really cause a lot of > confusion. > Tom was asking for an option to disable this behaviour for those of us who dislike it. I personally find it very confusing, annoying, and even with data-loss potential, so I'd welcome a way to disable it. Things get particularly confusing in darkroom view, where you have the image you are working on, the selected one, and the hovered-over one: which of the 3 images will ctrl-E apply to? What about ctrl-shift-C? Juan darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Import: I'm failing at step 1; advice please
FWIW, I just use a simple script that copies my images from the SD card to a Year/Month/Topic directory in my hard drive and renames the directory in the SD card to something that includes today's date. Then I use DT's import. Juan On Thu, Jun 25, 2020 at 10:54 AM Simon Wren wrote: > My (limited) understanding of the import function of darktable is that > it's not for effectively copying images from one location to another (i.e., > from a camera memory card to a hard disk) but rather for copying details > about images which exist on some medium (e.g., a hard disk). Such that it's > importing not the files themselves, but details about the files. > > I'm mostly using Linux these days so do use Rapid Photo Downloader, but > when I used LR and Windows (many moons ago) I used Downloader Pro quite > successfully to copy images from cards onto hard drives: > > https://www.breezesys.com/solutions/breeze-downloader/ > > On 25 June 2020 at 18:38 tony Hamilton wrote: > > > This is an update after a few days of intense, all-day, reading and > experimentation with the import function of DarkTable 3.0.2. What I am > going to write here is at considerable length and will not be well received > by the Darktable development team. It is my personal opinion; it reflects > my skill as a programmer (essentially non-existent) and the experience > using DT on my system. This caveat is not a cop-out: the major cause of my > problems with Darktable import looks like a Windows problem (compounded by > a design decision by the DT development team.). This means that some > Windows systems will behave as expected; mine do not. > > I find the import function in Darktable to be essentially dis-functional > and dangerous In my environment: there is the risk of loss of data which is > more probable than when using any of the other raw processors I am > considering, with the exception of RawTherapee. For my circumstance there > is no way that I will use the import function in DT (or Rawtherapee) even > for those limited cases where the function works at all. > > I have 4 computers running Win 10; 2 of them dual boot to Linux Mint 19.3 > (Cinnamon and XFCE). Most of my comments apply to the Windows > configuration. I would prefer to run DT in Linux, but a key requirement I > have – a robust and functionally adequate DAM – is currently met by a > Windows-only product: iMatch. > > There is no Windows configuration in which I can safely import either from > a media card in a reader or with a camera USB connected to the PC. I have 2 > cameras: Canon and Fuji. When using a card reader, the reader is never > discovered when I scan for connected devices. The media card is however > identified as a folder, with a drive ID. This is fatal: DT now regards this > drive as part of the database, so the included images become unavailable as > soon as the reader is removed from the PC. But worse – much worse -is that > DT will write on this device as soon as it is selected as a folder. This > awful: here is the scenario: you have taken some valuable photos. Until you > have been able to COPY them into your photo processing system, the ONLY > place they exist is on the media card. But now DT writes data on that card, > over which you have no control (which explains why DT was able to load 72 > of 52 images I thought I had on my card). This is absolutely unacceptable > to me. None of the other raw processors I am testing (Lightroom, Capture 1, > Exposure, DXO, OnOne, DigiKam) will do this (Rawtherapee does). They will > explicitly ask for permission to change the media in any way – usually to > delete images that have been ingested. DT (and RT) are unique in their > inability to differentiate between importing via Copy and importing via > making a link. > > The reason DT treat it as a folder is because the card reader is assigned > a drive letter, being Automounted. Google shows that many people have asked > how to stop this. But more worrying is that there are even more people who > have asked why the techniques to prevent automount do not work in Win 10. > There is no resolution from Microsoft to date for this problem. The best > they can offer is to do trouble shooting, which requires use of the Group > Policy Editor. That is, if you want to find more data to help MS solve the > problem, you have to buy the professional version of Win 10. I’m not going > to do that to solve a problem in DT! The implication from MS’s position is > that this problem does not occur on every PC – so your system my be OK. > None of mine are. > > But is gets worse: if you attempt to disable automount, this actually > works for real hard drives. This knocks out my key backup devices – a set > of large USB drives in a grandfather/father/son usage model. There is no > way I am going to commit updates to my DAM without a functional backup. So > the advice I have received from this mailing list, to disable automount, is > not advice I will follow. > > A not dissimilar
