Re: [darktable-dev] Visibility of stars

2019-12-17 Thread Julian Rickards
Great, thanks On Tue, Dec 17, 2019 at 1:29 PM Nicolas Auffray wrote: > The whole UI has been changed on 3.0 and visibility of stars is better. > Anyway, they come in a widget for thumbnails star so can't be changed by > CSS. > > > Le 17/12/2019 à 16:45, Julian Rickar

[darktable-dev] Visibility of stars

2019-12-17 Thread Julian Rickards
Is the visibility (colour) of the stars controlled in CSS in 3.0? Currently, in 2.6.3, I find them a bit faint. If not, not a deal breaker, then just a request for 3.01. ___ darktable developer mailing list to unsubscribe sen

[darktable-dev] Export settings, not storing "on conflict" setting

2019-12-10 Thread Julian Rickards
Hi: I'm running 2.6.3, I haven't tried any of the dev versions so can someone check this for me please? When I create/edit an Export preset and set the "on conflict" to "overwrite", it doesn't save this setting but reverts to "create unique filename". Is this "reluctance" to save the "on conflic

Re: [darktable-dev] basic adjustments

2019-11-18 Thread Julian Rickards
> to face new challenges and give a new start to your carreer." > Le 18/11/2019 à 16:30, Richard Hobday a écrit : > > -- Tongue firmly in cheek -- > en-GB or en-US ? > That is the real question. > They are two very different languages, at present darktable seems to &g

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

2019-11-18 Thread Julian Rickards
Perhaps: 200 RAW (200 JPG, ignored) On Mon, Nov 18, 2019 at 9:41 AM Timur Irikovich Davletshin < timur.davlets...@gmail.com> wrote: > Well, I agree it's not a big deal. But if one shoots (just as example) > raw+jpeg and then tries to import only raw files... — he will get > message of importing,

Re: [darktable-dev] basic adjustments

