Skip to main content
wckdtall
Inspiring
February 6, 2018
Question

Why doesn't Bridge batch rename adjust when a sequence goes beyond digit bounds?

  • February 6, 2018
  • 6 replies
  • 4024 views

In general, I use 2 digits for sequence numbers as a standard. Occasionally, I will have to go beyond this and use 3 digits if I end up with more than 100 assets. The problem is, Bridge doesn't adjust this and maintains duplicative file names with a "(1)" at the end of the name as an example. Is there anyway around this that doesn't isn't solved by 3 digits in a name? Otherwise seems like an oversight as it should be able to handle the transition from 99 to 100 and more importantly, if you were to use 1 digit or 2 digits, you'd hit this cap very quick. Add to this the fact you can't undo a batch rename, and it's a huge problem.

    This topic has been closed for replies.

    6 replies

    wckdtall
    wckdtallAuthor
    Inspiring
    March 15, 2019

    Scripting would seem to accomplish what's needed in this case, but if you have multiple files with the same date and time, if there are duplicates, you'll probably always have to include "-1" for the first number or it will sort to the end if you have multiples at least on mac. It may be easier to include milliseconds in the file name, as long as your camera is not "THE FLASH", and primarily long as you don't have similar number sequences in your file names. You should be able to use batch rename with callbacks like the below:

    Regex as follows, but also relies on what you've selected to rename:

    ([0-9]{4})([0-9]{2})([0-9]{2})([0-9]{2})([0-9]{2})([0-9]{2})

    The above should be able to be combine into a shorter statement, but Bridge and other adobe programs don't fully support RegEx.

    Hope this helps!

    photofusionstudio
    Participant
    February 18, 2019

    Did you ever find an update to this?

    I found that Lightroom will do a better job at this but it's so damn slow!

    Legend
    February 18, 2019

    The only fix I can think of would be to warn you that you have too many files selected for that naming option. Otherwise it will do what you ask, which is use x number of digits.

    photofusionstudio
    Participant
    February 18, 2019

    hmmm, that's not the problem I'm running into. I'm finding Bridge renames differently than Lightroom (which I prefer this naming pattern but Lightroom can get bogged down to easily)

    For example.

    Lightroom can rename files

    name-yymmddhhmmss

    name-yymmddhhmmss-1

    name-yymmddhhmmss-2

    whereas Bridge wants to use

    name-yymmddhhmmss (1)

    name-yymmddhhmmss (2)

    I only want that extra sequence number used only where there are multiple photos per second, if that makes sense. Also I just don't like ()  or spaces in filenames

    Stephen Marsh
    Community Expert
    Community Expert
    February 9, 2018

    Just to confirm, you would like Bridge to gracefully and intelligently handle exceptions where the user has asked for a range of sequential digits that conflict with the number of files being renamed, as in this image example:

    Stephen Marsh
    Community Expert
    Community Expert
    February 8, 2018

    Preserve the current filename:

    (this example is not a standard rename as the find and replace are the same, it is used to force an update to the preserved filename metadata).

    Restore the preserved filename:

    Legend
    February 8, 2018

    You can preserve the current filename in XMP so that it is available to restore.

    Chuck Uebele
    Community Expert
    Community Expert
    February 8, 2018

    I don't believe there is anything you can do, other than making sure you check how many files you have that you want to number - I've done the same thing, many time. It would be nice. Only thing I can suggest is that if you accidentally do that, change the sort order to date taken, and renumber them.