Duplicate RAW image files in Sessions

Peter Charles

• August 08, 2019 10:32

I've started using Sessions and my first two have a complete duplicate set of RAW files, which as you can imagine is a huge waste of space.

The question is: what went wrong here?

The files were imported to a sessions folder that I created on an external drive, so they exist under that folder along with the usual four Sessions folders and the session database. At some point a sub-folder was created with the folder name composed of the date and time. I assume this second folder was created by the import process. I certainly didn't create it.

0

• 

  SFA

  • August 08, 2019 11:14

  It sounds like you have taken and existing folder and opened it in the session (maybe creating a "favourite" reference in the session?) and then instructed C1 to Import the contents to another folder.
  
  If that is the case then you can simply remove the 'favourite' status from the original folder and the session will no longer look at it.
  
  After that it is up to you what you do with that folder.
  
  Alternatively simply stick with that original folder and delete the newly created imports.
  
  Personally, and assuming my guess is correct, I would stick with the images in a folder contained within the overall session folder structure since is makes it so much easier to 'manage' and archive the session as a single complete entity.
  
  However there can be different and flexible "needs" that might suggest the 'favourites' approach is desirable and there would be nothing wrong with that at all so long as one is aware of the requirements for 'managing' referenced folders when backing up, reorganising a system, etc.
  
  If you do not think my suggestion is what has happened then we probably need to know some more about the steps you followed in order to identify what happened and how to avoid the duplication in a way that best suits your preferences.
  
  
  Grant

  0
• 

  Peter Charles

  • August 08, 2019 11:36

  Thanks for the reply.
  
  I have been able to determine that the named folder can be safely deleted. Now that I think of it, perhaps these folders were created as part of a backup process. I may have ticked off "Backup", but I just don't recall.
  
  I ran some tests afterward on my other Mac and everything was fine. I think I was over managing the import process because of the external drive. KISS principle next time.

  0

Post is closed for comments.