Frank Schroeter

Moderator
  • Total activity 153
  • Last activity
  • Member since
  • Following 0 users
  • Followed by 0 users
  • Votes 0
  • Subscriptions 92

Activity overview

Latest activity by Frank Schroeter
  • Frank Schroeter commented,

    Gerhard, the question of "why does Capture One not test beta macOS releases" has been discussed in this thread before. We do! And if we identify issues during those tests, we investigate them and f...

  • Frank Schroeter commented,

    Randy Becker, here, this is the change I was referring to. I feel this is pretty obvious and discoverable.

  • Frank Schroeter commented,

    Randy Becker, Ian Wilson, if you look at the download page, you will notice a minor change in how we state the System Requirements: We now state the oldest required and as a footnote, we state the ...

  • Frank Schroeter commented,

    Adrian Lambert, yes, what you see may be related. Fujifilm have not released a firmware update that would improve the USB power management yet.

  • Frank Schroeter commented,

    Peter Postmus, I was referring to both our bug database and support database (where customers report issues or ask questions). Neither contains reports of blocking issues with Capture One 16.3 and ...

  • Frank Schroeter commented,

    Peter Postmus, what I said was "there are no known issues with Capture One 16.3 running on macOS Sequoia" and that is exactly what I meant. It is a different statement from "Capture One 16.3 is com...

  • Frank Schroeter commented,

    Please create a support ticket.

  • Frank Schroeter commented,

    Peter Postmus, there are no known issues with Capture One 16.3 running on macOS Sequoia.

  • Frank Schroeter commented,

    Official comment

    We now have concluded all tests and investigations of high priority problems. I apologise for the long wait, but we want to be 100% sure that our recommendations for system configuration do not blo...

  • Frank Schroeter commented,

    Another update, all the tethering issues we got our hands on so far seem to be resolved by executing  tccutil reset All com.captureone.captureone16in Terminal. Make sure Capture One is not running ...