Batch renaming adds "1" at the end of some files

Yoguko

• 2. November 2015 13:00

Hello

I was wondering if anyone came across this issue.

I´m batch renaming about 450 files.

My preset for renaming is "Job Name"-"4DigitCounter".

It should give me something like this: "Jobname-0001", up to "Jobname-0450"

However, up to capture number 6, the naming goes like this: "Jobname-0001 1", "Jobname-0002 1", etc.

I´ve reset the counters and I tried renaming one by one, but it won´t work.

The following error pops up:

"The new name may contain invalid characters, be too long, is already taken or you don't have permissions to write the file. Please choose a different name."

All the files are in the same place, so I don´t see how these first 6 should be a problem.

Any ideas?...

Thank you

0

• 

  Permanently deleted user

  • 2. November 2015 13:52

  I had and still have the same behaviour and reported it to C1 support a couple of month ago and it is still not fixed in 8.3.4
  
  What happens is, that if you have a picture(s) in your batch that exist already with the very same Jobname-xxxx, then C1 adds a ' 1' to the end of those picture files. This means files are not overwritten they are added a ' 1' to the end of the filename.
  
  You can circumvent this when you give your batch a dummy name like Jobdummy-xxxx in a first rename run and then on second rename run you give it the name you really want it to be (like Jobname-xxxx).
  
  Please report this to C1 support as well, so they get that fixed finally someday in the future. A batch rename should override all pictures selected and not add some crazy ' 1' at the end of a duplicate.

  0
• 

  Yoguko

  • 2. November 2015 14:15

  Hi Andy
  
  Thank you for your reply.
  
  I don´t think that is the same that´s happening to me, even though your solution worked for me.
  
  I usually work on the original file names, as they come out of the camera. Flagging, editing, etc.
  
  It´s only just before I export them that I rename them. There are no other files with the same name, anywhere.
  
  It still adds that annoying "1", and sometimes "2", to some files, not all.
  
  Having to rename a batch twice is just silly...

  0
• 

  Permanently deleted user

  • 2. November 2015 15:11

  Hm, then I'd really advise you to contact support and have that sorted out with them. Looks like a timing problem in writing filenames to disk then.
  
  I totally agree, renaming a batch twice is silly and it's annoying. At least it helps you for the moment.

  0
• 

  Albert

  • 6. August 2022 17:10

  Old thread, I know, but for those who have this problem and landed here thanks to a google search like I did, the solution that worked for me is to make sure the C1 Trash was emptied before doing the batch renaming.

  0

Post ist für Kommentare geschlossen.