Re: [darktable-dev] Russian translation - po edit issue

[Timur Irikovich Davletshin]

Good evening Yana,

Actually, I was planing to push update by the end of the week. I'm very
sorry for missing 3.8 release, I was away from Russia and had no time
to do it well.

This topic is language-specific and others are not very interested. So
you can address me directly in Russian.

Timur.

On Wed, 2022-02-23 at 22:06 +0700, Яна Тунгушпаева wrote:
> Hi all!
> I'm trying to start doing a translation into Russian, but I've never
> used po edit before.
> I followed this instruction 
> https://github.com/darktable-org/darktable/blob/master/doc/TRANSLATORS.md
>  but when I try to update from POT file, I only see 23 or so
> untranslated strings (screenshot attached).
> Could someone kindly tell me what I'm doing wrong? What could be
> wrong?
> Thank you in advance for your help!
> Have a nice day!
> 
> 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] OBS → Stable branch snapshots

[Timur Irikovich Davletshin]

Nope, I'm not. I need snapshots from the stable release branch (future
3.4.1), not the  stable release branch.

Timur.

On Fri, 2021-01-15 at 18:23 +0100, Nicolas Auffray wrote:
> You are just on wrong repository for official 3.4.0 release.
> The 3.4.0 stable release is on darktable repository in Opensuse: 
> https://software.opensuse.org/download.html?project=graphics:darktable=darktable
> And not in darktable:stable one. In that one, you have the 3.4.0-
> git15 that you note.
> You could see all repositories regarding your distrib in that page
> (click on display experimental packages (yellow button):
> https://software.opensuse.org/package/darktable
> 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] OBS → Stable branch snapshots

[Timur Irikovich Davletshin]

It's like one year ago...

Latest 3.4 branch via OBS is darktable_3.4.0~git15.b2a685928_amd64.deb
Latest 3.4 via github is 0e4ecc1

Master branch builds are fine.

Timur.

On Fri, 2021-01-15 at 13:54 +0100, Andreas Schneider wrote:
> On Friday, 15 January 2021 09:49:33 CET Timur Irikovich Davletshin
> wrote:
> > Dear developers (darix?), any chance of getting updates for stable
> > release branch snapshots on OBS? Builds are not working for quite a
> > while.
> 
> Can you please be more precise?
> 
> The only failing build is currently Debian_Next ...
> 
> https://build.opensuse.org/package/show/graphics:darktable:stable/darktable
> 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] OBS → Stable branch snapshots

[Timur Irikovich Davletshin]

Dear developers (darix?), any chance of getting updates for stable
release branch snapshots on OBS? Builds are not working for quite a
while.

Timur.

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Bug spotted in color calibration normalization

[Timur Irikovich Davletshin]

Thank you Aurélien for letting us know about the bug! But I'm sure very
few users read developer mailing list. It's worth releasing urgent bug
fix release in order to reduce impact on user edits.

On Fri, 2021-01-08 at 19:45 +0100, Aurélien Pierre wrote:

> Let me know if that deeply messes-up your current edits, so we can
> find a solution, and please don't use normalization on green and blue
> channels until darktable 3.4.1 is released (which should be soon
> because we already have a load of bugfixes).



___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] White-ish 1px border around selected photos in lighttable

[Timur Irikovich Davletshin]

Mica, it is totally your right. But sending both public and private
letters to every new user about what someone thinks is a good mannered
behavior is a little bit annoying. Especially from someone who is not
affiliated with mailing list administration.

On Thu, 2020-10-08 at 15:51 -0700, Mica Semrick wrote:
> Instead of being so smug, Timur, you could follow the one rule you 
> should be following already:
> 
> 1. Be an adult
> 
> I guess I need a mail rule to move your message into the trash
> though, 
> so I can avoid having my inbox flooded by such childish nonsense.
> 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] White-ish 1px border around selected photos in lighttable

[Timur Irikovich Davletshin]

Mica, solution is simple:

1. Don't be embarrassed to express you ideas about people abusing their
rights of using email attachments. Discuss the issue.
2. Make it into "law" - https://www.darktable.org/ (how to get in
contact section) and probably mailing list footer.
3. Punish - strip off attachments of bigger size.
4. Forget about the issue.

On Wed, 2020-10-07 at 22:21 -0700, Mica Semrick wrote:
> Seriously, you two have to stop. It is embarrassing.
> 


___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] White-ish 1px border around selected photos in lighttable

[Timur Irikovich Davletshin]

Speak for yourself. I'm sure others can express their feelings about
such letters without your help. Gosh, man, lecturing every new person
on good manners after receiving mail attachment? Patrick, adjust your
attitude, don't act like an old fart.

On Wed, 2020-10-07 at 17:36 -0400, Patrick Shanahan wrote:
> 
> Ah, yes, doesn't exist for YOU.  Have some consideration for others
> that
> yourself.  I believe there is a word for that, ... 
> 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] White-ish 1px border around selected photos in lighttable

[Timur Irikovich Davletshin]

So you're complaining about the problem which doesn't exist!

臘‍♂

On Wed, 2020-10-07 at 16:44 -0400, Patrick Shanahan wrote:
> It's not a matter of opening them, my mail service delivers to my
> private
> server.  I automagically receive all mail and ensuing traffic.  
> and it was 122kb, not 95kb.
> 
> Please have some respect for others than yourself.
> 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] White-ish 1px border around selected photos in lighttable

[Timur Irikovich Davletshin]

Patrick, come on! Not again.

1. Not your private mailing list and there are no rules regarding
message format, size, etc.
2. IMAP clients use partial fetch, no need to download unwanted
messages. Just don't open them if you're on measured service in the
middle of the ocean :)
3. 95 kB message in 21 century in photo community? Seriously?

With all respect,

Timur.

On Wed, 2020-10-07 at 15:43 -0400, Patrick Shanahan wrote:
> 
> very ill mannered to post large files to the mailing list.  Some may
> be on
> measured service and not even be interested in your pictures.
> 
> post large files to a file-sharing service and provide the url.
> 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Nikon D80: Blown out highlights shown and exported in pink color ?

[Timur Irikovich Davletshin]

Hi, Rainer.

Try changing base curve module settings "preserve colors" from
"luminance" (which is new default) to "none" (old behavior). New one
can produce highlight clipping in high key shots.

Timur.

On Tue, 2020-09-29 at 09:51 +0200, Rainer Krienke wrote:
> Hello,
> 
> recently I wanted to reedit a photo from 2008 taken with a Nikon D80.
> When opening the raw with darktable 3.2.1 (in darkroom as well as
> lighttable) I observed that in the mostly unprocessed raw, areas with
> blown out highlights are shown in pink color, not white.
> 
> Exporting this raw to jpg results in a jpg where the pink areas are
> also
> visible just like in darktable.
> 
> I created a screen shot to show you this problem. Its available by:
> https://userpages.uni-koblenz.de/~krienke/tmp/dt/Screenshot_20200928_093618.png
> 
> I found out that if I disable the white balance module the pink color
> turns to white but as soon as I activate WB again those areas are
> also
> getting pink again, so I cannot correct it without seeing "pink".
> 
> I opened the raw photo with the raw converter I used those days which
> was Aftershot Pro and it shows these areas as white which is what I
> would have expected.
> 
> Bug? Any ideas?
> 
> Thanks
> Rainer

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Adjustable panel width removal

[Timur Irikovich Davletshin]

Wow, I'm not used to this approach in darktable.

Best wishes for this year!

On Sat, 2020-01-04 at 09:45 +0100, Jean-Luc Coulon (f5ibh) wrote:
> Hi,
> Because you can now adjust it from the gui by grabbing the limit and
> move it around...
> 
> J-L
> 
> Le sam. 4 janv. 2020 à 09:19, Timur Irikovich Davletshin <
> timur.davlets...@gmail.com> a écrit :
> > Good Saturday morning dear developers!
> > 
> > What is the reason of removing adjustable panel width in recent
> > commits
> > both to master and 3.0 branches? Was something broken?
> > 
> > Thanks in advance,
> > 
> > Timur.
> > 
> > ___
> > 
> > darktable developer mailing list
> > to unsubscribe send a mail to 
> > darktable-dev+unsubscr...@lists.darktable.org
> > 
> 
> _
> __ darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Adjustable panel width removal

[Timur Irikovich Davletshin]

Good Saturday morning dear developers!

What is the reason of removing adjustable panel width in recent commits
both to master and 3.0 branches? Was something broken?

Thanks in advance,

Timur.

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] OBS → Update builds

[Timur Irikovich Davletshin]

Dear developers, any chance of getting update for builds on OBS? Master
branch is fine but stable release branch and latest release are
old (2.6.3 and 2.6.2 respectively).

Congratulations with fresh release!

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Debian builds → proper naming

[Timur Irikovich Davletshin]

Nicolas, I'm talking about builds provided by dt developers — 
https://software.opensuse.org/download.html?project=graphics:darktable:master=darktable

Timur.

On Thu, 2019-12-05 at 15:01 +0100, Nicolas Auffray wrote:
> Hi Timur,
> 
> Maybe but linux packages builds are not related to darktable teams.
> For 
> Debian builds, you have to see that with Debian team, not darktable
> one.
> 
> 
> Le 05/12/2019 à 05:08, Timur Irikovich Davletshin a écrit :
> > Hi developers!
> > 
> > It can be considered as a bug since creators of darktable insist on
> > lower case spelling. Debian builds use "Darktable" spelling which
> > should be fixed.
> > 
> > Timur.
> > 
> > ___
> > 
> > darktable developer mailing list
> > to unsubscribe send a mail to 
> > darktable-dev+unsubscr...@lists.darktable.org
> > 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Debian builds → proper naming

[Timur Irikovich Davletshin]

Hi developers!

It can be considered as a bug since creators of darktable insist on
lower case spelling. Debian builds use "Darktable" spelling which
should be fixed.

Timur.

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Base curve → New defaults

[Timur Irikovich Davletshin]

Hi developers!

I noticed that new imports (3.0 branch) have odd color casts in
hightlights due to changed defaults in base curve module. Preserve
color = luminance is the one which causes problems. I'm not telling
that it is a bug, I'm questioning using it as default settings because
color rendering with such settings is far from builtin JPEG (which is a
good start for editing).

Thank you in advance,

Timur.

P.S. for example import this 
https://discuss.pixls.us/t/playraw-autumn-island/4288 image and play
with preserve color in base curve module. Compare results with builtin
JPEG.

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Debian → Empty tools directory

[Timur Irikovich Davletshin]

Hi developers!

There is no need to create empty directory /usr/lib/darktable/tools if
tools are not supplied in Debian builds:

https://software.opensuse.org/download.html?project=graphics:darktable:master=darktable

Thank you dealing fast with previous issue with lost translations,

Timur.

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Filmic (RGB or not) explained

[Timur Irikovich Davletshin]

Thank you a lot! It was most instructive.

Timur.

On Sun, 2019-12-01 at 01:08 +0100, Aurélien Pierre wrote:
> Hi,
> This is my video on filmic RGB, explaining how it works and how to do
> it in real-life cases: 
> https://www.youtube.com/watch?v=zbPj_TqTF88=youtu.be I hope
> it resolves most of the misunderstandings and trial-errors sessions
> that always end-up in frustration.
> A shorter addendum is on the way to explain specifically to users of
> darktable 2.6 what changed between the 2.6 and 3.0.
> Cheers,
> Aurélien.
> 
> _
> __ darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Debian builds → Translation files

[Timur Irikovich Davletshin]

Hi developers!

All translation files are gone from Debian builds since yesterday:

https://software.opensuse.org/download.html?project=graphics:darktable:master=darktable

Thank you in advance,

Timur.

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Database backups question

[Timur Irikovich Davletshin]

But it's created all the time. What is the point of that? I'm already
on 3.0 why create new backups every time?

On Mon, 2019-11-25 at 17:34 +0100, Pascal Obry wrote:
> Hi Timur,
> 
> > I'm a bit confused by files with suffix "-pre-3.0.0" in profile
> > directory. Is it some sort of safety feature create them all the
> > time?
> > I understand that we have to make backups before migration but
> > what's
> > the point of creating them for fresh library?
> 
> It is a backup. As you have used the dev version this is certainly
> not
> very useful for you. But for all new users migrating from 2.6 to 3.0
> it
> is expected to be a good thing!
> 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Monochrome Module - issues

[Timur Irikovich Davletshin]

Mouse works fine for me in monochrome module dt 3.0 builds.

Timur.

On Mon, 2019-11-25 at 14:14 +, Richard Hobday wrote:
> 3.0.0rc1+84~g801c58d80
> Mint 19 (Ubuntu 18.04)
> 
> I seem to have lost the ability to use the mouse in the Monochrome
> Module.
> 
> Scrolling within the module simply moves the 'circle' around but does
> not resize as  in 2.6.2.
> 
> Anyone else able to reproduce this?
> _
> __
> darktable developer mailing list
> to unsubscribe send a mail to 
> darktable-dev+unsubscr...@lists.darktable.org
> 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Database backups question

[Timur Irikovich Davletshin]

Hi developers!

I'm a bit confused by files with suffix "-pre-3.0.0" in profile
directory. Is it some sort of safety feature create them all the time?
I understand that we have to make backups before migration but what's
the point of creating them for fresh library?

Timur.

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: Fwd: [darktable-dev] Cameras listed in Lens Correction module

[Timur Irikovich Davletshin]

Glad it helped. Sure it's good to have it in auto, but you can choose
any camera with same sensors type and lens mount. I believe it's the
only thing which matters.

Timur.

On Sun, 2019-11-24 at 22:09 +1100, Bruce Williams wrote:
> Thanks Timur!
> That did the trick. :)
> Cheers,
> Bruce Williams
> --
> 
> 
> audio2u.com
> brucewilliamsphotography.com
> shuttersincpodcast.com
> sinelanguagepodcast.com
> 
> e-mail | Twitter | LinkedIn | Facebook | Soundcloud | Quora
> --
> 
> 
> 
> 
> -- Forwarded message -
> From: Timur Irikovich Davletshin 
> Date: Sun, Nov 24, 2019 at 10:07 PM
> Subject: Re: [darktable-dev] Cameras listed in Lens Correction module
> To: 
> 
> 
> Update your lens data via "lensfun-update-data" if it's not there...
> well, https://github.com/lensfun/lensfun — file bug report.
> 
> Timur.
> 
> On Sun, 2019-11-24 at 21:58 +1100, Bruce Williams wrote:
> > Hi all,
> > Who do we talk to re: cameras missing from the above-named module?
> > I shoot with an a7iii, which is now a 12 month old camera at least,
> > and yet, even in 3.0 rc1, it is not listed in the Lens Correction
> > module's camera drop-down list.
> > Cheers,
> > Bruce Williams
> > 
> > --
> > audio2u.com
> > brucewilliamsphotography.com
> > shuttersincpodcast.com
> > sinelanguagepodcast.com
> > 
> > e-mail | Twitter | LinkedIn | Facebook | Soundcloud | Quora
> > --
> > 
> > 
> > 
> >
> _
> > __ darktable developer mailing list to unsubscribe send a mail
> to
> > darktable-dev+unsubscr...@lists.darktable.org 
> 
> _
> __
> darktable developer mailing list
> to unsubscribe send a mail to 
> darktable-dev+unsubscr...@lists.darktable.org
> 
> 
> _
> __ darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Cameras listed in Lens Correction module

