ther than the somewhat disorienting way it works now... but don't
forget that you're using a development build... you should be prepared for
things like that. :-)
--
jys
darktable user mailing list
to unsubscribe send a mail to d
xpired" lately, but the situation could be different on different
distros, or maybe even different versions of the same distro.
https://en.wikipedia.org/wiki/FreeType#History
--
jys
darktable user mailing list
to unsu
able-org/darktable/commit/cbb2b1dbfcea60d65ae30c692504e27c8fbb014e
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
On Sat, Oct 3, 2020, at 09:27, Michael Jacobs wrote:
> No jys, it's not the same issue as the one described in the link. I
> did only import raw files, no raw + jpg pairs.
Ah, looking closer at the attached image I see what you meant by "2/3 black"...
by area. That does seem t
ith previous DT are OK.
>
> Compressing the history stack of the affected pictures doesn't always
> fix this issue.
>
> Any hint to fix this ?
https://www.mail-archive.com/darktable-user@lists.darkta
for things that aren't strictly
"configuration"). Also, pay attention to tooltips when hovering over controls
in darktable... they often provide useful information. In this case, the
tooltip for the first module widget shows
On Fri, Sep 25, 2020, at 12:25, Marc Sitkin wrote:
> If so, do I lose my module presets, or are these stored elsewhere? Thanks
Presets are stored in the data.db file.
--
jys
darktable user mailing list
to unsubscr
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
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
onal fallback attempts to handle this case. There's
a fair amount of that going on already, as seen here:
https://github.com/darktable-org/darktable/blob/b2995917b067bf703c2ac46e6e954fe5f1e224a8/src/common/exif.cc#L983
--
jys
_
length (and aperture, if vignetting correction is involved)... for whatever
that's worth.
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
able from a terminal, do you get any
output about invalid Lensfun profiles? Have you modified the slr-nikon.xml
database file (for instance to alter the "173" model name as discussed
elsewhere)?
--
jys
darktabl
us isn't on one of the module
controls. Also, if you haven't hidden the small preview in the upper-left
corner, you'll notice it has a little box representing the current displayed
area... you can drag that around.
--
jys
___
yours and see
if anything looks funny...
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
rences dialog and didn't have any
problem, FWTW.
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
into the pipe, I guess...
in any case it seems to work well for me.
...and I would also echo the appreciation for the general improvements in this
area. I'm happy with the rendering from just exposure+filmic for all but a few
cases now.
heory"... but ultimately what matters is that you get results that you like,
of course. :-)
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
er, and probably especially so if your "scanner" is a
15-year-old sensor with a base ISO of 200.
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
rst one, which also uses the color balance module to further
correct some of the extreme color cast into something a little more neutral.
Note the use of the parametric blend to constrain the processing to the shadow
areas. You could do even better with more time spent on the maskin
ers instead of moving a curver around. Improvements
to filmic in the upcoming 3.2 release allow you to get similar to camera output
more easily (without needing the color balance module for increasing
saturation), so watch for that if you adopt this approach.
--
jys
_
camera to be adequate for
general purposes now, using the linear RGB workflow with the
soon-to-be-released filmic v4... the fact that many of the worst indoor light
sources seem to be improving these days also helps reduce the need to profile
for that reason.)
-
s, but switching to 'no' makes flat colors. Can anybody explain
> this behavior to me?
This thread isn't specifically about that, but discusses some of the current
thinking about the situation:
https://discuss.pixls.us
On Sat, Jul 25, 2020, at 10:57, Mikael Ståldal wrote:
> Which Darktable module(s) are useful?
This is a good place to start if you're interested in the benefits of the
"linear RGB" workflow:
https://pixls.us/articles/darktable-3-rgb-or-lab-which-modules-help/#navl
"applied".That's what the history stack is for.
Anyway, so much has changed with all of these things that I can't even remember
exactly how things were in 2.6.2 anymore, so that's about all I can tell you,
sorry. ;-)
--
jys
__
ule could
be useful here? By default darktable tries to include as much valid pixel area
as possible.
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
cause the black level control isn't set by the
auto-adjustment... but you could check it out.
Also, for whatever it's worth, there's instructions for doing something like
what you describe with Gimp here:
https://photo.stackexchange.com/questions/63692/how-can-i-get-a-uniform-white-balance-on-a-ba
because nobody else could reproduce, and
I concluded it was something weird about my somewhat messy Slackware system.
I'll reopen it, you can add your observations there:
https://github.com/darktable-org/darktable/i
There's more information about using enfuse here:
https://patdavid.net/2013/01/focus-stacking-macro-photos-enfuse.html
On Mon, Apr 20, 2020, at 03:29, Frank J. wrote:
> I do focus-stacking with the following workflow:
>
> 1. Export minimal pre-processed pictures of the stack from darktable
along with a few other missing GUI elements... but the first
thing to check would be the setting of darktable preferences > GUI options >
darkroom > "show search module text entry" (or the setting
"plugins/darkroom/search_iop_by_text=show gro
iop ordering into a form which can be managed as presets, etc... you
can revert to pre-3.0 ordering or save your own custom orderings. I don't know
if it will be in a release before 3.2 though. For a discussion similar to
yours, see https://github.com/darktable-org/darktable/issues/3
graphical
shells. Due to the overwhelming use of this analogy, it may sometimes be used
to refer to directories even without the specific context of a graphical shell,
but for native speakers at least, the actual meaning is very easily understood.
--
jys
__
hown as (368)).
If exiv2 isn't producing a name for matching, LensFun has nothing to match. If
your exiv2 version is at least 0.26 you can provide your own mapping as
explained here:
https://dev.exiv2.org/projects/exiv2/wiki/Lens_Recognition_in_Exiv2_v026_(and_lat
the pipe using the legacy order, the new one
> introduced in dt 3.0 (and also creating presets).
One other thing to be aware of if you've been using module re-ordering along
with copy/paste: copying from an image with a custom module ordering now does
not apply the custom ordering to the past
the IV version can comment on
this (preferably at the github link, since it's not strictly a darktable topic,
but otherwise here) it would be appreciated. Thanks!
[1]
https://github.com/lensfun/lensfun/commit/8f194dadf50b95506c0d60ae8e87614b9bd1586e
--
jys
DT export process. I thought
> that at this stage, the file was not yet copied to it final destination
> and I searched the temporary file. Thank to point me again on this.
> For my "exif" need, I'll use this solution.
>
> Regards,
> Fabrice.
>
> On 27/01/2020 18:
nly strings. I'm not sure what the best method would be
for reliably locating the value you want... maybe ask on exiftool forums?
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
on (event, image, filename, format, storage)
os.execute("exiftool" .. filename )
end
)
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
t-very-intuitive behavior where a hovered item overrides other selection...
it can be quite hazardous when deleting. I prefer keyboard shortcuts in
general, but have trained myself to click buttons for these operations mostly
because of this "feature
orruption which you can
describe in detail, you should probably post an issue at github. FYI, there
should be backups of the databases in your config folder, renamed with an
appended version string, if you need to recover and didn't create backups
yourself (which you really should do before
t that
filmic RGB is an excellent way to *make further adjustments* is reason enough
to try to integrate it, IMHO.
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
applied (and it sounds like it's being done correctly here, just not
automatically for some reason).
Maybe there's an issue with the darktable build itself... is this the package
that was mis-versioned as 2.6?
--
jys
r in the processing order, but they shouldn't be large or "bad"
differences.
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
else can try to reproduce the problem with it.
If they can't, there's something else weird in your set-up (bad auto-preset?).
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
On Fri, Jan 10, 2020, at 10:11, dt-l...@stefan-klinger.de wrote:
> jys (2020-Jan-09, excerpt):
> > If you're using a darktable version from after the panel-dragging
> > was added, you should also have numbered versions of those,
> > something like:
&
ns of those, something like:
darkroom/ui/0/panels_collapse_controls=FALSE
lighttable/ui/1/panels_collapse_controls=FALSE
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Arch Linux
> Intel Xeon E3-1535M v5
> Nvidia Quadro M2000M, Driver 440.44
> darktable 3.1.0+289~gf788bfff3
>
>
>
> darktable user mailing list
> to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
>
>
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
age).
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
s after shooting a WB target under different lighting
conditions).
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
used with together, but I'll add the extra precision just in case
there's a GR IV with the same lens and different sensor some day. Thanks for
testing.
--
jys
darktable user mailing list
to unsubscribe send a mail
little things with fixed-lens profiles that are needed
to work right in darktable; the one that's not obvious from observation of
examples is that the mount name should start with lowercase.)
--
jys
darktable user mailin
, I tore the relevant part of my Lua mess out and posted it here a while
back:
https://www.mail-archive.com/darktable-user@lists.darktable.org/msg07784.html
--
jys
darktable user mailing list
to unsubscribe send a mail
changed in the new 3.0 manual if it hasn't been already.
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
0.3.95/structlfDatabase.html#a3cfbcf0233c39ec4cbdf89386f0ecb40
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
iew buttons to see all modules in order).
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
On Mon, Nov 11, 2019, at 12:27, jys wrote:
> I haven't tested using 3.0 sidecars in 2.6, but it doesn't
> seem like a sane thing to do... at the very least, much of the
> information about editing history would be useless.
I just did a quick test of ingesting 3.0 XMP files i
the *.xmp files to *.xmp-26 or
similar, which should be easily reversible (or purgeable) if you want to use
sidecars with 3.0.
My guess is once you go 3.0, you won't go back (I don't think I could at this
point), but I would consider waiting a bit for rc1, since there's been quite a
fe
n off XMP creation in
preferences, probably in the 2.6 version just before upgrading). I haven't
tested using 3.0 sidecars in 2.6, but it doesn't seem like a sane thing to
do... at the very least, much of the information about editing history would be
useless.
, it's easiest/cleanest to just back up that
whole directory by whatever means you prefer.
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
and probably on github rather than
redmine). There have been many interesting changes to the lighttable view. :-)
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
If, like me, you would rather not have those arrow buttons on the screen, you
can now hide them. Look in darktablerc for 'panels_collapse_controls' in the
various views, and set the ones you don't want to see to "FALSE".
--
jys
___
s don't install directly to the system, but rather to a
"package" directory, which is then converted to an actual package with the
usual Slackware tools. You can then install/uninstall/update/archive this
package
irectory useful, too. :-)
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
ember if this
feature was in the last release or not, but without it you need to make the
window actually slightly larger than the screen for this to work on both sides.
--
jys
darktable user mailing list
to unsubscribe se
On Tue, Sep 3, 2019, at 11:48, jys wrote:
> That path is releative to the "src" directory, adjust accordingly.
Oops, actually the base git directory.
--
jys
darktable user mailing list
to unsubscrib
ens falloff... it's worth emphasizing that
modules should NOT be re-arranged just for UI convenience purposes, because
doing so will alter the actual processing order.
Anyway, that's what comes to mind, hopefully it gives a starting point for
further exploration.
--
jys
__
is reflecting not only any changes you make to levels, but
also any other operations which happen later in the "pipe" (higher in the
module list) than "levels"... this includes the channel mixer module.
--
jys
__
rrection module, which needs this information,
the crop factor is taken from the LensFun database, so you probably don't need
to worry, FWIW.
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
s when
I've wanted to do this. The alternative is allowing a margin, then final
cropping with an external application, which isn't terribly convenient.
--
jys
darktable user mailing list
to unsubscribe send a mail to da
ser-friendly based on this,
it can be considered public domain for that purpose. Short of that, it should
be considered pseudo-code... please don't attempt to use it if you aren't
already comfortable with Lua scripting.
--
jys
__
ion to do that on export, currently.
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
ction operators... maybe you meant
this one:
https://www.youtube.com/watch?v=tMn37-xf6X0
I really don't love youtube tutorials as a way of learning myself, but if I had
to, his are pretty good! There's a lot of time spent on "global tonemap",
though, only to dismiss it, so maybe skip to
map module, or the "fusion" feature of
the basecurve module (which can be used even with a "flat" basecurve). For a
more film-like mapping, try the "filmic" module, maybe in conjuction with
"local contrast". Of course, you can use a
On Sun, Jun 9, 2019, at 02:38, dt-l...@stefan-klinger.de wrote:
> jys (2019-Jun-08, excerpt):
> > master has an option to not apply base curves
>
> Awww, did not see this being added — all work for nothin...
But you can do more with an auto-applied style than just di
to" on
import, but I never bothered to add this to my import script since current
master has an option to not apply base curves, and I find that auto-presets
work for everything else. :D
--
jys
darktable user mailing
harder things than that in git master
lately. Just sayin'.
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
both are potentially useful in different use cases.
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
ith the same operators that work with ISO, etc would
be great. Potentially a GUI in the form of a bounding box on the map could
eventually be added.
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-u
e Between 45.84 and 45.88
> and
> image-Longitude Between -84.60 and -84.65
I'm afraid the geotagging filter is simply a boolean (true or false) value...
it doesn't actually evaluate the location data beyond whether it exists or not.
It's an interesting ide
curve instead of base curve, which gives much better
results. It also uses the color lookup table module for color adjustments at
the same time. You can use either of these independently of the other by
applying the resulting style, then saving the settings in the
Those shortcuts aren't in a release version yet, but TAB is.
On Sat, Jun 1, 2019, at 05:56, jjb wrote:
> Thanks, but that does not work for me. On Fedora 30. VERSION 2.6.2-1.fc30
>
> On 6/1/19 1:56 PM, Patrick Shanahan wrote:
> > * jjb [06-01-19 06:41]:
> >> I would like to see panels in
>From the ExifTool release notes;
> CORRUPTION WARNING: Patched problem where Canon DPP would destroy a CR3 image
> if the file had previously been edited by DPP then Exiftool. (If you have
> edited any CR3 images with ExifTool that had been previously edited by DPP,
> then re-edit with
rve + color lookup table (such as produced by using
darktable-chart utility), and some use the newer filmic module in place of the
tone curve. The curves should be a good fit, the color profiling may be more
camera-specific.
--
jys
_
to be a directly equivalent method, but
there may be a way of obtaining similar results using the methods that are
available.
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
type. There's an example of that here:
https://darktable.gitlab.io/doc/en/lua_chapter.html#lua_storage_example
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
ustment when you want it. Again, this is probably not exactly how
the author intended it to be used, so keep that in mind as you find your own
optimal workflow. :)
--
jys
darktable user mailing list
to unsubscribe
te what basecurve does (and
in that case, you might want to just stick with basecurve).
Anyway, attached is a quick and dirty attempt to at least get the filmic curve
into the same ballpark as the basecurve, as a place to *start* with a
comparison,
might make
sense to give the user some options in the GUI about where to store it. Some
people may want to keep it in a root image directory, for instance, to
facilitate backup or transport along with those images... maybe even an opti
On Sun, Mar 24, 2019, at 17:25, jys wrote:
>
> According to the API, the lua combobox widget can be set as editable =
> true, but I can't seem to make this actually work. If there's anything
> wrong in combobox.c, I'm not smart enough to find it. Am I missing
> something?
A
via CSS?
I also noticed that the online API docs haven't been updated with recent fixes
(although the PDF version has been).
Thanks for any help,
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable
ght vision: all nodes in curve set to zero, blue shift 0%
> - soften: size 0%, saturation 0%, mix 100%
> - colorize: saturation 0, source mix 100%
> - vignetting: saturation -1, scale 0%, fall-off strength 0%
don't f
that the "changed" tag is added in some cases even when no
manual edits have been made by the user in darkroom mode, so it's possible you
don't actually have any "untouched" images (as far as darktable is concerned).
This is fixed in current master; see
https://github.com/da
On Thu, Mar 7, 2019, at 22:55, Pascal Obry wrote:
> Le vendredi 08 mars 2019 à 01:30 -0500, jys a écrit :
> > I also noticed that the lens correction module now also allows
> > multiple instances, so there's potential for awesome here.
>
> I don't see this here.
You
webs obsolete. :P
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
It's not just you, anyway.
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
by default for fixed-lens cameras would
make sense, since there's no problem with lens ID ambiguity, and many such
cameras really need the correction to produce usable images (having been
designed with the assumption that it will be applied).
--
jys
_
hare/lensfun on linux, and I believe
darktable/lensfun on Windows).
As you've found, the presets on that module don't play nicely with
auto-selection... if that module ever gets some love from developers, that
might be something that could be
ker/histogram always
use the profile that the soft proofing toggle is set to (whether soft proofing
is enabled or not)? Or would changing to this behavior be to dispruptive to
existing workflows?
--
jys
darktable user mailing
shipping these with darktable has
been deprecated, hence the lack of updates to colormatrices.c in recent years.
Some of what's in there probably shouldn't be, but removing it now could break
some existing stacks, so... there you go
ion about that here:
http://www.imatest.com/docs/veilingglare/#target
--
jys
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
a truly dark space beyond it. The
best way to keep light spill off of the "black" area is for there to be nothing
there for light to hit. ;)
--
jys
darktable user mailing list
to unsubscribe send a mail to d
1 - 100 of 112 matches
Mail list logo
