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

Variants into Folders / albums

Comments

3 comments

  • SFA
    Variants are not separate source and edit files. The variant edits reside with in the same edit file no matter how many there are as such you cannot segregate them into folders for purpose UNLESS you copy everything for that image to the folder and, in effect, create a separate edit file for each final purpose for the file.

    However if you then make any changes to the basic edit that you want to use across all variants you would need to apply the changes to each edit file in turn.

    You could consider using Keywords or other EXIF data that is searchable and defined separately for each variant.

    As for Smart Albums - the nature of smart Albums, as I understand them, is that they are Smart in the sense that select and "group" images by performing a search on the available content at the time they are brought into play. Dynamic in other words. In theory they will not know how many files they will present to you until the search is run and complete. The number may be different to last time.

    I suppose it would be possible to set each defined smart album to run some sort of perpetual update process or for every application action to report itself to all smart albums in case a "count" number should be adjusted but realistically I think the system overhead would be difficult to justify.



    Maybe it would be worth making the suggestion in a Support Case with an explanation of what benefits you would see from the numbers so that the design team fully understand the need.

    HTH.


    Grant
    0
  • Paul Steunebrink
    With Smart Albums you can split or separate variants from each other. You can use rating or color tag to group specific variants into an smart album. More flexibility comes through the use of keywords.
    0
  • Permanently deleted user
    Can I fork an image? Create a copy from a specified variant? F2 clones the original, F3 clones a clone? is there an F4 that takes a snapshot and creates a separate file? That would do for now.

    Editorial: Everybody else on the planet offers a count for "smart folders". SQL even has a special function specifically for that purpose. But I suspect that C1 Catalogs are not databases so all that functionality is lost. That is why C1 is slow. I imagine it is because it is constantly hitting the disk for every task.

    [quote="SFA" wrote:
    Variants are not separate source and edit files. The variant edits reside with in the same edit file no matter how many there are as such you cannot segregate them into folders for purpose UNLESS you copy everything for that image to the folder and, in effect, create a separate edit file for each final purpose for the file.

    However if you then make any changes to the basic edit that you want to use across all variants you would need to apply the changes to each edit file in turn.

    You could consider using Keywords or other EXIF data that is searchable and defined separately for each variant.

    As for Smart Albums - the nature of smart Albums, as I understand them, is that they are Smart in the sense that select and "group" images by performing a search on the available content at the time they are brought into play. Dynamic in other words. In theory they will not know how many files they will present to you until the search is run and complete. The number may be different to last time.

    I suppose it would be possible to set each defined smart album to run some sort of perpetual update process or for every application action to report itself to all smart albums in case a "count" number should be adjusted but realistically I think the system overhead would be difficult to justify.


    Maybe it would be worth making the suggestion in a Support Case with an explanation of what benefits you would see from the numbers so that the design team fully understand the need.

    HTH.


    Grant
    0

Post is closed for comments.