[Timur Irikovich Davletshin]

Update your lens data via "lensfun-update-data" if it's not there...
well, https://github.com/lensfun/lensfun — file bug report.

Timur.

On Sun, 2019-11-24 at 21:58 +1100, Bruce Williams wrote:
> Hi all,
> Who do we talk to re: cameras missing from the above-named module?
> I shoot with an a7iii, which is now a 12 month old camera at least,
> and yet, even in 3.0 rc1, it is not listed in the Lens Correction
> module's camera drop-down list.
> Cheers,
> Bruce Williams
> 
> --
> audio2u.com
> brucewilliamsphotography.com
> shuttersincpodcast.com
> sinelanguagepodcast.com
> 
> e-mail | Twitter | LinkedIn | Facebook | Soundcloud | Quora
> --
> 
> 
> 
> _
> __ darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] histogram and file export are broken in git master

[Timur Irikovich Davletshin]

I confirm.

All new imports are black. Linux, builds from 
https://software.opensuse.org/download.html?project=graphics:darktable:master=darktable

Timur.

On Sat, 2019-11-23 at 14:59 +0100, Pascal Obry wrote:
> Alexander,
> 
> > An image is displayed correctly in the darkroom, but the histogram
> > shows
> > it is almost black and the resulting file is black too.
> 
> I cannot reproduce this. Can you open a GitHub ticket and tell us
> more
> about the context? Profile used? RAW ? Export profile? etc...
> 
> Thanks,
> 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] 3D LUT → segmentation fault

[Timur Irikovich Davletshin]

Hi developers!

Can anyone confirm dt master builds segmentation fault on loading big
HaldLUT file like this? Unlike other files from that source it is twice
bigger.

File: 

https://drive.google.com/open?id=1WoPFoouBbJlbQa5VsWXiT2kPJMH5NREI

File comes from:

http://rawpedia.rawtherapee.com/Film_Simulation#RawTherapee_Film_Simulation_Collection

Thanks in advance,

Timur.

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] UI glitches → Buttons and stuff

[Timur Irikovich Davletshin]

Good evening developers!

Coming back to this topic. There is another harbor of buttons with
wrong order I've discovered.

Steps to reproduce:

1. Open lighttable mode → tagging module.
2. Create any tag if list of available tags is missing.
3. Right click on created tag:
a) "delete tag" action opens confirmation window with reversed
button order. Same for "delete branch".
b) "create tag..." opens dialog window with reversed button
order. Same for "edit tag...".

Timur.

On Mon, 2019-11-11 at 12:57 +0100, Nicolas Auffray wrote:
> Hi,
> At Timur, please test my PR here : 
> https://github.com/darktable-org/darktable/pull/3362
> sams96 replies this day that my PR fix this. I never had this issue
> so that was not the purpose on start but if it helps !
> Have a good day
> 
> Le 11/11/2019 à 03:57, Sam a écrit :
> > Hey Timur, I opened an issue on github for this, but it seems like
> > it's just you and I that see this so I was wondering what OS and
> > maybe DE you're using?
> > 
> > Thanks
> > 
> > On Fri, 8 Nov 2019 at 02:49, Timur Irikovich Davletshin <
> > timur.davlets...@gmail.com> wrote:
> > > Buttons in following darkroom modules require fixing too:
> > > 
> > > vignetting, rgb levels, levels, color mapping, basic adjustments.
> > > 
> > > Timur.
> > > 
> > > On Thu, 2019-11-07 at 15:09 +0800, Sam wrote:
> > > > I've added fixes to a couple of these to my pull request here.
> > > > 
> > > 
> > > 
> > 
> > ___
> >  darktable developer mailing list to unsubscribe send a
> > mail to darktable-dev+unsubscr...@lists.darktable.org 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] UI glitches

[Timur Irikovich Davletshin]

Man come on! The point is in the topic. I copy it for you: "UI
glitches". It is not about your wishes.

I told you already, once you manage to get your rules to official dt
page people will be more likely to respect them: 
https://www.darktable.org/contact/#how-to-get-in-contact

You just scarring off new users by your letters. You send it to EVERY
user who sends attachments in letters.

Hugs and kisses,

Timur.

On Tue, 2019-11-19 at 08:54 -0500, Patrick Shanahan wrote:
> * Timur Irikovich Davletshin  [11-19-19
> 08:41]:
> > Perhaps rather than scaring off every new user on mailing list with
> > your letters you will concentrate on something else.
> > 
> > On Tue, 2019-11-19 at 08:30 -0500, Patrick Shanahan wrote:
> > > * Timur Irikovich Davletshin  [11-19-
> > > 19
> > > 08:23]:
> > > > Patrick, I believe we already discussed it.
> > > > 
> > > > On Tue, 2019-11-19 at 08:02 -0500, Patrick Shanahan wrote:
> > > > > please utilize a file-share service rather than uploading
> > > > > large
> > > > > files to everyone on the list
> > > 
> > > I believe "discussed" is a bit of a stretch.  Why don't you
> > > create
> > > issues and attach needed examples there and provide the dev's
> > > with a
> > > more singular place to watch instead of expecting them to react
> > > to
> > > bloated emails?
> > > 
> > > ps: announced recently that the dev's are quite busy, perhaps
> > > rather
> > > minor nit-pics might be postponed until the major problems are
> > > solved.
> > >   
> 
> ah, when lacking a proper response, divert attention to something
> else
> which is also irrelevant.
> 
> --> /dev/null

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] UI glitches

[Timur Irikovich Davletshin]

Perhaps rather than scaring off every new user on mailing list with
your letters you will concentrate on something else.

On Tue, 2019-11-19 at 08:30 -0500, Patrick Shanahan wrote:
> * Timur Irikovich Davletshin  [11-19-19
> 08:23]:
> > Patrick, I believe we already discussed it.
> > 
> > On Tue, 2019-11-19 at 08:02 -0500, Patrick Shanahan wrote:
> > > please utilize a file-share service rather than uploading large
> > > files
> > > to everyone on the list
> 
> I believe "discussed" is a bit of a stretch.  Why don't you create
> issues
> and attach needed examples there and provide the dev's with a more
> singular place to watch instead of expecting them to react to bloated
> emails?
> 
> ps: announced recently that the dev's are quite busy, perhaps rather
> minor
> nit-pics might be postponed until the major problems are solved.
>   

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] image information → export width/height

[Timur Irikovich Davletshin]

Hi dear developers!

What is the point of "export width" and "export height" in "image
information"? It seems to be straightforward but no matter what I do
they remain just zeroes. Is it not working the way it was meant to be
or I miss something?

Thank you in advance,

Timur.

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] TIFF compression level

[Timur Irikovich Davletshin]

Hi Diederik!

Well, this is what I see every start. System: Debian 10, I tried
starting with empty profile. Will you remove that single line of code?

Thanks for quick reply,

Timur.

On Mon, 2019-11-18 at 21:23 +, Diederik ter Rahe wrote:
> Hi Timur, Pascal,
> 
> I used to see this when I was working on the patch. At the time,
> there was an issue caused by some module->gui_init routines
> resetting darktable.gui->reset to 0 on exit, rather than resetting it
> to the value it had on entrance. Which would lead the next gui_init
> routine to be called with reset=0 and this would then start showing
> toasts.
> See here 
> https://github.com/darktable-org/darktable/pull/2788#issuecomment-513164959
> 
> I thought I had cleaned all of these cases up, so there wasn't
> anything left to fix at start time and I don't see any spurious
> toasts myself (Windows rc1 build). Do you see it in latest master?
> There may have been a regression regarding this in any of the modules
> called before "TIFF module->gui_init". TIFF is just the last one in
> the loop, I believe, which is why that's the toast that remains on
> the screen. Unfortunately I haven't got a build environment set up at
> the moment so can't quickly check...
> 
> Best,
> Diederik
> 
> 
> On Monday, 18 November 2019, 18:38:18 GMT, Pascal Obry <
> pas...@obry.net> wrote:
> 
> 
> Hi Timur,
> 
> > What is the point of giving user notification on dt start about
> TIFF
> > compression level? 
> 
> No point. That's a side effect of the toast being displayed when
> changing module sliders from a key without opening the module.
> 
> Some of this has already been fixed by Diederik (in CC).
> 
> There is more to fix at start time.
> 
> I don't have time to look at this. Diederik, do you think you can
> have
> a look?
> 
> Thanks,
> 
> -- 
>   Pascal Obry /  Magny Les Hameaux (78)
> 
>   The best way to travel is by means of imagination
> 
>   http://www.obry.net
> 
>   gpg --keyserver keys.gnupg.net --recv-key F949BD3B
> 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Re: lowpass bilateral filter → banding artifacts

[Timur Irikovich Davletshin]

https://github.com/darktable-org/darktable/issues/3435 — this issue can
be closed, was fixed by 
https://github.com/darktable-org/darktable/commit/d4156db4a3ebc8df7f872eb04bcef6530a2f4f70

Thanks a lot!

Timur.

On Sat, 2019-11-16 at 17:33 +0300, Timur Irikovich Davletshin wrote:
> Christian, thanks!
> 
> Timur.
> 
> On Sat, 2019-11-16 at 14:38 +0100, Christian wrote:
> > Timur,
> > I've opened a ticket for this issue:
> > 
> > https://github.com/darktable-org/darktable/issues/3435
> > 
> > christian
> > 
> > Am 16.11.2019 um 08:31 schrieb Timur Irikovich Davletshin:
> > > So I played around with different pictures and modules and these
> > > are
> > > some results:
> > > 
> > > 1. no link with memory tiling settings
> > > 2. no link with sensor type or demosaic settings (visible on
> > > pictures
> > > with monochrome sensors)
> > > 3. visible on all pictures with big blocks of dark and bright
> > > small
> > > objects
> > > 3. distance between artifact lines is linked with radius setting
> > > of
> > > bilateral filter.
> > > 4. visible in exported pictures
> > > 5. shadows and highlights with bilateral filter has similar
> > > bug...
> > >   a) it is not visible in exported pictures
> > >   b) it is not visible in low zoom factors
> > >   c) visible on screen in zoom factors 50-100%
> > > 
> > > This last one may give some clues.
> > 
> > ___
> > __
> > __
> > darktable developer mailing list
> > to unsubscribe send a mail to 
> > darktable-dev+unsubscr...@lists.darktable.org
> > 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] import folder → file count

[Timur Irikovich Davletshin]

No, dt will say that you're importing 400 files, but in fact 200 will
be imported.

Timur.

On Mon, 2019-11-18 at 10:36 -0500, Julian Rickards wrote:
> Perhaps: 200 RAW (200 JPG, ignored)
> 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] basic adjustments

[Timur Irikovich Davletshin]

Well, my point was not about American vs British. It was just an
example of inconsistency. And odd tradition of lowercasing all capitals
make it only worse. Regarding this particular case... Well I think this
information (colorspace, type of curve) somehow must be delivered to
user. Otherwise developers will be asked same questions over and over.
They'll become annoyed, start being aggressive, users will be confused
even more and leave for another software :)

Timur.

On Mon, 2019-11-18 at 09:36 -0500, Julian Rickards wrote:
> grAy is the American spelling and there's nothing wrong with that
> (despite being a Canadian and using British spelling, LoL) but Timur
> is correct, there should be consistency and, in addition to sticking
> to the same spelling of gray/grey, I think that that the English
> version of the documentation (and GUI) should be either all British
> or all American English spelling, not just American for some and
> British for others.
> 
> On Mon, Nov 18, 2019 at 8:29 AM Timur Irikovich Davletshin <
> timur.davlets...@gmail.com> wrote:
> > Actually I agree. Darktable lacks of terminology unification across
> > modules. E.g. AFAIR there are around 6 different names for 18%
> > gray. In
> > some places it is "grey" but in others it is "gray".
> > 
> > Timur.
> > 
> > On Mon, 2019-11-18 at 14:03 +0100, Moritz Moeller wrote:
> > > On 15.11.19 12:02, parafin wrote:
> > > > I think these numbers don't have units, so why do expect them
> > to
> > > > mean
> > > > the same thing in different modules, even if we ignore the pipe
> > > > order?
> > > 
> > > Because that's the most basic requirement of usability. That
> > things 
> > > named the same way act the same way and mean the same thing
> > across a 
> > > single app – at the very least.
> > > 
> > > > It's not promised anywhere in the documentation as far as I can
> > > > see.
> > > 
> > > 
> > > I went through the Photoshop & Lightroom docs and I can't find
> > any 
> > > promise in the entirety of them that slider ranges of things
> > sharing
> > > a 
> > > name will match in range & effect.
> > > Yet they do.
> > > Go figure ...
> > > 
> > > 
> > > Beers,
> > > 
> > > .mm
> > >
> > ___
> > __
> > > __
> > > darktable developer mailing list
> > > to unsubscribe send a mail to 
> > > darktable-dev+unsubscr...@lists.darktable.org
> > > 
> > 
> > ___
> > 
> > darktable developer mailing list
> > to unsubscribe send a mail to 
> > darktable-dev+unsubscr...@lists.darktable.org
> > 
> 
> _
> __ darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] basic adjustments

[Timur Irikovich Davletshin]

Maybe it's time to choose project leader and start collecting
donations?

On Mon, 2019-11-18 at 15:11 +0100, Aurélien Pierre wrote:
> darktable also lacks a board of investors, a CTO, a head of UX, a
> project management, a panel of test users, a famous photographer as a
> brand ambassador, many tracking features to collect statistics on
> usage "to improve the performance", an annual coding sprint in the
> Bahamas and a couple of off-shore accounts to pay for the whores and
> whisky during that sprint. 
> Until that, darktable is done be piling up code randomly produced by
> random people, 90% of them being non-native English speakers, some
> writing grey, some writing gray, and contrast still means "pushing
> whites further away from blacks" with no implication on the actual
> algorithm or colour space used to do so.
> By the way, changing strings variables in C code does not actually
> require coding knowledge (just how to use grep and git - which might
> be worse than actually coding) and only needs a proper design backed
> with some argumentation (same-named settings having the same effect
> is a very good argument, now how do we actually fix the soft in a UI-
> consistent yet technically-accurate way ?). I'm waiting for the pull
> requests…
> Le 18/11/2019 à 14:29, Timur Irikovich Davletshin a écrit :
> > Actually I agree. Darktable lacks of terminology unification across
> > modules. E.g. AFAIR there are around 6 different names for 18%
> > gray. In
> > some places it is "grey" but in others it is "gray".
> > 
> > Timur.
> > 
> > On Mon, 2019-11-18 at 14:03 +0100, Moritz Moeller wrote:
> > > On 15.11.19 12:02, parafin wrote:
> > > > I think these numbers don't have units, so why do expect them
> > > > to
> > > > mean
> > > > the same thing in different modules, even if we ignore the pipe
> > > > order?
> > > 
> > > Because that's the most basic requirement of usability. That
> > > things 
> > > named the same way act the same way and mean the same thing
> > > across a 
> > > single app – at the very least.
> > > 
> > > > It's not promised anywhere in the documentation as far as I can
> > > > see.
> > > 
> > > 
> > > I went through the Photoshop & Lightroom docs and I can't find
> > > any 
> > > promise in the entirety of them that slider ranges of things
> > > sharing
> > > a 
> > > name will match in range & effect.
> > > Yet they do.
> > > Go figure ...
> > > 
> > > 
> > > Beers,
> > > 
> > > .mm
> > > _
> > > 
> > > __
> > > darktable developer mailing list
> > > to unsubscribe send a mail to 
> > > darktable-dev+unsubscr...@lists.darktable.org
> > > 
> > 
> > ___
> > 
> > darktable developer mailing list
> > to unsubscribe send a mail to 
> > darktable-dev+unsubscr...@lists.darktable.org
> > 
>  
> _
> __ darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] basic adjustments

