Histogram vs Destination Profile
When I change the destination profile (Process Tool panel), the histogram in the Exposure Tool panel doesn't reflect the change. On the other hand, the clipping warning does change. If I choose a different destination, the preview photo displays the profile change (I use Image>Proof Profile>Selected Destination). So, why doesn't Capture One reflect the change of destination profile in the histogram?
Any idea?
Faeyer
Any idea?
Faeyer
0
-
Check exposure tool I believe the changes are displayed here.
Capture tool should diplay RAW data when in the end of the day you can modify profiles but it is RAW data you are trully interested in when exposing.0 -
Ulf,
Thank you for your prompt reply but it doesn't address my concern. So, let me re-phrase my question:
I'd like to have the histogram of the Exposure Tool panel reflect my destination/output profile, just the way the clipping warning does.
Try this: - Choose a destination with ProPhoto as destination profile
- Go to the Epsosure tool and move the EC slider until the exposure warning show minimal clipping.
- Take a screenshot
- Go to the Process Tool panel and select a destination with sRGB as destination profile
- Return to the Exposure Tool panel
- Now, the clipping zone is NOT the same but the histogram has not changed. How is this possible?
You can see this in a screenshot movie (QuickTime) at this address: http://tinyurl.com/bs964
I believe that the histogram displayed in the Exposure Tool panel shows how the resulting file will look rather than the initial RAW data. If it displayed the RAW data, it wouldn't change if you move the WP, BP, GP, EC, Sat or CC sliders...
FWIW, Adobe Camera Raw does update the histogram when the output profile is changed.
Now, If I'm heading in the wrong direction, correct me!
Faeyer0 -
I believe we are mixing up two things.
Capture Tab and Exposure tab.
Capture Tab is static while Exposure tab change (In reference to PhotoShop, PhotoShop does not have a \"Capture\" section)
I will check in to the destination, it might be that you just have the windows bellow to check this, but do not see this as a final answer just yet.0 -
It sounds like you are expecting the histogram to change when you change the output colour space. The colour string elements should do perhaps. I'm not sure about the luminance part as I expect this shouldn't change. The exposure warning might be triggered by out of gamut even though the discrete colour values don't change. Perhaps all that is missing is a trigger for a histogram redraw when profiles are changed. Setting a generic grey profile shoud set all rgb values to equal if the histogram reflects the predicted processed image. BUT...
What should the histogram show you when you have 3 output options ticked in your process panel for the same image; an sRGB, a Photopro and a greyscale? Obviously this would confuse the system so perhaps thats why it is the way it is?0 -
[quote="UlfLiljegren" wrote:
I believe we are mixing up two things.
Capture Tab and Exposure tab.
Capture Tab is static while Exposure tab change (In reference to PhotoShop, PhotoShop does not have a "Capture" section)
I will check in to the destination, it might be that you just have the windows bellow to check this, but do not see this as a final answer just yet.
Ulf,
I'm talking about the Exposure tab and NOT the Capture tab. I fully understand that the Capture tab histogram must be static. But my concern was about the Exposure tab. See my QT movie and read what Damien says below (and my reply).
Thanks for your help,
Faeyer0 -
Hi Damien, [quote="damienlovegrove" wrote:
It sounds like you are expecting the histogram to change when you change the output colour space..
Right (and only in the Exposure tab) 😉[quote="damienlovegrove" wrote:
The exposure warning might be triggered by out of gamut even though the discrete colour values don't change...
The gamut is the range of all possible colors which can be represented or produced on a device . So clipping and output profiles are linked.[quote="damienlovegrove" wrote:
...Perhaps all that is missing is a trigger for a histogram redraw when profiles are changed...
Yes, I do think that either something doesn't send a redraw message to the histogram in the Exposure panel or something is wrong (or I'm missing something and exposing my ignorance).[quote="damienlovegrove" wrote:
What should the histogram show you when you have 3 output options ticked in your process panel for the same image; an sRGB, a Photopro and a greyscale? Obviously this would confuse the system so perhaps thats why it is the way it is?
While you can tick more than one destination you can only select one. You can even select an unticked destination. This makes sense to me and you are right that if we could select multiple destinations it would confuse the system.
http://mail.mediancer.ch:8100/~feyer/po/selectedvschecked.jpg
Please, note that the preview image reflects the selected destination. You can easily see this if you switch between a large gamut profile such as ProPhoto annd a smaller gamut profile such as sRGB.
Faeyer0 -
[quote="damienlovegrove" wrote:
What should the histogram show you when you have 3 output options ticked in your process panel for the same image; an sRGB, a Photopro and a greyscale? Obviously this would confuse the system so perhaps thats why it is the way it is?
...but you realize that you can only have 1 destination profile as softproof ? i think that the histogram is not showing the softproof profile effect is a bad idea. btw c1 is the only converter with this behavior, it seems c1 user like surprises 😉0 -
My previous post was a bit dippy, sorry for that. Since then I've had another play and I see exactly what you mean. The great thing is that fixing the bug doesn't involve any new features and so it should be really easy to do. Because I spend my life in Adobe 1998 and rarely dive into CMYK or sRGB I've not noticed the glitch before. Pretty crucial stuff and it definately deserves a high priority. It's worth posting it as a feature request as well in case it gets overlooked at the next upgrade. Good luck! 0 -
No problem Damien 😄
I do my work almost exclusively in Adobe RGB or ProPhoto but sometimes I have to do it for sRGB. That's where my problems start!
I hope they get this bug fixed as soon as possible.
Faeyer0 -
[quote="faeyer" wrote:
I hope they get this bug fixed as soon as possible.
Faeyer
i did ask for this i guess at least 2 times during the last beta tests but it seems that the c1 developer don't see this as a problem. for rgb i think it's easy to implement but a cmyk histogram is another story, anyway it would be very helpful and a real advantage compared to the competition. what i also miss is a black point compensation for the relative color-metric rendering intent and the warning that for all matrix rgb output spaces only rel. col. rendering intent is used for conversion independent from what rendering intent you have selected in the preferences !!!0 -
[quote="CSP" wrote:
[quote="faeyer" wrote:
I hope they get this bug fixed as soon as possible.
Faeyer
i did ask for this i guess at least 2 times during the last beta tests but it seems that the c1 developer don't see this as a problem. for rgb i think it's easy to implement but a cmyk histogram is another story, anyway it would be very helpful and a real advantage compared to the competition. what i also miss is a black point compensation for the relative color-metric rendering intent and the warning that for all matrix rgb output spaces only rel. col. rendering intent is used for conversion independent from what rendering intent you have selected in the preferences !!!
BP compensation would be helpful too as would be a warning for the rendering intent.
Let's hope they put our requests in v 4.0!
Fayer0
Post ist für Kommentare geschlossen.
Kommentare
11 Kommentare