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

Edgardo Hoszowski (2019-Jun-12, excerpt): > > > Edgardo Hoszowski (2019-Jun-11, excerpt): > > > > I usually want to keep the (off) modules when compressing history, > > > > so the current behavior should be kept. > > > > > > My implementa

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

h is already in master and was not built by me, can > break images, do so in bulk mode, not undoable, and without showing > the effect in lighttable). > > Edgardo Hoszowski (2019-Jun-11, excerpt): > > I usually want to keep the (off) modules when compressing history, > &

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

I can see myself using such an option from time to time, but I usually want to keep the (off) modules when compressing history, so the current behavior should be kept. As already said somewhere here, some (off) modules can't be removed from history, or it will change the edit. In particular, modul

Re: [darktable-dev] Naming Module Instances

I agree that there's not much space, so the description usually is not fully displayed and the result text is confusing, but just hiding the module's name won't probably do it, some other logic should be defined. For instance, when creating a new instance the #{instance number} is set, by just hid

Re: [darktable-dev] ATTENTION: darktable master may have some GUI glitches

Can you share a print screen of the lighttable/darktable with some modules opened? (import, collect images, select, etc..) I'm on xubuntu, upgraded to 18.04, installed the fonts, and I'm not sure if what I'm having is correct, but it doesn't look OK. El dom., 14 abr. 2019 a las 20:10, David Vince

Re: [darktable-dev] Unsupported input profile

> Good question...can't say I've ever noticed that reported in darkroom, > where should I look for it? > Do you mean sRGB? If so, that's what it should be. > > Sorry, I should be more specific, in darkroom go to the 'input color profile' module, and there the 'input profile' setting. > _

Re: [darktable-dev] Unsupported input profile

> On Sat, 13 Apr 2019 11:39:27 +1000, Edgardo Hoszowski > wrote: > > > Can't duplicate, the input color profile is enhanced color matrix, is > > that correct? > > That's a question I can't answer, not something I have any knowledge of. > I mean, is t

Re: [darktable-dev] Unsupported input profile

Can't duplicate, the input color profile is enhanced color matrix, is that correct? Maybe it has something to do with the raw, does this happens with raw's from other cameras? El vie., 12 abr. 2019 a las 22:22, Terry Duell () escribió: > On Sat, 13 Apr 2019 11:13:40 +1000, Edga

Re: [darktable-dev] Unsupported input profile

That's strange, should be the full path+file name in the console, unless you're using an in-memory profile. Can you share a xmp? El vie., 12 abr. 2019 a las 22:08, Terry Duell () escribió: > Hello Edgardo, > > On Sat, 13 Apr 2019 10:03:33 +1000, Edgardo Hoszowski > wrote:

Re: [darktable-dev] Unsupported input profile

No reference to the profile that's not supported? El vie., 12 abr. 2019 a las 20:52, Terry Duell () escribió: > Hello, > A build of the current master (9dce2d1eff6b8f134b83310a0500fa5c1fc8c78a) > is putting a message up on each image in Darkroom ' unsupported input > profile has been replaced by

Re: [darktable-dev] darktable from current git doesn't response after database conversion

Sure, no problem, seems that the issue can be fixed by cleaning the install directory anyway. El mié., 13 mar. 2019 a las 18:04, Heiko Bauke () escribió: > Hi Edgardo, > > Am 12.03.19 um 12:51 schrieb Edgardo Hoszowski: > > Can you share your old config directory? If is too big ma

Re: [darktable-dev] darktable from current git doesn't response after database conversion

Can you share your old config directory? If is too big maybe remove some images, just a few should do it. (I don't need the actual images, just the config directory) ___ darktable developer mailing list to unsubscribe send a m

Re: [darktable-dev] darktable from current git doesn't response after database conversion

Should work with any version, at least if it works with 2.6 Do you know the database version you are migrating from? El lun., 11 mar. 2019 a las 21:17, Heiko Bauke () escribió: > Hi, > > Am 10.03.19 um 12:28 schrieb Alexander Rabtchevich: > > Darktable doesn't run (doesn't show lightroom). Afte

Re: [darktable-dev] darktable from current git doesn't response after database conversion

