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

Photos missing after Batch Rename

Comments

6 comments

  • ernst.w

    Did you take a look into the Capture One Trash Tray?

    0
  • Mateusz Marczewski

    I did and it was empty. However, I tried synchronising the specific folder once more and, this time, I was able to import the missing photos. All of the editing was gone and I had to do it all over again but at least I was able to finish my work. 

    I think doing File -> Verify Catalog or Session -> Repair allowed me to synchronise and import the missing images. When I tried importing manually before, Capture One told me that the photos were already in the Catalog. 

    Also, I recently updated Capture One to the latest version (Build 14.3.1.14). I suspect this may have something to do with my issue. Anyway, I hope this does not happen again in the future.

    0
  • SFA

    Mateusz,

    Is there any possibility that your renaming definition might have cause conflicts in identity (naming) as the files were processed?

    Losing the edits suggests that the associated record containing the edit data were either misnamed or not processed correctly.

    I cannot recall what, if any, level of detail is recorded in the log files when a renaming process is run. It might be worth checking.

    0
  • Mateusz Marczewski

    Thanks SFA.

    This is unlikely, the name itself was project specific / unique and not even close to anything else I used in the past. 

    Also, I cannot see any details of the renaming process in the log files. 

    0
  • Jon Stewart

    I confronted comparable sort of issue last time, I am as yet looking for some appropriate arrangement.

     

    myaarpmedicare

    -1
  • SFA

    Mateusz,

    I was thinking more about a conflict of naming rules in the same batch of files rather than from an historic perspective.

    Something I experienced many years ago when attempting a slightly optimistic multipass rename batch only to discover that in some cases that an intermediate name state caused great confusion for the following step and the process failed totally.

    It was the sort of thing one has to learn by experience at some point I suppose but have been very cautious ever since. The potential problem was not obvious to me at the time of planning the process and script.

    0

Post is closed for comments.