Zum Hauptinhalt gehen

Capture one won't import photos, says they are duplicates?

Kommentare

11 Kommentare

  • Ian Wilson
    Moderator
    Top Commenter

    Are you sure that the images don't already exist in the catalog, which is what it is telling you? Have you looked in the All Images collection?

    Ian

    0
  • Miles

    Hi Ian, 

    Thank you very much - I checked  "all images" in my collection, and they didn't appear. But I didn't check the trash, and that's where they were.

    I imported them last night, but as the previews were generating I got a call on the computer, so I deleted the import, but didn't clear the trash.  

    Problem solved - thank you, apologies for a silly question!!

    0
  • Ian Wilson
    Moderator
    Top Commenter

    I don't think you can call it a bug. If it's in the catalog trash, you can drag it out again unless you have emptied the trash. If it let you import it again when it is still in the trash, you could then have two copies of the same image in the catalog.

    Ian

    0
  • Walter Rowe
    Moderator
    Top Commenter

    If it's in the Catalog Trash, it's in the catalog. One could argue that Exclude Duplicates is doing the right thing. You might have deliberately moved it to Trash and thus it should be skipped when Exclude Duplicates is enabled.

    0
  • Walter Rowe
    Moderator
    Top Commenter

    A better implementation would tell you WHERE it already exists, not simply skip over it. It could put it in the Event log so you could look for it if you didn't expect a file to be skipped.

    0
  • SFA
    Top Commenter

    Given the nature of the Catalog (or Session) trash, it is really only a "hidden folder".

    If "All Images" had an option to include "Hidden Folders" with a flag to show the images that are hidden things would become clearer for the user  - especially when one is coming across the missing file issue for the first time.

    0
  • Walter Rowe
    Moderator
    Top Commenter

    If that were done, you would then want an overlay indicator telling you it represents a hidden item. This gets more and more complicated as it requires more and more attributes. The more complicated, the more room for bugs and errors.

    I prefer it simpler. I know to look in the Trash if something doesn't import when Exclude Duplicates is enabled.

    1
  • SFA
    Top Commenter

    I agree Walter, but others will surely have a different opinion.

    If something has to be changed let's at least keep it as simple (and utilitarian) as possible!

    0
  • Ian Wilson
    Moderator
    Top Commenter

    It is a little different in this case in that the Capture One catalog trash is not the same thing as the system trash. You can send something to the catalog trash, and even empty the catalog trash, and the original file can still be where it was in your file system (depending on the options you chose when you emptied the trash). 

    Ian

     

    0
  • SFA
    Top Commenter

    The screen capture that Miles posted has identified that the file is already in the catalog - so the import process is doing exactly what it is supposed to do if one does not want duplicates.

    I guess if one then allows duplicates the images would import are normal but with an instance serial suffix - i.e. a _1  (or probably just space 1)  for the file name. 

     

    Miles, you obviously had a good reason for stopping the import when a call came in  - but I assume that means that you were importing directly from the iPhone and that the phone would not allow you to take the call and allow the import to run?

    I'm wondering whether you might find it more convenient to adopt a process that simply copies the images to the computer and then run the C1 import from there. There would be less risk of interruption to the process  -especially the C1 import part of it  - and it might be a faster process overall - especially if your phone is usually quite busy being a phone rather than a camera!  ;)

    (That's not something I would have expected to ever have any need to write a decade ago...)

    0
  • Ian Wilson
    Moderator
    Top Commenter

    @... - I'm not really trying to defend anything. But I suspect that just allowing the image to be imported again could be a recipe for creating more trouble than it solves. For instance, if you have done some editing to an image before inadvertently sending it to the trash, and then you reimport it, would that re-import pick up the previous edits or not? What would happen if you had different edits to two different versions of the image?

    I agree with the comment from Walter Rowe that it would be helpful if the error message could tell you where in the catalog the image already exists, and that, it seems to me, would be a better solution than importing it again.

    Ian

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.