メインコンテンツへスキップ

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

コメント

14件のコメント

日付 投票
  • Thomas Kyhn Rovsing Hjørnet
    Top Commenter
    No fix for the keystone issue yet.
    0
  • Paul Steunebrink
    thomaskyhn wrote:
    No fix for the keystone issue yet.

    To be honest, that was not something to be expected for a maintenance release.
    0
  • Thomas Kyhn Rovsing Hjørnet
    Top Commenter
    Paul_Steunebrink wrote:
    thomaskyhn wrote:
    No fix for the keystone issue yet.

    To be honest, that was not something to be expected for a maintenance release.

    You're maybe right, though it can reasonably be regarded as a serious issue.
    0
  • Paul Steunebrink
    thomaskyhn wrote:
    Paul_Steunebrink wrote:
    thomaskyhn wrote:
    No fix for the keystone issue yet.

    To be honest, that was not something to be expected for a maintenance release.

    You're maybe right, though it can reasonably be regarded as a serious issue.

    No doubt a serious issue, you for me you get the credits for bringing this to Capture One's attention. But I assume it requires a rewrite of a lot of code to fix this.
    0
  • Thomas Kyhn Rovsing Hjørnet
    Top Commenter
    Paul_Steunebrink wrote:
    No doubt a serious issue, you for me you get the credits for bringing this to Capture One's attention. But I assume it requires a rewrite of a lot of code to fix this.

    That's very likely; it does seem like a more or less fundamental issue with how these adjustments are made.
    0
  • Paul Steunebrink
    thomaskyhn wrote:
    Paul_Steunebrink wrote:
    No doubt a serious issue, you for me you get the credits for bringing this to Capture One's attention. But I assume it requires a rewrite of a lot of code to fix this.

    That's very likely; it does seem like a more or less fundamental issue with how these adjustments are made.

    Agree.
    0
  • Permanently deleted user
    Paul_Steunebrink wrote:
    Today, Capture One 20.0.2 is released with numerous bug fixes and new camera support for the Leica SL2 and the Fujifilm X-T200.

    You find more details in the release notes at:
    https://support.captureone.com/hc/en-us/articles/360005112057-Capture-One-20-0-2-release-notes


    These release notes are completely useless. Example: think about this statement for a second: 'Fixed various crashes'. And then combine with the complete lack of response on bug reports.
    0
  • HeKoVS
    Scroll down in 'release notes' to contents and select 20.0.2 Bug Fixes Mac or Windows
    happy capture
    0
  • Permanently deleted user
    This release finally seems to have fixed the problem of C1 not calling the GPUâ€"something that's existed at least under Mojave since C1 12. And this fix isn't mentioned in the release notes. For me this is a big improvement. I'm looking forward to trying the other fixes. At least now my MBPs' upgraded GPUs are finally being used.
    0
  • Mark Johnson
    mmmm my C120 has work great on my last MBP and the new one I have now, fast, never crashers, does everything I need it too do, so, do I upgrade?
    0
  • David Toose
    I see that the existence of the Leica M10-P continues to be denied. Grrr!
    0
  • Sansith Koraviyotin
    Still not support A7R4 live view via USB-C ?
    0
  • Eric Valk
    Paul_Steunebrink wrote:
    thomaskyhn wrote:
    Paul_Steunebrink wrote:
    No doubt a serious issue, you for me you get the credits for bringing this to Capture One's attention. But I assume it requires a rewrite of a lot of code to fix this.

    That's very likely; it does seem like a more or less fundamental issue with how these adjustments are made.

    Agree.


    In my work for a company in a different industry (with SW having many complex features run on many different HW platforms), for significant SW feature changes I usually estimate 15% of the effort in coding, 20% in design and review, 50% - 60% in verification and fixes, and the balance for documentation and project management.

    Although coding is absolutely essential, its the verification that eats up effort.
    • Does the modified feature cause problems with any other feature that is used afterwards

    • Does the modified feature work correctly if any other feature or combinations of features has been used before it?

    • Does the modified feature work correctly on every image file type and size?

    • Does the modified feature work sensibly if the original feature was used before it

    • Does the modified feature work correctly with supported HW accessories

    • Does the modified feature work correctly with supported GPUs
    0
  • Martin Knowles
    Other fun thing to be aware of: despite what the release notes would have you believe, color casts on LCC-applied images are only fixed if you *aren't* running OpenCL. If you are, you still get corrupted files. (Now featuring even more corruption if you're resizing images. Might start calling this "fine art").

    <angrily files another support case to add to the ones he's submitted since beta, deletes CO20 once again, curses Phase loudly a few times for effectively breaking people using their flagship back on tech cameras, pours himself a stiff drink, and goes back to CO12 so he can get work done...>
    0

投稿コメントは受け付けていません。