x7fff93fff700 (LWP 17554)] > [New Thread 0x7fff937fe700 (LWP 17555)] > [New Thread 0x7fff92ffd700 (LWP 17556)] > [New Thread 0x7fff927fc700 (LWP 17557)] > [Thread 0x7fffe31ab700 (LWP 17530) exited] > [Thread 0x7fff8a7fc700 (LWP 17552) exited] > [New Thread 0x7fff8a7fc700 (LWP 1755

Re: [darktable-dev] darktable from current git doesn't response after database conversion

095)] > [New Thread 0x7fffc5286700 (LWP 5096)] > [New Thread 0x7fffba420700 (LWP 5097)] > [New Thread 0x7fffb9c1f700 (LWP 5098)] > [New Thread 0x7fffb941e700 (LWP 5099)] > [New Thread 0x7fffb8c1d700 (LWP 5100)] > [New Thread 0x7fffb1193700 (LWP 5101)] > [Thread 0x7fffc5286700 (LWP

Re: [darktable-dev] darktable from current git doesn't response after database conversion

> The situation with unknown plugins can happen for a regular user. I > haven't created the anlfyeni plugin by myself - it have been in the > database for sometimes. And the program should threat the unknown > plugins somehow in a common matter at the conversion stage. > I'll try to modify the sour

Re: [darktable-dev] darktable from current git doesn't response after database conversion

This has probably nothing to do with performance, but this errors are saying that an iop_order must be defined for some iop: operation anlfyeni with no iop_order while upgrading database you have to add it in the right order somewhere here: https://github.com/darktable-org/darktable/blob/master/

[darktable-dev] Re: [darktable-user] ATTENTION: darktable master may go unstable.

So everybody is in the same page, a few notes: Modules can now be moved pretty much everywhere (with shift + drag), if not, the system will not allow it (i.e. RAW modules can't be mixed with Lab/RGB modules) The only exception is: Lab modules can't be before input color profile or after output col

Re: [darktable-dev] Under/over exposure indicator behaviour

There's a new profile setting, histogram profile, on the same pop-up that the softproof profile, that now controls the profile where the histogram, color picker and overexposed work. When softproof or gamma checks are active the histogram and color picker works on that profile, but the overexposed

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

b. 2019 a las 18:59, Timur Irikovich Davletshin (< timur.davlets...@gmail.com>) escribió: > 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 Iriko

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

Can you share the xmp? El lun., 18 feb. 2019 a las 18:22, Timur Irikovich Davletshin (< timur.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

Re: [darktable-dev] filmic crashing dt

Something is going on, it doesn't crash for me, but if I start a new edit, disable the base curve, and in filmic use the auto tune levels I get a B&W image. With and without opencl. El dom., 27 ene. 2019 a las 22:53, David Vincent-Jones () escribió: > darktable 2.7.0+338~g5b7dd1909 > > Just start

Re: [darktable-dev] Re: Setting up a minimal development environment on Windows XP

Before I move to linux I had a VM with xubuntu. It work really well and a lot faster than any windows VM that I had at the time. With that I've been able to do some developments, but eventually I moved to linux for good, still with xubuntu. El mié., 17 oct. 2018 a las 6:44, Anton Shepelev () escr

Re: [darktable-dev] How do you feel about code bounties ?

For lock position and size of drawn masks for safe panning/zooming, you have now a new shortcut to allow to pan & zoom while editing masks, you can find it on views->darkroom 2018-09-08 2:24 GMT-03:00 Aurélien Pierre : > Hi everyone, > > looking at the

[darktable-dev] Masks and history

Hi, Right now masks are not handled by history, and with the new retouch module this will be an issue, as this module is almost all about drawn masks, so I would like to add this functionality. My idea is to record on history a snapshot of dev->forms each time a mask is modified, if it is modifie

[darktable-dev] edges detection mask

Hi, I would like to add an option for edges detection to the masks, I find that it can be very useful when I don't want to sharpen the noise or denoise the edges. I have a test version where I implemented sobel, prewitt & dof that seems to do a good job. Is working on the previous db version, but

Re: [darktable-dev] Mask problem

2016-11-18 14:04 GMT-03:00 Ulrich Pegelow : > Am 17.11.2016 um 01:54 schrieb Edgardo Hoszowski: > >> >> I've done some quick testing: >> >> -circle >> >> shift adjusts the feather anywhere >> control adjusts the opacity anywhere >>

Re: [darktable-dev] Mask problem

2016-11-16 16:22 GMT-03:00 Ulrich Pegelow : > Am 16.11.2016 um 14:27 schrieb Edgardo Hoszowski: > >> Hi, >> >> Another option is to adjust the feather with the shift pressed, this way >> control adjusts the opacity, shift the feather and no key the size, the >

Re: [darktable-dev] Mask problem

Hi, Another option is to adjust the feather with the shift pressed, this way control adjusts the opacity, shift the feather and no key the size, the 3 with the mouse over the shape+feather. This can be useful when the feather is very small or the shape is very small, in both cases is difficult to