Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Capture One 9.1.1 is released!

Comments

6 comments

  • Robert Whetton
    fixed the sluggishness of 9.1! 😄
    0
  • Denis Mortell
    Try the following...........

    1. Open an image and don't make ANY changes to it.

    2. Open the Advanced Colour Editor. (ACE)

    3. Noting the RGB reading at the top of the screen, Pick Color Correction using the colour sampler tool in the Advanced Colour Editor.

    4. Note that the RGB reading in the ACE is identical to the RGB reading at the top of the screen - as it should be.

    5. Now, make EITHER a Curve change OR a Levels change to the image.

    6. Hover the colour picker tool over the same area of the image and note the RGB reading at the top of the screen. It will have changed, as it should.

    7. Now, with the Curve (or Levels) change still inputted, take another sample from the SAME area of the image.

    8. You will note that the RGB reading in the ACE panel is IDENTICAL to the first sample's RGB reading taken BEFORE the Curves (or Levels) adjustment. i.e. it is not the same as the reading at the top of the screen. BUT, the new colour sample should have an RGB IDENTICAL to that at the top of the screen. It doesn't.

    9. In other words, the Curves (or Levels) adjustment is NOT sticking.

    I wrote to Support about this late last year about this. I was told that it was a major fault and would be reported directly to Denmark. Zip! 🤬

    For what it's worth, I'm Windows 10 Pro.

    Thanks.

    D.
    0
  • Denis Mortell
    Ps.

    If you take a colour sample in the Advanced Colour Editor (having made NO adjustments to the image) the RGB readings will be identical top of scree AND in the ACE panel, as I've said.

    Now, if you, say, reduce the Exposure value of the image, you will reduce the RGB reading at the top of the screen. If you then take another ACE colour sample, the RGB reading top of screen and ACE will be IDENTICAL, as they should be.

    In other words, the Exposure adjustment is sticking where the Curves and Levels adjustments are not.

    This is indeed a "major bug" as the support person who replied to me termed it, and it is shambolic that it still hasn't been fixed.

    It renders serious colour editing within the ACE a waste of time.

    D.
    0
  • Christian Gruner
    [quote="Dinarius" wrote:
    Try the following...........

    1. Open an image and don't make ANY changes to it.

    2. Open the Advanced Colour Editor. (ACE)

    3. Noting the RGB reading at the top of the screen, Pick Color Correction using the colour sampler tool in the Advanced Colour Editor.

    4. Note that the RGB reading in the ACE is identical to the RGB reading at the top of the screen - as it should be.

    5. Now, make EITHER a Curve change OR a Levels change to the image.

    6. Hover the colour picker tool over the same area of the image and note the RGB reading at the top of the screen. It will have changed, as it should.

    7. Now, with the Curve (or Levels) change still inputted, take another sample from the SAME area of the image.

    8. You will note that the RGB reading in the ACE panel is IDENTICAL to the first sample's RGB reading taken BEFORE the Curves (or Levels) adjustment. i.e. it is not the same as the reading at the top of the screen. BUT, the new colour sample should have an RGB IDENTICAL to that at the top of the screen. It doesn't.

    9. In other words, the Curves (or Levels) adjustment is NOT sticking.

    I wrote to Support about this late last year about this. I was told that it was a major fault and would be reported directly to Denmark. Zip! 🤬

    For what it's worth, I'm Windows 10 Pro.

    Thanks.

    D.


    Can you give me your Support case number? I can then take a look for the bug-report in our systems.
    0
  • Denis Mortell
    Hi Christian,

    Thanks for taking an interest in this.

    The Case ID is 211596.

    The specific part of it that I refer to is dated 09/02/2016 at 19:59, when the person replying to me wrote, "I consider this a sizeable bug and am submitting it to the team for remedy..............Thanks for bringing this to my attention."

    You could also look at Case ID 207448.

    Many thanks.

    D.
    0
  • Boris Bashutin
    9.1.1 works faster than 9.1.0 - which has problems with working speed and previews speed. Was very sluggish.

    When could we wait for Pentax K-1's PEF support?
    0

Post is closed for comments.