Zum Hauptinhalt gehen

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

Migrating from Apple Photos to CO9

Kommentare

5 Kommentare

  • EnderWiggins
    I don't think there is a direct way Photos>C1 available.

    Do you still have your iPhoto-Library intact, before moving it over to Photos? If you do, you could try to open that in Aperture (which is possible) and then use the Aperture-Importer from within C1. Don't know if that works, just a thought.
    0
  • Jeffrey Jakucyk
    That's basically what I did with the couple of iPhoto libraries I have. Even though iPhoto and Aperture have had a "unified library architecture" or whatever they call it, so that each program can read libraries from the other, Capture One would not import a library created with iPhoto. So I imported the iPhoto library into Aperture and then was able to import that to Capture One. I don't know of a path from Apple Photos though.

    One other thing to watch out for. If you have old photos or scans that are less than approximately 500 pixels on one side (I'm not sure of the actual size, it might be something like 517 pixels), then Capture One will treat them as read-only. Thus you will not be able to change any edits or keywords or even star ratings on those. You CAN change the color tag, so there's a way to mark them for excluding from smart albums and such, but it's a pain. I did submit a bug report/feature request about this, because it's one thing to limit editing ability for new files, but locking imported files so you can't even change the metadata is not cool.
    0
  • HawkSoft
    My problem is that I never bought Aperture and now it's too late.

    Anyway, I've taken the plunge and bought the Sony Pro version of Capture One.

    After doing a few tests I decided to do an export from iPhotos and Photos so that I will get all my edited versions with keywords but will not have the originals in Capture One. I've got space to keep the original photo libraries on disc so will be able to access the originals if needed.

    The export took less than 2 hours.
    Importing the first 14k photos took less than 2 hours, after that things slowed to a crawl and the remaining 6k photos took another 8 hours. My iMac only had 8GB of RAM (now 32GB) but even so this suggests poor memory management somewhere ;(

    First impressions are that image rendering is MUCH better, even with .JPGs from 1st/2nd generation digital cameras and scans of historic prints but the user interface is bewildering compared to iPhoto and there is no obvious workflow. I have started to experiment with processes.
    0
  • HansB
    [quote="HawkSoft" wrote:
    ...
    but the user interface is bewildering compared to iPhoto and there is no obvious workflow
    ...


    The UI of CO faces towards RAW development and is clean and technical. Exactly how I like it to be for this purpose.
    Photos and iPhoto are facing towards viewing and sharing.
    Two things I would not compare.

    But the sequence of the tools in CO makes sense. As I posted in this thread: viewtopic.php?f=61&t=22368 (some more in that thread)

    [quote="HansB" wrote:
    I keep my tool sequence in workflow order, top down. Global things first, followed by normal adjustments, and ending with fine tuning.

    High Dynamic Range, for example, has a big impact on the histogram, therefore High Dynamic Range above Levels.
    White Balance changes the look of all colors, therefore White Balance above color adjustments.
    Levels above Curve.
    And so on.

    Surprise! Doing so ends up with something that looks like the standard sequence given by PO.
    ...


    Feel free to create your own tab order and tool sequence for your workflow. You can create, add and remove tool tabs and you can arrange, add and remove tools on every tool tab.


    Regards,
    Hans
    0
  • HawkSoft
    [quote="HansB" wrote:
    The UI of CO faces towards RAW development and is clean and technical. Exactly how I like it to be for this purpose.
    Photos and iPhoto are facing towards viewing and sharing.
    Two things I would not compare.

    But the sequence of the tools in CO makes sense.

    We are probably going to disagree on this but I do not think the UI design of CO9 is anything special.

    Photos is a great viewing program on the iPad, as a desktop application it's horrible!
    iPhoto was most (but not all) of what a serious amateur photographer needed and was very intuitive to use like most *classic* Mac software.

    As someone who has worked with many different GUIs over several decades I would say that the CO9 GUI is pretty typical for a technically focussed tool. The fact that it is virtually impossible to use without watching a couple of (lengthy) videos is not good 5/10.

    Yes, you can shuffle the tool tabs but that is only a small part of setting up a workflow ☹️
    If more of the Sessions concepts (like keeping source and output files together) were part of the Catalogue system that would be an improvement. At present it is too easy to create a big mess.
    0

Post ist für Kommentare geschlossen.