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

Copying images from one catalog to another catalog

Kommentare

5 Kommentare

  • Paul Steunebrink
    In short the process is that you File > Export > Originals from the source catalog (including adjustments) and import them into the new catalog (including adjustments).

    Another option is to copy the catalog file and rename it (to Urban).
    Next, you open it and remove all images you do not want.
    You can also remove the images in your Landscape catalog after your Urban catalog is setup.
    0
  • NNN634863802867218057
    Export>original does not export only Tiff or jpg or any other pixel image fiel format ?
    0
  • Paul Steunebrink
    [quote="NNN634863802867218057" wrote:
    Export>original does not export only Tiff or jpg or any other pixel image fiel format ?

    I assume that if your original in the catalog is a Tiff, it will export that Tiff.
    0
  • NNN634863802867218057
    In fact your solution exports the raw file with its adjustments. The danger of this solution is that you will have multiple instances of the raw file and it consumes HD space. What I'm looking for, if it exists, it to import in a catalog B the "variation" (it is called like that in the french version of the software C1, don't know if it is the same in english) of the raw file. That shouldn't be a problem theoricallky because the raw file is never changed in itself. I think that in other raw software, it is a xml file containing all parameters. I didn't find yet where all the editing parameters are stored in C1, because when I do the "export" thing you told me about, I can only see the raw file in the destination folder.
    0
  • SFA
    [quote="NNN634863802867218057" wrote:
    In fact your solution exports the raw file with its adjustments. The danger of this solution is that you will have multiple instances of the raw file and it consumes HD space. What I'm looking for, if it exists, it to import in a catalog B the "variation" (it is called like that in the french version of the software C1, don't know if it is the same in english) of the raw file. That shouldn't be a problem theoricallky because the raw file is never changed in itself. I think that in other raw software, it is a xml file containing all parameters. I didn't find yet where all the editing parameters are stored in C1, because when I do the "export" thing you told me about, I can only see the raw file in the destination folder.



    In your first post you indicated that you have left the RAW files in a folder on your machine and that they are NOT in the Catalog.

    If that is the case then the catalog will contain your edit files, preview files, EXIF information files, database that cross referneces everything for fast searching and so on. But not the original RAW files if they are reference at an external location.

    So if, as Paul suggested, you make a copy of the catalogue and rename it that copy will still reference the external RAW files assuming the reference is an Absolute reference not a Relative reference.

    You then simply need a way to identify and segregate the URBAN images in one file and the Landscape images in the other ... or maybe even leave some image in both catalogues if the subject matter would work in both.

    Creating an efficient way to segregate the images is something you will need to define no matter which way you approach the task. If you already have a suitable populated tag in your exif data somewhere that should make it quite easy to do.

    That's the theory.

    If your RAW (or more generally "source") files are stored IN the catalogue then you could still split the catalogue in the same way but if you which to share any of the source files in both catalogues then you will need to keep the source duplicated in both catalogues. I would not necessarily see that as a problem if it required unless it results in duplication of all of your source images (foro purposes other than backup). If the number of shared files is small the amount of storage capacity used would likely be relatively small and so the overhead and cost not very large.

    It is possible I am missing something that is important to you but from my current understanding the challenge looks lke something that could be relatively easily resolved.

    HTH.


    Grant Perkins
    0

Post ist für Kommentare geschlossen.