[Timur Irikovich Davletshin]

Actually I agree. Darktable lacks of terminology unification across
modules. E.g. AFAIR there are around 6 different names for 18% gray. In
some places it is "grey" but in others it is "gray".

Timur.

On Mon, 2019-11-18 at 14:03 +0100, Moritz Moeller wrote:
> On 15.11.19 12:02, parafin wrote:
> > I think these numbers don't have units, so why do expect them to
> > mean
> > the same thing in different modules, even if we ignore the pipe
> > order?
> 
> Because that's the most basic requirement of usability. That things 
> named the same way act the same way and mean the same thing across a 
> single app – at the very least.
> 
> > It's not promised anywhere in the documentation as far as I can
> > see.
> 
> 
> I went through the Photoshop & Lightroom docs and I can't find any 
> promise in the entirety of them that slider ranges of things sharing
> a 
> name will match in range & effect.
> Yet they do.
> Go figure ...
> 
> 
> Beers,
> 
> .mm
> _
> __
> darktable developer mailing list
> to unsubscribe send a mail to 
> darktable-dev+unsubscr...@lists.darktable.org
> 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Bug in frame tool Darktable 3.0.0rc1-win64

[Timur Irikovich Davletshin]

Linux version works fine with these settings.

Timur.

On Sun, 2019-11-17 at 18:02 +0100, 8...@gmx.net wrote:
> This seems to work in any image:
> 
> - switch on the frame tool in Darktable 3.0.0rc1-win64
> - adjust frameline size > 0%
> - adjust frameline offset = 100%
> - get a crash
> 
> _
> __
> darktable developer mailing list
> to unsubscribe send a mail to 
> darktable-dev+unsubscr...@lists.darktable.org
> 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] dt 3.0rc1 → gamma module

[Timur Irikovich Davletshin]

Aurélien, thanks for your answer. But I find it a bit confusing if
compared to behavior of old versions.

Timur.

On Sun, 2019-11-17 at 14:16 +0100, Aurélien Pierre wrote:
> Hi,
> the gamma module does not do what it says anymore. It's a leftover of
> dt 0.x before the output colour profile was added.
> It has always been there but didn't appear in the history before. It
> still doesn't appear in UI. I don't remember why we made every module
> appear in the history now (except the mask manager, which function I
> don't understand), but here it is.
> The gamma module is now only converting the floating point output of
> the pipe (image or masks) to 8 bits unsigned integers, to be sent to
> the display. As such, it is not used when exporting to a file.
> Aurélien.
> Le 17/11/2019 à 14:02, Andreas Schneider a écrit :
> > On Sunday, 17 November 2019 10:30:00 CET Timur Irikovich Davletshin
> > wrote:
> > > Hi dear developers!
> > > 
> > > Short question. What is gamma module which has appeared in
> > > history
> > > stack in dt 3.0 builds? There is no such module in darktable nor
> > > it can
> > > be disabled in history stack. Is it something that has got into
> > > history
> > > stack by mistake or some hidden darkroom module?
> > 
> > See, e.g.
> > 
> > https://www.cambridgeincolour.com/tutorials/gamma-correction.htm
> > 
> > 
> > Andreas
> > 
> > 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] dt 3.0rc1 → gamma module

[Timur Irikovich Davletshin]

Hi dear developers!

Short question. What is gamma module which has appeared in history
stack in dt 3.0 builds? There is no such module in darktable nor it can
be disabled in history stack. Is it something that has got into history
stack by mistake or some hidden darkroom module?

Thank you in advance,

Timur.

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Styles → Hierarchy levels

[Timur Irikovich Davletshin]

Hi dear developers!

There is another thing I noticed in master branch builds. It looks like
lighttable → styles supports hierarchy by using "|" as a divider. It
imposes no limits on the number of "|" and looks just fine. But in
darkroom mode only one level of hierarchy is supported, the rest is
just flattened being list of "level1 | level2".

Thank you in advance,

Timur.

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Re: lowpass bilateral filter → banding artifacts

[Timur Irikovich Davletshin]

Christian, thanks!

Timur.

On Sat, 2019-11-16 at 14:38 +0100, Christian wrote:
> Timur,
> I've opened a ticket for this issue:
> 
> https://github.com/darktable-org/darktable/issues/3435
> 
> christian
> 
> Am 16.11.2019 um 08:31 schrieb Timur Irikovich Davletshin:
> > So I played around with different pictures and modules and these
> > are
> > some results:
> > 
> > 1. no link with memory tiling settings
> > 2. no link with sensor type or demosaic settings (visible on
> > pictures
> > with monochrome sensors)
> > 3. visible on all pictures with big blocks of dark and bright small
> > objects
> > 3. distance between artifact lines is linked with radius setting of
> > bilateral filter.
> > 4. visible in exported pictures
> > 5. shadows and highlights with bilateral filter has similar bug...
> > a) it is not visible in exported pictures
> > b) it is not visible in low zoom factors
> > c) visible on screen in zoom factors 50-100%
> > 
> > This last one may give some clues.
> 
> _
> __
> darktable developer mailing list
> to unsubscribe send a mail to 
> darktable-dev+unsubscr...@lists.darktable.org
> 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] tone equalizer, filmic rgb → icon background

[Timur Irikovich Davletshin]

Nic, I'm just saying that this behavior looks a bit confusing from user
standpoint.

I'm sorry for not posting to github. MS decided that I cannot use it — 
https://help.github.com/en/github/site-policy/github-and-trade-controls
 and I'm too lazy to use VPN for that purpose.

Timur.

P.S. there is no need to reply both to personal email and mailing list.

On Fri, 2019-11-15 at 19:32 +0100, Nicolas Auffray wrote:
> I have never say they are not pickers, just they are not same one... 
> Just see how they renders and where they are on modules UI. Size is
> not 
> the same, and also color. just see that they are visibly
> different... 
> But remember that it's an open source software, so feel free to
> change 
> that the way you want if you don't like that, for you or you could
> even 
> propose a PR on Github... Hmm
> 
> Color pickers on curve modules are here to apply black, grey and
> white 
> parts of curve (so they are colored in... black, grey, white). If
> hover, 
> that could only be on background. Other color pickers are not related
> to 
> black, grey and white. So if we had a hover effect, it would be
> better 
> to do that just on the picker (not the background but the picker 
> himself). It's a possibility, but for me it's good as it is actually 
> (and nobody else seems to have problem with that...). That's my view
> here !
> 
> 
> Le 15/11/2019 à 18:40, Timur Irikovich Davletshin a écrit :
> > If they are not pickers why use same icon? And if all other icons
> > have
> > hover action, why not these? Hmm...
> > 
> > Timur.
> > 
> > On Fri, 2019-11-15 at 18:25 +0100, Nicolas Auffray wrote:
> > > Hi Timur,
> > > 
> > > It would really be better to post issues on Github (to let all
> > > know
> > > and
> > > follow that). Anyway, some answers on what I see :
> > > 
> > > 1. Yes, this icon doesn't seems to have CSS editing possibility
> > > (maybe I
> > > make a mistake but on what I see with GTK inspector...). So
> > > posting
> > > on
> > > Github to let Aurélien see that (as it is his module work) would
> > > be
> > > better.
> > > 
> > > 2 and 3. That's not issues. All color pickers like these ones
> > > (see
> > > exposure module for example) are displayed the same way. Color
> > > picker
> > > on
> > > rgb curve are not same color picker (colored one, black, grey and
> > > white
> > > and not on same place like others color picker ; so having a
> > > different
> > > way is not a problem as they are not totally the same). Not
> > > needed
> > > to
> > > have them have the exact same behavior.
> > > 
> > > Nicolas
> > > 
> > > 
> > > Le 15/11/2019 à 18:09, Timur Irikovich Davletshin a écrit :
> > > > Hi developers!
> > > > 
> > > > 1. tone equalizer module → display exposure mask icon has no
> > > > hover
> > > > background lightening. Compare with display mask icon in drawn
> > > > mask
> > > > blending.
> > > > 
> > > > 2. Same problem in tone equalizer module → masking tab → picker
> > > > tool
> > > > next to mask exposure compensation and mask contrast
> > > > compensation.
> > > > 
> > > > 3. filmic rgb module → scene tab → four picker tools need hover
> > > > background lightening. Compare with picker tool in rgb curve or
> > > > tone
> > > > curve.
> > > > 
> > > > Thank you advance,
> > > > 
> > > > Timur.
> > > > 
> > > > ___
> > > > 
> > > > 
> > > > darktable developer mailing list
> > > > to unsubscribe send a mail to
> > > > darktable-dev+unsubscr...@lists.darktable.org
> > > > 
> > ___
> > 
> > darktable developer mailing list
> > to unsubscribe send a mail to 
> > darktable-dev+unsubscr...@lists.darktable.org
> > 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] tone equalizer, filmic rgb → icon background

[Timur Irikovich Davletshin]

If they are not pickers why use same icon? And if all other icons have
hover action, why not these? Hmm...

Timur.

On Fri, 2019-11-15 at 18:25 +0100, Nicolas Auffray wrote:
> Hi Timur,
> 
> It would really be better to post issues on Github (to let all know
> and 
> follow that). Anyway, some answers on what I see :
> 
> 1. Yes, this icon doesn't seems to have CSS editing possibility
> (maybe I 
> make a mistake but on what I see with GTK inspector...). So posting
> on 
> Github to let Aurélien see that (as it is his module work) would be
> better.
> 
> 2 and 3. That's not issues. All color pickers like these ones (see 
> exposure module for example) are displayed the same way. Color picker
> on 
> rgb curve are not same color picker (colored one, black, grey and
> white 
> and not on same place like others color picker ; so having a
> different 
> way is not a problem as they are not totally the same). Not needed
> to 
> have them have the exact same behavior.
> 
> Nicolas
> 
> 
> Le 15/11/2019 à 18:09, Timur Irikovich Davletshin a écrit :
> > Hi developers!
> > 
> > 1. tone equalizer module → display exposure mask icon has no hover
> > background lightening. Compare with display mask icon in drawn mask
> > blending.
> > 
> > 2. Same problem in tone equalizer module → masking tab → picker
> > tool
> > next to mask exposure compensation and mask contrast compensation.
> > 
> > 3. filmic rgb module → scene tab → four picker tools need hover
> > background lightening. Compare with picker tool in rgb curve or
> > tone
> > curve.
> > 
> > Thank you advance,
> > 
> > Timur.
> > 
> > ___
> > 
> > darktable developer mailing list
> > to unsubscribe send a mail to 
> > darktable-dev+unsubscr...@lists.darktable.org
> > 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] tone equalizer, filmic rgb → icon background

[Timur Irikovich Davletshin]

Hi developers!

1. tone equalizer module → display exposure mask icon has no hover
background lightening. Compare with display mask icon in drawn mask
blending.

2. Same problem in tone equalizer module → masking tab → picker tool
next to mask exposure compensation and mask contrast compensation.

3. filmic rgb module → scene tab → four picker tools need hover
background lightening. Compare with picker tool in rgb curve or tone
curve.

Thank you advance,

Timur.

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] lowpass bilateral filter → banding artifacts

[Timur Irikovich Davletshin]

Hi dear developers.

There a strange thing I noticed with lowpass filter module (master
branch builds).

Steps to reproduce:

1. Load raw picture from this post: 
https://discuss.pixls.us/t/play-raw-sensible-presets/11088

2. Apply lowpass filter with bilateral filter setting.

3. Result is the right part of this picture (left is original picture) 
https://drive.google.com/open?id=17O0nYXHMZxhe5EUaVo-28Rnj3dFNpRT4

4. Notice dark horizontal and light vertical banding artifacts. They
remain in exported picture.

Question: Is it expected bilateral algorithm problem or implementation
thing?

Thanks for your comments in advance,

Timur.



___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] UI glitches → Buttons and stuff

[Timur Irikovich Davletshin]

For consistency of conversation I'll copy my private reply to Sam:

===

Sam, there is a couple of other visual glitches I noticed.

1: screenshot1.png — line height of empty directory removal dialog. To
reproduce it create empty folder, put some raw file in it and
physically remove it from lightroom → selected image[s].

2: screenshot2.png — another button order problem in creation of new
style. Should be reversed like you made it before.

3: Another problem may appear if you right click little display button
in right bottom corner (set display profile, lightroom mode). Popup is
too narrow to fit default strings in English. Not saying about
languages like French or Russian which tend to have longer words.

Thanks for your work in advance,

Timur.

===

On Mon, 2019-11-11 at 10:57 +0800, Sam wrote:
> Hey Timur, I opened an issue on github for this, but it seems like
> it's just you and I that see this so I was wondering what OS and
> maybe DE you're using?
> 
> Thanks
> 
> On Fri, 8 Nov 2019 at 02:49, Timur Irikovich Davletshin <
> timur.davlets...@gmail.com> wrote:
> > Buttons in following darkroom modules require fixing too:
> > 
> > vignetting, rgb levels, levels, color mapping, basic adjustments.
> > 
> > Timur.
> > 
> > On Thu, 2019-11-07 at 15:09 +0800, Sam wrote:
> > > I've added fixes to a couple of these to my pull request here.
> > > 
> > 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] UI glitches → Buttons and stuff

[Timur Irikovich Davletshin]

PR looks fine for me, but I believe it has got nothing todo with
problem I described. Anyways, this problem is not visible after
Aurelien removed bold font in darktable.css — 
https://github.com/darktable-org/darktable/commit/337323535dfe6543b1fc875ac5339b44ab250ad0

Thanks for your work,

Timur.

On Mon, 2019-11-11 at 12:57 +0100, Nicolas Auffray wrote:
> Hi,
> At Timur, please test my PR here : 
> https://github.com/darktable-org/darktable/pull/3362
> sams96 replies this day that my PR fix this. I never had this issue
> so that was not the purpose on start but if it helps !
> Have a good day
> 
> Le 11/11/2019 à 03:57, Sam a écrit :
> > Hey Timur, I opened an issue on github for this, but it seems like
> > it's just you and I that see this so I was wondering what OS and
> > maybe DE you're using?
> > 
> > Thanks
> > 
> > On Fri, 8 Nov 2019 at 02:49, Timur Irikovich Davletshin <
> > timur.davlets...@gmail.com> wrote:
> > > Buttons in following darkroom modules require fixing too:
> > > 
> > > vignetting, rgb levels, levels, color mapping, basic adjustments.
> > > 
> > > Timur.
> > > 
> > > On Thu, 2019-11-07 at 15:09 +0800, Sam wrote:
> > > > I've added fixes to a couple of these to my pull request here.
> > > > 
> > > 
> > > 
> > 
> > ___
> >  darktable developer mailing list to unsubscribe send a
> > mail to darktable-dev+unsubscr...@lists.darktable.org 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] darktable 3.0.0rc0 released

