Re: [darktable-user] darktable 2.6 on Windows, performance issues with large database

[Marc Cousin]

On 10/03/2019 09:31, Pascal Obry wrote:

Ok, I may have an idea.

Can you do that:

- backup your library.db
- run

$ sqlite3 library.db

And enter the following command at the "sqlite >" prompt.

CREATE INDEX tagged_images_index ON tagged_images (imgid, tagid);

And test again. If still slow you may try:

CREATE INDEX tagged_images_imgid_index ON tagged_images (imgid);

Thanks.


Sorry for intruding, but as I'm a DBA guy… :)

That's a bit weird if these indexes improve anything:

(imgid,tagid) is the primary key, so it's auto-indexed.

And a composed index on (imgid,tagid) is perfectly capable of answering 
questions on predicates on imgid alone. In this 2-column tables case, 
it's theoretically even more efficient than having an index on only 
imgid, as it saves a trip to the table to fetch tagid (as the index 
contains all required columns).


So in adding these indexes improved anything, wouldn't it mean that 
there was something fishy on the table ? (missing primary key for instance…)


Regards


darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org

Re: [darktable-user] exporting jpegs: 'quality %'

[Marc Cousin]

On 17/12/2016 20:10, darkta...@911networks.com wrote:
> On Sat, 17 Dec 2016 13:54:52 -0500
> Patrick Shanahan  wrote:
>
>> what %'s do the values 10 and 6 represent?  one w/o photoshop has no
>> knowledge.  are the other "steps (1 to 12)" relevant to your request?
>>
>> one would guess "quality %" would relate to a percentage of 256,
>> but ... -- 
> In photoshop:
>
> https://helpx.adobe.com/photoshop/how-to/save-as-jpeg.html
>
> step 4 of 4 
>
> The values of 'Quality' range from 1 to 12
>
Well, almost anything but lightroom uses percentage for jpeg export…

This article seems to give pointers:
https://photographylife.com/jpeg-compression-levels-in-photoshop-and-lightroom


darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org

Re: [darktable-user] Upgrading to GTK 3.20 ruins all menus (at least in darkroom)

[Marc Cousin]

Or simply install downgrade : https://aur.archlinux.org/packages/downgrade



On 15/04/2016 11:36, Tuấn Kiệt Hồ wrote:
> You could try downgrading to GNOME 3.18 by setting your mirror to Arch
> Linux Archive on April 8th 2016 (more info:
> https://wiki.archlinux.org/index.php/Arch_Linux_Archive)
>
> On Fri, Apr 15, 2016 at 4:27 PM,   wrote:
>> Hi guys,
>>
>> any updates on this topic. Working on ArchLinux with latest Gtk and darktable
>> is more or less unusable with the broken appearance.
>>
>> Regards
>> Karsten
>>
>> On Monday, April 11, 2016 9:01:25 PM CEST Normand Fortier wrote:
>>> Of course, silly me, I do not get the warnings after correcting the css
>>> file... So no more warnings but appearance does not change.
>>>
>>> Le 2016-04-11 20:47, Owen Mays a écrit :
 I get the warnings when I launch darktable (no options) from the
 command line. The warnings show up in the terminal window.

 -Owen

 On Mon, Apr 11, 2016 at 7:41 PM, Normand Fortier

 > wrote:
 A silly question, but how did you get the warnings? I just
 upgraded to gtk 3.20 (archlinux), if I start darktable with -d all
 I do not get the warnings as part of the output. Anyway I tried
 modifying /usr/share/darktable/darktable.css to correct the
 warnings, but the appearance of darktable does not change (still
 has the large buttons on top).

 Normand

 Le 2016-04-10 14:23, Owen Mays a écrit :
 I would be happy to work on a solution if someone could point
 me to a gtk/css reference or guide. I found this:
 
 https://developer.gnome.org/gtk3/stable/GtkWidget.html#GtkWidget--> >  
s-wide-separators but all it says is

 "|GtkWidget:wide-separators| has been deprecated since version
 3.20 and should not be used in newly-written code. Use CSS
 properties on the separator elements to style separators; the
 value of this style property is ignored."

 Can anyone tell me what the buttons on the top of each module
 are called? (the on/off, presets menu, and reset buttons). It
 looks like their size has been expanded and is pushing
 everything else too large.

 Thanks,

 Owen

 On Sun, Apr 10, 2016 at 12:51 PM, Pascal Obry  >> wrote:
 Le dimanche 10 avril 2016 à 12:40 -0500, Owen Mays a écrit :
 > I have created an issue in redmine:
 http://redmine.darktable.org/issu

 > es/10990
 > Let me know if there is more information that would be

 helpful,

 or if

 > there is anything else I can test.

 Nothing more until either someone with Gtk 3.20 step in or my
 GNU/Debian sid move to 3.20 :)

 --

   Pascal Obry /  Magny Les Hameaux (78)

   The best way to travel is by means of imagination

 http://v2p.fr.eu.org
 http://www.obry.net

   gpg --keyserver keys.gnupg.net 

 

 --recv-key F949BD3B

 __
 __>
 darktable user mailing list
 to unsubscribe send a mail to

 darktable-user+unsubscr...@lists.darktable.org
 

 >



 __
 __ darktable user mailing list to unsubscribe send a mail
 to
 darktable-user+unsubscr...@lists.darktable.org
 

 __
 __ darktable user mailing list
 to unsubscribe send a mail to
 darktable-user+unsubscr...@lists.darktable.org
 

 __
 __ darktable user mailing list to unsubscribe send a mail to
 darktable-user+unsubscr...@lists.darktable.org
>>> 
>>> darktable user mailing list

Re: [darktable-user] Upgrading to GTK 3.20 ruins all menus (at least in darkroom)

[Marc Cousin]

On 10/04/2016 09:28, Pascal Obry wrote:
> Le dimanche 10 avril 2016 à 02:18 -0500, Owen Mays a écrit :
>> I'm seeing the same thing. It looks like the buttons (the on/off for
>> each module, the dropdown button for presets, the rotate left and
>> rotate right buttons, etc) are now enormous.  
>>
>> If I launch from the command line, I see these warnings:
>>
>> (darktable:11842): Gtk-WARNING **: Theme parsing error:
>> darktable.css:30:26: The :insensitive pseudo-class is deprecated. Use
>> :disabled instead.
> ...
>
>> (darktable:11842): Gtk-WARNING **: Theme parsing error:
>> darktable.css:436:30: The style property GtkWidget:wide-separators is
>> deprecated and shouldn't be used anymore. It will be removed in a
>> future version
>>
>> (darktable:11842): Gtk-WARNING **: Theme parsing error:
>> darktable.css:437:30: The style property GtkWidget:separator-width is
>> deprecated and shouldn't be used anymore. It will be removed in a
>> future version
>>
>> (darktable:11842): Gtk-WARNING **: Theme parsing error:
>> darktable.css:438:31: The style property GtkWidget:separator-height
>> is deprecated and shouldn't be used anymore. It will be removed in a
>> future version
>>
>>
>> Should this be a bug post in redmine?
> Yes please.
>
> I have attached a darktable.css fixed blindly. I don't have Gtk+ 3.20
> so can't say it works or not.
>
> Please put it into:
>
>~/.config/darktable
>
> And report if it works or not.
>
It doesn't work for me. Got rid of the parsing error, but the offset is
still here.

Regards

darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org