Zum Hauptinhalt gehen

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

Kommentare

16 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
  • John Friend
    Top Commenter

    I would say this is a bug or at least a user-unfriendly implementation.  If you've deleted something (even if still in the trash), you should be able to import it again.  Or, worst case, it should tell you that the duplicate is in the trash.

    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
  • John Friend
    Top Commenter

    You can argue semantics on whether to call it a bug or not, but that evades the point that it's a compromised user experience when it won't let you import something and won't tell you why. This is fairly common with Capture One - it makes errors and doesn't tell you why the operation is failing such that you would have a chance at understanding what needs to be done to correct the issue yourself.  A better user experience would be one of the following:

    1. Tell you it's in the trash and that's why you can't import it
    2. Tell you it's in the trash and offer to remove it from the trash so you can import it
    3. Just import it - if/when you try to restore the duplicate from the trash, tell you then that you can't because there's a dup
    4. Just import it and get rid of the one in the trash
    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
  • John Friend
    Top Commenter

    Walter Rowe - So are you arguing that the current implementation that leaves the user totally confused is a good implementation?  Technically correct (by some interpretations) has absolutely nothing to do with a good user experience.  This user experience could certainly be better.

    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
  • John Friend
    Top Commenter

    I disagree that you should have to "just know to look in the trash" or "know to look in some log file".  A good program doesn't make you know something you've never encountered before in order to understood what it did.  It tells you what it did.  If it gets an error, it explains what the error was caused by in a way that is clear enough that even a beginner with the program will understand what happened.  You guys forget that you were once new to C1 and didn't know anything about this problem or about some log file and would have been just as confused as the OP.  Generating confusion for new users is not what good programs do.

    At the very least, it should tell you that it couldn't import it because it was already in the catalog or in the trash.

    And, this notion that the trash is "in the catalog" is an implementation side effect, not a familiar user concept from other computing experiences.  Nowhere else are you prohibited from doing things because something of the same name or same file is in the trash.  That doesn't happen copying an email into your inbox (just because the same email is in the trash).  That doesn't happen copying a file into a folder just because the same file is in the trash.  The fact that the trash is generating a duplicate conflict is just a side effect of the way C1 implements the trash, not at all what users expect from all their other experiences with something called "trash".  This is not a behavior that users are familiar with or expect. So, C1 is just being lazy here and not informing you more specifically why you can't import it.  It's on them and we shouldn't be letting them off the hook just because we're more experienced and have learned about this trash issue.

    Now, obviously there are much, much more important issues to worry about in C1, but on principal, we shouldn't be saying it's OK for C1 to just skate and not tell the user what's really going on here such that a new user will have to go to some online forum to figure out their problem.  That's just bad user interface design and bad error reporting when that happens (and a little too common in C1).

    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
  • John Friend
    Top Commenter

    Yes it's different than all other experiences you have with how trash works. That's precisely why they should tell you that the trash is why mport wouldn't import it.

    Why are you defending a behavior and error message that leaves the user confused? Since when is that the desired outcome?

    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

    John Friend - 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.