[Timur Irikovich Davletshin]

Thank you for quick and useful reply.

Good night!

On Tue, 2019-11-05 at 23:00 +0100, Nicolas Auffray wrote:
> > Nicolas, can you fix those two issues I addressed earlier? I just
> > copy
> > from one of my letters to this mailing list.
> > 
> > 
> > 
> > 1. Default dt theme has switched to sans-serif as default font but
> > #live-sample-data still uses "courier". I believe "monospace" is
> > better
> > choice if aliased font is used in all other places (like serif,
> > sans-
> > serif, monospace).
> 
> Already done and merged yesterday on master : 
> https://github.com/darktable-org/darktable/pull/3287
> 
> > 2. Bold font is used on hovering elements like buttons which I find
> > a
> > bit odd (string length changes) so I played a bit and removed all
> > "bold" lines in theme — it changed nothing. Is this behavior hard-
> > coded directly somewhere or I can change it in theme?
> 
> It's work in progress by Aurélien Pierre. See here :
> 
> https://github.com/darktable-org/darktable/pull/3068
> 
> 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] darktable 3.0.0rc0 released

[Timur Irikovich Davletshin]

On Tue, 2019-11-05 at 19:49 +0100, Nicolas Auffray wrote:
> ... I'm the author of grey theme...

Nicolas, can you fix those two issues I addressed earlier? I just copy
from one of my letters to this mailing list.

1. Default dt theme has switched to sans-serif as default font but
#live-sample-data still uses "courier". I believe "monospace" is better
choice if aliased font is used in all other places (like serif, sans-
serif, monospace).

2. Bold font is used on hovering elements like buttons which I find a
bit odd (string length changes) so I played a bit and removed all
"bold" lines in theme — it changed nothing. Is this behavior hard-
coded directly somewhere or I can change it in theme?

Regards,

Timur.

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] darktable 3.0.0rc0 released

[Timur Irikovich Davletshin]

On Tue, 2019-11-05 at 22:22 +0100, Nicolas Auffray wrote:
Looks like I'm having bad day and have to repeat myself once again. I
was talking about default Debian 10 installation. This uses 11 pt size
like most distro do.

As I said I know that theme is "entirely" CSS adjustable. This is how I
fixed it in my case. I just set same font size as in gsettings get
org.gnome.desktop.interface font-name.

> Hum, have you read what we have said ? It's also related to dpi 
> rendering, so it is the way that works in GTK (related to font OS
> size 
> and dpi rendering)... What I just add is how on start em, px, etc.
> work 
> with CSS. And the new darktable UI is entirely adjustable by CSS 
> (colors, fonts, sizes, etc...).
> 
> To help on issue you precise, it would be better having more details
> on 
> your specific configuration, how it really renders on your OS, and
> for 
> example precise what you ask me on start : what size 1em is equal in 
> darktable on your OS ? And also precise what parafin just ask.
> 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] darktable 3.0.0rc0 released

[Timur Irikovich Davletshin]

I know how it should look like, but it is not the way it works in GTK
implementation. Size differs in browsers (they use 16 as base for 1em
usually) and GTK.

On Tue, 2019-11-05 at 21:45 +0100, Nicolas Auffray wrote:
> em size and how it works is not related to GTK but a standard usage
> on 
> screen rendering. So all apps, system should use this standard
> thing. 
> It's noted for example on CSS standard W3C page : 
> https://www.w3.org/Style/Examples/007/units.en.html
> 
> Anyway, it seems as Aurelien precise it, that some
> systems/configuration 
> applied a default dpi not too standard that change that. So quite 
> difficult to find that if any people who develop darktable have
> these 
> specific systems. So, in other dpi standard screen (if I remember
> well, 
> default dpi is 72dpi), the 1em=1.333px is no more avalaible, making
> the 
> font size acting differently...
> 
> 
> Le 05/11/2019 à 20:54, Timur Irikovich Davletshin a écrit :
> > On Tue, 2019-11-05 at 20:47 +0100, Aurélien Pierre wrote:
> > > Setting font size to 1em should tell GTK to use the default OS
> > > font
> > > size, no matter its value.
> > Size doesn't match default OS settings (Debian 10 default
> > installation)
> > on 3 displays I tried (2 low-dpi, 1 high-dpi). Do you have link on
> > GTK
> > documentation which says that 1em equals default size? I'd be glad
> > to
> > know logic behind it.
> > 
> > Thank you in advance,
> > 
> > Timur.
> > 
> > ___
> > 
> > darktable developer mailing list
> > to unsubscribe send a mail to 
> > darktable-dev+unsubscr...@lists.darktable.org
> > 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] darktable 3.0.0rc0 released

[Timur Irikovich Davletshin]

On Tue, 2019-11-05 at 20:47 +0100, Aurélien Pierre wrote:
> > Real size of 1em is 13.33px on my OS (with default OS font on
> > 10 size). If I increase my OS font on 11 size, the size of 1em
> > become 14.66. 1em = 1.px, so just the normal
> > behaviour. 
> > 

Nicolas, strange thing... I didn't get this reply from you. Thanks
Aurelien for keeping copy of it for me :)

I confirm, it look like what I get on my system. And it proves that 1em
is anything but default system font size in GTK.

Thanks,

Timur.

P.S. Aurelien, btw, your letter font size is oversized too )))

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] darktable 3.0.0rc0 released

[Timur Irikovich Davletshin]

On Tue, 2019-11-05 at 20:47 +0100, Aurélien Pierre wrote:
> Setting font size to 1em should tell GTK to use the default OS font
> size, no matter its value.

Size doesn't match default OS settings (Debian 10 default installation)
on 3 displays I tried (2 low-dpi, 1 high-dpi). Do you have link on GTK
documentation which says that 1em equals default size? I'd be glad to
know logic behind it.

Thank you in advance,

Timur.

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] darktable 3.0.0rc0 released

[Timur Irikovich Davletshin]

Hi, Nicolas!

Don't take offense, I'm not yelling :)

But can you tell me, what is real size of 1em (used in your theme too)
in GTK/Linux and GTK/MacOS?

Thanks for your work on themes, btw.

Timur.

On Tue, 2019-11-05 at 19:49 +0100, Nicolas Auffray wrote:
> Many people I know use darktable, even on Linux correctly. And I'm
> the 
> author of grey theme so work a lot on the UI and made many tests on
> my 
> system. I never had issue you relate, even on my previous 27" full
> HD 
> screen, my Macbook Pro retina 13" or my new 24" WQHD screen. So that 
> would say it's about a specific config (probably darktable default
> theme 
> as it's OS font size related). So with no more details (screen 
> resolution, theme used, default OS font (font used and size)
> especially 
> if you use darktable theme), that would be difficult to help and
> find 
> why you have what you describe.
> 
> It's easy to yell, not so easy to find why some people have specific 
> issues and not other, especially if few details are given. And about
> UI 
> issues, a capture screen is always a good idea. And probably Github 
> issues part is a better way (with the whole details I post here) to 
> continue. For example, I anwser on this related issue (maybe the
> author 
> is one of you) : 
> https://github.com/darktable-org/darktable/issues/3295
> 
> 
> Le 05/11/2019 à 19:39, Timur Irikovich Davletshin a écrit :
> > Actually I have same issue on Linux too. But I was tired telling
> > Aurelien about font size issues and modified theme to match my
> > needs.
> > 
> > On Tue, 2019-11-05 at 19:21 +0100, Moritz Moeller wrote:
> > > On 5.11.19 19:18, Nicolas Auffray wrote:
> > > > Anyway, that's not ok as the new UI is now size adjustable (by
> > > > using
> > > > CSS, not have anymore hardcoded things and use emphasis sizes
> > > > on
> > > > most
> > > > parts to adjust correctly). It seems to be a MacOS specific
> > > > issue...
> > > It's not an issue for me but for a first time user ... they'd
> > > probably
> > > close the app and never open it again. :)
> > > 
> > > I couldn't even resize the main window to fit my screen. It would
> > > lock
> > > at a width about 20% larger.
> > > 
> > > .mm
> > > _
> > > 
> > > __
> > > darktable developer mailing list
> > > to unsubscribe send a mail to
> > > darktable-dev+unsubscr...@lists.darktable.org
> > > 
> > ___
> > 
> > darktable developer mailing list
> > to unsubscribe send a mail to 
> > darktable-dev+unsubscr...@lists.darktable.org
> > 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] darktable 3.0.0rc0 released

[Timur Irikovich Davletshin]

Actually I have same issue on Linux too. But I was tired telling
Aurelien about font size issues and modified theme to match my needs.

On Tue, 2019-11-05 at 19:21 +0100, Moritz Moeller wrote:
> On 5.11.19 19:18, Nicolas Auffray wrote:
> > Anyway, that's not ok as the new UI is now size adjustable (by
> > using 
> > CSS, not have anymore hardcoded things and use emphasis sizes on
> > most 
> > parts to adjust correctly). It seems to be a MacOS specific
> > issue...
> 
> It's not an issue for me but for a first time user ... they'd
> probably 
> close the app and never open it again. :)
> 
> I couldn't even resize the main window to fit my screen. It would
> lock 
> at a width about 20% larger.
> 
> .mm
> _
> __
> darktable developer mailing list
> to unsubscribe send a mail to 
> darktable-dev+unsubscr...@lists.darktable.org
> 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Default theme → Courier and hover fonts

[Timur Irikovich Davletshin]

Hi,

1. Default dt theme has switched to sans-serif as default font but
#live-sample-data still uses "courier". I believe "monospace" is better
choice if aliased font is used in all other places (like serif, sans-
serif, monospace).

2. Bold font is used on hovering elements like buttons which I find a
bit odd (string length changes) so I played a bit and removed all
"bold" lines in theme — it changed nothing. Is this behavior hard-coded 
directly somewhere or I can change it in theme?

Regards,

Timur.

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] dt master branch → Debian Next deps

[Timur Irikovich Davletshin]

Thank you for this comprehensive reply.

Cheers,

Timur.

On Tue, 2019-05-28 at 11:55 +0200, parafin wrote:
> Basically it was decided that depending on just fonts-roboto is the
> right thing to do. In oldstable Debian it's the only package that
> exists
> and it contains the actual fonts, in other Debians it's a meta-
> package
> that depends on actual package (-hinted in stable, -unhinted in
> newer). Looks like that in testing and unstable -hinted package is
> dummy and doesn't contain anything. So your original request to
> depend
> on all variants makes sense only for stable, but you mention Debian
> Next, which I assume is testing. I'm not sure what's this whole mess
> with -hinted and -unhinted is all about, but anyway it doesn't look
> like packagers should care about it, fonts-roboto is the right thing
> to
> depend on.
> 
> As for requires vs recommends dependency there was a disagreement.
> pmjdebruijn chose "recommends" for his Ubuntu packages, darix on the
> other hand thinks that "requires" is the right thing to do. I don't
> think we managed to convince him otherwise, it's his decision in the
> end after all.
> 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] dt master branch → Debian Next deps

[Timur Irikovich Davletshin]

On Sun, 2019-05-19 at 13:42 -0400, Patrick Shanahan wrote:
> 
> fwiw:   most of the discussion re: darktable
>   was conducted on freenode irc, #darktable
>   but present contributors seem to dislike that and do
> not go there.  discussion has become disjointed and
> difficult to follow.  but I am a user and bug contributor
> will little/no programming.  this is what I see.
>   there has been discussion about the preferred forum but
> no agreement or resolution that I have seen.
> 
> 

Thanks Patrick for your help. I'll mail him a bit later if doesn't
reply here.

Cheers,

Timur.

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] dt master branch → Debian Next deps

[Timur Irikovich Davletshin]

On Sun, 2019-05-19 at 16:54 +0200, Pascal Obry wrote:
> 
> I would say that this is up to the packager. My take is:
> 
> - On Linux Roboto should be a dependency for best experience. But
> certainly not mandatory.
> 
> - On Windows and MacOS clearly state that this should be installed by
> users.
> 

Well, just as expected conversation goes far beyond original topic )))

1. Can we just change dependencies in deb file like this:
fonts-roboto → fonts-roboto|fonts-roboto-hinted|fonts-roboto-unhinted
?

2. Moving fonts to "recommends" instead of "depends" probably is a good
idea too. This what nearly all other packages do. E.g. libreoffice 
packages with long list of recommended fonts. It is good to respect
those who uses "--no-install-recommends" option.

Cheers,

Timur.

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] dt master branch → Debian Next deps

[Timur Irikovich Davletshin]

Hi!

I'm not looking forward for another heated discussion with Aurelien
about fonts ))) I'm just telling that all three packages provide same
font just in different versions and I don't see why darktable should
prefer hinted over unhinted or vice versa.

Packaging fonts in dt bundle... well I don't think it is a good idea at
least for Linux. Windows and mac — last time I checked default theme
relied on fonts available in default OS installation.

Timur.

On Sun, 2019-05-19 at 10:58 +0200, parafin wrote:
> I think dt should just include needed custom fonts and not depend on
> system ones if theme requires specific font. So for example default
> theme uses system font, that's fine, elegant theme uses specifically
> Roboto font - it should be bundled together with the theme then.
> 
> The reasoning for it is the following:
> Since dt now supports different themes, I assume there should be a
> way
> for users to install additional themes, not included in DT
> repository.
> Such additional themes too may depend on custom fonts, and requiring
> user to somehow install these fonts by themselves is not a workable
> approach. So there should be a way for dt to use fonts not installed
> in
> the system (which also will help packagers with existing Roboto font
> problem). The main problem of course is how to do it, especially
> since
> dt supports 3 OSes with different font systems. But IMHO this must be
> solved before doing next major release.

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] dt master branch → Debian Next deps

[Timur Irikovich Davletshin]

Hello, dear developers!

There is one minor problem with current debs from OBS. They depend on
fonts-roboto package, but Roboto font is available via several other
packages — fonts-roboto-hinted, fonts-roboto-unhinted.

Probably fonts-roboto|fonts-roboto-hinted|fonts-roboto-unhinted will be
more logical than just fonts-roboto.

Kind regards,

Timur.

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] [BUG?] Fuji RAF Files are not cropped to nominal (EXIF) size

[Timur Irikovich Davletshin]

Hi Chris.

I believe this question was addressed couple times already. Camera
sensors in fact have bigger resolution than in camera JPGs (or stock
software). They crop it to avoid quality issues which may occur in some
sensors. I believe it is camera specific.

Timur.

On Thu, 2019-04-11 at 19:48 +0200, Christian wrote:
> Hi.
> Fuji X-Trans II Files do have a nominal size of 4896 x 3264 px.
> The ooc-JPGs do have exactly this size.
> 
> But after export from darktable the JPGs are a bit larger
> (eg. 4932 x 3296).
> 
> I tried also another converter (RFC EX 2.0). This generates JPGs with
> the original size.
> 
> So: Is this behaviour intended?
> 
> As workaround I created a preset for the crop module.
> 
> Chris
> 
> _
> __
> darktable developer mailing list
> to unsubscribe send a mail to 
> darktable-dev+unsubscr...@lists.darktable.org
> 

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Lens correction with FF lenses used on APS-C