2019-11-18 Thread Julian Rickards
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 (

Re: [darktable-dev] Q: Store GPS location in RAW instead of XMP?

2019-11-16 Thread Julian Rickards
Yup, that'll explain my confusion. Thanks On Fri, Nov 15, 2019 at 5:28 PM jys wrote: > > > On Fri, Nov 15, 2019, at 12:35, Julian Rickards wrote: > > Does that suggest then that the GPS data is stored in the associated > > JPG? What if the user doesn't shoot

Re: [darktable-dev] Q: Store GPS location in RAW instead of XMP?

2019-11-15 Thread Julian Rickards
Does that suggest then that the GPS data is stored in the associated JPG? What if the user doesn't shoot JPG? What about other EXIF data, where is that stored? Just curious. On Fri, Nov 15, 2019 at 3:32 PM Aurélien Pierre wrote: > Hi, > > we never touch the raw files to avoid any risk of data c

Re: [darktable-dev] darktable 3.0.0rc0 released

2019-11-06 Thread Julian Rickards
;s all. On Wed, Nov 6, 2019 at 12:19 PM Moritz Moeller wrote: > On 6.11.19 14:35, Julian Rickards wrote: > > From my perspective, filmic2 isn't appropriate. I work in the > > publication services section of an Ontario (Canada) government ministry > > and when we as

Re: [darktable-dev] darktable 3.0.0rc0 released

2019-11-06 Thread Julian Rickards
>From my perspective, filmic2 isn't appropriate. I work in the publication services section of an Ontario (Canada) government ministry and when we assign "2" to a publication, "1" is gone and no longer available. If the original filmic is gone from this version, then I would just name the new one

Re: [darktable-dev] Drag-and-drop to change module order

2019-11-01 Thread Julian Rickards
Agreed On Fri, Nov 1, 2019 at 3:15 PM jys wrote: > > > On Fri, Nov 1, 2019, at 10:33, Julian Rickards wrote: > > My wishes and comments are GUI-only and related only to the Favourites > tab. > > > > There is another conversation tied into this one about re-orde

Re: [darktable-dev] Drag-and-drop to change module order

2019-11-01 Thread Julian Rickards
this is GUI only - which indeed would be a big > improvement for me. > Now everything seems to be different? > In my view there is a risk that the normal user deteriotes the result > more than it would help him - just a thought. > > -- > > regards > Bernhard > &

Re: [darktable-dev] Drag-and-drop to change module order

2019-11-01 Thread Julian Rickards
In my opinion, re-ordering the modules in the favourites shouldn't be a problem with the pp order. In the same way that you may have written down, on paper, the modules you want to use, in the order you want to use them, re-ordering favourites in this way shouldn't be any different. However, I had

Re: [darktable-dev] Drag-and-drop to change module order

2019-11-01 Thread Julian Rickards
I agree with David, re-ordering the modules in the Favourites tab should *not* affect the pixel-pipe order but I wonder if David and Pascal are thinking differently. As I understand it, Aurlien was re-ordering the modules in the "Pixel-pipe" tab, which of course affected the pp order. However, some

Re: [darktable-dev] (Future) Feature Request - Re-order Favourites Modules

2019-10-29 Thread Julian Rickards
Great, thanks! On Tue, Oct 29, 2019 at 9:57 AM Maurizio Paglia wrote: > Hi Jules, > I am asking for this feature since more or less a couple of years. > So I can simply support your request. > > Thanks, > Maurizio > > Il giorno mar 29 ott 2019 alle ore 14:15 Julian R

[darktable-dev] (Future) Feature Request - Re-order Favourites Modules

2019-10-29 Thread Julian Rickards
Hi: I've just thought of this (too late to be considered for 3.0, LoL). Some people use the Favourites list of modules a lot and it might be nice to be able to order the favourite modules in the order in which you'd like to use them. It is not intended to affect the pixel pipe order. Jules

Re: Fwd: [darktable-dev] Standardization of the writing of mouse interactions in the user manual

2019-10-02 Thread Julian Rickards
ructions in the manual to your system. On Wed, Oct 2, 2019 at 8:44 AM Sturm Flut wrote: > Hi, > > Am 02.10.19 um 14:31 schrieb Julian Rickards: > > This is not clear to me because the mouse wheel can be rolled towards > > the user or away from the user. Perhaps Ctrl+(scroll wh

Re: Fwd: [darktable-dev] Standardization of the writing of mouse interactions in the user manual

2019-10-02 Thread Julian Rickards
Regarding: Ctrl+(mouse wheel) or (scroll wheel) This is not clear to me because the mouse wheel can be rolled towards the user or away from the user. Perhaps Ctrl+(scroll wheel away) and Ctrl+(scroll wheel towards). Although this is rather wordy, you need to differentiate between "away" and "to

[darktable-dev] Move mask modes

2019-09-29 Thread Julian Rickards
dt 2.6.2 on Linux Mint 19.1 I wanted to create a mask but exclude an area within it. I couldn't figure it out but got some help, it was the "mode difference" that I needed. Perfect except, why are these modes in the Mask Manager and not part of the mask creation functions in whatever modules allo

[darktable-dev] Documentation

2019-09-24 Thread Julian Rickards
I'd like to help with documentation but I'm not a very experienced user. Might there be something I could do such as proofing or technical editing (testing)? I presume that I'd have to have 2.7 installed (which I would do but I haven't done so yet). Would I have to keep with nightly builds?

Re: [darktable-dev] 64-stroke limit in "spot removal" module?

2019-08-29 Thread Julian Rickards
dt crashed on me a couple of times while creating many line masks but none of the masks were lost and I was able to continue until all 34 were complete. It happened while creating the masks but not afterwards when I was doing other things and the exports went fine. However, there may also be a limi

[darktable-dev] Simple Text Watermark Editor

2019-08-27 Thread Julian Rickards
I know that there's been a message about halting new features for the next release in December but I'd like to post this for, if nothing else, future consideration. It is my understanding that the Simple Text watermark content must be in SVG format. However, the documentation is not very clear on

Re: [darktable-dev] tagging module improvements

2019-08-06 Thread Julian Rickards
> At least in 2.7.x you can filter images by tag in the "collect images" > module and then apply a style to all filtered images. > > kind regards, > Simon > > > > Am 06.08.19 um 16:33 schrieb Julian Rickards: > > Not sure if this might be of interest. > &

Re: [darktable-dev] tagging module improvements

2019-08-06 Thread Julian Rickards
Not sure if this might be of interest. When I see a composition that appears suitable for B&W, I switch my (Olympus E-M5) camera to Monochrome mode and when I import the image, I tag it "B&W". In Lighttable mode, the image shows up as B&W because of the embedded image in the RAW file but as soon a

Re: [darktable-dev] Error message

2019-08-06 Thread Julian Rickards
I will, good suggestion. I've since learned that my laptop (as I said, 13yrs old) is upgradeable to 8GB so I'll contact a local store and arrange for that. On Fri, Aug 2, 2019 at 2:19 AM KOVÁCS István wrote: > On Fri, 2 Aug 2019, 03:44 Julian Rickards, > wrote: > &

Re: [darktable-dev] Error message

2019-08-01 Thread Julian Rickards
g 2019, 20:56 Julian Rickards, > wrote: > >> I've been getting the following error >> >> 'tiling failed for module "atrous", image may be garbled' >> > > I think this belongs to the user list, but anyway: read the manual, and &g

[darktable-dev] Error message

2019-08-01 Thread Julian Rickards
When exporting to PNG from dt 2.6.2 (fullsized image, no cropping, 16bit png, compression 5, sRGB/Perceptual, Linux Mint 19.1), I've been getting the following error 'tiling failed for module "atrous", image may be garbled' However, the export does proceed and completes and I can't see any "garbl

Re: [darktable-dev] Blending options on their own

2019-06-21 Thread Julian Rickards
OK, thanks, I'll go to another source for help on this as help with using darktable is not suited to this list. On Fri, Jun 21, 2019 at 11:55 AM Patrick Shanahan wrote: > * Julian Rickards [06-21-19 11:26]: > > Sometimes, when I want a dramatic B&W, I'll convert usin

[darktable-dev] Blending options on their own

2019-06-21 Thread Julian Rickards
Sometimes, when I want a dramatic B&W, I'll convert using the Color Channel, then open a second instance to apply nothing more than the Softlight overlay. (I wish there was a way to apply both in the same instance of a module but the colours return when I use both the BW preset and a blending optio

Re: [darktable-dev] implementation question: remove all unused modules

2019-06-13 Thread Julian Rickards
> On Thu, Jun 13, 2019 at 11:55 AM Julian Rickards < > julian.ricka...@gmail.com> wrote: > >> Do people modify demosaic, input and output on a regular basis? If not, >>> could the options for each be moved to "Settings" so they

Re: [darktable-dev] implementation question: remove all unused modules

2019-06-13 Thread Julian Rickards
> > Do people modify demosaic, input and output on a regular basis? If not, > could the options for each be moved to "Settings" so they aren't listed as > a module but modifiable when needed? > > ___ darktable developer mailin

Re: [darktable-dev] implementation question: remove all unused modules

2019-06-13 Thread Julian Rickards
Not to throw gas on the fire but it seems to me that some of this is already done. In Lighttable, when you wish to copy the history from one image to another, there are some modules missing (input and output) and also, the "off" modules aren't included in the possible modules to copy over. On Thu

Re: [darktable-dev] implementation question: remove all unused modules

2019-06-11 Thread Julian Rickards
I must say that I've never used the Compress History option in the Lighttable, just in the Darkroom. Are there any differences? On Tue, Jun 11, 2019 at 1:01 PM jys wrote: > On Tue, Jun 11, 2019, at 07:47, thokster wrote: > > > Is the "compress history" button in lighttable view doing anything el

Re: [darktable-dev] implementation question: remove all unused modules

2019-06-10 Thread Julian Rickards
I'm not a programmer of any sort so take what I say with a grain of salt. When I compress the history, I like it to be clean so sometimes, there is/are module(s) with "(off)" in the compressed history. So what do I do? I enable them, then turn them off again so that they appear at the top of the l

Re: [darktable-dev] implementation question: remove all unused modules

2019-06-10 Thread Julian Rickards
Don't have much experience with styles so that point eluded me. Then it makes sense to have a checkbox to in/exclude the "off" modules. On Mon, Jun 10, 2019 at 9:21 AM wrote: > Julian Rickards (2019-Jun-10, excerpt): > > I have always wondered why "off" modul

Re: [darktable-dev] implementation question: remove all unused modules

2019-06-10 Thread Julian Rickards
I have always wondered why "off" modules were included in the compressed history stack so I'm in favour of having them removed. When you compress the history stack, you lose the details of the history that took you to the final stage so losing the "off" modules should be a no-brainer. On Mon, Jun

Re: [darktable-dev] Magnification of modules in Darkroom

2019-05-30 Thread Julian Rickards
I use an older laptop with limited screen real estate and some modules are quite large (height is the issue on my laptop) and any means of improving this would be appreciated. I don't know if it would be part of the consideration but sometimes (recognize that I'm not an expert at dt or photography)

