Zum Hauptinhalt gehen

Kommentare

16 Kommentare

  • John Friend
    Top Commenter

    What version of Capture One?  What version of OS?

    If MacOS Sonoma and Capture One 15.x, then there are some OS compatibility issues between those that are resolved in the latest 16.3.x.  In particular, there's an issue if exporting to certain iCloud-related directories that causes the exported files to be hidden.  A work-around was to pick a different directory that has nothing to do with iCloud.

    0
  • David Stavenow

    Hi John.

    Yeah I'm running Sonoma 14.1.1 and C1 15.3.1.15

    So I did what you suggested, chose another export directory and nothing changes. he thin is, I'm exporting a file in the same catalog from which I exported two days ago and with zero changes other than adding that new file.

    It won't even export what I exported two days ago. I've also tried all the re-boots, opening other catalogs and now using export directoies that aren't related to iCloud (as far as I know) which I have disabled anyway since I don't trust clouds.

     

    0
  • Walter Rowe
    Moderator
    Top Commenter

    Capture One 22 (15) only supports up to macOS 13.0.1. It is not supported on Sonoma. You need to upgrade your Capture One.

    https://support.captureone.com/hc/en-us/articles/7857694102557-Capture-One-22-15-4-3-release-notes#h_01GJF5F00CXDDSTDJ1E4VFWSQ9

    0
  • David Stavenow

    Not sure what you mean Walter.
    In the very link you sent it says:

    Apple® Macintosh® minimum requirements

    Intel® Core™ i3 (1st generation)
    8 GB of RAM
    10 GB of free hard disk space
    Calibrated monitor with 1280x800, 24-bit resolution at 96dpi
    macOS 10.15, macOS 11, macOS 12, macOS13*
    Internet connection to run Capture One Live
    * MacOS 13 is supported up to version 13.0.1

    I’m running MacOS 14.4 which according to spec is compatible.
    Or am I misunderstanding something?

    Does C1 support MacOS 11,12,13 and 15 but NOT 14?

    0
  • Walter Rowe
    Moderator
    Top Commenter

    It means that specific version of Capture One 22 is only supported on 10.x, 11.2, 12.x, and UP TO macOS 13.0.1 .. nothing newer. Newer versions of Capture One support newer operating systems.

    Capture One 23  represents Capture One version 16.0 thru 16.2.x. It changed name and versioning at Capture One 16.3 to simply be named Capture One and go by version "Capture One 16.3"

    Only Capture One 16.3.x supports macOS 14.4.1.

    Spend some time reading the release notes. They answer your question.

    https://support.captureone.com/hc/en-us/categories/360000430178-Release-notes

    0
  • David Stavenow

    Ok. Thanks.
    I’ll pay up. 🤓

    Hopefully it resolves my export issue which randomly appeared after running on OS 14 since it launched.

    (I still don’t understand why you would develop software that supports OS 11, 12, 13 -NOT 14- but 15.)

    0
  • Walter Rowe
    Moderator
    Top Commenter

    macOS 14 didn't exist when CO 22 was last updated. Capture One doesn't generally make older CO versions compatible with newer OS versions. You have to upgrade CO. macOS made changes that forced CO to also make changes for macOS 14.x.

    0
  • John Friend
    Top Commenter

    David Stavenow - (I still don’t understand why you would develop software that supports OS 11, 12, 13 -NOT 14- but 15.)

    They didn't.  Capture One 22 was in the market for several years and no longer being updated when Apple changed something in the OS that broke some functionality in Capture One 22 (15.x).  Capture One fixed that issue in their latest release, but did not re-release older versions to offer the fix (which is their usual policy).  Thus, you have to upgrade in order to get the fix.

    Whether this is really Apple's fault (breaking existing APIs) or Capture One's fault (using incorrect programming practices that just happened to work earlier, but weren't the proper way to write the code) or really some shared blame between the two is hard for us to know.

    0
  • Walter Rowe
    Moderator
    Top Commenter

    macOS 15 isn't out - not even to developers.

    0
  • David Stavenow

    Thanks

    0
  • David Stavenow

    I see. Then C1 shouldn’t say that it supports OS15

    0
  • David Stavenow

    Oops… my bad. I’ve read MacOS 10.15 as OS15.
    The reason for that is because Mac used to name their OS MacOSX with X meaning 10. So I automatically assumed it was version 15 and not 10.15.

    Life is complicated…

    0
  • David Stavenow

    Just a follow up on what was the cause of my issue.

    It turned out the problem was the origin of the file. It was a JPG file and I'm not sure I've even editied anything but a CR2 before. Apparently my version of C1, possibly in combo with my operating system, couldn't handle exporting JPGs. Why I don't know. So I converted it to Tiff first and after that it was smooth sailing.

    Also, I was wrong about using C1 15.3.1.15. It was 16.3.8.23 so I don't really know why it couldn't handle JPG.

    Thanks anyway those of you helping me out.

    /D

    0
  • SFA
    Top Commenter

    David,

    C1 can handle jpgs BUT it IS POSSIBLE to set a Preferences flag to make jpg editing void.

    Also there are some potential constraints for file sizes and dimensions (check the release notes for full details).

    However, I'm not sure that there is any specific constraint to exporting to the jpg format BUT, if you were not able to edit a jpg previously, your export would not really be an export at all since there would be nothing to convert to a jpg as it already IS a jpg with no edits applied. (Assuming I have followed your description well enough.)

    0
  • David Stavenow

    Hi and thanks for chiming in.

    There was no issue with sizes or editing the JPG. Editing was smooth but it didn't want to export. But once I converted the file to TIFF outside of C1, I imported the TIFF, I copy/pasted the adjustments from the JPG and… voila! No problem.

    So unless there's some other issue I'm not aware of, this most definitely was a bug or an incompatibility issue.

    0
  • SFA
    Top Commenter

    That sounds strange  - unless something has changed in the jpg creation routine in the later version of the OS and the currently referenced routine in the earlier C1 installation is no longer compatible. 

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.