Re: [darktable-user] Show size cropped picture in DT ?

[August Schwerdfeger]

I think he meant the size *after* cropping. I requested this at one point,
and a prototype was implemented, but it turned out to be too inefficient
and was removed.

--
August Schwerdfeger
aug...@schwerdfeger.name

On Thu, Feb 7, 2019 at 5:20 PM Patrick Shanahan  wrote:

> * Michael Jacobs  [02-07-19 17:23]:
> > In DT 2.6.0 (on Linux Mint), is there a way to display the size (width x
> > height) of a cropped picture in the image information tab ? (both in
> > lighttable & darkroom)
>
> the width and height in pixels are shown in the image information panel on
> the left in both light views lighttable and darkroom.   ???
>
> --
> (paka)Patrick Shanahan   Plainfield, Indiana, USA  @ptilopteri
> http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri
> Registered Linux User #207535@ http://linuxcounter.net
> Photos: http://wahoo.no-ip.org/piwigo   paka @ IRCnet freenode
>
> 
> 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

Re: [darktable-user] Show size cropped picture in DT ?

[Patrick Shanahan]

* Michael Jacobs  [02-07-19 17:23]:
> In DT 2.6.0 (on Linux Mint), is there a way to display the size (width x
> height) of a cropped picture in the image information tab ? (both in
> lighttable & darkroom)

the width and height in pixels are shown in the image information panel on
the left in both light views lighttable and darkroom.   ???

-- 
(paka)Patrick Shanahan   Plainfield, Indiana, USA  @ptilopteri
http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri
Registered Linux User #207535@ http://linuxcounter.net
Photos: http://wahoo.no-ip.org/piwigo   paka @ IRCnet freenode

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

[darktable-user] Show size cropped picture in DT ?

[Michael Jacobs]

In DT 2.6.0 (on Linux Mint), is there a way to display the size (width x
height) of a cropped picture in the image information tab ? (both in
lighttable & darkroom)


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

Re: [darktable-user] Inaccurate color display or color picker?

[Edgardo Hoszowski]

> I may not be understanding all the issues correctly, but this seems much
> less useful than basing the values on an output profile that you actually
> intend to use for exporting to. Would it make sense to have the
> picker/histogram always use the profile that the soft proofing toggle is
> set to (whether soft proofing is enabled or not)? Or would changing to this
> behavior be to dispruptive to existing workflows?
>
The main issue now is that is not clear the requirement or use-case, or
maybe there are many workflows with different needs. This way is the most
generic so people that want to check using the output color profile can do
it, and people that want it with the soft proofing also have a way to do
it. If this is an overkill and is better to have it only with one of those
profiles there's no problem, that can be done.


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

Re: [darktable-user] Inaccurate color display or color picker?

[Normand Fortier]

No problem, Edgardo. Thanks for all your work!

Normand

Le 19-02-07 à 13 h 13, Edgardo Hoszowski a écrit :
You are mixing things and getting off-topic here, we'll never be able to 
define a requirement this way.


The final histogram/color picker/overexpose does collect the data at the 
end of the pipe, that is, when it has finished processing the image. Not 
converting it to another profile makes no sense, as the last module can 
work on any colorspace, and the program will be choosing for you how the 
data is displayed.
What the PR does is to allow you to select the colorspace (or profile) 
on which the data is displayed. If you want you can select the 
colorspace of the last module, that's up to you.


El jue., 7 feb. 2019 a las 14:58, Normand Fortier 
(mailto:normand.fort...@cgocable.ca>>) 
escribió:


Le 19-02-07 à 07 h 36, Edgardo Hoszowski a écrit :
 > PR 2069 is ready, please test it.

Thank you for the quick response! Sorry for the long posts, but I think
we're not quite on the same page. I am still trying to figure how to
incorporate your PR into my DT source, so I can't test yet, but I read
the comments under your PR, here is my take.

The short story: the histogram and global color picker should indicate
the values at the end of the last module in the history stack (or of
whatever module/step is selected in history), without converting
them to
another profile, be it the destination/output profile or the display
profile. I don't see this as being tied to over/underexposure
specifically.

The detail: I admit I am still confused as to which profile is used by
DT modules that work in RGB. My initial understanding of the behaviour
of the global color picker and the main histogram was that, since they
report rgb values as per the display profile, it meant that the working
profile for RGB modules was the display profile. But your comment now
mentions that ProPhoto is actually being used as a working profile. On
the other hand the manual mentions the output color profile being
applied (at the place in the pipeline where DT switches from working in
Lab to working in RGB, I gather). Where does the ProPhoto profile come
into play then? Which modules work in ProPhoto, and which ones work in
the output profile?

If indeed modules working in rgb use ProPhoto as a profile, then
that is
good news, but then I would expect the main histogram and the global
color picker to provide data (histogram itself + rgb values) according
to the ProPhoto values.

