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

Importing "only new pictures" from an SD card

Andrea RICCI
HI folk, sorry for the newbie like question but I can't find the answer myself in other way
I do not systematically erase old pictures from an SD card and C8 seems incapable of detecting the pics which are ALREADY in the database. So I have to manually select the (new) ones I need to import.
Lighroom detects new from old pictures and only offers to import the new ones
Can anyone help finding the check box or menu or whatever 🤭 sort of command to avoid the manual selection ?
I searched online (general), in the knowledge base and found nothing
Thanks for your help 😄
0

Comments

10 comments

Date Votes
  • Paul Steunebrink
    Hi, I am sorry the bring bad news, but I am afraid such an option is not available in CO8.

    Do you use catalog or session? If catalog, do you store inside or outside the catalog?
    0
  • Andrea RICCI
    I am using catalogue, and storing outside catalogue...wrong?
    0
  • Paul Steunebrink
    [quote="andreariccieu" wrote:
    I am using catalogue, and storing outside catalogue...wrong?

    No, nothing wrong, but it makes it simpler to assess the issue. My understanding was that in this setup CO8 would double import, unless you write images to a new location compared with the previous import.
    0
  • SFA
    I don't use catalogs but from memory of reading about how they function C1 knows about its catalog contents so if the images are stored in the catalog it can check whether you are about to import the same images again and, for logical reasons of managing the size and efficiency of the catalog, exclude images from a second import which would be unnecessary (for that catalog).

    However if you are keeping the files externally the Catalog has no control at all over what you do with them at the time of import or in the future. Indeed I would suspect it can't even reliably know if they are the same files (although the nuance in that may not be a problem in practical use).

    So it's up to the user to manage it.

    It's slightly interesting that two of my compact cameras have an option to automatically create a new folder per month or per day - user selectable - and my DLSRs do not. If they did identifying different shoots for importing would be much easier in some ways, though sometimes less convenient in others.

    The simplest way to select the images on a Card with "running" contents is to filter by some criterion, such as date.

    More simply just sort by date and invert and select those you want from the top of the list (or the bottom if you don't invert).

    I have in the past used DAM type products that remembered which files had already been imported but have never really missed that facility if it is not available.


    I would guess there is no reason not to build in some functionality to keep track of imported files although doing so is a large part of a full DAM function.

    Raise a Support Case and make a development request so your wish is recorded.


    Grant
    0
  • Andrea RICCI
    Thanks Grant for the suggestion
    I would actually like to file a request for development
    I used to store files on Lightroom in pretty much the same way
    I guess that LR records the names of the files in the catalogue and that allows it to stop if the file is known or not (without holding the very file it self)

    Could you explain how to file a request for a development ?
    Thanks
    (Happy I have detected something useful also for others)
    0
  • SFA
    [quote="andreariccieu" wrote:
    Thanks Grant for the suggestion
    I would actually like to file a request for development
    I used to store files on Lightroom in pretty much the same way
    I guess that LR records the names of the files in the catalogue and that allows it to stop if the file is known or not (without holding the very file it self)

    Could you explain how to file a request for a development ?
    Thanks
    (Happy I have detected something useful also for others)


    To ask for some development from the C1 development team the best approach is to create a Support Case and in the title of the case use a term such as "Feature Request:" or "Enhancement Request:" followed by a short description of what
    the request will be about.

    Something like that. Phase can then be sure to have the request recorded in a system they use for support and development management.

    As I recall from using LR at version 1 (is it still the same?) LR required that all images were imported to the catalogue and having applied that rule it was quite possible to ensure that no duplication of imported image was possible for that catalogue. At V1 I don't think you could have more than one catalogue, at least not easily.

    Presumably a catalogue will not allow an index to have more than one image file with the same name, so it makes a lot of sense.

    However if you are not storing the images internally the potential naming conflict is a rather different matter. Two files with the same name out of a camera may well be different and cannot be assumed to be the same. (At that point it can get a little complex to write up so I won't try for the purpose of this discussion.)

    That means that the import process, in theory, cannot make any valid assumptions about what to do without reference to a set of rules that, presumably, the user would need to create ... and adhere to.

    Since the catalogue would only be storing a reference to an external file there is no concern about creating excessively large files from storing huge original images. If a user wished to have 2 internal "imports" that point to the same external image there is no reason to prevent that. Perhaps one for colour and one for B&W Referenced in different sections of the same catalogue ? (I'm not saying that is the right way to approach the requirement, just that some people may feel most comfortable if allowed to work that way.)

    Once you are into the swing of controlling the images it is not, in my opinion, a significant problem to manage imports oneself rather than have a system do it for you. But then I'm from a Windows world ....



    Grant
    0
  • NNN635468147870723611
    Same here, I come from Aperture, so in Aperture there's an option during import to select if you want Aperture to import duplicates or not.

    So from my understanding, if I save my photos via catalog, it'll not double import? Cause right now I'm using the catalog feature and it doesn't seem to work, or do I have to set a collection location for it? Cause right now it's default so it'll not assign to any pre-defined collections, I view my photos by recent import and then once I select what I want to keep, I'll assign them to their collections.
    0
  • CAPTURE NIKON D700
    Hello friends,
    you are disgusting a theme wich are been told moor times in the past !
    a very simple Apps in App Store have automaticly this function 😐 and C1 8 dont have it ❗️
    OHHHHH.
    because Phase one is Build auf Profis Tester , who are Shooting only one - tows Images with 80 MB and modifying it in C1
    thats way they dont need this function 😂
    and please dont compare with Aperture !
    0
  • Orwell
    [quote="NNN635468147870723611" wrote:
    Same here, I come from Aperture, so in Aperture there's an option during import to select if you want Aperture to import duplicates or not.

    So from my understanding, if I save my photos via catalog, it'll not double import? Cause right now I'm using the catalog feature and it doesn't seem to work, or do I have to set a collection location for it? Cause right now it's default so it'll not assign to any pre-defined collections, I view my photos by recent import and then once I select what I want to keep, I'll assign them to their collections.


    I was also an Aperture user and I believe that Aperture only checked for duplicate filenames. If you renamed your files on import, the feature was pretty useless. And you should definitely be renaming your files on import.
    0
  • SFA
    [quote="Orwell" wrote:


    I was also an Aperture user and I believe that Aperture only checked for duplicate filenames. If you renamed your files on import, the feature was pretty useless. And you should definitely be renaming your files on import.


    I can't comment on the Aperture functionality but going back some way before I discovered Capture One I had concluded that for me naming concerns meant that somewhere I needed to create "shoots" (sessions in C1 terminology) and manage the naming myself. As I recall Zoombrowser (being a Canon user that seemed to be the DAM like product provided) could deal with not importing the same file twice but not always effectively for what I was trying to do.

    I never did get to the point of discovering what would happen if the in-camera numbering looped round or I loaded a card from a different camera that used the same naming sequence (for example). As I recall the date the image was taken was part of the selection criteria.

    Grant
    0

Post is closed for comments.