[Timur Irikovich Davletshin]

I believe it does. Changing body type (full-frame instead of aps-c)
changes geometry. Body type description is nothing more than just a
file in /usr/share/lensfun/version_1 with cropfactor parameter being
the only meaningful information used for geometry calculaton.

Timur.

On Sat, 2019-02-23 at 14:42 +0100, Florian W wrote:
> Hi,
> I happen to use on my Canon 750D (APC-C) 2 lenses designed for full
> frame (Canon EF 50mm f/1.8 STM and Canon EF 28mm f/2.8 IS USM) 
> I wondered if the lens correction module takes into account that the
> camera is full frame or APS-C to apply the proper correction ?
> 
> Can someone tell me ?
> Thanks
> 
> _
> __ darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org 
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Retouch → brush placement bug?

[Timur Irikovich Davletshin]

See attached.

Timur.

On Mon, 2019-02-18 at 18:39 -0300, Edgardo Hoszowski wrote:
> Can you share the xmp?
> 
> El lun., 18 feb. 2019 a las 18:22, Timur Irikovich Davletshin ( .davlets...@gmail.com>) escribió:
> > Hi!
> > 
> > I noticed one strange behavior in recent master 2.6 branch build
> > (via
> > OBS).
> > 
> > Module: retouch
> > 
> > Description: I place and click onto white spot with circle brush
> > (healing mode activated). Brush was added as expected, white spot
> > removed but circles are not correctly placed. Screenshots attached:
> > step #1 shows where I clicked, step #2 shows place, where it was
> > added.
> > 
> > Other modules used (except ordinary): invert, tone curve, crop and
> > rotate.
> > 
> > Can someone test it and confirm it?
> > 
> > Thanks in advance,
> > 
> > Timur.
> > ___
> > 
> > darktable developer mailing list
> > to unsubscribe send a mail to darktable-dev+unsubscribe@lists.darkt
> > able.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

_DSC0002.NEF.xmp
Description: XML document

[darktable-dev] Non-applicable modules → 2.6 vs. 2.4

[Timur Irikovich Davletshin]

Hello everybody!

I've just noticed that 2.6 and current master branch no longer shows
messages when trying to open non-applicable modules.

E.g. open typical raw file and open "scale pixels" module.
2.6 shows empty space, while 2.4 is more informative and instructs that
 "automatic pixel rotation only works for the sensors that need it".

Degradation noticed in following modules: scale pixels, rotate pixels,
chromatic aberrations (not available for monochrome cameras or regular
images),

Works: white balance and invert (not available for monochrome cameras).

Regards,

Timur.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Middle grey naming

[Timur Irikovich Davletshin]

Hi,

../src/iop/filmic.c:1841:
"target middle grey"

../src/iop/profile_gamma.c:125
"grey point"

../src/iop/filmic.c:1679
"middle grey luminance"

../src/iop/profile_gamma.c:881
"middle grey luma"

and "gray percentile" in levels.

I'm so confused... are they the same?

Yeah, "grey" vs. "gray" and "favorite" vs. "favourite" is another
battleground.

Timur.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Tone curve → Bug or feature?

[Timur Irikovich Davletshin]

Hi!

I don't know if this is a bug or a feature in tone curve module, but
curve scaling algorithm works only for L channel. If this was done
intentionally then it's worth to hide meaningless controls (scale algo
+ base of logarithm). But I prefer it to work for every channel.

Screenshot attached.

P.S. Another point, can you fix "independant" → "independent"?

Thanks in advance for your explanations,

Timur.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Metainfo — Selected background

[Timur Irikovich Davletshin]

On Sat, 2019-01-26 at 14:13 +0100, Stefan Klinger wrote:
> 
> Yes, I would really like this.  I would also like to have better
> visual cues of whether a button is selected or not (e.g., gamut
> check,
> or the occasional dropper).  IMHO the design could be less chic and
> more helpful.
> 
> You could try to achieve this by changing the CSS:
> 
> $ cd whatever/your/install/path/is
> $ find share/darktable -name \*.css
> share/darktable/style/lightbox.css
> share/darktable/style/style.css
> share/darktable/pswp/default-skin/default-skin.css
> share/darktable/pswp/photoswipe.css
> share/darktable/darktable.css
> 
> But unless you really know what you're doing, that may break a lot of
> DT's appearance, and the CSS is not exactly well documented.  I've
> been there, trying to get a usable font size.  Also, you'd be
> responsible to adapt your fix to future darktable
> updates.  Meanwhile,
> I've given up and simply squint and swear when I need to read
> something.
> 

Well, font size is an easy part — darktable.css (other css files are
not related to dt theming), look for 8pt. The rest is not so easy, file
is quite confusing because widget names are not documented.

Timur.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Metainfo — Selected background

[Timur Irikovich Davletshin]

Hi!

How do you think, is it worth to change background of selected lines in
the metainfo so it looks more visible?

See screenshot attached (that line actually selected)

Regards,

Timur.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] bauhaus controls → negative zero

[Timur Irikovich Davletshin]

Problem is not in internal floating point operations but in UI
inconsistency of mouse and keyboard operations. I can get -0.00 using
mouse (and this -0.0 will be restored after file reopening) but I can't
enter it via keyboard — unnecessary minus is just discarded. I believe
that mouse operations should follow same logic and just discard it.

Timur.

On Sun, 2018-12-23 at 11:27 +0100, Matthieu Moy wrote:
> - Original Message -
> > From: "Timur Irikovich Davletshin" 
> > I'm not sure if this is a bug or something I don't understand.
> > 
> > Bauhaus controls let me specify (and eventually store) negative
> > zeros
> > like -0.00EV in exposure module. Is it different from 0.00EV or
> > there
> > is some hidden rounding problem like -0.001?
> 
> Probably just a consequence of using floating point numbers in the
> implementation.
> 
> Floating points accept +0.0 and -0.0, but these numbers behave the
> same in almost all operations (+0.0 == -0.0 for example). AFAIK the
> only different thing is that 1/+0.0 == +infinity while 1/-0.0 ==
> -infinity. You may care about that as a programmer writing very
> tricky programs with floating point numbers, but as a darktable user,
> they are just the same!
> 
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] bauhaus controls → negative zero

[Timur Irikovich Davletshin]

I'm not sure if this is a bug or something I don't understand.

Bauhaus controls let me specify (and eventually store) negative zeros
like -0.00EV in exposure module. Is it different from 0.00EV or there
is some hidden rounding problem like -0.001?

Tested in current master builds.

Thanks in advance,

Timur.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] WebP export → Couple issues

[Timur Irikovich Davletshin]

This patch does declared work in avoiding unnecessary color conversion
in lossless mode.

But it doesn't fix none of my issues. I've got my profile reset before
testing. First export in lossy mode gave me a set of very little files
of very bad quality, 300-600 kb for 20Mpx+ images. Then I just moved
quality slider forth and back leaving it at default 95% and it worked.
So, probably Sturm Flut is right about nature of this problem.

Regarding last issue, quality slider in lossless mode — nothing's
changed. It is there.

Regards,

Timur. 

On Sun, 2018-12-16 at 22:05 +0100, Pascal Obry wrote:
> Hi Timur,
> 
> > Couple issues I noticed recently while playing with WebP export:
> > 
> > 1. Default settings (95%, lossy) provides rather mediocre results
> > and
> > IMO is unusable. Probably something higher should be used.
> > 2. Lossless settings should hide quality slider because it makes
> > zero
> > difference for the end image.
> 
> There is a PR waiting integration made recently.
> 
> https://github.com/darktable-org/darktable/pull/1866
> 
> You may want to test it and report if it solves your issues.
> 
> If it is the case please report on this PR.
> 
> Thanks,
> 
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] WebP export → Couple issues

[Timur Irikovich Davletshin]

1. Yep, you right about first issue. That helped.
2. It would be better to set 0-9 slider and set coder accordingly. At
least cwebp has this kind of logic for lossless files.

Thanks for help,

Timur.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] WebP export → Couple issues

[Timur Irikovich Davletshin]

Hi everybody,

Couple issues I noticed recently while playing with WebP export:

1. Default settings (95%, lossy) provides rather mediocre results and
IMO is unusable. Probably something higher should be used.
2. Lossless settings should hide quality slider because it makes zero
difference for the end image.

Regards,

Timur.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Russian translation update

[Timur Irikovich Davletshin]

Can anyone push updated Russian translation for the upcoming 2.6
release?

Thanks in advance,

Timur.

On Sun, 2018-05-20 at 13:15 +0300, Timur Irikovich Davletshin wrote:
> On Sat, 2018-05-05 at 12:37 +0200, Tobias Ellinghaus wrote:
> > 
> > Thank you, pushed to master. Could you update the 2.4.x branch,
> > too?
> > I am not 
> > sure if just picking the changes is the right thing – I have no way
> > of 
> > checking. :-)
> > 
> > > Regards,
> > > 
> > > Timur.
> > 
> > Tobias
> 
> Dear Tobias, just a little update to Russian translation file (more
> clear job control messages). Works both for 2.4.x and 2.5.
> 
> Timur.<>


signature.asc
Description: This is a digitally signed message part

Re: [darktable-dev] liquify.c → "scrool" typo

[Timur Irikovich Davletshin]

On Sat, 2018-12-15 at 11:55 +0100, Pascal Obry wrote:
> Le samedi 15 décembre 2018 à 13:53 +0300, Timur Irikovich Davletshin
> a
> écrit :
> > Can someone change "scrool" (instead "scroll") typo?
> > 
> > #: ../src/iop/liquify.c:3355
> > #: ../src/iop/liquify.c:3359
> > #: ../src/iop/liquify.c:3363
> > 
> > This actually breaks all translations, so probably manual
> > correction of
> > "po" files would be good thing to do.
> 
> Can you open an issue? Will assign this to me for after 2.6. We can't
> change string at this point so fix will be in 2.6.1.
> 
> Thanks,
> 

OK.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] liquify.c → "scrool" typo

[Timur Irikovich Davletshin]

Can someone change "scrool" (instead "scroll") typo?

#: ../src/iop/liquify.c:3355
#: ../src/iop/liquify.c:3359
#: ../src/iop/liquify.c:3363

This actually breaks all translations, so probably manual correction of
"po" files would be good thing to do.

Regards,

Timur.

signature.asc
Description: This is a digitally signed message part

Re: [darktable-dev] Online help → dt crashing

[Timur Irikovich Davletshin]

Same to you 

On Mon, 2018-10-29 at 10:58 +0100, rawfiner wrote:
> Thank you.
> I think I have all I need to fix this.
> Have a good day
> rawfiner
> 

signature.asc
Description: This is a digitally signed message part

Re: [darktable-dev] Online help → dt crashing

[Timur Irikovich Davletshin]

English both in OS and dt.

On Mon, 2018-10-29 at 10:34 +0100, rawfiner wrote:
> I mean, is it in english, or another language? (And same question
> concerning your operating system)
> rawfiner
> 
> Le 29 oct. 2018 10:29 AM, "Timur Irikovich Davletshin"  h...@gmail.com> a écrit :
> > LANG=C.UTF-8
> > 
> > On Mon, 2018-10-29 at 10:19 +0100, rawfiner wrote:
> > > Could you also tell me the language you use inside darktable
> > please?
> > > Is the language of your system supported by darktable?
> > > Thanks
> > > rawfiner
> > > 

signature.asc
Description: This is a digitally signed message part

Re: [darktable-dev] Online help → dt crashing

[Timur Irikovich Davletshin]

LANG=C.UTF-8

On Mon, 2018-10-29 at 10:19 +0100, rawfiner wrote:
> Could you also tell me the language you use inside darktable please?
> Is the language of your system supported by darktable?
> Thanks
> rawfiner
> 

signature.asc
Description: This is a digitally signed message part

Re: [darktable-dev] Online help → dt crashing

[Timur Irikovich Davletshin]

Actually I'm not building it myself, I use official OBS packages.

I've installed *-dbgsym package, and... and see output in the
attachment.

I tried to start dt with emptied profile and it works as expected. So
problem might be in my settings/database/cache somewhere.

Timur.

On Mon, 2018-10-29 at 09:42 +0100, rawfiner wrote:
> The backtrace has very little information unfortunately.
> Did you build the code in "release" mode?
> If so, could you please build the code in "debug" mode instead, and
> give the backtrace obtained in this mode?
> Thanks
> rawfiner
> this is darktable 2.5.0~git712.547f168ab reporting a segfault:

#0  0x7f14a3185b3a in __waitpid (pid=pid@entry=25559, 
stat_loc=stat_loc@entry=0x0, options=options@entry=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:29
#1  0x7f14a34821c0 in _dt_sigsegv_handler (param=11) at 
./src/common/system_signal_handling.c:118
#2  
#3  _main_do_event (event=, data=) at 
./src/libs/tools/global_toolbox.c:245
#4  0x7f14a1be7e15 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#5  0x7f14a1c18ea2 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#6  0x7f14a28087f7 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f14a2808a60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f14a2808d82 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f14a20d5d55 in gtk_main () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#10 0x7f14a353436c in dt_gui_gtk_run (gui=) at 
./src/gui/gtk.c:1242
#11 0x5571c32c58b0 in main (argc=, argv=) at 
./src/main.c:83

=

  Id   Target Id Frame 
