A new large merge is about to happen.
This time it is on the GUI side. A large rewrite from Aurélien which
makes everything related to layout, font size, etc... done directly in
CSS. No more messing in GTK code to add GUI borders, spacing, colors...
The good news is that we will be able to have
> 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.
>
_
On Sat, 13 Apr 2019 12:02:10 +1000, Edgardo Hoszowski
wrote:
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 mea
> 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 that the input profile you see if you enter to da
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.
Maybe it has something to do with the raw, does this happens with raw's
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, Edgardo Hoszowski
> w
On Sat, 13 Apr 2019 11:13:40 +1000, Edgardo Hoszowski
wrote:
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:0
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:
>
> > No reference to t
Hello Edgardo,
On Sat, 13 Apr 2019 10:03:33 +1000, Edgardo Hoszowski
wrote:
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 u
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
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 linear Rec709 RGB'.
Not seen anything like this on previous builds when editing the very same
images.
Is this an
I would think that Fujifilm's rational is that the original raw edge
pixels are really not to be valued and only are used for the 'final
edge' calculation.
On 2019-04-12 1:26 a.m., Christian wrote:
Hi,
Understand. But there may be users who prefer a consistend size
between ooc and processed im
Hi,
Understand. But there may be users who prefer a consistend size
between ooc and processed images or when using several raw converters in
parallel.
So I suggest an option in the export-pane :
[x] crop to original/nominal size
logic: if image is larger than original size and not
has been crop
13 matches
Mail list logo