As I mentioned earlier, that is what RawTherapee does: it uses ProPhoto
as default working profile
(https://rawpedia.rawtherapee.com/Color_Management#Working_Profile);
the
UI indicates "If enabled, the working profile is used for rendering the
main histogram and the Navigator panel".

That is also what Lightroom does: "Lightroom uses a wide gamut RGB
space
similar to ProPhoto RGB to do all the image calculations, and the
histogram and RGB percentage readouts are based on this native
Lightroom
RGB space."
http://www.adobepress.com/articles/article.asp?p=1930486

Normand


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

Re: [darktable-user] Inaccurate color display or color picker?

[jys]

On Thu, Feb 7, 2019, at 09:57, Normand Fortier wrote:

> That is also what Lightroom does: "Lightroom uses a wide gamut RGB space 
> similar to ProPhoto RGB to do all the image calculations, and the 
> histogram and RGB percentage readouts are based on this native Lightroom 
> RGB space."
> http://www.adobepress.com/articles/article.asp?p=1930486

I may not be understanding all the issues correctly, but this seems much less 
useful than basing the values on an output profile that you actually intend to 
use for exporting to. Would it make sense to have the picker/histogram always 
use the profile that the soft proofing toggle is set to (whether soft proofing 
is enabled or not)? Or would changing to this behavior be to dispruptive to 
existing workflows?

-- 
jys

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

Re: [darktable-user] Inaccurate color display or color picker?

[Edgardo Hoszowski]

You are mixing things and getting off-topic here, we'll never be able to
define a requirement this way.

The final histogram/color picker/overexpose does collect the data at the
end of the pipe, that is, when it has finished processing the image. Not
converting it to another profile makes no sense, as the last module can
work on any colorspace, and the program will be choosing for you how the
data is displayed.
What the PR does is to allow you to select the colorspace (or profile) on
which the data is displayed. If you want you can select the colorspace of
the last module, that's up to you.

El jue., 7 feb. 2019 a las 14:58, Normand Fortier (<
normand.fort...@cgocable.ca>) escribió:

> Le 19-02-07 à 07 h 36, Edgardo Hoszowski a écrit :
> > PR 2069 is ready, please test it.
>
> Thank you for the quick response! Sorry for the long posts, but I think
> we're not quite on the same page. I am still trying to figure how to
> incorporate your PR into my DT source, so I can't test yet, but I read
> the comments under your PR, here is my take.
>
> The short story: the histogram and global color picker should indicate
> the values at the end of the last module in the history stack (or of
> whatever module/step is selected in history), without converting them to
> another profile, be it the destination/output profile or the display
> profile. I don't see this as being tied to over/underexposure specifically.
>
> The detail: I admit I am still confused as to which profile is used by
> DT modules that work in RGB. My initial understanding of the behaviour
> of the global color picker and the main histogram was that, since they
> report rgb values as per the display profile, it meant that the working
> profile for RGB modules was the display profile. But your comment now
> mentions that ProPhoto is actually being used as a working profile. On
> the other hand the manual mentions the output color profile being
> applied (at the place in the pipeline where DT switches from working in
> Lab to working in RGB, I gather). Where does the ProPhoto profile come
> into play then? Which modules work in ProPhoto, and which ones work in
> the output profile?
>
> If indeed modules working in rgb use ProPhoto as a profile, then that is
> good news, but then I would expect the main histogram and the global
> color picker to provide data (histogram itself + rgb values) according
> to the ProPhoto values.
>
> As I mentioned earlier, that is what RawTherapee does: it uses ProPhoto
> as default working profile
> (https://rawpedia.rawtherapee.com/Color_Management#Working_Profile); the
> UI indicates "If enabled, the working profile is used for rendering the
> main histogram and the Navigator panel".
>
> That is also what Lightroom does: "Lightroom uses a wide gamut RGB space
> similar to ProPhoto RGB to do all the image calculations, and the
> histogram and RGB percentage readouts are based on this native Lightroom
> RGB space."
> http://www.adobepress.com/articles/article.asp?p=1930486
>
> Normand
>
>
> 
> 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

Re: [darktable-user] Inaccurate color display or color picker?

[Normand Fortier]

Le 19-02-07 à 07 h 36, Edgardo Hoszowski a écrit :

PR 2069 is ready, please test it.


Thank you for the quick response! Sorry for the long posts, but I think 
we're not quite on the same page. I am still trying to figure how to 
incorporate your PR into my DT source, so I can't test yet, but I read 
the comments under your PR, here is my take.


The short story: the histogram and global color picker should indicate 
the values at the end of the last module in the history stack (or of 
whatever module/step is selected in history), without converting them to 
another profile, be it the destination/output profile or the display 
profile. I don't see this as being tied to over/underexposure specifically.


The detail: I admit I am still confused as to which profile is used by 
DT modules that work in RGB. My initial understanding of the behaviour 
of the global color picker and the main histogram was that, since they 
report rgb values as per the display profile, it meant that the working 
profile for RGB modules was the display profile. But your comment now 
mentions that ProPhoto is actually being used as a working profile. On 
the other hand the manual mentions the output color profile being 
applied (at the place in the pipeline where DT switches from working in 
Lab to working in RGB, I gather). Where does the ProPhoto profile come 
into play then? Which modules work in ProPhoto, and which ones work in 
the output profile?


If indeed modules working in rgb use ProPhoto as a profile, then that is 
good news, but then I would expect the main histogram and the global 
color picker to provide data (histogram itself + rgb values) according 
to the ProPhoto values.


As I mentioned earlier, that is what RawTherapee does: it uses ProPhoto 
as default working profile 
(https://rawpedia.rawtherapee.com/Color_Management#Working_Profile); the 
UI indicates "If enabled, the working profile is used for rendering the 
main histogram and the Navigator panel".


That is also what Lightroom does: "Lightroom uses a wide gamut RGB space 
similar to ProPhoto RGB to do all the image calculations, and the 
histogram and RGB percentage readouts are based on this native Lightroom 
RGB space."

http://www.adobepress.com/articles/article.asp?p=1930486

Normand


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

Re: [darktable-user] Inaccurate color display or color picker?

[Edgardo Hoszowski]

PR 2069 is ready, please test it.


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