Re: [darktable-dev] Naming Module Instances

2019-05-25 Thread Julian Rickards
4 > Subject: Re: [darktable-dev] Naming Module Instances > To: Julian Rickards , < > darktable-dev@lists.darktable.org> > > > Hello Julian, > > > I'm using 2.4.4 so take this with a grain of salt. > > Yes, please update to 2.6.2... > > > I appreciate tha

Re: [darktable-dev] Naming Module Instances

2019-05-25 Thread Julian Rickards
Ah, thanks. On Sat, May 25, 2019 at 12:13 PM Pascal Obry wrote: > Hello Julian, > > > I'm using 2.4.4 so take this with a grain of salt. > > Yes, please update to 2.6.2... > > > I appreciate that when a new instance of a module has been created, > > that it be named "module #" but I'd like to be

[darktable-dev] Naming Module Instances

2019-05-25 Thread Julian Rickards
I'm using 2.4.4 so take this with a grain of salt. I appreciate that when a new instance of a module has been created, that it be named "module #" but I'd like to be able to name the instance so that I know what I did with it. On a somewhat related note, when choosing a preset, I'd like the modul

Re: [darktable-dev] Options shouldn't be tied to Filmstrip

2019-04-26 Thread Julian Rickards
9 at 1:08 PM Patrick Shanahan wrote: > * Julian Rickards [04-26-19 10:42]: > > Ah, yes, that is a better description. > > > > However, I still maintain that they are not relevant to the film strip > > which (obviously) is part of the bottom panel but more re

Re: [darktable-dev] Options shouldn't be tied to Filmstrip

2019-04-26 Thread Julian Rickards
: > * Julian Rickards [04-26-19 08:54]: > > Hi: > > > > There are 6 options that appear below the main view window in Darkroom > > mode: soft proof, over/underexposure, raw overexposed warning, presets, > > access to styles and one other that I can't determi

[darktable-dev] Options shouldn't be tied to Filmstrip

2019-04-26 Thread Julian Rickards
Hi: There are 6 options that appear below the main view window in Darkroom mode: soft proof, over/underexposure, raw overexposed warning, presets, access to styles and one other that I can't determine here. Access to these options are tied to the visibility of the film strip which I think is wrong

[darktable-dev] Feature request: History read-only in snapshot module

2019-04-23 Thread Julian Rickards
Hi: Maybe it's just me but I have to be careful when using the Snapshot module to compare two different stages of history because I've occasionally left myself in the earlier stage, then perform an edit thereby erasing the history afterwards. I agree with the Snapshot module being based on differ