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

avoid double copy Image to C1 Catalog

CAPTURE NIKON D700
is there any way in the new version C1 9
to avoid double copy Images to catalog from SD Card ?
i came from Version 7 then 8 and now to 9 and still missing this easy function .
Is there any way to find double images inside catalog ?
what did Phase one thought here.

Thanks !
0

Comments

19 comments

Date Votes
  • CAPTURE NIKON D700
    i think i am alone with this problem here !
    HIM... maybe i over read something in the Manuel construction.
    0
  • RichardT
    Perhaps your case is the same as in the following thread?



    Richard
    0
  • peter Frings
    [quote="RichardT" wrote:
    Perhaps your case is the same as in the following thread?



    Richard


    I believe the OP refers to the fact that there is no way to "Ignore duplicates" when importing from a memory card, like you can in LR, AP and others.

    If that is indeed the requested feature, then sorry, but C1 doesn't have it. File it as an enhancement request in the technical support page, as many others have probable/hopefully done before you.

    Peter.
    0
  • CAPTURE NIKON D700
    If that is indeed the requested feature, then sorry, but C1 doesn't have it. File it as an enhancement request in the technical support page, as many others have probable/hopefully done before you.

    i was wondering way can such function like this bee build bevor, in one of the best professional RAW Converter in the world.
    how do professional users behaves in this situation after they pushed the button import .
    every thing goes double inside the catalog. 😲

    is there any kind of Apple scrip to us for that ?

    I hop Phase one send us update for that.

    Thanks !
    0
  • John Doe
    [quote="CAPTURE NIKON D700" wrote:

    how do professional users behaves in this situation after they pushed the button import .
    every thing goes double inside the catalog. 😲

    If you have a good, organized workflow, you shouldn't get any duplicate. That's probably why not many users complain about this.
    0
  • OddS.
    [quote="CAPTURE NIKON D700" wrote:
    ...i was wondering way can such function like this bee build bevor


    Duplicate image is not a simple concept.

    Within a disk folder holding images referenced in a LR catalog I duplicated (copied) a raw file with a new file name. The Import module in my LR 6.6 does not see the new file as a duplicate. The original raw file is greyed out (indicating already in catalog), LR marks the new file as ready for import.
    0
  • CAPTURE NIKON DPRO1
    looks like that it's hard to program such
    function like this in a professional C1 Program .
    the old Apture and Nikon software offers since long time this function.

    Professionals can look which images on the memory card still
    not imported in the DB ... ?
    maybe this " issue" looks very easy for me. and I'm also not a programmer , but I could imagine.
    if you identified photos on local SD card from there ID number. which been written from Camera in the EXFI files and match them with the DB.
    this can happens only in the background.

    one moor question :
    if this could not bee build now in C1 , why we don't get a filter function inside C1 to remove these duplicate files ?
    its only one DB to search inside !
    0
  • John Doe
    In what circumstance exactly do you get duplicates? Never happened to me…
    0
  • RichardT
    Until now I hadn't understood why people were complaining about duplicate imports because it has never happened to me. In fact, if I try to import duplicates, Capture One displays an error message and skips over the duplicates:

    http://i1381.photobucket.com/albums/ah220/Python54/phase_one/skipping_image_zpsgoubuucl.jpg

    After a bit of experimenting, I believe this only happens for me because I never import directly from a memory card. I first copy the image files from the memory card to a HDD. I then import images from the HDD into CO. I always use a catalog and leave the images in their "Current Location".

    It appears that Capture One does have functionality for checking for duplicate imports but it only appears to be used for certain types of import, such as the method I use.

    Richard
    0
  • CAPTURE NIKON DPRO1
    In what circumstance exactly do you get duplicates? Never happened to me…


    i have a camera and C1 app on PC.
    i copy from Camera SD Card to PC.
    very simple and normally workflow 💡

    it dons't mater if i use c1 in catalog or session, in booth way i can't avoid double image copy in the DB.
    there is no control i found for that, i am wondering how authors getting in c1 a warranty signed showing duplicate.

    i can't let my DB growing with unneeded Data.
    this issue is not completed solved in c1 i could call it a missing function in a Professional Application.
    i will bee thank to Phase one Team if they could find us a solution.
    0
  • John Doe
    [quote="CAPTURE NIKON D700" wrote:
    In what circumstance exactly do you get duplicates? Never happened to me…


    i have a camera and C1 app on PC.
    i copy from Camera SD Card to PC.
    very simple and normally workflow 💡

    it dons't mater if i use c1 in catalog or session, in booth way i can't avoid double image copy in the DB.

    Same here. Never get duplicates. You must be doing something wrong.

    i will bee thank to Phase one Team if they could find us a solution.

    I would say your problem stands between your chair and your keyboard.
    0
  • OddS.
    [quote="CAPTURE NIKON D700" wrote:
    ...i copy from Camera SD Card to PC.


    Is that process really capable of producing a duplicate file? I would guess that a plain copy without changes to the target filename would overwrite the target file. The net result would be exactly one copy per source file no matter how many times a file is copied. There are two well known ways to avoid overwriting; copy to a different destination folder or copy to a file with a different name.

    Change of target filename may be an automatic function to prevent overwriting, typically by appending a postfix _1, _2,... or (1), (2),... or -A, -B,... or similar to the filename. It may also be a process generated filename set up by yourself, for example by using Capture One token mechanism to include a sequence counter token.

    I may have misunderstood your process completely, but I can not help thinking that somehow you must be including a source file in multiple copy sessions and also be copying to a different filename each time. As far as I know, a duplicate with a different filename also fools the duplicate detector in LR (see my previous post).

    I wonder if a simple remedy would be to copy once from the memory card and then clear or format the card before a new copy session is initiated, probably meaning to clear/format before you continue shooting with that memory card. Your file copy sessions (import?) would then never see the same source file twice.
    0
  • peter Frings
    Regardless of whether it's considered a bug or not, it's very easy to import the same image twice:

    - create a new catalog, managed.
    - import 1 image from an SD card.
    - import that same image from the same DF card.
    -> Now you have 2 images in your catalog. They're actually 2 files, stored in different subfolders in your catalog.

    Do the same with a simple session:
    -> same result: two different images, 2 different files in your Capture folder.

    Both AP and LR would automatically recognise that this file is already in the catalog and disable that file for selection. And when importing all files, they would simply skip these duplicates (without giving errors!).

    However, most C1 users probably format their SD cards after importing them (and after backing them up), so this particular problem never rises.

    Hope this clarifies the issue for those with a decent workflow 😊
    Peter.
    0
  • CAPTURE NIKON D700
    Regardless of whether it's considered a bug or not, it's very easy to import the same image twice:

    - create a new catalog, managed.
    - import 1 image from an SD card.
    - import that same image from the same DF card.
    -> Now you have 2 images in your catalog. They're actually 2 files, stored in different subfolders in your catalog.

    Do the same with a simple session:
    -> same result: two different images, 2 different files in your Capture folder.

    Both AP and LR would automatically recognise that this file is already in the catalog and disable that file for selection. And when importing all files, they would simply skip these duplicates (without giving errors!).

    However, most C1 users probably format their SD cards after importing them (and after backing them up), so this particular problem never rises.

    Hope this clarifies the issue for those with a decent workflow 😊
    Peter.


    Thanks Peter ! you got it understand, for some how saying i am downing something wrong. no i am not.
    AP , Nikon NX , and Apple Fotos got it build for long time , but C1 not,
    i love C1 to use and i see its important to get such function like this build inside Professional Application. "PRO"

    agin here is my workflow.
    1. i keep my old pictures of SD Card
    2. i the C1 import dialog i rename the Images Data Name with yy.mm.DD .
    3. i hit the import button and the process start to run.
    4. after a week i find double images are showing in the C1 browse called like yy.mm.DD_1 , 2 ,3 .....
    its the same picture with same name + index 1
    some time i make a mistake and copy these images agin and agin from old SD Card back in session , because i am using many SD Card from different cameras .. how do the Profi solve this in workflow ! the software should do some help.
    for me .
    how do i know that image was been imported to DB before ?


    Thanks for helping .
    0
  • peter Frings
    [quote="CAPTURE NIKON D700" wrote:

    agin here is my workflow.
    1. i keep my old pictures of SD Card
    2. i rename the Images Data by like yy.mm.DD using the C1 build function in the import menu
    3. i import image to C1 in my Session catalog folder "Capture"
    4. after a week i find double images called like yy.mm.DD_1 , 2 ,3 .....
    some time i make a mistake and copy the same images for one week back in session , i used many SD Card .. how do the Profi solve this Please !

    Thanks ,


    I believe there is a very simple thing you can do, as I already stated before, and that does not rely on a feature in Capture One.

    Format your card after importing it!

    Why do you keep all those images on your card? Import them, back them up, and then format it. Start with an empty card. No more duplicates, guarantee! You will be surprised how much easier life can be! It's not because your card can store 32GB that you have to store 32 GB. As many craftsmen will tell you: keep your workplace clean.

    As a sidenote: I already did that even when using Ap and then Lr.

    Cheers,
    Peter.
    0
  • CAPTURE NIKON D700
    thanks for your suggestion " Format your card after importing it! "
    i don't agree on this, because of one simple easy circumstances.

    1. a Cheep Storing place " in special porpoise such like small Archive

    2. when The Card don't belongs you .

    3. good Mobility to shear them with authors Programs,

    apart from this .... we saw how you can build your own mistake inside " you are a human , believe me one day some one will find in his
    Catalog , pictures looks exact the same but with different names and then asking them self : have you already Format your Card bevor ?

    in my view a professional application should have this build inside.

    also many users and i got in mistakes when changing workflow from Catalog to session, importing images from one place to anthers
    on the same HD used from C1 software.
    i know this software is for Profi ! and you should now what your doing
    but this is a reproducible gap in C1 that i knows since long time ago starting with V 7 , 8. current V 9

    i was wondering way do we get this function build inside Media Pro " find duplicate" and not in C1 !
    maybe because C1 works with two methods Catalog or Session and its hard to recognize the images ID in DB ?

    i don't know i am not Programer !

    my thanks to Phase one team if they could look back to this issue and find us in the future a solution please

    Capture one still bee my favorites .
    0
  • H. Cremers
    [quote="CAPTURE NIKON D700" wrote:
    thanks for your suggestion " Format your card after importing it! "
    i don't agree on this, because of one simple easy circumstances.

    1. a Cheep Storing place " in special porpoise such like small Archive

    2. when The Card don't belongs you .

    3. good Mobility to shear them with authors Programs,

    apart from this .... we saw how you can build your own mistake inside " you are a human , believe me one day some one will find in his
    Catalog , pictures looks exact the same but with different names and then asking them self : have you already Format your Card bevor ?

    in my view a professional application should have this build inside.

    also many users and i got in mistakes when changing workflow from Catalog to session, importing images from one place to anthers
    on the same HD used from C1 software.
    i know this software is for Profi ! and you should now what your doing
    but this is a reproducible gap in C1 that i knows since long time ago starting with V 7 , 8. current V 9

    i was wondering way do we get this function build inside Media Pro " find duplicate" and not in C1 !
    maybe because C1 works with two methods Catalog or Session and its hard to recognize the images ID in DB ?

    i don't know i am not Programer !

    my thanks to Phase one team if they could look back to this issue and find us in the future a solution please

    Capture one still bee my favorites .


    So, Capture Nikon D700, again you keep on complaining what Capture One does, in spite of all the good advice you have received on how to prevent the "issue" you see.

    Why don't you take that advice, work out your own workflow to your liking and stop menacing Phase One and us with posts that don't help anyone, not even yourself.

    Perhaps trying the suggestions and responding back to them could help some other users and also yourself.

    Peace.
    0
  • SFA
    As I recall Catalogue functionality has always has an ability to identify duplicate files being imported from a folder. Not sure if that only applies to catalogues with internally stored files rather than referenced files or vice versa but in theory could be both I suppose.

    Of perhaps "from named location"?

    So if the disk and path and files name are seen again the warning is given.

    However, what happens if one uses the file renaming facility on import?

    How is there then an opportunity to identify was has been imported before?

    Furthermore is in camera file naming rolls over and is repeated - or is simply repeated after formatting a card, or if two cameras are in use, how much checking needs to be applied to ensure the correct and intended decisions are made?

    I used to use the Canon supplied Zoombrowser software back way when and that seemed very clever knowing what had already been plucked from the camera. But later, especially when using multiple cameras and several thousand images a day, I became more convinced that I needed to have an active involvement in the loading - partly to make myself check that I had not mislaid a card or two during the day.

    Unless one has a very strict and structured work flow without deviation I suspect the reliance on automatic selection of "what's unknown to the system" may not be an entirely comfortable feeling. It certainly wasn't for me, at least not all of the time.


    Grant
    0
  • mharris
    [quote="OddS" wrote:

    Duplicate image is not a simple concept.


    I disagree. From a programming perspective, identifying a duplicate image is incredibly easy. During import C1 simply needs to store a CRC (or MD5) hash of the raw image file. Then that hash can be compared to new files being imported. It doesn't matter if the file gets renamed or stored in a different location because a hash only looks at file content.


    I think the duplicate import issue would also be improved an alternative way if C1 had better duplicate file handling generally. Currently when C1 encounters a file with the same name (whether thats on import or output processing) it simply writes the new file with _1 or _2 on the end. It would be far more useful if it gave the user the choice to control what happens.. Ignore, Overwrite, or Rename. This could be a global application preference, or (even better) ask the user via a prompt each time.

    Because raw files (in theory) never change, importing the same one multiple times with _1 on the end is a bit of a workflow disaster. So while importing I would always choose the Ignore option.

    When outputting, sometimes I just want a new TIFF to fix a previous one that had an obvious mistake, I dont want to keep the previous one because it was a duff. Here I would choose to Overwrite. If I want to keep different revisions of the output I'd choose Rename.

    So this is not only more useful for the user, but it also helps the duplicate import issue. Perhaps it doesn't "solve" it, but it does at least alert the user to the situation and allows them to decide what action to take.
    0

Post is closed for comments.