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. ⚠️

Create CO9 catalogue in CO10

Jamie Bunce
I have a new subscription for CO10 and an expired trial for CO9. However, I am working for a client that requires me to work for them in CO9 catalogues. Is there a work around for this, for example can I create a catalogue in CO10 using the CO9 processing engine? Unfortunately I can't test as I have an expired trial.
0

Comments

5 comments

Date Votes
  • John Doe
    Can't you install CO9 alongside CO10?
    0
  • Eric Nepean
    I have installed diffrent versions of Capture One like this:

    Applications
    --CaptureOneVersions
    -----CaptureOne 9
    ---------CaptureOne.app (version 9.3)
    -----CaptureOne 10_0
    ---------CaptureOne.app (version 10.0.2)
    -----CaptureOne 10_1
    ---------CaptureOne.app (version 10.1.1)

    Then an alias (link) in my user desktop takes me to the version I want.

    This seems to work for trials, beta and so forth.

    But the real issue is getting an activated version of CO9. I would raise a support ticket and see if CO support can help you here.
    0
  • SFA
    [quote="NN635148508354122836UL" wrote:
    I have a new subscription for CO10 and an expired trial for CO9. However, I am working for a client that requires me to work for them in CO9 catalogues. Is there a work around for this, for example can I create a catalogue in CO10 using the CO9 processing engine? Unfortunately I can't test as I have an expired trial.


    The CO9 catalogue is different to the C10 catalogue.

    A CO9 catalogue can be updated to C10 but there is no way that I am aware of to move C10 back to C09.

    The "Engines" are a separate matter and nothing much to do with being able to read the catalogue. However again, as one would expect, there is no known backwards compatibility from a C10 edited image to a C9 engined version (other than re-editing.)

    As I understood the activation if you have an activated V10 licence then you can also run older versions alongside when they suitably installed. I assume this works for a subscription licence but you could always try it to see.


    HTH.


    Grant
    0
  • Eric Nepean
    One thing to be aware of when multiple versions of C1 are available, is that there is a tendency for C1 to open with the catalog last open in any other version. Certainly this happens with different minor versions of the same major version, not sure if this behaviour occurs between major versions like 9 and 10.

    The potential issue is that a newer version automatically opening a catalog from an older version may make incompatible changes (same major release, betas)or automatically upgrade (different major release)

    When testing a beta I try to be very diligent in closing the catalog before quitting C1.

    A more rigorous approach might be to create a separate user account for each version; e.g. account A only has the link for CO9, and Account B only has the link for CO10. Referenced images can still be shared.

    The other potential issue is due to keywords - CO10 handles keywords differently and better than CO9.
    You probably don't want to share CO generated Metadata (like keywords) back and forth between CO9 and CO10. Keep in mind that Metadata may be in an XMP sidecar or embedded in a TIFF or JPG. So a careful choice of Metadata syncing is needed.
    0
  • John Doe
    Might sound overkill, but actually what I would do to play it absolutely safe is create a small partition on the Mac's drive and install only OS X and CO9. Then I would reboot on this partition when I have to work for this specific client.
    0

Post is closed for comments.