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

Split variants into collections

Permanently deleted user
Hello there,

Capture One useer since many years here. There’s one simple function I cannot find: Let’s say I have 2 variants of 1 picture: One color, one b&w. Now I have two collections. One collection should have my b&w variants, the other should have the color images.

This doesn’t work as I can only put the variants as a whole into a collection. That’s a mess.

Any solution for this? I kind of want to seperate the variants to handle them as single images.

Thanks
Tobi
0

Comments

5 comments

Date Votes
  • Permanently deleted user
    This came up in a webinar a while back. The answer was that what you're seeing is the Collection behavior. Apparently the only way to do what you want is to create smart albums with the appropriate criteria. If the specific process criteria you want isn't available as a smart album criterion, try assigning a color tag to those images and base the smart album on color tag.
    0
  • Permanently deleted user
    [quote="Nature Isme" wrote:
    This came up in a webinar a while back. The answer was that what you're seeing is the Collection behavior. Apparently the only way to do what you want is to create smart albums with the appropriate criteria. If the specific process criteria you want isn't available as a smart album criterion, try assigning a color tag to those images and base the smart album on color tag.


    Using smart albums is exactly my workaround right now, but it's very inconvenient. The most intuitive way would be to activate a simple drag and drop function to put single variants into collections.

    Any other ways to do it?
    0
  • SFA
    If you have referenced images I presume one option would be to have two (or more) catalogues or sessions and separate them that way but referencing the same original image.

    It would work for sessions using different versions of C1 (i.e. data base data structure differences) but I'm not sure about 2 sessions or catalogues of the same release.

    If storage capacity is not a limitation just have 2 copies of the file and allow the edit activity to diverge.


    Grant
    0
  • Jochen Schmidt
    This is one thing that was really simple in Aperture: Each album (the collection equivalent) could have its own "album pick" of a set of variants.

    In technical terms this is a relation between a collection and a variant. It is not the same relation as in "is part of collection". My guess is that collections in C1 do hold "photos" and therefore there is no distinction of variants. If you close the variant stacks you will see the same topmost variant in any collection - this is a global state. So the DB model of collection would need to get extended to allow storing selected variant for any stack in the collection. This isnt trivial but also not impossible.

    One other thing that I often miss are more general "stacks". C1 only offers a "variant stack" when cloning new variants of an image. A new master (RAW or done with "Edit in") will always start a new Stack because any file can only have one stack an each stack relates directly to one file. In Aperture it was possible to arbitrarily group images into stacks. This really are different concepts even if they seem to be similar to the users.

    I think the most flexible thing would be a new kind of grouping construct, that can be part of a collection like an image, but also can contain arbitrary variants of images by itself with one item selected as the "cover" or "key" image.
    0
  • Eric Nepean
    [quote="Neonsquare" wrote:
    This is one thing that was really simple in Aperture: Each album (the collection equivalent) could have its own "album pick" of a set of variants.

    In technical terms this is a relation between a collection and a variant. It is not the same relation as in "is part of collection". My guess is that collections in C1 do hold "photos" and therefore there is no distinction of variants. If you close the variant stacks you will see the same topmost variant in any collection - this is a global state. So the DB model of collection would need to get extended to allow storing selected variant for any stack in the collection. This isnt trivial but also not impossible.

    One other thing that I often miss are more general "stacks". C1 only offers a "variant stack" when cloning new variants of an image. A new master (RAW or done with "Edit in") will always start a new Stack because any file can only have one stack an each stack relates directly to one file. In Aperture it was possible to arbitrarily group images into stacks. This really are different concepts even if they seem to be similar to the users.

    I think the most flexible thing would be a new kind of grouping construct, that can be part of a collection like an image, but also can contain arbitrary variants of images by itself with one item selected as the "cover" or "key" image.

    I really miss Aperture style stacks as well. I wonder how professionals get along without them, they are invaluable for managing the images from burst shots and bracket shots.

    I note that in the last release COP aquired new metadata types for stacking
    • Sequence Count
    • Sequence ID
    • Sequence Total
    • Sequence Type

    However these are currently only available for images from Phase One cameras.
    0

Post is closed for comments.