Incremantal Ingest from Backup-Card

[ErwinScheriau]

Most time (especially when doing sports) I`m shooting on two cards, card #2 is sort of backup.
Now here's the problem: I do ingest pics from card #1, when something important happens during ingest, I continue shooting on card #2. But when I want to ingest the pics from card #2 PM is importing all the pics, even those I already have imported from card #1.
As you can imagine this is a big timeloss when there are 300 or more pics on the card.
Any Ideas?

[Kirk Baker]

Most time (especially when doing sports) I`m shooting on two cards, card #2 is sort of backup.
Now here's the problem: I do ingest pics from card #1, when something important happens during ingest, I continue shooting on card #2. But when I want to ingest the pics from card #2 PM is importing all the pics, even those I already have imported from card #1.
As you can imagine this is a big timeloss when there are 300 or more pics on the card.
Any Ideas?

So you've got a situation where card #2 has all of the images of card #1, plus new images that card #1 doesn't have?

PM has no way of telling that the two cards are related.  PM puts an ID file on your cards when an Ingest starts and each card will have a different ID.  This ID is used to look up what files have been copied for that particular ID.  Any files that haven't been copied for that card ID are copied.

It's not feasible to do what you ask.  It's a hard problem to solve since at the time of card #1 being Ingested, card #2 is not known to PM.

PM would have to search all card IDs and compare your card #2's files against them to see if a file has ever been ingested from all known sources.  To be completely certain, PM would have to use more than filename, date, and file size information for the comparison.  It would have to checksum each file first and the database would have to be extended to include a checksum.  This could be time consuming.  All Incremental Ingests would have to be exhaustive searches.

-Kirk

[Linwood]

I assume ingestion speed is not the issue but you don't want to have to cull through them?

If you went ahead and ingested, and had your file name duplicate handing to (say) put an A, B, C etc. on the end if the name, can you then delete them with a pattern match like *A.NEF, etc?    Or to be safe, move them with that pattern just in case something weird happened?

[Linwood]

I did give this a try and it seems to work (again, it doesn't avoid the ingest, just the subsequent culling).

I have the file handling preferences set to append a letter (A, B, C).   Since my camera always has digits in the last part of the file name, then anything with a letter there is was a duplicate file name.  And at least on Nikons, the file names are the same on backup files (not sure what you are shooting).

So when I ingested a card with a few shots extra on the second card, I got a bunch of files like DD5_5706A.NEF, and could just delete from the command line *A.NEF and what's left are the original files plus those which were incremental to the first disk.

[schlotz]

Most time (especially when doing sports) I`m shooting on two cards, card #2 is sort of backup.
Now here's the problem: I do ingest pics from card #1, when something important happens during ingest, I continue shooting on card #2. But when I want to ingest the pics from card #2 PM is importing all the pics, even those I already have imported from card #1.
As you can imagine this is a big timeloss when there are 300 or more pics on the card.
Any Ideas?

So you've got a situation where card #2 has all of the images of card #1, plus new images that card #1 doesn't have?

PM has no way of telling that the two cards are related.  PM puts an ID file on your cards when an Ingest starts and each card will have a different ID.  This ID is used to look up what files have been copied for that particular ID.  Any files that haven't been copied for that card ID are copied.

It's not feasible to do what you ask.  It's a hard problem to solve since at the time of card #1 being Ingested, card #2 is not known to PM.

PM would have to search all card IDs and compare your card #2's files against them to see if a file has ever been ingested from all known sources.  To be completely certain, PM would have to use more than filename, date, and file size information for the comparison.  It would have to checksum each file first and the database would have to be extended to include a checksum.  This could be time consuming.  All Incremental Ingests would have to be exhaustive searches.

-Kirk

It possibly could be easy though.  What if the fine people at CameraBits were to add a check box & logic (if used the ID logic is abandoned & replaced with filename lookup) to allow by-passing any duplicate file it encounters during the ingest process?  JMTC 

The OP describes a real-time issue many sports photographers run into.  While the filename check process will most likely be slower, not having to cull out 100's of duplicates when under a time crunch at the end of a game might make up the difference plus some.  ALTERNATE: save the ID file from the first card to the computer's hard drive and thru a check box on the ingest window, allow it to be used for the pending ingest of a different card.  Obviously the default would to be 'off' AND it would be toggled off automatically after the ingest is done.