Andreas Schneider (2019-Apr-28, excerpt):
> Also you should create a git repo in your pictures directory and
> check all XMP files into git! So in cases something goes wrong you
> can go back!
I have stopped doing this. The reason I've started using git for XMPs
was that DT always writes the XMP
Christian (2019-May-01, excerpt):
> 2.6.2.
> Seems I haven't been aware that the talk is about 2.7. :)
Beware, even with 2.7 it depends on what you use, I can reproduce what
Patrick says with release-2.7.0-1080-gbfd635681, but not with
release-2.7.0-222-g8467e4210.
--
http://stefan-klinger.de
Hi,
I've found a couple of minor glitches, but I'm confused about where to
report them. Is that happening on github now (where exactly>), or
still on redmine?
Or should I post them here first? Individual messages, or all in one
email?
Thanks!
Stefan
--
http://stefan-klinger.de
Hi,
for testing I'd like to run DT without installing it, and without
interfering with my setup and foto collection. Installing to an
alternative destination would be ok, but I'd rather just recompile and
run it.
What is needed to achieve this? Currently I have
tmp="/tmp";
# copy some
Florian Hühn (2019-May-02, excerpt):
> If you rerun
> cmake --build './build' --target install -- -j "$(nproc)"
ok. But it is necessary to install, right?
> Just two thoughts about the isolation issue: Maybe consider setting
> LD_LIBRARY_PATH as well to reduce your chances of accidentially mixin
parafin (2019-May-19, excerpt):
> I think dt should just include needed custom fonts and not depend on
> system ones if theme requires specific font.
Imagine every program packing the fonts it likes, each of them in the
version the developer found the time to include. Should the fonts
also be mai
Aurélien Pierre (2019-May-29, excerpt):
> I guess I will have to record video tutorials in English then…
No, please, just write it down. I hate watching videos until the
presenter finally gets to the point. There's already too many videos
and not enough good searchable concise test.
--
http:/
dt-l...@stefan-klinger.de (2019-Jun-04, excerpt):
> and not enough good searchable concise test.
"text", not "test".
Case in point: Text is easier to edit/bugfix/adapt later on.
--
http://stefan-klinger.deo/X
I prefer receiving plain text messages, not e
Hi,
I've drafted [1] an implementation to make "compress history stack" to
also remove all unused modules, i.e., the ones switched off. But
there are some questions:
1. This was so easy to do, maybe it's a bad idea to do this at all?
2. I have derived the SQL from looking at other statement
Julian Rickards (2019-Jun-10, excerpt):
> I have always wondered why "off" modules were included in the compressed
> history stack so I'm in favour of having them removed. When you compress
> the history stack, you lose the details of the history that took you to the
> final stage so losing the "of
para...@paraf.in (2019-Jun-10, excerpt):
> I think we still have default-on modules not recorded in history
> stack (highlight reconstruction and white balance), so removing all
> “off” steps might modify the image.
Hmmm. So if I understand you correctly, the problem is that removing
all unused m
para...@paraf.in (2019-Jun-10, excerpt):
> Another approach is to add exceptions for specific iops, but that’s
> ugly IMHO.
I've implemented exceptions for modules 2 (orientation and highlight
reconstruction) and 3 (white balance), added a checkbox, and added the
default setting to `darktableconfi
Pascal Obry (2019-Jun-10, excerpt):
> Le lundi 10 juin 2019 à 15:05 +0200, dt-l...@stefan-klinger.de a
> écrit :
> >* Maybe "remove unused moduls" and "compress history stack"
> > should be entirely separate operations?
>
> Yes for sure.
Being a good or bad idea in general is a d
thokster (2019-Jun-11, excerpt):
> Hi,
>
> Am 11.06.19 um 15:32 schrieb dt-l...@stefan-klinger.de:
>
> > This option is not about saving disk space, but rather about cleaning
> > up.
>
> Is the "compress history" button in lighttable view doing anything else?
Woha. I have been talking about "comp
Julian Rickards (2019-Jun-11, excerpt):
> I must say that I've never used the Compress History option in the
> Lighttable, just in the Darkroom. Are there any differences?
[see my reply to thokster]
--
http://stefan-klinger.deo/X
I prefer receiving plain te
Patrick Shanahan (2019-Jun-11, excerpt):
> important is to not *break* already processed images by a change.
Yes, I'm aiming at that. AFAIK, my current implementation would not
break anything, see below. (The implementation reachable from
lighttable, which is already in master and was not built
Edgardo Hoszowski (2019-Jun-12, excerpt):
> > Edgardo Hoszowski (2019-Jun-11, excerpt):
> > > I usually want to keep the (off) modules when compressing history,
> > > so the current behavior should be kept.
> >
> > My implementation already takes care about all these exceptional
> > modules I'm awa
Aurélien Pierre (2019-Jun-13, excerpt):
> There is no image if the white balance has been disabled, just random
> bits for debugging purposes. The input color profile expects
> D50-balanced input, and this one is always on. Same with the highlight
> clipping module, most software have it built in t
Hi.
How are modules identified? By number, or by name?
* In the database, the `history` table has fields `module` and
`operation`, see SQL stuff below.
Somehow, this naming led me to the assumption that the modules are
identified by number and offer different operations.
* In t
19 matches
Mail list logo