* 1Thread 0x7f14a39fdb40 (LWP 25539) "darktable" 0x7f14a3185b3a in 
__waitpid (pid=pid@entry=25559, stat_loc=stat_loc@entry=0x0, 
options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:29
  2Thread 0x7f1487cda700 (LWP 25540) "gmain" 0x7f14a2eb567d in poll () 
at ../sysdeps/unix/syscall-template.S:84
  3Thread 0x7f1486cd8700 (LWP 25542) "gdbus" 0x7f14a2eb567d in poll () 
at ../sysdeps/unix/syscall-template.S:84
  4Thread 0x7f148589d700 (LWP 25543) "worker 0" 0x7f14a2eb567d in poll 
() at ../sysdeps/unix/syscall-template.S:84
  5Thread 0x7f148509c700 (LWP 25544) "worker 1" 
pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  6Thread 0x7f148489b700 (LWP 25545) "kicker" 0x7f14a2e8e28d in 
nanosleep () at ../sysdeps/unix/syscall-template.S:84
  7Thread 0x7f146700 (LWP 25546) "worker res 0" 
pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  8Thread 0x7f146f7fe700 (LWP 25547) "worker res 1" 
pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  9Thread 0x7f1467fff700 (LWP 25548) "worker 0" 0x7f149c7b9d1e in ?? () 
from /usr/lib/x86_64-linux-gnu/libgomp.so.1
  10   Thread 0x7f1453a3a700 (LWP 25554) "lua thread" 0x7f14a2eb567d in 
poll () at ../sysdeps/unix/syscall-template.S:84
  11   Thread 0x7f143700 (LWP 25557) "darktable" 0x7f149c7b9d1e in ?? 
() from /usr/lib/x86_64-linux-gnu/libgomp.so.1
  12   Thread 0x7f144e517700 (LWP 25558) "pool" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

=

Thread 12 (Thread 0x7f144e517700 (LWP 25558)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1  0x7f14a284e36a in g_cond_wait_until () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2  0x7f14a27dce89 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3  0x7f14a27dd4ac in g_async_queue_timeout_pop () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4  0x7f14a2830e9d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5  0x7f14a28303d5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#6  0x7f14a317c494 in start_thread (arg=0x7f144e517700) at 
pthread_create.c:333
__res = 
pd = 0x7f144e517700
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139725190035200, 
3250201707460804846, 0, 139725279246335, 139725190035200, 93947150357120, 
-3228072016622796562, -3228431035466530578}, mask_was_saved = 0}}, priv = {pad 
= {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 
pagesize_m1 = 
sp = 
freesize = 
__PRETTY_FUNCTION__ = "start_thread"
#7  0x7f14a2ebeacf in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:97
No locals.

Thread 11 (Thread 0x7f143700 (LWP 25557)):
#0  0x7f149c7b9d1e in ?? () from /usr/lib/x86_64-linux-gnu/libgomp.so.1
No symbol table info available.
#1  0x7f149c7b7690 in ?? () from /usr/lib/x86_64-linux-gnu/libgomp.so.1
No symbol table info available.
#2  0x7f14a317c494 in start_thread 

Re: [darktable-dev] Online help → dt crashing

[Timur Irikovich Davletshin]

Debian stable, 64 bit, I don't know what items are supplied with online
help (I know that import was the first) but it crashed every time I
clicked (~10 times). I did not clean my profile, just jumped from
2.4.4.

Timur.

On Sun, 2018-10-28 at 21:24 +0100, rawfiner wrote:
> Hello
> Could you give more details about this?
> Does this happens whatever you click on, or does it happens only when
> you click on something that has a help url?
> Do you have anything special activated (lua scripts, some
> preferences, etc)?
> Any other information that could help me to reproduce?
> Thanks
> rawfiner
> 
> Le dimanche 28 octobre 2018, Timur Irikovich Davletshin  s...@gmail.com> a écrit :
> > Hello!
> > 
> > I don't know is it just me or dt's fault but when I click online
> > help
> > icon and then click something in dt (e.g. import tab) I get crash.
> > 
> > Timur.
> > 
> > P.S. Crash report attached.
> 
> 

signature.asc
Description: This is a digitally signed message part

[darktable-dev] Online help → dt crashing

[Timur Irikovich Davletshin]

Hello!

I don't know is it just me or dt's fault but when I click online help
icon and then click something in dt (e.g. import tab) I get crash.

Timur.

P.S. Crash report attached.this is darktable 2.5.0~git712.547f168ab reporting a segfault:

#0  0x7fab30f62b3a in __waitpid (pid=8614, stat_loc=0x0, options=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:29
#1  0x7fab3125f1c0 in ?? () from 
/usr/bin/../lib/x86_64-linux-gnu/darktable/libdarktable.so
#2  
#3  0x7faaddd28f15 in ?? () from 
/usr/lib/x86_64-linux-gnu/darktable/plugins/lighttable/libglobal_toolbox.so
#4  0x7fab2f9c4e15 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#5  0x7fab2f9f5ea2 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#6  0x7fab305e57f7 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7fab305e5a60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7fab305e5d82 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7fab2feb2d55 in gtk_main () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#10 0x7fab3131136c in dt_gui_gtk_run () from 
/usr/bin/../lib/x86_64-linux-gnu/darktable/libdarktable.so
#11 0x555bb37ba8b0 in main ()

=

  Id   Target Id Frame 
* 1Thread 0x7fab317dab40 (LWP 8589) "darktable" 0x7fab30f62b3a in 
__waitpid (pid=8614, stat_loc=0x0, options=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:29
  2Thread 0x7fab15ab7700 (LWP 8590) "gmain" 0x7fab30c9267d in poll () 
at ../sysdeps/unix/syscall-template.S:84
  3Thread 0x7fab152b6700 (LWP 8591) "pool" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7fab14ab5700 (LWP 8592) "gdbus" 0x7fab30c9267d in poll () 
at ../sysdeps/unix/syscall-template.S:84
  5Thread 0x7fab07638700 (LWP 8593) "worker 0" 
pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  6Thread 0x7fab06e37700 (LWP 8594) "worker 1" 0x7fab30c9267d in poll 
() at ../sysdeps/unix/syscall-template.S:84
  7Thread 0x7fab06636700 (LWP 8595) "kicker" 0x7fab30c6b28d in 
nanosleep () at ../sysdeps/unix/syscall-template.S:84
  8Thread 0x7fab05e35700 (LWP 8596) "worker res 0" 
pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  9Thread 0x7fab05634700 (LWP 8597) "worker res 1" 
pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  10   Thread 0x7faaf73bb700 (LWP 8598) "worker 1" 0x7fab2a596d1e in ?? () 
from /usr/lib/x86_64-linux-gnu/libgomp.so.1
  11   Thread 0x7faae19f8700 (LWP 8605) "lua thread" 0x7fab30c9267d in poll 
() at ../sysdeps/unix/syscall-template.S:84
  12   Thread 0x7faad57fc700 (LWP 8609) "darktable" 0x7fab2a596d1e in ?? () 
from /usr/lib/x86_64-linux-gnu/libgomp.so.1

=

Thread 12 (Thread 0x7faad57fc700 (LWP 8609)):
#0  0x7fab2a596d1e in ?? () from /usr/lib/x86_64-linux-gnu/libgomp.so.1
No symbol table info available.
#1  0x7fab2a594690 in ?? () from /usr/lib/x86_64-linux-gnu/libgomp.so.1
No symbol table info available.
#2  0x7fab30f59494 in start_thread (arg=0x7faad57fc700) at 
pthread_create.c:333
__res = 
pd = 0x7faad57fc700
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140371703088896, 
-1301645533854090859, 0, 140727531100847, 0, 140373247508544, 
1349402811886418325, 1349322471942994325}, mask_was_saved = 0}}, priv = {pad = 
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 
pagesize_m1 = 
sp = 
freesize = 
__PRETTY_FUNCTION__ = "start_thread"
#3  0x7fab30c9bacf in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:97
No locals.

Thread 11 (Thread 0x7faae19f8700 (LWP 8605)):
#0  0x7fab30c9267d in poll () at ../sysdeps/unix/syscall-template.S:84
No locals.
#1  0x7fab305e59f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2  0x7fab305e5d82 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3  0x7fab3134b3e4 in ?? () from 
/usr/bin/../lib/x86_64-linux-gnu/darktable/libdarktable.so
No symbol table info available.
#4  0x7fab3060d3d5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5  0x7fab30f59494 in start_thread (arg=0x7faae19f8700) at 
pthread_create.c:333
__res = 
pd = 0x7faae19f8700
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140371906496256, 
-1301645533854090859, 0, 140727531089615, 140371906496256, 140372416152672, 
1349500395690867093, 1349322471942994325}, mask_was_saved = 0}}, priv = {pad = 
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 
pagesize_m1 = 
sp = 
freesize = 
__PRETTY_FUNCTION__ = "start_thread"
#6  0x7fab30c9bacf in clone () at 

Re: [darktable-dev] Re: Improving built-in color profiles

[Timur Irikovich Davletshin]

On Thu, 2018-05-31 at 13:25 -0400, William Ferguson wrote:
> In regards to the copyright question, I looked at the output of
> dcamprof dcp2json and the json file has the line
> 
> "ProfileCopyright": "Copyright 2009 Adobe Systems, Inc."
> 
> To extract the profiles and convert them, on Linux and MacOS:
> 
> Download the MacOS Adobe Camera Raw package
> 
> Compile and install dcamprof and xar if they aren't on your system
> 
> unzip CameraRaw_10_3_mac.zip
> xar -x -f CameraRaw_10_3.pkg
> cd CameraRawProfiles.pkg/
> mv Payload Payload.gz
> gunzip Payload.gz
> cpio -i < Payload
> cd CameraProfiles
> 
> At this point there are 2 directories, Adobe Standard and Camera. 
> Adobe Standard has the standard Adobe profile.  Camera contains
> subdirectories for each camera with multiple profiles.
> 
> cd Adobe\ Standard
> 
> dcamprof dcp2json Canon\ EOS\ 7D\ Standard.dcp 7DStandard.json
> dcamprof make-icc -n "Canon EOS 7D Standard" 7DStandard.json
> 7DStandard.icc
> mv 7DStandard.icc ~/.config/darktable/color/in
> 
> Substitute your camera for Canon EOS 7D.
> 
> I converted a couple of the profiles and tried them.  They didn't
> make a huge difference, but then my camera is old and it's
> performance fairly well known.
> 
> Hope this helps,
> 
> Bill
> 

So I tested those ICCs in Rawtherapee and compared them with DCP
(Rawtherapee provides this support) and result it following: my problem
with color cast was in temperature. Using correct temperature in
dcp2icc solved my issue.

Timur.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Re: lens correction → tooltip tabulation

[Timur Irikovich Davletshin]

On Sat, 2018-05-26 at 11:04 +0200, Tobias Ellinghaus wrote:
> 
> Yes, by translators. I updated the German one.
> 
> > Timur.
> 
> Tobias

If file attached in previous letter isn't good enough (it fixes all .po
files without touching translation lines) can you apply it just to
ru.po? Russian translation file has correct tabulation already.

Timur.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Re: lens correction → tooltip tabulation

[Timur Irikovich Davletshin]

Tobias, I believe translation files should be updated accordingly to
changes in lens.c — https://github.com/darktable-org/darktable/commit/8
b8bfc7c689c8f91bb544088283022ad219dd71b otherwise translations are
broken in that part.

Timur.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.orgFrom 86046f14edaca98a48ca054d4b9de82520fc3a1d Mon Sep 17 00:00:00 2001
From: "Timur I. Davletshin" 
Date: Sat, 26 May 2018 08:06:49 +0300
Subject: [PATCH] Reflect changes in lens.c

---
 po/af.po | 2 +-
 po/ca.po | 2 +-
 po/cs.po | 2 +-
 po/da.po | 2 +-
 po/de.po | 2 +-
 po/el.po | 2 +-
 po/es.po | 2 +-
 po/fr.po | 2 +-
 po/he.po | 2 +-
 po/hu.po | 2 +-
 po/it.po | 2 +-
 po/ja.po | 2 +-
 po/pl.po | 2 +-
 po/ru.po | 2 +-
 po/sk.po | 2 +-
 po/sl.po | 2 +-
 po/sv.po | 2 +-
 po/uk.po | 2 +-
 18 files changed, 18 insertions(+), 18 deletions(-)

diff --git a/po/af.po b/po/af.po
index 757db81a9..277d3c29e 100644
--- a/po/af.po
+++ b/po/af.po
@@ -5462,7 +5462,7 @@ msgid ""
 "focal range:\t%s\n"
 "aperture:\t\t%s\n"
 "crop factor:\t%.1f\n"
-"type:\t\t\t%s\n"
+"type:\t\t%s\n"
 "mounts:\t\t%s"
 msgstr ""
 
diff --git a/po/ca.po b/po/ca.po
index 25aa0a2e1..aae84ba21 100644
--- a/po/ca.po
+++ b/po/ca.po
@@ -6958,7 +6958,7 @@ msgid ""
 "focal range:\t%s\n"
 "aperture:\t\t%s\n"
 "crop factor:\t%.1f\n"
-"type:\t\t\t%s\n"
+"type:\t\t%s\n"
 "mounts:\t\t%s"
 msgstr ""
 "fabricant:\t\t%s\n"
diff --git a/po/cs.po b/po/cs.po
index fec6362e4..c7bad8ec5 100644
--- a/po/cs.po
+++ b/po/cs.po
@@ -6955,7 +6955,7 @@ msgid ""
 "focal range:\t%s\n"
 "aperture:\t\t%s\n"
 "crop factor:\t%.1f\n"
-"type:\t\t\t%s\n"
+"type:\t\t%s\n"
 "mounts:\t\t%s"
 msgstr ""
 "výrobce:\t\t%s\n"
diff --git a/po/da.po b/po/da.po
index aabd38b6c..c382ae7f1 100644
--- a/po/da.po
+++ b/po/da.po
@@ -6580,7 +6580,7 @@ msgid ""
 "focal range:\t%s\n"
 "aperture:\t\t%s\n"
 "crop factor:\t%.1f\n"
-"type:\t\t\t%s\n"
+"type:\t\t%s\n"
 "mounts:\t\t%s"
 msgstr ""
 "producent:\t\t%s\n"
diff --git a/po/de.po b/po/de.po
index 58cf7de18..90d0b463d 100644
--- a/po/de.po
+++ b/po/de.po
@@ -7097,7 +7097,7 @@ msgid ""
 "focal range:\t%s\n"
 "aperture:\t\t%s\n"
 "crop factor:\t%.1f\n"
-"type:\t\t\t%s\n"
+"type:\t\t%s\n"
 "mounts:\t\t%s"
 msgstr ""
 "Hersteller:\t\t%s\n"
diff --git a/po/el.po b/po/el.po
index 2640fbbb5..fc135f528 100644
--- a/po/el.po
+++ b/po/el.po
@@ -6043,7 +6043,7 @@ msgid ""
 "focal range:\t%s\n"
 "aperture:\t\t%s\n"
 "crop factor:\t%.1f\n"
-"type:\t\t\t%s\n"
+"type:\t\t%s\n"
 "mounts:\t\t%s"
 msgstr ""
 
diff --git a/po/es.po b/po/es.po
index 14f6abc7e..547c169be 100644
--- a/po/es.po
+++ b/po/es.po
@@ -6972,7 +6972,7 @@ msgid ""
 "focal range:\t%s\n"
 "aperture:\t\t%s\n"
 "crop factor:\t%.1f\n"
-"type:\t\t\t%s\n"
+"type:\t\t%s\n"
 "mounts:\t\t%s"
 msgstr ""
 "fabricante:\t\t%s\n"
diff --git a/po/fr.po b/po/fr.po
index 3a0dec9c4..70a0bebef 100644
--- a/po/fr.po
+++ b/po/fr.po
@@ -7078,7 +7078,7 @@ msgid ""
 "focal range:\t%s\n"
 "aperture:\t\t%s\n"
 "crop factor:\t%.1f\n"
-"type:\t\t\t%s\n"
+"type:\t\t%s\n"
 "mounts:\t\t%s"
 msgstr ""
 "fabricant:\t\t%s\n"
diff --git a/po/he.po b/po/he.po
index 8d1151b43..9ffb4d63d 100644
--- a/po/he.po
+++ b/po/he.po
@@ -6863,7 +6863,7 @@ msgid ""
 "focal range:\t%s\n"
 "aperture:\t\t%s\n"
 "crop factor:\t%.1f\n"
-"type:\t\t\t%s\n"
+"type:\t\t%s\n"
 "mounts:\t\t%s"
 msgstr ""
 "יצרן:\t\t%s\n"
