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

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

Capture One Catalog and Picture Organization

コメント

4件のコメント

  • John Doe
    Why create thousands of albums when you can select the relevant pictures by using date filters (since the capture date is already included in each picture's metadata) ?
    0
  • Permanently deleted user
    It sounds like you just had C1 import everything, in which case all images were ingested in a single import, and so all of the images will be in Recent Imports in addition to being in your library (which at this point sounds like it's just an unstructured entity containing everything C1 knows about).

    It would help to know whether your Aperture library was managed or referenced. Your situation's fairly easy to resolve if you had a referenced library whose on-disk structure is what you want—namely, folders for each day (or month or year or whatever). If you'd imported the library into C1, then C1 should also recognize your referenced folder structure. If not, you could manually add each folder in C1 (the "+" button in the Library pane) and then synchronize folders (right-click on each folder).

    If you had an unstructured managed library (or a single-folder referenced library containing all of your images) where everything was stored in one place and then you created albums for each day, then you'll need to recreate your albums in C1. If that's the case, though, I'd highly recommend that you first create an on-disk referenced library folder structure and then have Capture One export relevant images to appropriate folders, at which point you'd have what I think you're looking for.

    Both C1 and Aperture have options for managed and referenced libraries. For your "vacation" scenario, if you think that in the future you'll look for images under the project, then I'd suggest that you import the images into a folder named for the vacation or whatever, and create a collection that mirrors the folder structure. I find it very easy to fluidly move between C1 and Finder when my on-disk structure mirrors the C1 library structure as much as possible.
    0
  • NNN636223405860662750
    For Aperture I had a Managed library and want the same for C1. I want the imported unmodified originals to be in a date structured organized catalog. I don't want a referenced library, all too often someone would muck with the referenced original and I would loose the link. By having a folder by date were is no implied meaning of the pictures. I may have gone to the beach for 3 days and the ball game also during those 3 days. I may have taken 400 pictures doing those 3 days. When I create an album for the beach trip and a 2nd album for the ball game I will pull what I want.

    If I leave recent Imports alone and under User Collections i create smart albums, one per day. I can also create projects and or groups for organization. I don't want referenced on disc folders. My external drives (-10) change all the time.

    how do i get smart albums to display photo counts in the sidebar
    0
  • Permanently deleted user
    I think you're going to have to resort to using a manually created set of collections. But I'd encourage you to think about this very carefully.

    Aperture's Managed Library consists of a folder hierarchy that's saved within an OS package. You can right-click on the "Aperture Library file", "show package contents" and see this. So in reality you DO have a folder structure; it's just that Aperture created it. You can always get the actual file out of the library if needed.

    C1's managed catalogs are different. C1 stores the files in its own database, so the actual file truly is lost to the Finder and you need C1 to extract it (which it can easily do). But you'll no longer have Finder access to the files.

    One implication: if your library ever outgrows a disk and you need to expand it (or divvy it up among multiple disks), you'll need to work through C1. Also, I'm not sure that a C1 managed catalog can span several drives. With a referenced library, it's easy to reference any number of drives. Also, you always have access to individual files if you want to use them without going through C1's export dialog (and the long wait while C1 launches), and there are other advantages.

    Your concern about frequent, unpredictable drive swaps is easily dealt with by getting disciplined about which drive(s) are connected to your computer at which time. Also, C1 can edit offline files just fine.
    0

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