diff --git a/po/hu.po b/po/hu.po
index 2c207754c..4be357cdc 100644
--- a/po/hu.po
+++ b/po/hu.po
@@ -6990,7 +6990,7 @@ msgid ""
 "focal range:\t%s\n"
 "aperture:\t\t%s\n"
 "crop factor:\t%.1f\n"
-"type:\t\t\t%s\n"
+"type:\t\t%s\n"
 "mounts:\t\t%s"
 msgstr ""
 "gyártó:\t\t%s\n"
diff --git a/po/it.po b/po/it.po
index db9dadd2e..97d3424a6 100644
--- a/po/it.po
+++ b/po/it.po
@@ -7047,7 +7047,7 @@ msgid ""
 "focal range:\t%s\n"
 "aperture:\t\t%s\n"
 "crop factor:\t%.1f\n"
-"type:\t\t\t%s\n"
+"type:\t\t%s\n"
 "mounts:\t\t%s"
 msgstr ""
 "Produttore:\t\t%s\n"
diff --git a/po/ja.po b/po/ja.po
index d0de231b0..8d457ee03 100644
--- a/po/ja.po
+++ b/po/ja.po
@@ -6868,7 +6868,7 @@ msgid ""
 "focal range:\t%s\n"
 "aperture:\t\t%s\n"
 "crop factor:\t%.1f\n"
-"type:\t\t\t%s\n"
+"type:\t\t%s\n"
 "mounts:\t\t%s"
 msgstr ""
 "メーカー:\t\t%s\n"
diff --git a/po/pl.po b/po/pl.po
index 37633b04c..c5a7e0174 100644
--- a/po/pl.po
+++ b/po/pl.po
@@ -6943,7 +6943,7 @@ msgid ""
 "focal range:\t%s\n"
 "aperture:\t\t%s\n"
 "crop factor:\t%.1f\n"
-"type:\t\t\t%s\n"
+"type:\t\t%s\n"
 "mounts:\t\t%s"
 msgstr ""
 "producent:\t\t%s\n"
diff --git a/po/ru.po b/po/ru.po
index fcaf1ceaf..ef2b47f30 100644
--- a/po/ru.po
+++ b/po/ru.po
@@ -7028,7 +7028,7 @@ msgid ""
 "focal range:\t%s\n"
 "aperture:\t\t%s\n"
 "crop factor:\t%.1f\n"
-"type:\t\t\t%s\n"
+"type:\t\t%s\n"
 "mounts:\t\t%s"
 msgstr ""
 "Производитель:\t\t%s\n"
diff --git a/po/sk.po b/po/sk.po
index 5d674390c..14375bdc2 100644
--- a/po/sk.po
+++ b/po/sk.po
@@ -6271,7 +6271,7 

[darktable-dev] lens correction → tooltip tabulation

[Timur Irikovich Davletshin]

Is it possible to remove (in lens.c:1709) "/t" in "type:\t\t\t%s\n" so
columns look aligned (see screenshot)?

Timur.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Russian translation update

[Timur Irikovich Davletshin]

On Sat, 2018-05-05 at 12:37 +0200, Tobias Ellinghaus wrote:
> 
> Thank you, pushed to master. Could you update the 2.4.x branch, too?
> I am not 
> sure if just picking the changes is the right thing – I have no way
> of 
> checking. :-)
> 
> > Regards,
> > 
> > Timur.
> 
> Tobias

Dear Tobias, just a little update to Russian translation file (more
clear job control messages). Works both for 2.4.x and 2.5.

Timur.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.orgFrom c1fcb3ba1e177488b6777b5043c7e075bfa383b1 Mon Sep 17 00:00:00 2001
From: "Timur I. Davletshin" 
Date: Sun, 20 May 2018 13:07:05 +0300
Subject: [PATCH] Simplify job control translation

---
 po/ru.po | 124 +++
 1 file changed, 62 insertions(+), 62 deletions(-)

diff --git a/po/ru.po b/po/ru.po
index 6a6257818..fcaf1ceaf 100644
--- a/po/ru.po
+++ b/po/ru.po
@@ -1669,11 +1669,11 @@ msgstr "Импортирование снимков с камеры"
 
 #: ../src/control/jobs/control_jobs.c:140
 msgid "failed to create film roll for destination directory, aborting move.."
-msgstr "Ошибка создания съёмки, импортирование прервано..."
+msgstr "Ошибка создания съёмки, импортирование прервано"
 
 #: ../src/control/jobs/control_jobs.c:333
 msgid "exposure bracketing only works on raw images."
-msgstr "Сведение экспозиций работает только со снимками в Raw."
+msgstr "Сведение экспозиций работает только со снимками в Raw"
 
 #: ../src/control/jobs/control_jobs.c:340
 msgid "images have to be of same size and orientation!"
@@ -1683,9 +1683,9 @@ msgstr "У снимков должен быть одинаковый разме
 #, c-format
 msgid "merging %d image"
 msgid_plural "merging %d images"
-msgstr[0] "Объединяется %d снимок"
-msgstr[1] "Объединяются %d снимка"
-msgstr[2] "Объединяются %d снимков"
+msgstr[0] "Объединение %d снимка"
+msgstr[1] "Объединение %d снимков"
+msgstr[2] "Объединение %d снимков"
 
 #: ../src/control/jobs/control_jobs.c:493
 #, c-format
@@ -1696,25 +1696,25 @@ msgstr "Записан файл HDR «%s»"
 #, c-format
 msgid "duplicating %d image"
 msgid_plural "duplicating %d images"
-msgstr[0] "Дублируется %d снимок"
-msgstr[1] "Дублируются %d снимка"
-msgstr[2] "Дублируются %d снимков"
+msgstr[0] "Дублирование %d снимка"
+msgstr[1] "Дублирование %d снимков"
+msgstr[2] "Дублирование %d снимков"
 
 #: ../src/control/jobs/control_jobs.c:545
 #, c-format
 msgid "flipping %d image"
 msgid_plural "flipping %d images"
-msgstr[0] "Поворачивается %d снимок"
-msgstr[1] "Поворачиваются %d снимка"
-msgstr[2] "Поворачиваются %d снимков"
+msgstr[0] "Поворот %d снимка"
+msgstr[1] "Поворот %d снимков"
+msgstr[2] "Поворот %d снимков"
 
 #: ../src/control/jobs/control_jobs.c:618
 #, c-format
 msgid "removing %d image"
 msgid_plural "removing %d images"
-msgstr[0] "Убирается %d снимок"
-msgstr[1] "Убирается %d снимка"
-msgstr[2] "Убирается %d снимков"
+msgstr[0] "Удаление из коллекции %d снимка"
+msgstr[1] "Удаление из коллекции %d снимков"
+msgstr[2] "Удаление из коллекции %d снимков"
 
 #: ../src/control/jobs/control_jobs.c:719
 #, c-format
@@ -1724,19 +1724,19 @@ msgstr "Не удалось отправить %s в корзину%s%s"
 #: ../src/control/jobs/control_jobs.c:720
 #, c-format
 msgid "could not physically delete %s%s%s"
-msgstr "Не удалось физически удалить с диска %s%s%s"
+msgstr "Не удалось удалить с диска %s%s%s"
 
 #: ../src/control/jobs/control_jobs.c:726
 msgid "physically delete"
-msgstr "Физически удалить"
+msgstr "Удалить с диска"
 
 #: ../src/control/jobs/control_jobs.c:727
 msgid "only remove from the collection"
-msgstr "Убрать из коллекции"
+msgstr "Удалить из коллекции"
 
 #: ../src/control/jobs/control_jobs.c:728
 msgid "skip to next file"
-msgstr "К следующему файлу"
+msgstr "Переход к следующему файлу"
 
 #: ../src/control/jobs/control_jobs.c:729
 msgid "stop process"
@@ -1744,27 +1744,27 @@ msgstr "Остановить процесс"
 
 #: ../src/control/jobs/control_jobs.c:734
 msgid "trashing error"
-msgstr "Ошибка при удалении"
+msgstr "Ошибка удалении в корзину"
 
 #: ../src/control/jobs/control_jobs.c:735
 msgid "deletion error"
-msgstr "Ошибка удаления"
+msgstr "Ошибка удаления с диска"
 
 #: ../src/control/jobs/control_jobs.c:864
 #, c-format
 msgid "trashing %d image"
 msgid_plural "trashing %d images"
-msgstr[0] "Удаляется %d снимок"
-msgstr[1] "Удаляются %d снимка"
-msgstr[2] "Удаляется %d снимков"
+msgstr[0] "Удаление в корзину %d снимка"
+msgstr[1] "Удаление в корзину %d снимков"
+msgstr[2] "Удаление в корзину %d снимков"
 
 #: ../src/control/jobs/control_jobs.c:866
 #, c-format
 msgid "deleting %d image"
 msgid_plural "deleting %d images"
-msgstr[0] "Удаляется %d снимок"
-msgstr[1] "Удаляются %d снимка"
-msgstr[2] "Удаляются %d снимков"
+msgstr[0] "Удаление %d снимка"
+msgstr[1] "Удаление %d снимков"
+msgstr[2] "Удаление %d снимков"
 
 #: ../src/control/jobs/control_jobs.c:1040
 msgid "failed to 

[darktable-dev] NEF → White balance failed to read

[Timur Irikovich Davletshin]

What can I do to fix this? I posted sample here already — https://discu
ss.pixls.us/t/nikon-a-specific-raw-sample-wanted/5483/20

[rawspeed] (_DSC0137.NEF)
rawspeed::NikonDecompressor::NikonDecompressor(const
rawspeed::RawImage&, rawspeed::ByteStream, rawspeed::uint32), line 172:
Nikon 14-bit lossy-after-split raws are still broken.
[temperature] failed to read camera white balance information from
`_DSC0137.NEF'!
allocation failed???

Timur.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Russian translation update

[Timur Irikovich Davletshin]

It works for 2.4 too, I just noticed that some things were added in
master. So I updated things like 'media' in printing mode, metainfo
(export width x height) and some new error messages. I also changed
other messages with aim to give them short and uniform look.

Timur.

On Sat, 2018-05-05 at 12:37 +0200, Tobias Ellinghaus wrote:
> Am Freitag, 4. Mai 2018, 12:35:33 CEST schrieb Timur Irikovich
> Davletshin:
> > See small patch in the attachment to reach 100% translation in
> > current
> > master branch.
> 
> Thank you, pushed to master. Could you update the 2.4.x branch, too?
> I am not 
> sure if just picking the changes is the right thing – I have no way
> of 
> checking. :-)
> 
> > Regards,
> > 
> > Timur.
> 
> Tobias
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Russian translation update

[Timur Irikovich Davletshin]

Just as documentation says, that small patches can be sent via mailing
lists :)

See patch in the attachment. It's just small addition to changes which
Alexandre Prokoudine generously agreed to commit.

Regards,

Timur.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.orgFrom df0aa5f56956a3fcf52f392cfe193185b7f2e458 Mon Sep 17 00:00:00 2001
From: "Timur I. Davletshin" 
Date: Wed, 2 May 2018 19:36:32 +0300
Subject: [PATCH] Russian translation update.

---
 po/ru.po | 201 +++
 1 file changed, 112 insertions(+), 89 deletions(-)

diff --git a/po/ru.po b/po/ru.po
index 90ebd4def..c68de7e57 100644
--- a/po/ru.po
+++ b/po/ru.po
@@ -117,8 +117,7 @@ msgstr "Всегда запрашивать подтверждение на уд
 
 #: ../build/src/preferences_gen.h:1687
 msgid "ask before erasing images from disk / discarding history stack"
-msgstr ""
-"Подтверждение удаления снимков и удаления истории изменений"
+msgstr "Подтверждение удаления снимков и удаления истории изменений"
 
 #: ../build/src/preferences_gen.h:1699
 msgid ""
@@ -686,7 +685,7 @@ msgstr "Профиль планировщика OpenCL"
 #: ../src/gui/preferences.c:587
 msgctxt "preferences"
 msgid "default"
-msgstr "Вернуть исходные значения"
+msgstr "По умолчанию"
 
 #: ../build/src/preferences_gen.h:2833
 msgctxt "preferences"
@@ -706,11 +705,10 @@ msgid ""
 "parallel on two different GPUs; very fast GPU - process both pixelipes "
 "sequentially on the GPU."
 msgstr ""
-"defines how preview and full pixelpipe tasks are scheduled on OpenCL enabled "
-"systems. default - GPU processes full and CPU processes preview pipe "
-"(adaptable by config parameters); multiple GPUs - process both pixelpipes in "
-"parallel on two different GPUs; very fast GPU - process both pixelipes "
-"sequentially on the GPU."
+"Определяет поведение планировщика на системах, поддерживающих OpenCL. "
+"По умолчанию — GPU обрабатывает полноразмерные изображения, а CPU предпросмотр. "
+"Несколько GPU — обработкой каждой задачи занимается выделенный GPU. "
+"Очень быстрый GPU — обе задачи выполняются на одном GPU параллельно."
 
 #: ../build/src/preferences_gen.h:2872
 msgid "always use LittleCMS 2 to apply output color profile"
@@ -895,18 +893,23 @@ msgid ""
 "them through a lighttable. It also enables you to develop raw images and "
 "enhance them in a darkroom."
 msgstr ""
+"darktable управляет цифровыми фотографиями в формате Raw, позволяя просматривать их, каталогизировать и редактировать."
 
 #: ../data/darktable.appdata.xml.in.h:3
 msgid ""
 "Other modes besides lighttable and darkroom are a map for geotagging, "
 "tethering, print and a slideshow."
 msgstr ""
+"Помимо этого darktable поддерживает геотеггинг, режим дистанционной съёмки, "
+"печать и слайдшоу."
 
 #: ../data/darktable.appdata.xml.in.h:4
 msgid ""
 "darktable supports most modern camera's raw formats, and does all of its "
 "processing at very high precision."
 msgstr ""
+"darktable поддерживает большой спектр современных камер и "
+"выполняет обработку снимков с очень большой точностью."
 
 #: ../data/darktable.desktop.in.h:1
 msgid "Virtual Lighttable and Darkroom"
@@ -942,23 +945,25 @@ msgid ""
 "average dE: %.02f\n"
 "max dE: %.02f"
 msgstr ""
+"Средн. dE: %.02f\n"
+"Макс. dE: %.02f"
 
 #: ../src/cli/main.c:106
 msgid "TODO: sorry, due to API restrictions we currently cannot set the BPP to"
-msgstr ""
+msgstr "Извините, но из-за ограничений API установка BPP на данный момент не поддерживается"
 
 #: ../src/cli/main.c:118
 msgid "unknown option for --hq"
-msgstr ""
+msgstr "Неизвестный параметр для --hq"
 
 #: ../src/cli/main.c:134
 msgid "unknown option for --upscale"
-msgstr ""
+msgstr "Неизвестный параметр для --upscale"
 
 #: ../src/cli/main.c:188
 #, c-format
 msgid "error: output file is a directory. please specify file name"
-msgstr ""
+msgstr "Ошибка: Файл вывода не может быть каталогом. Укажите имя файла."
 
 #: ../src/cli/main.c:197
 msgid "output file already exists, it will get renamed"
@@ -1145,7 +1150,7 @@ msgstr "BRG (для тестирования)"
 #: ../src/common/cups_print.c:322
 #, c-format
 msgid "file `%s' to print not found for image %d on `%s'"
-msgstr ""
+msgstr "Не найден файл «%s» для печати снимка %d на «%s»"
 
 #: ../src/common/cups_print.c:383
 #, c-format
@@ -1155,12 +1160,12 @@ msgstr "Ошибка при печати снимка %d на «%s»"
 #: ../src/common/cups_print.c:385
 #, c-format
 msgid "printing image %d on `%s'"
-msgstr "Печать снимка %d на `%s'"
+msgstr "Печать снимка %d на «%s»"
 
 #: ../src/common/darktable.c:211
 #, c-format
 msgid "found strange path `%s'"
-msgstr "Найдено странное расположение `%s'"
+msgstr "Найдено странный путь «%s»"
 
 #: ../src/common/darktable.c:228
 #, c-format
@@ -1170,7 +1175,7 @@ msgstr "Ошибка при загрузке каталога «%s»"
 #: ../src/common/darktable.c:251
 #, c-format
 msgid "file `%s' has 

Re: [darktable-dev] Sony a7iii

[Timur Irikovich Davletshin]

Have you tried it after conversion to DNG?

On Mon, 2018-04-30 at 08:47 -0700, Barton Hewett wrote:
> Hi, just got a new Sony a7iii and get this message when trying to 
> develop picture shot on camera.  I'm guessing this is because camera
> is 
> so new and not in database yet?
> 
> 
> 
> _
> __
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscribe@lists.darktab
> le.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Re: [darktable - Feature #12143] (New) Usability → Presets from official documentation

[Timur Irikovich Davletshin]

If you need those presets/examples from DT documentation:

1. Close DT
2. Save presets.sql
2. Open terminal
3. cd ~/.config/darktable
4. sqlite3 data.db < ~/Downloads/presets.sql

These includes:
1. 'lowpass' module → 'bring up shadows',
2. 'highpass' module → 'gritty details',
3. B/W film presets in 'channel mixer' module
4. 'increase contrast & saturation' in 'tone curve' module,
5. non-local means + (HSV) lightness operator and wavelet + (HSV)
color/chroma in 'profiled denoise' module.

Hope you will find it useful.

On Sun, 2018-04-15 at 17:23 +0300, redm...@darktable.org wrote:
> Issue #12143 has been reported by Timur Davletshin.
> 
> 
> Feature #12143: Usability → Presets from official documentation
> https://www.darktable.org/redmine/issues/12143
> 
> * Author: Timur Davletshin
> * Status: New
> * Priority: Low
> * Assignee: 
> * Category: 
> * Target version: 
> * Affected Version: 2.4.2
> * System: all
> * bitness: 64-bit
> * hardware architecture: amd64/x86
> 
> Make approaches described in official documentation available as
> modules presets.
> 
> For example:
> 
> 1. Lowpass module with negative contract and blending operator to
> bring up shadows,
> 2. Highpass to improve contrast (gritty details example),
> 3. Film presets in 'channel mixer' module documentation section,
> 4. Color saturation example from 'tone curve' section,
> 5. Profiled denoise presets: non-local means + (HSV) lightness
> operator and wavelet + (HSV) color.
> 
> Thanks in advance.
> 
> 
> 
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

presets.sql
Description: application/sql

Re: [darktable-dev] Bug report

[Timur Irikovich Davletshin]

You don't need another instance to add second shape. IMO everything
works as expected.

On Fri, 2018-04-20 at 22:31 +0300, Henkka wrote:
>   Tried to make two low pass masks. Mission impossible. Watch this 
> video. Easier to show than try to tell.
> 
> https://youtu.be/wBy8nYlOpmQ
> 
> _
> __
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscribe@lists.darktab
> le.org
> 
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Re: XML parser → Huge sidecar files

[Timur Irikovich Davletshin]

BTW, thanks for pointing to the "cleanup unused shapes" solution!

On Tue, 2018-04-17 at 18:27 +0200, Ulrich Pegelow wrote:
> You don't need to do this manually. Just go into the mask manager
> (left 
> hand panel in the darkroom view), press the right mouse button. On
> the 
> menu that appears you select "cleanup unused shapes".
> 
> In your case the huge number of invisible shapes comes from the spot 
> removal tool. The root cause lies in a combination of two facts. 
> darktable does not delete shapes automatically and spot removal
> shapes 
> do not appear in the mask manager. So even if you reset the spot
> removal 
> tool all shapes created will still exist in the data set and you do
> not 
> even know because the mask manager does not tell you. We should
> consider 
> how to change this behavior.
> 
> In the time being you can manually clean up unused shapes with the 
> method described above.
> 
> ulrich
> 
> 
> Am 16.04.2018 um 10:55 schrieb Timur Irikovich Davletshin:
> > Well, I was able to edit them with sed script to remove all masks,
> > but
> > parsing XML to find used/unused masks is beyond my skills (I'm not
> > familiar with XMP standards). I believe future DT releases should
> > sort
> > this out in some way. At least for this issue is very critical, it
> > slows down opening/closing files in my library multiple times.
> > 
> > On Mon, 2018-04-16 at 10:19 +0200, sturmflut wrote:
> > > Hello,
> > > 
> > > I can confirm this for the latest version in the darktable-2.4.x
> > > branch
> > > (commit edf1168371be288f071986d93a47fb3e082573de). The sidecar
> > > files
> > > seem to contain an awful lot of masks, but I can't seem to see
> > > which
> > > module even uses them?
> > > 
> > > cheers,
> > > Simon
> > > 
> > > 
> > > On 15.04.2018 20:28, Timur Irikovich Davletshin wrote:
> > > > It looks like I was able to find what action causes this
> > > > problem.
> > > > 
> > > > Steps to reproduce:
> > > > 
> > > > 1. Download, unpack and import as folder — https://drive.google
> > > > .com
> > > > /ope
> > > > n?id=14sZLgnpZSV5W3pw1K_8owHW29Heq9EWz (don't pay attention to
> > > > content
> > > > and settings)
> > > > 2. Choose second picture and click (in lighttable mode) copy
> > > > history
> > > > stack and choose, let's say, 'shadows and highlights' settings.
> > > > 3. Apply it (paste) to first picture, open it, compress history
> > > > stack
> > > > and close DT.
> > > > 4. Now compare XMP files, first one is twice bigger than second
> > > > one
> > > > (in
> > > > my case ~700kB vs ~1400kB). Meanwhile in darkroom mode history
> > > > stack
> > > > looks the same.
> > > > 
> > > > Can anyone comment, what is going on here?
> > > 
> > > _
> > > 
> 
> _
> __
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscribe@lists.darktab
> le.org
> 
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Re: XML parser → Huge sidecar files

[Timur Irikovich Davletshin]

Actually I didn't get why masks are getting copied when I ask only
particular module settings. But anyway I hope it will change soon,
opening every file (especially when they are so slow) is just so time
consuming. It should be 'all at once' action :)

On Tue, 2018-04-17 at 18:27 +0200, Ulrich Pegelow wrote:
> You don't need to do this manually. Just go into the mask manager
> (left 
> hand panel in the darkroom view), press the right mouse button. On
> the 
> menu that appears you select "cleanup unused shapes".
> 
> In your case the huge number of invisible shapes comes from the spot 
> removal tool. The root cause lies in a combination of two facts. 
> darktable does not delete shapes automatically and spot removal
> shapes 
> do not appear in the mask manager. So even if you reset the spot
> removal 
> tool all shapes created will still exist in the data set and you do
> not 
> even know because the mask manager does not tell you. We should
> consider 
> how to change this behavior.
> 
> In the time being you can manually clean up unused shapes with the 
> method described above.
> 
> ulrich
> 
> 
> Am 16.04.2018 um 10:55 schrieb Timur Irikovich Davletshin:
> > Well, I was able to edit them with sed script to remove all masks,
> > but
> > parsing XML to find used/unused masks is beyond my skills (I'm not
> > familiar with XMP standards). I believe future DT releases should
> > sort
> > this out in some way. At least for this issue is very critical, it
> > slows down opening/closing files in my library multiple times.
> > 
> > On Mon, 2018-04-16 at 10:19 +0200, sturmflut wrote:
> > > Hello,
> > > 
> > > I can confirm this for the latest version in the darktable-2.4.x
> > > branch
> > > (commit edf1168371be288f071986d93a47fb3e082573de). The sidecar
> > > files
> > > seem to contain an awful lot of masks, but I can't seem to see
> > > which
> > > module even uses them?
> > > 
> > > cheers,
> > > Simon
> > > 
> > > 
> > > On 15.04.2018 20:28, Timur Irikovich Davletshin wrote:
> > > > It looks like I was able to find what action causes this
> > > > problem.
> > > > 
> > > > Steps to reproduce:
> > > > 
> > > > 1. Download, unpack and import as folder — https://drive.google
> > > > .com
> > > > /ope
> > > > n?id=14sZLgnpZSV5W3pw1K_8owHW29Heq9EWz (don't pay attention to
> > > > content
> > > > and settings)
> > > > 2. Choose second picture and click (in lighttable mode) copy
> > > > history
> > > > stack and choose, let's say, 'shadows and highlights' settings.
> > > > 3. Apply it (paste) to first picture, open it, compress history
> > > > stack
> > > > and close DT.
> > > > 4. Now compare XMP files, first one is twice bigger than second
> > > > one
> > > > (in
> > > > my case ~700kB vs ~1400kB). Meanwhile in darkroom mode history
> > > > stack
> > > > looks the same.
> > > > 
> > > > Can anyone comment, what is going on here?
> > > 
> > > _
> > > 
> 
> _
> __
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscribe@lists.darktab
> le.org
> 
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Re: XML parser → Huge sidecar files

[Timur Irikovich Davletshin]

Well, I was able to edit them with sed script to remove all masks, but
parsing XML to find used/unused masks is beyond my skills (I'm not
familiar with XMP standards). I believe future DT releases should sort
this out in some way. At least for this issue is very critical, it
slows down opening/closing files in my library multiple times.

On Mon, 2018-04-16 at 10:19 +0200, sturmflut wrote:
> Hello,
> 
> I can confirm this for the latest version in the darktable-2.4.x
> branch
> (commit edf1168371be288f071986d93a47fb3e082573de). The sidecar files
> seem to contain an awful lot of masks, but I can't seem to see which
> module even uses them?
> 
> cheers,
> Simon
> 
> 
> On 15.04.2018 20:28, Timur Irikovich Davletshin wrote:
> > It looks like I was able to find what action causes this problem.
> > 
> > Steps to reproduce:
> > 
> > 1. Download, unpack and import as folder — https://drive.google.com
> > /ope
> > n?id=14sZLgnpZSV5W3pw1K_8owHW29Heq9EWz (don't pay attention to
> > content
> > and settings)
> > 2. Choose second picture and click (in lighttable mode) copy
> > history
> > stack and choose, let's say, 'shadows and highlights' settings.
> > 3. Apply it (paste) to first picture, open it, compress history
> > stack
> > and close DT.
> > 4. Now compare XMP files, first one is twice bigger than second one
> > (in
> > my case ~700kB vs ~1400kB). Meanwhile in darkroom mode history
> > stack
> > looks the same.
> > 
> > Can anyone comment, what is going on here?
> 
> _
> __
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscribe@lists.darktab
> le.org
> 
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Re: XML parser → Huge sidecar files

[Timur Irikovich Davletshin]

It looks like I was able to find what action causes this problem.

Steps to reproduce:

1. Download, unpack and import as folder — https://drive.google.com/ope
n?id=14sZLgnpZSV5W3pw1K_8owHW29Heq9EWz (don't pay attention to content
and settings)
2. Choose second picture and click (in lighttable mode) copy history
stack and choose, let's say, 'shadows and highlights' settings.
3. Apply it (paste) to first picture, open it, compress history stack
and close DT.
4. Now compare XMP files, first one is twice bigger than second one (in
my case ~700kB vs ~1400kB). Meanwhile in darkroom mode history stack
looks the same.

Can anyone comment, what is going on here?

On Sat, 2018-04-07 at 19:22 +0300, Timur Irikovich Davletshin wrote:
> Hello everybody!
> 
> I'm sorry but I will address this question again (posted earlier as
> user question) because this issue just irritates me quite often.
> 
> I have a lot of files imported in 2014-15 which have problem I
> describe
> a bit later. May be it will give some clues but files imported in
> 2012-
> 13 and in 2016 (and later) are not affected (years started to use
> DT).
> I open files randomly time to time so DT updates old saidecar files
> if
> it likes. So affected files are not original files created in 2014-
> 15.
> 
> I don't know since which DT version it started but all files which
> are
> affected now have huge sidecar files — 10-25 megabytes. So as
> expected
> XML parser (which is single threaded I believe and not hardware
> accelerated) takes very long time to load and write sidecar files.
> Meanwhile editing is not any slower.
> 
> I tried little trick — I just removed all history stack by clicking
> "original" and compressing it. I expected sidecar to shrink but it
> remained nearly the same. I tried opening this file and it is full of
> old tags related to masks, spot removal, etc... which were used long
> time ago and no longer present in history stack or mask manager.
> Looks
> like DT doesn't handle (or couldn't handle in earlier versions)
> importing of files created in previous DT versions.
> 
> Thanks is advance,
> 
> Timur.
> 
> P.S. Sample RAW + XMP (plus XMP after removing history stack):
> https://
> drive.google.com/open?id=1RwMA7Aq5PiF3iORSGsN5xpkYEv-IEHQ0
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] DNG vs RAW → Lens and focus info

[Timur Irikovich Davletshin]

On Wed, 2018-04-04 at 13:36 +0200, Tobias Ellinghaus wrote:
> Am Mittwoch, 4. April 2018, 13:15:39 CEST schrieb Timur Irikovich
> Davletshin:
> > Hello everybody!
> > 
> > Just decided to play with DNG converter and discovered problem
> > related
> > to lens data interpretation by DT (2.4.2).
> > 
> > 1. NEF file loaded by DT applies correct lens parameters.
> > Lens info shown by DT: Nikon AF-S DX Nikkor 18-55mm f/3.5-5.6G
> > VR II
> > 
> > 2. DNG file cannot apply it because wrong EXIF information is used
> > (short lens name vs. full).
> > Lens info shown by DT: 18.0-55.0 mm f/3.5-5.6
> > 
> > 3. Focus information also is lost in DNG.
> 
> That's why we tell everyone to never convert to DNG.
> 
> Tobias
> 
> [...]

So, after little digging I found following (correct me if I'm wrong):

1. DT relies only on libexiv2 in extraction of EXIF metadata.
2. exiv2 fails to extract vendor specific information from DNG file
(converted via Adobe DNG Converter) when compared with exiftool. But
original NEF data is there.
3. As last resort for lens detection DT relies on Exif.Photo.LensModel,
which is just ASCII string encoded by converter.
4. Converter writes ambiguous data in Exif.Photo.LensModel without. No
vendor, no exact model, just '18.0-55.0 mm f/3.5-5.6'.
5. Feeding vague data to lensfun gives no good results.
6. Native DNG by Pentax use non-standard vendor specific Exif.Pentax*
namespace.
7. Focus distance information is also vendor specific.

If not mistaken problem should be fixed on very root... which is
libexiv2. But it's just MHO.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org